Back up an organization for safeguarding and restore it to either the same or new organization.
For administrators or developers, backing up an organization is critical. Should the organization get corrupted or tests fail due to a major code change, you can restore from a known good state.
Organization backups also offer a quick way to populate a new pre-release or development organization using any backup snapshot.
Enabling or disabling backup and restore
You can enable or disable the backup and restore functionality. By default, it is disabled.
1In Administrator, select Organization.
2Select the Backup and Restore tab.
3Select Enable Organization Backup and Restore.
The backup settings are displayed. If you disable Enable Organization Backup and Restore, the backup settings are suspended.
Backing up an organization
Configure a schedule to back up the organization. You can configure the backup frequency, start date and time, and the backup retention period.
2Select the backup frequency. You can choose from Daily, Weekly, Bi-weekly, or Monthly.
3Specify the start date to begin the backup schedule.
4Specify the start time for the backup. You have four time options, six hours apart.
Tip: Minimize or avoid changes during the backup windows to prevent potential data inconsistency and ensure accurate data snapshots.
5Specify how long to retain the backups, ranging from 30 to 120 days. Once a backup reaches this age, it is automatically deleted.
If backups exist, they appear under the Backup tab below the backup settings. You can browse and filter the backups, and you can remove individual backups through the Action menu.
Backups don't contain sensitive information such as passwords, licenses, and metering information.
Restoring an organization
Restore an organization if you encounter errors and want to roll back to a known good state. You can also provision a new organization by restoring an existing backup to it.
There are many reasons why you might want to restore an organization, including corruption or tests fail due to major code changes.
The restore feature is also useful to provision a new pre-release or development organization using the most current or last known good backup snapshot. You can use this pre-release organization to pilot a new initiative or to validate the latest release from Informatica.
Use the following guidelines when restoring:
•Sensitive information such as passwords, licenses, and metering information aren't backed up and therefore not restored. If you are restoring to a newly created a new organization, you must obtain a license as with any new organization.
•The restore process may require minor downtime, ranging from 30 minutes to 1 hour. This is to resolve issues such as assets involved in the restoration might be actively executing jobs. Or, connections might have changed since the backup was made. You may be prompted to fix connections and runtime environments if they have changed since the backup.
•If assets were created since the backup, you can either delete these newly created assets or keep them. You might also be prompted to keep or discard other configuration changes during restore.
•Log files created after a backup aren't removed during a restore.
•If the restore fails, download the error log, fix the errors, and try restoring again.
If you are restoring to a new organization, some of these guidelines won't apply, such as resolving nassets created after a backup.
Restoring to the same organization
The most common scenario is restoring a backup to the same organization.
1On the Backup and Restore page, select the Backup tab.
2Locate the backup to restore and then select Restore to current organization as shown in the following image:
3Click Validate and Restore to begin.
Functionality within the organization may be limited while the restore is in progress.
You can see the status of the restore in the Status column of the Restore tab.
Restoring to a different organization
You can restore a backup made from one organization to a different organization. This is often the fastest way to provision a new pre-release or development organization, to test a new initiative or to validate the latest release of Intelligent Data Management Cloud.
If you are restoring to a new organization, be sure to obtain the proper licensing through the normal means. The restore does not include licenses.
1Open the Backup and Restore page of the organization with the backup that you will restore on the other organization.
2In the Backup tab, select Fetch token for restore from the Action menu of the appropriate backup, as shown in the following image:
3Click Copy to copy the token and then click Close.
Note: The token is valid for only one hour. If it is not used within that time, you must obtain a new token.
4Log in to the organization where you want this backup to be restored.
5In Administrator, select Organization and then select the Backup and Restore tab.
6In the Restore tab, click Restore With Backup Token as shown in the following image:
7Paste the token in to the Backup Token field.
8Click Continue.
9Click Validate and Restore to begin.
Functionality within the organization may be limited while the restore is in progress.
You can see the status of the restore in the Status column of the Restore tab.
