We have been working on a process to copy our Content Server data and refresh it in QAS in parallel with an ECC refresh, and the process we have been somewhat successful with is this:
- Take a backup of the PRD Content Server
- Restore it to the QAS Content Server
- Set the repositories in ECC QAS so that both QAS and PRD repo definitions in OAC0 point to the QAS HTTP address (very key here, unless you want to move actual records from PRD to QAS). In our case the data is there from the data restore, we simply want to change the storage location name to QAS.
- Execute the DMS_RELOCATE_CONTENT report to migrate the storage categories from 'PRD' to 'QAS'
The last step is where we have only been partially successful. In DMS_RELOCATE_CONTENT, we *only* specify the old storage location and the new storage location, and once complete the majority of the documents are moved.
What I am finding it that even without setting a filter on document status, the documents with status 'RT' (Retired) are not migrating - they still show the original storage location, and ideally we want to update those as well - we want to move all of the documents in the system from the old storage location (PRD) to the new (QAS).
We can continue to access the documents with RT status by having a second Content Repo definition for PRD, but in actuality 'redirect' it to the QAS HTTP address for the content server. The concern is confusing users who select documents in CV04N, and see the storage location as 'PRD', when in reality it is accessing from the QAS Content Repo through this redirect.
The issue is that anytime we select a doc in CV04N, the Storage Category is the original - the category was not changed when the DMS_RELOCATE_CONTENT report was executed. No filter was used on the documents in the report, so I can see no reason they should not have migrated. All other document statuses appear to have migrated as expected.