This section contains the following topics:
Browsing Volume Related under Arcserve UDP View
Arcserve UDP Installation Related
Symptom
Create an Instant VM in Hyper-V Cluster environment. But after completing live migration of Instant VM to other Hyper-V node, the Instant VM cannot work.
Solution
Move the Instant VM to other storage before live migrating to other Hyper-V node in the cluster. Moving the Instant VM to other storage copies all the data from recovery point to the current virtual machine and makes it permanent.
If you create an Instant VM to Hyper-V and protect it as a VM node by Host-Based Agentless plan, then creating a Virtual Standby VM or Instant VM for such a node will fail.
Solution
As a workaround, you can use either of the following solutions:
If a node is previously protected by using shared folder as backup destination in Arcserve UDP v5, after upgrading Arcserve UDP from version 5 to version 6, the recovery point is not listed out in step 1 of creating an Instant VM.
Solution
As a workaround, modify and save the plan which protects the node. After the plan deployment is completed, try to create an Instant VM again.
The Instant VM on VMware failed to boot up and enter to the EFI environment if the source node is a Windows 2008 server and boots from the EFI system.
Solution
Add a Windows boot entry into the EFI environment manually:
Follow these steps:
The Windows boots up successfully from the Windows Boot Manager option.
Browsing volumes with Arcserve UDP View takes long time and the mounting volume fails, if the data store is deduplication data store and the Arcserve UDP Data Store Management Service is not started.
Solution
First, start the Arcserve UDP Data Store Management Service and then browse the volume.
After fresh installation of Arcserve UDP Agent for Windows without running any backup or restore job, browsing volumes with Arcserve UDP View fails.
Solution
Before browsing the volume, perform one of the following options:
Arcserve UDP console installation fails displaying error code 1603 in setup logs.
Solution
This installation issue occurs when any characters (< > & |) are part of the Windows PATH variable.
Remove the characters temporarily from the Windows path variable and add them back after the successful installation of Arcserve UDP console.
Symptom
When IPv6 is enabled on one or more network interfaces in a Windows backup proxy machine, UDP VMware VM backup can fail or crash while attempting to open a disk with the proxy.
Solution
The cause is a stack buffer overrun in one of the VDDK modules libcurl.dll when trying to enumerate DNS servers having multiple IPv6 network interfaces. Although IPv6 is enabled in all versions of Windows 8 and Windows Server 2012, the only known workaround is to disable IPv6 on the backup proxy's network interfaces.
For more information, refer to the link.
Symptom
The registry BLI upper filter of volume class is removed. As a result, the BLI driver cannot monitor volumes.
Solution
You can continue to perform an Incremental backup after reinstalling the Change Tracking Driver.
Follow these steps:
<installation path>\Arcserve\Unified Data Protection\Engine\BIN\DRIVER
<installation path>\Arcserve\Unified Data Protection\Engine\BIN\DRIVER
Symptom
Enable the BitLocker for some volumes, if the related volume is in the backup setting. After restarting the machine, the next backup job changes to verify backup job.
Solution
For non-Windows 2012/ 2012R2:
For Windows 2012/ 2012R2, it’s known issue.
Symptom
Some of the backup job may fail to use the hardware snapshot and return to software snapshot in the host-based agentless backup plan for Hyper-v VMs. This may happen as you check the options Backup each VM individually using a separate snapshot and use NetApp hardware snapshot with transportable option enabled.
Solution
This issue occurs when there are more than one Hyper-V VM in the plan and backups are run as per the schedule. As a workaround, you can modify the host-based agentless plan and uncheck the option “Backup each VM individually using a separate snapshot”.
Note: This solution is applicable only to Microsoft Hyper-V.
Symptom
Nimble hardware snapshot creation fails for agent-based backups and Hyper-V VMs host-based agentless backups.
Solution
When using the Nimble hardware snapshot, ensure the following:
If the backup job contains greater or lesser volume than the volume collection, then the nimble hardware snapshot creation fails and returns to software snapshot.
Symptom
The following list of OpenSSL binaries are redistributable binaries from NetApp and face security vulnerabilities:
libeay32.dll
ssleay32.dll
These binaries are part of the following folders:
Solution
These binaries are of version 1.0.2a. These binaries are being used when the user creates a host based agentless plan, the protected nodes are VMware VMs and the Snapshot type as backup is hardware snapshot.
Refer to the site https://www.openssl.org/ for more details on security vulnerabilities.
Symptom
"Failed to Stop Service" error is coming in the log when SQlServerWriter(Sql 2016 RC2) is restored.
Solution
No action required. It should stop and start the service successfully and error should not be displayed in the log.
Symptom
While using the Arcserve UDP WAN Gateway to add and connect remote sites behind NAT, the Installation Report page of the UDP Gateway setup still includes the old link for the Arcserve UDP Agent for Linux in version 6.0 (February 2016) instead of the new link for Update 1 (May 2016).
Solution
If using the WAN gateway, ignore these links at the end of the Gateway setup, and instead use the following download URLs for the Linux Agent.
Symptom
Unable to add or update a node when the Collect UDP Dashboard information for Arcserve Backup jobs option is enabled with caroot authentication.
Solution
Use Windows authentication.
|
Copyright © 2016
|
|