Doing a DR recovery directly from a replication context target mtree or directory isn't recommended anyway. Look into the Data Domain "filesys fastcopy" command to duplicate your replicated data to static read/write copy for temporary DR testing.
There are some whitepapers that discuss this concept. On Fri, Aug 2, 2013 at 4:01 AM, Tuncel Mutlu (BT İşletim ve Teknik Destek Bölümü) <[email protected]> wrote: > Hi, > > I have EMC Data Domain here and a remote one and I am doing replication > between them. TSM is v5.5.6.100 on AIX, so is the Storage Agent on both > end. The files backup also on AIX, file client is v6.2.4.4. These are file > backups. > > To prepare for a restore on the remote location: > - previously has copied the rootvg (AIX) couple of days ago (DB and LOG > disks has not changed), remote virtual library and drives were avaiable > - copied the DB and LOG disks after the backup (SVC replication) > - copied VOLHIST and DEVCONFIG to the appropriate directory > - changed DSMSERV.OPT, added DISABLESHEDS YES and NOMIGRRECL > - opened the TSM and using a script disable sessions, deleted sheds, disk > pool volumes, paths, drives, libraries, redefined the virtual library and > drives > > When I tried to do a test restore for a small file (there a 5 of them and > 42 of the big ones), there is failure and it says cannot find the file, on > TSM it says cannot mount read-only cartridge (the cartridges are READWRITE > on TSM, but on VTL there are RORD - Read Only / Replication Destination), I > tried all kind of stuff but couldn't get thru, so I deleted the replication > pair relationship and then it worked. After starting the restore with 12 > concurrent sessions, I saw the following: > > ANR1699I Resolved MUHORAP11_STG to 1 server(s) - issuing command Q MOUNT > against server(s). > ANR1687I Output for command 'Q MOUNT ' issued against server MUHORAP11_STG > follows: > ANR8330I LTO volume CB0060L3 is mounted R/O in drive AKDD5_DB_DRV03 > (/dev/rmt14), status: IN USE. > ANR8329I LTO volume CB0100L3 is mounted R/W in drive AKDD5_DB_DRV02 > (/dev/rmt13), status: IDLE. > ANR8330I LTO volume CB0067L3 is mounted R/O in drive AKDD5_DB_DRV04 > (/dev/rmt15), status: IN USE. > ANR8330I LTO volume CB0069L3 is mounted R/O in drive AKDD5_DB_DRV05 > (/dev/rmt16), status: IN USE. > ANR8330I LTO volume CB0068L3 is mounted R/O in drive AKDD5_DB_DRV06 > (/dev/rmt17), status: IN USE. > ANR8330I LTO volume CB0064L3 is mounted R/O in drive AKDD5_DB_DRV07 > (/dev/rmt18), status: IN USE. > ANR8330I LTO volume CB0073L3 is mounted R/O in drive AKDD5_DB_DRV08 > (/dev/rmt19), status: IN USE. > ANR8330I LTO volume CB0065L3 is mounted R/O in drive AKDD5_DB_DRV09 > (/dev/rmt20), status: IN USE. > ANR8330I LTO volume CB0004L3 is mounted R/O in drive AKDD5_DB_DRV10 > (/dev/rmt21), status: IN USE. > ANR8330I LTO volume CB0080L3 is mounted R/O in drive AKDD5_DB_DRV11 > (/dev/rmt22), status: IN USE. > ANR8330I LTO volume CB0075L3 is mounted R/O in drive AKDD5_DB_DRV12 > (/dev/rmt23), status: IN USE. > ANR8330I LTO volume CB0079L3 is mounted R/O in drive AKDD5_DB_DRV13 > (/dev/rmt0), status: IN USE. > ANR8330I LTO volume CB0074L3 is mounted R/O in drive AKDD5_DB_DRV14 > (/dev/rmt1), status: IN USE. > ANR8334I 13 matches found. > ANR1688I Output for command 'Q MOUNT ' issued against server MUHORAP11_STG > completed. > ANR1694I Server MUHORAP11_STG processed command 'Q MOUNT ' and completed > successfully. > ANR1697I Command 'Q MOUNT ' processed by 1 server(s): 1 successful, 0 > with warnings, and 0 with errors. > > The cartridge which is mounted R/W is the same one which was requested > before, It contains all of the small files and pieces of 2 big ones. > > My question is why a restore will require cartridge to mount R/W ? The > pools on the destination side of VTL replication are R/O, and only deleting > the pair relationship will make the R/W, but I don't want to do it again. > > Regards, > > Tuncel > > > > > > > Değerli görüş ve önerilerinizi internet sayfamızdaki Bize Ulaşın > bölümünden iletebilirsiniz. > Bu e-posta ve muhtemel eklerinde verilen bilgiler kişiye özel ve gizli > olup, yalnızca mesajda belirlenen alıcı ile ilgilidir. Size yanlışlıkla > ulaşmışsa lütfen göndericiye bilgi veriniz, mesajı siliniz ve içeriğini > başka bir kişiye açıklamayınız, herhangi bir ortama kopyalamayınız. Bu > mesaj veya ekleri, aksi sözleşme ile veya mesaj içeriğinde açıkça > belirtilmedikçe, herhangi bir işleme ilişkin olarak Bankamız adına herhangi > bir teklif, kabul veya teyit amacı taşımamaktadır. Verilen bilgilerin doğru > veya eksiksiz olmasına yönelik bir garanti verilmemekte olup, bilgiler > önceden bildirilmeksizin değiştirilebilecektir. Bu mesajın içeriği > Bankamızın resmi görüşlerini yansıtmayabileceğinden Akbank T.A.Ş. hiçbir > hukuki sorumluluğu kabul etmez. > > > You are kindly requested to share your valuable views and opinions to us > via the Contact Us section on our website. > The information provided in this e-mail and any attachments it may contain > is proprietary and confidential, and is only related with the receiver of > this message. If it is sent to you by mistake; please inform the sender, > delete the message and do not explain its contents to anyone, and do not > copy it in any form. Unless otherwise provided by contract, this message is > not intended to act as a banking transaction such as an offer, purchase or > sale of a financial transaction or confirmation of a remittance. No > guarantee is given for the accuracy or integrity of any or all information > provided herein and such information may be changed without prior notice. > Akbank T.A.Ş. acknowledges no legal responsibility whatsoever as may be > related with or arise out of the content of this message as it may not > reflect the official policy of our Bank.
