Package Backup and Restore (SSIS Service)
Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
This topic discusses the Integration Services service, a Windows service for managing Integration Services packages. SQL Server 2012 supports the service for backward compatibility with earlier releases of Integration Services. Starting in SQL Server 2012, you can manage objects such as packages on the Integration Services server.
SQL Server Integration Services packages can be saved to the file system or msdb, a SQL Server system database. Packages saved to msdb can be backed up and restored using SQL Server backup and restore features.
For more information about backing up and restoring the msdb database, click one of the following topics:
Integration Services includes the dtutil command-prompt utility (dtutil.exec), which you can use to manage packages. For more information, see dtutil Utility.
Any configuration files that the packages include are stored in the file system. These files are not backed up when you back up the msdb database; therefore, you should make sure that the configuration files are backed up regularly as part of your plan for securing packages saved to msdb. To include configurations in the backup of the msdb database, you should consider using the SQL Server configuration type instead of file-based configurations.
The backup of packages that are saved to the file system should be included in the plan for backing up the file system of the server. The Integration Services service configuration file, which has the default name MsDtsSrvr.ini.xml, lists the folders on the server that the service monitors. You should make sure these folders are backed up. Additionally, packages may be stored in other folders on the server and you should make sure to include these folders in the backup.