NetBackup™ Web UI Cloud Administrator's Guide

Troubleshooting

When you start a subsequent (twice) restore operation on the same VM, an error occurs during a 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 in the following article.

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

If you try to restore files or folders from a partition or a file system that Snapshot Manager does not support, 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:

You can filter any files or folders that Snapshot Manager does not support. In the bp.conf file on the primary server, enable the CP DISKMAP check by setting the following flag.

CP_DISKMAP_CHECK = true/yes

Backup from restore operation is partially successful when disk is full on the selected target directory. The 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 a backup from restore, if a live mount is created successfully, then even if other errors are reported apart from ASSET_NOT_FOUND, it is considered as partial success. If no network devices or a file system are mounted on the target location, or the disk is full, the following messages are displayed in the 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 or the file system must have been mounted on the target path, hence the Snapshot Manager agent considers the free space on the device or file system. As the copy fails with space error, it is logged into the summary report. For example:

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

Workaround:

Partial recovery may be due to the following reasons:

In these partial recovery cases, the created instant access is not deleted and is available for the next 24 hours.

You can configure the instance access retention interval using the CLOUD_VM_IA_RETENTION_INTERVAL_IN_HOURS parameter in the bp.conf file. (Default value is 24 hours.)

Workaround:

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

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

If any one of the disks in the VM is not initialized, download or restore of the VM 's 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 that instant access uses to retrieve files from a VM backup. If a disk is not initialized, libguestfs cannot retrieve the files.

Workaround:

Initialize the disk and back up the VM. Then try again to download or restore the VM files using instant access.

This error occurs when you try granular restore from a snapshot with at least one of the selected files from the boot volume, and the destination volume of restoration being a boot volume.

Workaround:

To restore files and folders from the boot volume or file system, specify a block volume as the target path.

During granular restore from snapshot, this error occurs for VMs that do not have the Oracle Cloud Agent installed, or have the disks attached using the paravirtualized attachment method.

Error in the Activity monitor:

[{'error': 'The selected files/folders were skipped from recovery as the snapshot does not contain the corresponding file system.', 'mount': 'Unknown Mount Point/Drive'}]}}"

Workaround:

Do the following:

This error occurs when the Block Volume Management plug-in for the Oracle Cloud Agent is not enabled on the target VM.

Workaround:

Do the following: