03 - Pre-Restore Processes
Between the time that you took your initial backup and wrote your playbook, some time will have elapsed. During this time, the client has likely added or changed data in their source system.
Prior to completing the restore, you should do the following:
1. Create a fresh backup of the source system.
2. Re-apply your playbook to the fresh backup.
By doing the above, when you're ready to actually start the migration, you will be migrating the client's current data with all of the tweaks you prepared in your playbook.
Related Articles
04 - Pre-Restore Review
All Consultants Prior to restoring data into a destination system, you should thoroughly review and test your playbook. Your playbook should be complete and cover all the data that you expect to migrate as part of your project. Thoroughly review and ...
01 - Tweaking a Restore
Sometimes after restoring a backup, a customer may want you to tweak the data that is in their new system. Tweaking data post-restore is easy! Let's say that the customer wants you to "mark as complete" all tasks that are related to archived (closed) ...
02 - Restore-Specific Database Columns
The following columns are commonly used when Universal Migrator is restoring data into a destination system. Restore Ordering and Priority Action_Group The Action_Group allows you to mass-segment data. Only the data with the highest Action_Group in ...
08 - Special Topics: Restore Performance and Threading
When Universal Migrator transfers data, it takes a number of precautions to ensure that bad things do not happen in the destination system. Threading Universal Migrator uses multiple threads to transfer data concurrently. Each thread is assigned a ...
Training: Overview
Welcome to the Migration Academy! This series will help you learn everything you need to know in order to deliver high-value, rock-solid data and document migrations. Completion of the academy generally takes 4-8 hours and is required in order to ...