Forum Discussion

LubosDvorak's avatar
LubosDvorak
Level 4
8 months ago
Solved

BMR: Could not read saved configuration file=X:\bmrcli.xml

I am testing Bare Metal Recovery. Test environment is virtual (VMware). The recovered system is booted from boot ISO. It connects to the master server but during the step "Establishing restore environment" this error message is shown:

The restore has stopped due to the following error: Could not read saved configuration file, file=X:\bmrcli.xml

NetBackup servers and client version is 10.3.

Any ideas?
Thank you.

BMR
  • kiyan's avatar
    kiyan
    8 months ago

    follow the manual properly .definitely a step is missing which is causing the issue. I have made note of BMR restoration for myself (windows physical server to Virtual machine).which might help you (master server is a linux)

    put the name (same as source) and ip address (can be different) to master, media server, boot server in the host file (in media server, master server, boot server)
    on the master server, go to /usr/open/netbackup/db/altnames,create No.Restriction file (touch )


    boot the VM with SRTBOOT>cancel and go to generic discovery
    generic discovery > give a name > provide a name and static ip
    once the discovery is finished, do not boot the server yet.
    go to netbackup master server, confirm the date you want to restore from, go to BMR, create configuration to that particular time and then copy the configuration to change it 
    click on initialize devices , select configuration and click ok
    on network interface, click initialize ,select network interface (which is the new destination) click on it and select change and change the IP

    go to volume, disk view,initialize,and do the changes if required (map them)
    now our copy configuration is ready, prepare to restore, (select use policy as well)and click ok
    once it is done, restart the destination server(VM) and boot from the server.
    (generic restore BMR)provide the same IP and make it permeant>contact master server > accept >enter the reissue token
    it will restore all drivers, configuration (system state), registry
    after the restore is over, you must login by local admin first time , so the BMR cleanup happens at netbackup server.(it might fails if you do not do it)

    I hope the above is useful to you.If you have active support, I suggest, you open a ticket and take note of all steps for your future.

     

    Regards,

3 Replies

Sort By
  • LubosDvorak's avatar
    LubosDvorak
    Level 4
    8 months ago

    P.S.: The file "C:\Program Files\Veritas\NetBackup\BareMetal\client\data\bmrcli.xml" on the client has been backed up by the BMR client backup job.

    • kiyan's avatar
      kiyan
      Level 6
      8 months ago

      follow the manual properly .definitely a step is missing which is causing the issue. I have made note of BMR restoration for myself (windows physical server to Virtual machine).which might help you (master server is a linux)

      put the name (same as source) and ip address (can be different) to master, media server, boot server in the host file (in media server, master server, boot server)
      on the master server, go to /usr/open/netbackup/db/altnames,create No.Restriction file (touch )


      boot the VM with SRTBOOT>cancel and go to generic discovery
      generic discovery > give a name > provide a name and static ip
      once the discovery is finished, do not boot the server yet.
      go to netbackup master server, confirm the date you want to restore from, go to BMR, create configuration to that particular time and then copy the configuration to change it 
      click on initialize devices , select configuration and click ok
      on network interface, click initialize ,select network interface (which is the new destination) click on it and select change and change the IP

      go to volume, disk view,initialize,and do the changes if required (map them)
      now our copy configuration is ready, prepare to restore, (select use policy as well)and click ok
      once it is done, restart the destination server(VM) and boot from the server.
      (generic restore BMR)provide the same IP and make it permeant>contact master server > accept >enter the reissue token
      it will restore all drivers, configuration (system state), registry
      after the restore is over, you must login by local admin first time , so the BMR cleanup happens at netbackup server.(it might fails if you do not do it)

      I hope the above is useful to you.If you have active support, I suggest, you open a ticket and take note of all steps for your future.

       

      Regards,