Backup Related

• When you apply the Backup Failure filter under Protection Failure on the All Nodes page, the status of backup job shows as incomplete even though the backup job gets completed successfully with warnings, and gets listed under the Backup Failure category. However, you can restore the backed-up data safely and securely.
• After upgrading to Windows 10 or installing Microsoft updates such as Threshold Update or Creator Update on Windows 10, the system removes the tracing driver upper filter of volumes and converts the first job to a verify backup. At the same time, Arcserve UDP installs the BLI driver automatically and remaining jobs will run as incremental jobs.

• Backup, restore, or BMR collection fails when operating COM-based components such as VSS, VDS. Event ID 10006, 1503, or 6287 may display in the Windows Event log.
• Symptom
• The following message is found in the event log:
• Illegal operation attempted on a registry key that has been marked for deletion or Windows detected your registry file is still in use by other applications or services. The file is unloaded now. The applications or services that hold your registry file may not function properly afterwards.
• Solution
• For cause and solution, see the Microsoft KB article 2287297.
• Mounting a volume fails and the following error message appears:
• Failed to mount recovery point to path: "Z:"iu. Incorrect function.
• Symptom
• Mounting the session to a driver letter fails.
• When the destination is a local folder and on a FAT32 volume, mounting a driver only supports creating the cache file on NTFS volume.
• Solution
• Add a new registry key and customize the cache file path to a different volume.
• Follow these steps:
  1. Create the AFStorHBAMgmt key on HKEY_LOCAL_MACHINE\SOFTWARE\Arcserve\Unified Data Protection\Engine.
  2. Create the string value CacheFilePath.
• More Information:
• The cache file is created by mounting a driver when a writable volume is mounted. For Granular Restore and Catalog Restore job, a writable volume is created. If the session is to back up volumes on Windows 8, Windows 2012, or a later operating system, always mount a writable volume when you mount a session to a driver letter.
• When you submit a backup job from the Arcserve UDP Agent (Windows) UI, the backup job may not launch when the backup destination is using a data store on a Recovery Point Server.
• Symptom
• The backup job submitted appears successful. But, in the Arcserve UDP Agent (Windows) UI, you cannot see any job monitor because the backup job meets the maximum concurrent node count setting in the data store. The backup job is placed into the waiting queue.
• Solution
• Open the Arcserve UDP Console and the pending job monitor appears on the node view.
• If the Arcserve UDP Agent (Windows) machine is rebooted when a backup job is running, the job is marked as crashed on the Arcserve UDP Agent (Windows) home page. But, the Arcserve UDP Console displays no job history for the job, because the job history item is sent to the Arcserve UDP Console at the end of the job.
• Note: After reboot, the job history is not sent from the Agent to the server.
• Compression percentage of the host-based agentless verify backup jobs appear incorrect in the job monitor.
• Symptom
• When a host-based agentless verify backup job is running and compression is enabled in the plan, the compression percentage displayed on the job monitor is higher than the actual percentage.
• Solution
• The compression percentage printed in the activity log appears correct after the host-based agentless Verify backup job is completed.
• Note: All other backup jobs, including Agent backup jobs and Host-based Agentless Full/Incremental backup jobs, do not display this problem.
• VMware VM backup job finishes successfully but dump file is generated.
• Symptom
• The backup job of VMware VM finishes successfully on the Arcserve UDP Console. The job is marked using the green icon and the following message appears in the activity log:
• Backup job completed successfully
• However, the backend process dump file, such as AFBackend.exe.7912.00.dmp is generated in the BIN folder of the agent installation path.
• For example: C:\Program Files\Arcserve\Unified Data Protection\Engine\BIN.
• Solution
• The VDDK crashes occasionally when Arcserve UDP is closing API calls to VDDK. You can ignore, as this problem happens at the last phase of the backup job. By that time, the backup job is almost complete and recovery point is wrapped up successfully.
• During backup, some specific volumes are skipped.

Symptom

• The backup job skips some volumes that do not host the data store or contain path for the data store and Arcserve UDP Console displays a warning in the activity log.
• Solution
• Verify the partition attribute and update correctly.
• The Backup job fails repeatedly.
• Symptom
• If the BLI driver is not monitoring the volume that is included in the backup job, then the backup job fails to fetch the block size for the volume and the following error is displayed in the backup log:
• CMultiBitmapManager::AFDeviceIoControl::CAFLTCTL_GET_BLOCK_SIZE failed, mserr=1.
• CVolumeChangedBitmapFromVolumeDriver::OpenVolume::CAVOLCTL_GET_BLOCK_SIZE failed, mserr=1
• Solution
• As a workaround, use one of the following solution(s):
• Solution1:
• From backup configuration, exclude the specific volume that is not monitored.
• Solution2:
• Run the following command in the command prompt:
• <C:\Program Files\Arcserve\Unified Data Protection\Engine\BIN\DRIVER\Afflt.exe> -e -volumeid="\\?\{VolumeGuid}" -output=<log File Path>
• Note: In the above command, you need to enter the VolumeGuid and log File Path details of the volume that is not monitored.
• For example,
• <C:\Program Files\Arcserve\Unified Data Protection\Engine\BIN\DRIVER\Afflt.exe> -e -volumeid="\\?\Volume{125024c1-0000-0000-0000-40c4e8000000}\" -output="c:\afflt.log"
• After changing the proxy in the backup task, the backup job does not start.
• Symptom
• When you change the backup proxy for Host-Based Agentless/File on UNC or NFS path/Office 365 Exchange Online/ Office 365 SharePoint Online/Office 365 OneDrive backup task without changing the backup destination, the backup job can't be triggered. The activity log contains information that the backup task failed to start backup for the node.
• The reason for backup failure is because the nodes are not registered to the new proxy.
• Solution
• Re-deploy the plan from Console.