vmanageDB restore failed

[K.Inaba-MD]

It is an on-premise environment that cannot connect to the Internet.

version
　vmanage: 20.15.1
　vbond: 20.15.1
　vsmart: 20.15.1

I performed a backup and restore of vmanageDB by referring to the following site.
　https://www.cisco.com/c/en/us/support/docs/routers/sd-wan/220305-standalone-vmanage-disaster-recovery.html

I run the following command, but I cannot proceed to the next step.
vmanage# request nms configuration-db restore path /home/admin/202503_configdb.tar.gz
tar (child): /home/admin/202503_configdb.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
Backup vManage version: :
Current vManage version : 20.15.1
Aborting the restore because of version mismatch
vmanage#

The backed up version and the restored version match, but there is no value in the backup version field.
Does anyone know the cause or have experienced something similar?

[Jeongjun Park]

Check whether the file exists at the /home/admin/

tar (child): /home/admin/202503_configdb.tar.gz: Cannot open: No such file or directory

You can check it by using below commands.

vmanage# vshell

vmanage$ ls -al /home/admin

[K.Inaba-MD]

Thank you for your reply. It is as follows.
vmanage:~$ ls -l /ad home/admin/
total 2184
-rw-r--r-- 1 admin admin 2211740 Mar 19 06:42 20250319_configdb.tar.gz
-rw-r--r-- 1 admin admin 566 Mar 27 06:39 archive_id_rsa.pub
-rw------- 1 admin admin 18157 Mar 27 06:59 master_root.crt
vmanage:~$

I realized that the file permissions are 644.

[Jeongjun Park]

Good to hear.

Is it solved after modifying permissions ?

Please remark this as a solution If this is helpful.

[K.Inaba-MD]

I can't check it today, but I'll check it tomorrow or the day after.

[K.Inaba-MD]

I made a mistake with the file name.

[K.Inaba-MD]

The execution results are as follows.

vmanage:~$ ls -al
total 2212
drwxr-x--- 4 admin admin 4096 Apr 2 03:46 .
drwxr-xr-x 14 root root 4096 Mar 27 06:33 ..
-rw------- 1 admin admin 421 Mar 27 07:37 .bash_history
-rw-r--r-- 1 root root 411 Mar 27 06:39 .bashrc
-rwxr-xr-x 1 admin admin 241 Aug 12 2024 .profile
drwx------ 2 admin admin 4096 Mar 27 06:57 .ssh
-rw-r--r-- 1 admin admin 2211740 Mar 19 06:42 20250319_configdb.tar.gz
-rw-r--r-- 1 admin admin 566 Mar 27 06:39 archive_id_rsa.pub
drwx------ 2 admin admin 4096 Apr 2 03:46 bk
-rw------- 1 admin admin 18157 Mar 27 06:59 master_root.crt
vmanage:~$ cp -ip 20250319_configdb.tar.gz bk/20250319_configdb.tar.gz
vmanage:~$ ls -al bk/
total 2168
drwx------ 2 admin admin 4096 Apr 2 03:47 .
drwxr-x--- 4 admin admin 4096 Apr 2 03:46 ..
-rw-r--r-- 1 admin admin 2211740 Mar 19 06:42 20250319_configdb.tar.gz
vmanage:~$ chmod 666 20250319_configdb.tar.gz
vmanage:~$ ls -al
total 2212
drwxr-x--- 4 admin admin 4096 Apr 2 03:46 .
drwxr-xr-x 14 root root 4096 Mar 27 06:33 ..
-rw------- 1 admin admin 421 Mar 27 07:37 .bash_history
-rw-r--r-- 1 root root 411 Mar 27 06:39 .bashrc
-rwxr-xr-x 1 admin admin 241 Aug 12 2024 .profile
drwx------ 2 admin admin 4096 Mar 27 06:57 .ssh
-rw-rw-rw- 1 admin admin 2211740 Mar 19 06:42 20250319_configdb.tar.gz
-rw-r--r-- 1 admin admin 566 Mar 27 06:39 archive_id_rsa.pub
drwx------ 2 admin admin 4096 Apr 2 03:47 bk
-rw------- 1 admin admin 18157 Mar 27 06:59 master_root.crt
vmanage:~$ exit
exit
vmanage# request nms configuration-db restore path /home/admin/202503_configdb.tar.gz
tar (child): /home/admin/202503_configdb.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
Backup vManage version: :
Current vManage version : 20.15.1
Aborting the restore because of version mismatch
vmanage#

It's not completed successfully.

[Jeongjun Park]

Try to enter

vmanage# request nms configuration-db restore path /home/admin/20250319_configdb.tar.gz

[K.Inaba-MD]

The following command completed successfully.

vmanage# request nms configuration-db restore path /home/admin/20250319_configdb.tar.gz
Backup vManage version: : 20.15.1
Current vManage version : 20.15.1
vManage version compatibility check passed, proceeding with database restore.: 20.15.1 and 20.15.1
～
Starting NMS application server on localhost
Waiting for 180s for the instance to start...
Successfully restored database
vmanage#

Unable to re-authenticate the vbond and vsmart. 

[Jeongjun Park]

Hmm

So you've succeed to restore vManage DB now.

To establish control connections, troubleshoot step by step.

Also, vManage reboot may be helpful before any troubleshooting.

[K.Inaba-MD]

After the reboot, I executed the re-authentication of the vbond, but it still failed.

I performed the backup and restore by referencing the following site.
　Recover Standalone vManage by Disaster Recovery - Cisco

I have questions regarding the following.

1.
For Step 2 (Copy Backup Configuration and Root Certificate), should I only copy the root certificate of one vbond, or do I need to copy the certificates of all vbonds?

2.vbond has the following certificates. Which one is correct to copy ?
　master_root.crt
　vbond.crt

vbond-01:~$ ls -l
total 36
-rw-r--r-- 1 admin admin 565 Mar 4 05:07 archive_id_rsa.pub
-rw-r--r-- 1 admin admin 18157 Sep 4 2024 master_root.crt
-rw-r--r-- 1 admin admin 43 Sep 4 2024 root_ca_uuid_list
-rw-r--r-- 1 admin admin 1999 Sep 4 2024 vbond.crt
-rw-r--r-- 1 admin admin 1228 Sep 4 2024 vbond_csr
vbond-01:~$

[Jeongjun Park]

I'm sorry, I cant answer for your questions.

I've never copied the certs into vBond via CLI.

About step 8, Did you do below things ?

1. Navigate to Configuration > Devices > Controllers

2. Click "Edit" for vBond.

3. Fill the parameters.

4. Check whether vBond cert is signed automatically or not after 3.