Seeding an Aux copy with CacheDB
Copies in the storage policy
2. Seed Aux Copy with Dedupllication
3. Aux Copy (destination)
Please follow the steps below
1. Insert UsecacheDB and UseAuxcopyreadlesssplus into the source media agent on the primary copy
2. Create a library for the seed copy using the portable storage device, or the device to be moved to the remote location for seeding. (could also be cloud)
3. Create a Seed Aux copy with deduplication. This will use the source media agent and seed library created in step 2 for the data path. This copy can also be set to disk read optimized for faster transfer.
Note: It is the preferred method to create the seed copy with deduplication so that we generate the CL_DB folder on the source Media Agent, which will be used for moving the cache later on.
4. Run the seed copy until completion
5. Configure the Aux Copy (destination) with Deduplication and to use the destination Media Agent and destination library in the data path. Also, specify the copy policy to use the seed copy as the source.
6. Move the portable storage to the remote site
7. Once the storage is ready for access, run the secondary Aux copy until complete
8. Go back to the copy policy on the Aux Copy (destination) and uncheck specify source on the copy policy.
9. Do not run any new jobs yet
10. Go into the Job results directory and copy the aux_copy folder from CV_CLDB back to the source media agent in the same directory (Stop all services before doing this)
11. Change the destination copy on the deduplication tab to use network optomized
12. Test run the secondary copy again to test performance
13. If there is no cached errors, delete the seed copy and deconfigure and remove the seed library (if not needed for future usage)
1. If the seed copy is configured WITHOUT deduplication, the CV_CLDB folder will not be created in the source media agent job results directory.
2. Based on past incidents, if the seed copy does not have deduplication and the destination copy does, then the CV_CLDB folder can be created and utilized manually located in the same directory as the destination and copied to the source directory