Known Issues

• Apostrophe's are not allowed in file or folder names. See Minimum System Requirements or Managed Folder Settings in the user guide for additional information.
• ESXi Does not have the correct license to support HSR.
• In some isolated situations ImageManager FTP replication jobs are not written to the targeted destination folder. Instead, the replicated files are written to the root folder of the FTP Server. This is more likely to occur if the network connection is temporarily dropped. Arcserve plans on fixing this in a future release.
• ImageManager HSR to VMware vCenter may fail with an "Access Denied" error when it starts processing the HSR Job. This can be caused when VMware vCenter has host machines defined using FQDNs rather than using IP addresses and where the network DNS is not working, or is incorrectly configured. This might occur when a user spins up a new network without their domain controller, and temporarily uses a public DNS option (such as 8.8.8.8). ImageManager tries to get the target VMware host information from vCenter and then tries to write to the matching Datastore. However, the FQDN received from vCenter does not resolve in the local network. ImageManager then fails with an Access Denied error.
• HSR direct to vCenter: -31 Device error (MSVC90 Missing). This can occur in some rare situations if you don't have the Microsoft Visual C++ 2008 Redistributable Package installed on your machine. In this case, there should be a matching error in the Windows Application Event logs. In the unlikely event this problem still exists, you can manually download and install the latest Microsoft C++ runtime files from the Microsoft website.
• HSR to VHDX always results in the use of GPT partitioning style for the volume contained within the VHDX. Keep in mind that some earlier versions of Windows will not boot off a GPT volume and other versions do not support data volumes on a GPT disk.
• New ShadowStream Replication jobs may fail with the error message "Progress is no longer being reported, asking the send to stop" if you enabled UDP Flood Control (or similar) in your firewall. To fix this condition you need to configure your firewall to allow the new ShadowStream UDP traffic to pass through so that the total number of UDP packets sent or received by ShadowStream is not restricted. The ShadowStream Performance Benchmarks and Best Practices white paper provides more information.
• Arcserve recommends that you have a local "My Documents" folder on the machine where you are installing ImageManager. If you see "Unknown error encountered" during installation check to see if the My Documents folder exists. This could happen if a machine is configured so the "My Documents" folder is mapped to a network drive. In this case ImageManager may not be able to access the My Documents folder which could cause the failure. This is especially true if a silent install runs on an account where Windows prevents network access.
• In rare situations, an ImageManager HSR Job may fail with a generic "FFFFFFFF" error. An example error message is shown below:
• Copy

  12-Feb-2015 14:43:11 send error: HSR init - invalid or missing commit file : FFFFFFFF

• This can occur when you have more than one HSR Job to the ESXi Datastores and each job has the same values for [datastore name][virtual machine name][disk name]. For example, if you have multiple Datastores with the default name of "Datastore1", VM name of "Win2012" and disk name of "C:", the resulting .HSR commit files stored in the ImageManager Log folder will be identical. This will lead to failures of each job to access the same commit file.
• In some scenarios you may encounter an error pop-up message when you try to log into ImageManager. The error message includes the text: “The property 'AgentConnections' could not be created”. To work around this problem: 1. Login to ImageManager using a different user name, 2. Logout. 3. Log back in with the user name that originally failed. This will be fixed in a future release.
• Arcserve best practices recommends that you don’t replicate from ImageManager over a VPN connection. Arcserve recommends that you use iFTP or ShadowStream instead.
• If you install ShadowProtect 5.0.4 or 5.2.3 after ImageManager v6.5 or newer is installed on the same system, the ImageManager Startup menu icons and links may disappear. Run an ImageManager Installation Repair to restore the menu icons and links.