ADSM-L

Re: [ADSM-L] Using Datadomain for replication

2011-12-09 10:42:24
Subject: Re: [ADSM-L] Using Datadomain for replication
From: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 9 Dec 2011 09:35:25 -0600
We are currently building that setup.

We use a hosts entry to point to the DD.  The untested plan is to use a hosts 
entry to point the DR TSM to the replicated copy and avoid re-pointing the 
devclass.

Our connectivity is UNC across a private network.

We are a month or two from the DR testing.

Andy Huebner

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Bill Boyer
Sent: Friday, December 09, 2011 9:14 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Using Datadomain for replication

Anyone out there using a DDR as the primary FILE devclass, having it
replicate to a 2nd DDR in a recovery site and having to do a TSM recovery
using the 2nd DDR?



Are you using the UNC path name for the DEVCLASS or a drive mapping? This is
strictly Winders and CIFS, not NFS.



What I'm coming up against is at the 2nd site after restoring the DB all my
volumes still point to the primary DDR UNC name. I can change the DEVCLASS,
but that doesn't seem to effect the existing volumes, only new volumes. So
unless I also rename the 2nd DDR to the name of the primary DDR, all my
volumes are basically unavailable.



Just wondering how anyone else using DDR replication for TSM.



Bill Boyer
DSS, Inc.
(610) 927-4407
"Enjoy life. It has an expiration date." - ??

This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.

Thank you.

<Prev in Thread] Current Thread [Next in Thread>