With ARSADMIN RETRIEVE you will get the object from OAM as a file.
For example you've loaded a document with load-id of 1122-93-0-8FAA-20171102113800-20171102113800-5571
If you issue ARSADMIN Retrieve -g apgroup -h instance -m 2 -n 93-0 8FAAA 8FAA1 -d /u/temp (not the exact syntax)
You will get two files in /u/temp named 8FAAA and 8FAA1
Now if you issue:
ARSADMIN store -g newapgroup -h newinstance -m 2 -n<new primary - secondary storage> 8FAAA 8FAA1
(Run this command from /u/temp or direct the input using -d )
This will store the document in OAM for the new OD instance in the primary storage set for that application group.
You then need to move the index data from the old instance to the new. We used a form of DB2 unload -> DB2 load with modifications.
A few things to note for this method. You should be extremely comfortable working with DB2 as it requires a fair amount of manipulation of tables and values. You should also need to be comfortable with the inner workings of CMOD, how various tables, objects, settings.... are referenced/used and you have to account for resources if you are using them.
The Pro's we found using this method is it's quick, Most the of work can be scripted, Requires little or no actual down time, avoids the complications of moving AFP docs, and when done correctly preserves original expiration dates.
Con: Can be complicated and requires good advance planning, potential for really messing things up, and requires thorough verification
If you aren't pressed for time and expiration doesn't matter I'm sure an XML import/export to mirror the AGs and APs then some sort of straight up Doc get and Reload would be the easiest.
