NetBackup™ Web UI Cloud Administrator's Guide

Troubleshooting

When you trigger a subsequent (twice) restore operation on the same VM, an error occurs during restore operation. This error causes the following issues:

Workaround:

Check if the ssh daemon is running on the system. If not, then perform the steps that are mentioned in the the following document provided by Microsoft:

learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-ssh-connection

If you try to restore files or folders from partition or file system that are not supported by Snapshot Manager, then you get the following error in the restore job.

Error nbcs (pid=<processs id>) Failed to restore file(s) and folder(s) from snapshot for asset <asset name>

Workaround:

If you want to avoid listing files or folder while browsing for single file restore, which are not supported by Snapshot Manager, then enable CP DISKMAP check by setting below flag in bp.conf file of NetBackup master server.

CP_DISKMAP_CHECK = true/yes

Backup from restore operation is partially successful when disk is full on the selected target directory. Following messages are displayed:

Dec 29, 2022 2:57:51 PM - Info nbcs (pid=2244) Granular restore(SFR) is completed
    Dec 29, 2022 2:57:51 PM - Info nbcs (pid=2244) Summary of SFR Operation - Success files/folders count: 0 , 
    Failed files/folders count: 1 , Warning files/folders 
    count: 0, Skipped files/folders count: 0
    Dec 29, 2022 2:57:51 PM - Info nbcs (pid=2244) 
    Detailed restore summary report is available on recovery target host at location: 
    /var/log/flexsnap/restore/granular-restore-09b4d44d
    .
    .
    Dec 29, 2022 2:57:51 PM - Warning bprd (pid=1977) Granular Restore from backup completed with error. 
    Copy the files manually from live access mount: 
    ip-10-239-185-241:/mnt/vpfs_shares/vmfiles/8fcc/8fcc132b-a202-49a8-b654-81ff242a718a/livemount
    Dec 29, 2022 2:57:51 PM - end Restore; elapsed time 0:01:51
    the requested operation was partially successful(1)

For backup from restore if live mount is created successfully then even though there is other error reported apart from ASSET_NOT_FOUND, its considered as partial success. If there is no network devices/filesystem mounted on target location and disk is full then below messages can be seen in job details:

 Jan 02, 2023 12:11:16 AM - Error nbcs (pid=13934) 
187776K space required for file/folder restore while 20K is total available space on /disk1

In this case other network devices/file system must have been mounted on the target path, hence Snapshot Manager agent considers the free space on device/file system. But once it tries to copy the file it fails with space error logged into summary report. For example,

 /var/log/flexsnap/restore/granular-restore-09b4d44d in above Job details log

Workaround:

Partial recovery could be due to the following reasons:

In such partial recovery cases, the created instance access will not be deleted and will be available for next 24 hours.

The instance access retention interval is configurable by setting CLOUD_VM_IA_RETENTION_INTERVAL_IN_HOURS key in bp.conf file. (Default value is 24hrs).

Workaround:

User can perform manual steps to access the Instant access share on target host and then manfully copy the required files/folders.

Error nbcs (pid=44859) Target VM not found, asset_id <asset_id>

If one of VM's disks is not initialized, downloading or restoring VM files using Instant access fails with the following error:

Jan 24, 2023 11:58:47 AM - Error NBWMC (pid=3716) Internal Error: ('failed to find operation system information, please check the source VM', ('Failed to expose 
VMDK', 1006), None)
Failed to create the instant access mount.
(4001)

Libguestfs is a third party tool used by Instant access to retrieve files from VM backup. If a disk is not initialized, libguestfs will not be able to handle it.

Workaround:

Initialize the disk, backup the VM and try to download or restore VM files using Instant access again.