CDOT Tip #6

Here are some recent CDOT questions we’ve fielded:

Q: ”I reviewed the volume move portion of the ‘CDOT replication Guide’ (attached). I don’t see anything in document about migrating an SVMs root volume to another node/aggregate along with volumes it host. Just wanted to confirm that there are no issues using ‘volume move’ to migrate an SVM root vol?” 

A: Root Volumes for data vservers are no problem, go ahead and move them.  Node volumes are not Vol movable, however. They belong to the physical node.

Q: “The standard vol language will be UTF8 in CDOT, but we have many 7mode volumes which are set to ‘en_US’ or ‘C’. The destination volumes will inherit the same language as the source. Is there any way to convert the volume languages ‘en_US’ or ‘C’ to UTF8 once they have been migrated to CDOT?” 

A:  No - You cannot change the volume language after it is set; thus, if you want it to be something specific, it needs to be changed on the 7-Mode volume prior to migrating with the 7-Mode Transition Tool.

Q:  “Can I have a backup (snapvault) configured on a volume which is currently the destination of a 7mode to cdot migration?” 

A:   No - During a TDP snapmirror (snapmirror from 7 to C), you cannot cascade the destination volume.

Q: “The Oracle Database Team wrote a script to take snapshots of their oracle volumes in cdot. They have a similar script for 7mode. In 7mode, they take a snapshot via the script and we set retentions on the filer so that aged snapshots can be deleted. But, I can’t figure out how to create a policy which does NOT create a snapshot, but will delete aged snapshots. Any ideas how we can achieve this?”

A: Your best bet would be to estimate the space per snapshot, turn on snap autodelete, then size the volume/snapreserve to hold that many snapshots.  You could also use an outside script or snapcreator.

Q: “Is there a command to see snapmirror lag in CDOT?”

A: Snapmirror show with the –fields option is what you’re looking for!  There are a lot of fields you can include, from lag time to last-transfer-end-timestamp.