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 people karma can be a valuable learning experience :)
Rick Adamson Information Technology Southeastern Grocers LLC -----Original Message----- From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of Schneider, Jim Sent: Wednesday, August 29, 2018 12:00 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] cluster backup with CSV * This email originated outside of the organization. Use caution when opening attachments or clicking links. * ---------------------------------------------------------------------- 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 as a starting point. Jim -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson Sent: Wednesday, August 29, 2018 7:30 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] cluster backup with CSV 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 manager to create a new generic service resource. Add all cluster nodes as possible owners. Add the shared disk as a dependency. Specify the scheduler service that you need to failover. If you haven't done so open a command prompt and set the services password using dsmc. Something like: dsmc incr -nodename=<cluster-nodename> -password=<clusternode-password> -optfile=<full path to dsm.opt located on the shared resource> There will be a place to enter a registry key path where the scheduler service encrypted password is kept, I ignore it during setup of the resource..... then: Open registry editor and navigate to the scheduler service password location, it should be something like: HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\<nodename> Export that reg key and import it on all other cluster nodes. Open the properties page of the generic service resource you created above and add the path to registry key. Notes: I also edit the properties of the resource and disable its ability to cause failover, if the scheduler service happens to fail I don't want it to initiate a cluster failover. The scheduler service now needs to be stopped or started using the clustering/failover interface and not the services app. Hope that helps.... sorry if it's kind of vague I don't have access to my actual docs at the moment. Rick Adamson Information Technology Southeastern Grocers LLC -----Original Message----- From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of Schneider, Jim Sent: Tuesday, August 28, 2018 4:12 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] cluster backup with CSV * This email originated outside of the organization. Use caution when opening attachments or clicking links. * ---------------------------------------------------------------------- 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 the active node changed to a different server. This was TSM 7. Things may have changed. I don't know if this is best but it worked. Jim Schneider -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Michael P Hizny Sent: Tuesday, August 28, 2018 2:56 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] cluster backup with CSV We have just set up a Microsoft cluster with a Cluster shared volume. After installing the TSM 8.1.4 client on both cluster nodes, we would like to back up the cluster shared volume but TSM does not see this volume from either node. Is there a way to back this up with TSM or a special configuration so this disk is recognized? Thanks, Mike Michael Hizny Binghamton University ********************************************************************** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. **CONFIDENTIALITY NOTICE** This electronic message contains information from Southeastern Grocers, Inc and is intended only for the use of the addressee. This message may contain information that is privileged, confidential and/or exempt from disclosure under applicable Law. This message may not be read, used, distributed, forwarded, reproduced or stored by any other than the intended recipient. If you are not the intended recipient, please delete and notify the sender.
