Hi All
I recently rolled out TSM 5.5 for my company and last week we did a DR test one of our sites to ensure the rollout was successfull. However I couldn't restore any system states as the restore was trying to find them on the Primary Storage Pool (which had been destroyed) and not the copy pool (on tape).
The DR people at the centre said it was bug within TSM the the system states don't copy from the primary in the copy pools and to run the following command to find out what hasn't copied:
q content F:\<primary pool location> node=<nodename> copied=no
On running this I can see that all my system states are not copying to the copy pools and to tape to get stored offsite which is obvisouly and issue when it comes to restore.
Has anybody else had this and know if it can be fixed?
Thanks
Phill
(newbie)
I recently rolled out TSM 5.5 for my company and last week we did a DR test one of our sites to ensure the rollout was successfull. However I couldn't restore any system states as the restore was trying to find them on the Primary Storage Pool (which had been destroyed) and not the copy pool (on tape).
The DR people at the centre said it was bug within TSM the the system states don't copy from the primary in the copy pools and to run the following command to find out what hasn't copied:
q content F:\<primary pool location> node=<nodename> copied=no
On running this I can see that all my system states are not copying to the copy pools and to tape to get stored offsite which is obvisouly and issue when it comes to restore.
Has anybody else had this and know if it can be fixed?
Thanks
Phill
(newbie)