Dell NetWorker 19.9 Administration Guide

Limitations of Block based Backup

The limitations of block based backups are as follows:

• On Linux with udisk package version 1.0.1-2 or earlier installed, block based backups might fail to delete snapshot after backup.
• On Linux, if the load of the volume being backed up is high, then block based backup might fail due to insufficient storage capacity.
• During file level recovery of block based backups, the mount point path where the block based backup save set is mounted is listed when you select the destination path for recovering files.
• When a block based backup recover session is initiated and another user browses the mounted save set using OS tools and if the recover session is closed, then the mounted save set is not unmounted properly due to OS locking mechanism.
• When you try to recover a cloned block based backup save set from a remote client using recover binary with -l option to specify the pool name, the operation fails due to missing clone binary from client package.
• In case of PSS backups of a virtual client, the client parallelism value is picked from the active node and not from the active node client . If the picked value is less than user defined value then it results in backup failure.
• When backing up large number of save sets (exceeding 60 or more) and if PSS is enabled, then it might overload NetWorker server resources due to number of save sessions and the backups might time out.
• You cannot perform an image recovery of block based backup save set to a destination volume that does not have the same disk sector size as the source.
• Block based backup is not supported on Linux UEFI machines when secure boot is enabled.
• While performing block based backup file level recovery from cloned DDCT device; staging to user specified pool using -l option does not work from recover CLI.