We had our fall D/R hotsite test last week and all went well -- except for the recovery of our primary Windows 2003 file sharing system. It just takes WAY too long.
Part of the problem is the sheer number of files/directories per drive -- I'm working with the Intel/Windows admin group to try some changes when we swap this system out in November. Part of the problem is that the directory structure is scattered over a mass of other backups. I'm looking for suggestions on this. The system is co-located by drive, but only for five of the nine logical drives on the system. I may have to bite the bullet and run all nine logical drives through co-location. Is there any way to force the directory structure for a given drive to the same management class/storage pool as the data? I'm thinking I may have finally come up with a use for a second domain, with the default management class being the one that does co-location by drive. If I go this route -- how do I migrate all of the current data? Export/Import? How do I clean up the off-site copies? Delete volume/backup storage pool? I'm on TSM Server 5.3.2.0, with a 5.3 (not sure of exact level) client. TIA Tom Kauffman NIBCO, Inc CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
