Forum Discussion

Chidobrad's avatar
Chidobrad
Level 3
6 years ago
Solved

Catalog restore error

Hello All, please i have an issue. i did an operating systems upgrade from windows 2008 to windows 2016, in the process the application broke (i had done a catalog backup prior to upgrade with DR file intact). After successfull upgrade, i re-initiated installation of netbackup on master and Media successfully , then proceeded for catalog restore.. the restore was partial and not successfull (only policies were restored, other parameters lost). When i check the recover logs, it pointed to modifications done before catalog backup which couldnt be restored. Please find attached recover log... i need to know if this restore can be fixed (anyway) or my old data lost. Please i need help badly. Many thanks and awaiting replies from my able backup engineer specialists in this forum. thanks

8
Windows Server 2016
  • sdo's avatar
    sdo
    6 years ago

    There are thousands of messages like:

    09:06:17 (3.001) WRN - can't create directory: \\?\E:\Netbackup\alternate_db\images\fctirs-app-03 (WIN32 21: The device is not ready. )

    Maybe your E: volume was missing at time of recovery ?

  • sdo's avatar
    sdo
    Moderator
    6 years ago

    There are thousands of messages like:

    09:06:17 (3.001) WRN - can't create directory: \\?\E:\Netbackup\alternate_db\images\fctirs-app-03 (WIN32 21: The device is not ready. )

    Maybe your E: volume was missing at time of recovery ?

    • Chidobrad's avatar
      Chidobrad
      Level 3
      6 years ago

      Many thanks as this was the solution. The folder as at when catalog happened was E drive but after upgrade, it changed to drive F. after i changed it back to E... The catalog restore worked successfully and all my database and constituents are back. Many thanks and much appreciation for this.God bless

  • sdo's avatar
    sdo
    Moderator
    6 years ago

    MS state that there is no direct upgrade path from Windows 2008 or WIndows 2008 R2 direct to Windows 2016 - and that you have to hop through Windows 2012 R2 :

    https://docs.microsoft.com/en-us/windows-server/get-started/installation-and-upgrade

    They also state that "Upgrade works best in virtual machines where specific OEM hardware drivers are not needed for a successful upgrade." which is Microsoft speak for saying that in place Windows OS upgrades on physical servers are more likely to fail.

    Was your Windows OS upgrade on physical or virtual ?

      • sdo's avatar
        sdo
        Moderator
        6 years ago

        Did you create an E: volume and re-try the recovery ?