I just tested it with the TSM server, Windows did not have an issue connecting 
to the remote DD as if it was the local one with a simple hosts change.  So my 
idea of changing the hosts file will work.

The target is read-only, during a test or DR this would be changed.  In a test 
you would use a copy of TSM to hit a copy of the data, once the test is done 
overwrite the targets.  In a DR you would use the survivors.  Nothing here 
should be unexpected.


Andy Huebner

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Bill Boyer
Sent: Monday, December 12, 2011 11:56 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Using Datadomain for replication

That's fine, but it will fail even though you point the host entry to the DR
box. This is CIFS and the \\hostname\backup has to match the one of the DDR
you're pointing to. By default on the DDR the hostname is the CIFS NBT name
used. You can change the CIFS NBT name to something different (CIFS SET
nb-hostname <nb-hostname>) ...like the original servername in the devclass
without changing the hostname in the DDR. But that could lead to confusion.

Plus the target of the DDR replication is read-only. You'll have to break
the replication or make sure you don't write to those volumes.

I was hoping  to use a drive letter mapping for my DDR, but the question is
how to do this for a service that runs at startup. I have my TSM Server1
service set to run-as a local user that is also defined on the DDR so
authentication just passes on through. But how to map a drive automatically
when the service starts or the server starts....????

Then I could just do a snapshot of the target DDR ( as long as it's not
container replication) map my drive to the read/write snapshot and proceed
on.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Huebner,Andy,FORT WORTH,IT
Sent: Friday, December 09, 2011 10:35 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Using Datadomain for replication

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.

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.