Prime Infrastructure 3.3 Restoring Issue

[FABIAN JIMENEZ]

Hi Cisco Community,

I'm currently trying to migrate from a VM PI 3.3 to an physical appliance in the same version. I generated and exported the Virtual Prime backup to an External location (around 19 GB backup file),  after I initiated a restore on the Physical server. But are passed more than 30 hours and the log it's freezed to "Initiating restore.  Please wait...". I tryed to stop the server with "ncs stop" and tryed to initiate a new restoring but appear a message "that its not possible beacuse another backup is in progress".

Both servers are on the same version, and no have device or upgrade patchs. I don´t know what can I do to stop the process, beacuse i wouldn´t like to shutdown the server and put server in "unrecoverable state".

Can anyone help with this please?

[Leo Laohoo]

---

@FABIAN JIMENEZ wrote:

I'm currently trying to migrate from a VM PI 3.3 to an physical appliance in the same version

---

Whao!  From VM to hardware?  Is that wise?  

Raise a TAC Case because they'll need to stop the "backup" process and (forcefully) reload PI.

[FABIAN JIMENEZ · Accepted solution]

Hi Leo

I was refering to migrate the backup from CPI VMWare to the physical UCS server. I would think you understand.

I follow this procedure to restore the backup:

1 Take a new backup form legacy VM Prime

2 Access ssh to new Prime UCS and stop services "ncs stop"

3 From UCS KVM power down the server "Power>Power Cycle System (coold boot)"

4 Login again and run "ncs run reset db"

5 Export backup by ftp to local repository "url disk:/ftp"

6 Start a new restore procedure "restore 'filename'repository localftp application NCS"

7 The restore complete successfully

8 After starting appear the following error:

    ncs status:

   Health Monitor is running, with an error.

   initHealthMonitor(): can not start DB

I applied the following commands:

 ncs stop

 ncs cleanup

 ncs start

9 Checked the services once more time, access GUI with all backed information and verify successfully end of migration on new UCS