This is one example moving SSIS database from Dev to Test using back up and restore.

1. Backup

TEST

backup master key to file = 'filename_mk' encryption by password = 'Pwd';

BACKUP DATABASE SSISDB TO DISK = 'Filename' WITH COMPRESSION;

DEV

backup master key to file = 'Filename_mk_dev' encryption by password = 'pwd2'

BACKUP DATABASE SSISDB TO DISK = 'Filename_ssisdb_dev' WITH COMPRESSION;

2. Generate create login script (only if the destination instance never had any SSIS catalogue)

In Object Explorer in SQL Server Management Studio, expand the Security node and then expand the Logins node.

Right-click ##MS_SSISServerCleanupJobLogin##, and then click Script Login as > CREATE To > New Query Editor Window.

3. Restore SSISDB

RESTORE DATABASE SSISDB FROM  DISK = 'filename_ssisdb_dev'

4. Login create/check

a) run the scripts in step 2 (if the login does not exsit)

b) EXEC sp_procoption N'sp_ssis_startup','startup','on'

c) Map logins

Map the SSISDB user ##MS_SSISServerCleanupJobUser## (SSISDB database) to ##MS_SSISServerCleanupJobLogin##, by using the Login Properties dialog box in SQL Server Management Studio.

exec sp_change_users_login 'update_one', '##MS_SSISServerCleanupJobUser##', '##MS_SSISServerCleanupJobLogin##'

5. Restore master key in Test from Dev backup

Restore master key from file = 'Filename_mk_dev'   Decryption by password = 'pwd2' -- 'Password used to encrypt the master key during SSISDB backup'  Encryption by password = 'New Password'  Force 

--The current master key cannot be decrypted. The error was ignored because the FORCE option was specified. ignore this error

Possible issues: The master key file does not exist or has invalid format.

Solution: change the permission

6. Compatibility check

Determine whether the SSISDB catalog schema and the Integration Services binaries (ISServerExec and SQLCLR assembly) are compatible, by running catalog.check_schema_version.

catalog.check_schema_version [@use32bitruntime = ] use32bitruntime 

catalog.check_schema_version 1

eg. catalog.check_schema_version

COMPATIBILITY_STATUS 0

7. Check ssis

To confirm that the SSISDB database has been restored successfully, perform operations against the SSISDB catalog such as running packages that have been deployed to the Integration Services server. For more information, see Run a Package on the SSIS Server Using SQL Server Management Studio.

Reference:

https://msdn.microsoft.com/en-us/library/hh213291%28v=sql.120%29.aspx?f=255&MSPPError=-2147217396