Yea, we use the replication approach for many of our machines to an offsite DR
facility too.
But they had to learn the hard way that it may good for recovery it doesn't
address their need for having historical options of recovery, so backups I was
asked to reinitiate the backups.
For some peop
Rick,
Thank you for the notes. My company collapsed both cluster servers into a
single VM that is replicated via some vSphere magic to out alternate data
center for resurrection during a DR. I currently have no cluster backups. I
was providing notes on my TSM v5 cluster backup configuration
Jim,
Have you tried to create a cluster resource for the shared disk? The scheduler
service will then failover with the disk and you will not need to manually
start it every time there is a change in cluster node ownership.
At a high level:
In addition to what you have already done.
Use Failover
I created a TSM directory on the shared drive, added a dsm.opt file with a
domain statement. Registered a cluster name with TSM and created a scheduler
service for it on each of the cluster nodes. Only one node was active at a
time, and I had to restart the cluster scheduler service every time
Hello Michael,
TSM client doesn't support backup and archive of the objects on Cluster Shared
Volume File System (CSVFS).
Since version 7.1.4 the client code has been modified so backup, archive,
backup image operation of objects on CSVFS will fail.
Regards Uwe
> Am 28.08.2018 um 21:55 schrie
