-
Título
How to migrate (or even backup) an InTrust repository that is in use by existing tasks and jobs? -
Descrição
How to migrate (or even backup) an InTrust repository that is in use by existing tasks and jobs with the least impact on production?
-
Causa
Some customers to migrate (or backup) an InTrust repository that is in use by existing tasks and jobs without (or with little) impact on production.
-
Resolução
Ensure there are no Tasks and / or Jobs schedule running during the time these steps are being done:
1) Create a new Share in the new location where you will be migrating the current repository to (so it is accessible via UNC path for example).
2) In the InTrust Manager, create a new Repository, under the "Data Stores | Repositories" node, BUT, point this to the current repository (the physical location the repository is currently at before migration), this will mean there will be two repository pointers pointing to the same physical location.
3) In the InTrust Manager, under the same "Data Stores | Repositories" node, find the original Repository Pointer, under it's Properties, under the Repository tab, paste in the new UNC path of the Share you created in step 1.
4) Commit the changes, what this will do is the original Repository pointer will point to the new location already, so any Gathering / Importing / jobs will already be pointing to the correct (new) location, so when gathering or importing kicks off, the data will be going to the new location (via the same pointer the jobs are already set up to use).
5) Create a Repository Consolidation job, set it to Consolidate "All" data from the new repository (the new pointer, that points to the old repository), to the old repository (the old pointer, that points to the new location).This is the least intrusive way of doing a Repository migration, as it really only changes the pointer of the original repository to the new location, making the change transparent to all of the existing jobs.