I'm using it productive...
expire inventory right before replication to reduce the amount of data to replicate.
and to prevent ressource waiter timeouts: do not backup and replicate a node at the same time.
best practice: backup, expire, replication
to do so, I created an "expire and replicate" admin schedule which reschedules to "now+5 minutes" as long as backup is still running.
if you have a weak line and you need it during day for business, consider canceling replication.
somtimes this can take a while (up to hours for weak lines). a PMR is open for that.
last thing to know about: it is no replacement for a copypool. I'd call it an "addon" to disaster capabilities which allows you to "instantly" access data of a node, like some did it with daily "export node" in the past.
Von: Erwann Simon <erwann.simon < at > FREE.FR>
An: ADSM-L < at > VM.MARIST.EDU
Datum: 04.04.2012 19:45
Betreff: Re: [ADSM-L] Tsm Node replication on Version 6.3
Gesendet von: "ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU>
Did you attend these STE sessions last week :
I'm not using Node replication in production right now but I'm considering to use it soon.
I Think there is still missing some features such as being able to restore a failed volume of the source server from the target server. The idea behind is to avoid backing up stgs and just replicating nodes...
----- Mail original -----
De: "Robert Ouzen" <rouzen < at > UNIV.HAIFA.AC.IL>
À: ADSM-L < at > VM.MARIST.EDU
Envoyé: Mercredi 4 Avril 2012 14:10:18
Objet: [ADSM-L] Tsm Node replication on Version 6.3
Hi to all
I implant in my environment test the new feature on version 6.3 "TSM Node Replication" . The installation , configuration done without errors and made some test successfully !
Just wonder if someone is already work in production and can share some tips , recommendations …..