Hi
In our environment we have two physical servers (A and B) running multiple TSM instances on each.
A consultant recently visited us and suggested for DR purposes it would be a good idea to mount our TSM server instance configs on a share (via NAS/SAN that is replicated), so that if TSM instance 1 on server A fails, we could (if necessary) start this same TSM instance on server B by just mounting the share that has the instances configuration. Our TSM DB is mirrored between A and B using sequential writes. I hope that all made sense.
Is our consultant correct? What files would we need to start up the instance. We are using TSM 5.5 EE, and from another thread, it seems all we would need are DEVCNFG.OUT, VOLHIST.OUT, DSMSERV.OPT & and DSMSERV.DSK? Assuming server A was offline, would we need to do make any modifications to the DB in order for it to carry on as per normal?
Do we need any other files or need to take any additional steps to start a TSM Library Manager instance on another server?
Thanks
In our environment we have two physical servers (A and B) running multiple TSM instances on each.
A consultant recently visited us and suggested for DR purposes it would be a good idea to mount our TSM server instance configs on a share (via NAS/SAN that is replicated), so that if TSM instance 1 on server A fails, we could (if necessary) start this same TSM instance on server B by just mounting the share that has the instances configuration. Our TSM DB is mirrored between A and B using sequential writes. I hope that all made sense.
Is our consultant correct? What files would we need to start up the instance. We are using TSM 5.5 EE, and from another thread, it seems all we would need are DEVCNFG.OUT, VOLHIST.OUT, DSMSERV.OPT & and DSMSERV.DSK? Assuming server A was offline, would we need to do make any modifications to the DB in order for it to carry on as per normal?
Do we need any other files or need to take any additional steps to start a TSM Library Manager instance on another server?
Thanks
Last edited: