Forum Discussion

schrammd's avatar
schrammd
Level 5
13 years ago

Catalog recovery is in progress. Please wait...for hours

Trying to recover the entire catalog from a online backup and DR file to a DR box for hardware and OS refresh before eventually moving to 7.x.

Old box is master/media server Server 2003 x64 and was 6.5.4 but patched to 6.5.6 to allow for migration to newer machine.

New box is Server 2008 Ent.R2 SP1 x64 and running 6.5.6 with just local disks.

Nothing seems to be occuring, no IO and nothing on the CPU. Have VERBOSE line in vm.conf and bpdm log shows nothing of interest. bprecover -wizard from cmd line works but once it gets to the please wait part - it never has completed. Catalog backup is about 4GB so it shouldn't take that long.

Basically I took the full backup images from the local disk on the old master copied them to a local disk on the new box, and edited the DR file to have the right path to the files.

Any body have any ideas?

 

thanks!

thanks

 

  • Ok, progress. First off, Marianne- your picture reminds me of my mother-in-law and I feel like I'm at a family function here ;(.

    Anyhow- the issue is not with tape, as I said, catalog backups were going to SAN disk except those vaulted on tape. What I discovered after some amount of cursing, was that in the activity monitor the "problem" was actually right there in plain clothes but since I was doing the recover from cmd line - who would have known.

    Even though the DR file was edited to tell it where to look for the images, the recovery apparently needs the identical storage unit which the original catalog backup was made on existing on the new hardware. So, I took a SAN snapshot of the source LUN, gave it to the new box, mounted it, and voila- I can recover the DB in a jiffy. How cool is that.

    Thanks folks for your suggestions. Oh - and for those with enquiring minds 6.5.6 DOES run on 2008R2SP1 just fine thank you. On to the 7.x upgrades....yeeee haw

     

11 Replies

  •  

    No STU required ...
     
    Here are my STU - only disk (I just deleted the tape STUs ...)
     
    root@womble scripts $ bpstulist
    sp1 0 womble 0 -1 -1 3 0 "*NULL*" 1 1 524288 womble 0 6 0 0 0 0 Advance_DiskPool_sp1 womble 515527
    sp3 0 womble 0 -1 -1 3 0 "*NULL*" 1 1 524288 womble 0 6 0 0 0 0 Advance_DiskPool_sp3 womble 515527
     
    I ran a restore using my new fancy restore script ...
     
    root@womble scripts $ ./restore2.sh 04/18/2012
    Tmp restore directory /tmp/sym/restore already exists
    Please enter value for MASTER
    womble
    Please enter value for SOURCE
    flump
    Please enter value for DESTINATION
    flump
    Please enter value for FILELIST
    /tmp/filelist
     
    Looking in trylogs for job ...
     
    NUMBER_OF_IMAGES_REQUIRED 1334759279 1
    MEDIA_ID_NEEDED 1334759279 R1TP00
    RESTORING_FROM_IMAGE 1334759283 flump_1334758839
    LOG 1334759214 4 bpbrm 8836 telling media manager to start restore on client
    LOG 1334759214 4 bpbrm 8836 spawning a brm child process
    CONNECT 1334759214
    LOG 1334759214 4 bpbrm 8836 child pid: 8841
     
    LOG 1334759214 4 bpbrm 8841 start tar on client
    LOG 1334759214 4 tar 8845 Restore started.
    CONNECTED 1334759214
    LOG 1334759216 4 bptm 8840 Waiting for mount of media id R1TP00 (copy 1) on server flump.
    PROCESS 1334759216 8840 bptm
    MOUNTING 1334759216 R1TP00
    LOG 1334759216 4 bptm 8840 INF - Waiting for mount of media id R1TP00 on server flump for reading.
    REQUESTING_RESOURCE 1334759286 R1TP00
    RESOURCE_GRANTED 1334759287 R1TP00
    RESOURCE_GRANTED 1334759287 HP.C5713A.000
    MOUNTED 1334759272 R1TP00
    LOG 1334759272 4 bptm 8840 R1TP00
    LOG 1334759272 4 bptm 8840 INF - Waiting for positioning of media id R1TP00 on server flump for reading.
    POSITIONING 1334759272 R1TP00 1
    POSITIONED 1334759279 R1TP00
    BEGIN_READING 1334759279
     
    Regards,
     
    Martin