asked
Will the SSISBackup.bak be over written by other SQL instances?
We have a shared server that has SQL Server 2012 installed with multiple instances. On my instance while trying to create a SSISDB catalog, I ran into an error which led to my question. The error message was "The catalog backup file 'C:\Program Files\Microsoft SQL Server\110\DTS\Binn\SSISDBBackup.bak' could not be accessed. Make sure the database file exists, and then SQL Server service account is able to access it. (Microsoft.SqlServer.IntegrationServices.Common.ObjectModel)". It turned out that SSIS was not yet installed on this server, so I am getting this done. But in the meantime, if the SSISDB in my SQL instance gets backed up to the main SQL Server default location, what will happen to it if some other instance creates a SSISDB catalog? Does mine get over written or does a version number get added or do all instances have their SSISDB info stored in the one bak file?
I suspect this is not the location to which backups will be performed. It's probably the location from which an empty template is restored when creating a new repository. If some other instance creates a catalog, that catalog will be placed in the same directory as the master database and backups will happen in either the default backup location or the location specified in the backup command
17 People are following this question.
