----- "Wanda Prather" <[email protected]> wrote: > > I think the answer to your question is technically "no". > > The recommended way to move the metatdata is to set up DB2 HADR to > replicate the DB, which accomplishes what you want. > (If your DB isn't too big for your bandwidth, you can also backup the > DB to disk and ship the DB backup via FTP, but that's another story.) > > There is an STE presentation that includes the DB2 HADR setup: > http://www-01.ibm.com/support/docview.wss?uid=swg27021382 > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf > Of Xav Paice > Sent: Tuesday, February 07, 2012 11:40 PM > To: [email protected] > Subject: [ADSM-L] TSM 6.3 node replication > > Hi, > > I'm keen to make use of the new features in TSM 6.3, one of which is > node replication. However, the client I'm working with has limited > bandwidth between datacenters and there is no way that 4TB of change a > day is going to be copied across the link even if it is deduplicated. > Is there a way to replicate just the metadata and not the actual data, > whilst shipping copy pool tapes by courier? My original, pre-release, > understanding was that this was possible but the documentation is > leaving me less clear. > > I was thinking along the lines of configuring nodes for replication, > but disabling replication for the filespaces - but does that copy the > entries for data contained on the copy pool volumes even if it doesn't > copy the objects?
Thanks Wanda - that presentation was just what I needed. I guess I could also do db backups to virtual volumes located on a deduplicated storage pool.... lots to test out and play with.
