Restoring the Deployment Manager Server
If you have backed up the Deployment Manager server as described in
Backing Up and Restoring the Deployment Manager Server, you can restore the backup file. This restores all Deployment Manager resource metadata from the backup CAR file to a Deployment Manager server, with the option of overwriting any existing resource metadata by the same name.
Note: Sites and plans that exist on the Deployment Server but not in the CAR file are not affected by the restore operation and are retained.
To restore the Deployment Manager Server
1. If necessary, start Deployment Manager.
2. From the Admin menu, select Restore.
3. In the Upload dialog, click Browse and select the CAR file from the file system.
4. Optionally, check the Overwrite check box if you want to overwrite existing resources by the same name.
5. Type the password that was used to encrypt the CAR file.
6. Optionally, check the Ignore Encryption Errors check box to ignore any encryption errors.
Note: If this option is used, then all backup data will be imported regardless of whether a valid encryption key was provided. This means that the import will not fail. This option can be used to allow partially importing any backed up data. However, the import process will only import data that is not encrypted or can be decrypted using the provided encryption key. All encrypted portions of the backup data that cannot be decrypted will be imported as empty values and the import will otherwise succeed.
This affects all encrypted values in the backup data, which includes, but is not limited to data source and LDAP domain connection passwords.
7. Click Upload.
Deployment Manager displays “Result - Imported Successfully” on a successful import and you are returned to the Deployment Manager home page which shows updated values for sites and plans.
8. Refresh your browser to see the imported resources.
To restore the Deployment Management Server from command line
Using a command line tool, backup the Deployment Management server using this command:
curl -X POST -u <username:password> “http://<hostname>:<port>/rest/deploy/import_dm_metadata? -H "Content-Type:multipart/form-data" -v -F 'file=@localfilename' -F 'encryptionPassword=<encryption password>' -F 'overwrite=true/false'
For example:
curl -X POST -u admin:admin "http://localhost:9400/rest/deploy/import_dm_metadata" -H "Content-Type:multipart/form-data" -v -F 'file=@localfilename' -F 'encryptionPassword=password' -F 'overwrite=true/false'
with ignoreEncryption option:
$ curl -X POST -u admin:admin "http://localhost:9400/rest/deploy/import_dm_metadata" -H "Content-Type:multipart/form-data" -v -F 'file=@exportedDM.car' -F 'ignoreEncryption=true' -F 'overwrite=true'
Note: If -ignoreEncyption option is used, then all backup data will be imported regardless of whether a valid encryption key was provided. This means that the import will not fail. This option can be used to allow partially importing any backed up data. However, the import process will only import data that is not encrypted or can be decrypted using the provided encryption key. All encrypted portions of the backup data that cannot be decrypted will be imported as empty values and the import will otherwise succeed.
This affects all encrypted values in the backup data, which includes, but is not limited to data source and LDAP domain connection passwords.