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

 

7.1.x and Earlier
Backup and Recovery
NetBackup
Recovering
Troubleshooting
  • schrammd's avatar
    schrammd
    13 years ago

    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

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    Catalog recovery can ONLY be done to SAME NBU version, including patch level.

    Server migration and hardware update is covered in this TN: http://www.symantec.com/docs/TECH77447

    So, in summary - to upgrade to new hardware, you will have to upgrade existing master to NBU 7.1, then use procedure described in above TN to migrate to new hardware.

    W2008 R2 on NBU server is supported as from 7.0. See NetBackup 7 Operating System (CL) :    http://www.symantec.com/docs/TECH76648

    Master Compatibility List: http://www.symantec.com/docs/TECH59978

     

     

     

  • mph999's avatar
    mph999
    Level 6
    13 years ago

    Hi Marianne ...

    I think both servers are at 6.5.6 ...

     

    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.

    I think 7.x is planned for later.

     

    Question - is the disk configered as basic disk or advanced disk ?

    Martin

  • schrammd's avatar
    schrammd
    Level 5
    13 years ago

    yeah, so as to regards to the "supported" config, I have no way to push the existing box to 7.1 as I believe it will instantly screw my VCB system up royally. Thus, the goal was to get the new box rigged up with a current OS, make sure the catalog could be restored, then upgrade it to 7.1 and play with the new vstorage api, etc.

    Both machines are running 6.5.6 and if it wasn't "supported", that's fine. But 6.5.6 does run on the new box.

    The old machine uses just a basic disk for the catalog backup. The new box has no such disk at the moment, just a drive with the backup and DR files on it.

     

    thanks

     

  • schrammd's avatar
    schrammd
    Level 5
    13 years ago

    I see the job is stuck "mounting" although what it is trying to mount I can only guess is the original storage unit. Does this make sense? Does the DR server need to have identical storage units (at least for the catalog backup policy) in order for the recovery to work? The SAN Client Fibre Transport service will not start on the new box since there is no FC (yet).

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    VCB is still supported in 7.1.

    W2008 R2 is ONLY supported as Server as from 7.0.

    See compatibility list posted above.

    I believe it is pure luck that NBU is up and running on W2008 R2 on NBU 6.5.6.

    Let us try and troubleshoot your restore problem.

    If you don't mind, please copy & post all text in Activity Monitor tab as well as DR-file and Restore log.
    You can find catalog restore log in <install-path>\netbackup\logs\user-ops\<user-name>\logs\Recover######

    Please also tell us how path to Basic Disk STU on old server is different to the path where you copied the Catalog backup:

    The old machine uses just a basic disk for the catalog backup. The new box has no such disk at the moment, just a drive with the backup and DR files on it.

     

  • revarooo's avatar
    revarooo
    Level 6
    13 years ago

    For a DR recovery no storage units are used. You don't need any storage units configured at all.

  • mph999's avatar
    mph999
    Level 6
    13 years ago

    Can we also see the DR file / header file please.  Also, please confirm the old path and the new.

    Thanks,

    Martin

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    13 years ago

    The DR Server does indeed need Storage Units to be able to mount the tape

    You should have installed NetBackup and configured your tape library to ensure that the catalog tape can be seen correctly (correct barcode and media id generation rule etc.)

    The dr file should have said that the tape was found so maybe you DR has the wrong density (hcart2 instead of hcart3 etc)

  • revarooo's avatar
    revarooo
    Level 6
    13 years ago

    > The DR Server does indeed need Storage Units to be able to mount the tape

    I thought that was done at a tape level. It finds the tape and puts it into the same 'type' drive. I thought the storage unit was not used for a catalog recovery or a restore? For a catalog recovery I've never created a storage unit first. I may be mistaken as it's been a while since I've tried.

  • schrammd's avatar
    schrammd
    Level 5
    13 years ago

    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