Limitations

Limitations

The following categories displays respective limitations known to exist in this release:

Arcserve UDP Exchange Granular Restore (AEGR) Utility Related

• The current version of the AEGR Utility has the following limitations:
  • While processing dirty shutdown, database storages may not be restored to the topical condition.
  • Messages in the Outbox folder are not restored if they are not synchronized with the server.
  • Simultaneous recoveries are not supported.
  • Simultaneous running of more than one instance of the product is not supported.
    • In Arcserve UDP Version 6.0, the embedded AEGR Utility is installed in the Agent folder, which is different than the previous standalone version installation path. If you install the standalone AEGR utility after installing Arcserve UDP Version 6.0, the shortcut of AEGR utility points to the newly installed standalone AEGR utility installation path.
  • Encrypted emails are not restored.
  • Messages larger than 64MB are not supported.
  • Windows 2000, 98, ME, and 95 are not supported.
  • Recovery of delivery receipts and non delivery reports is not supported.
  • The AEGR Utility does not support the Run as different user mode.
• Search limitations:
  • Using wildcards at the beginning of a word in search is not supported.
  • The Date range search does not function in the Japanese version.
  • Limitations for search in a double-byte language:
    • The search feature does not function when the message body is searched.
    • Asterisk and Question Mark are not supported in a double byte language search and in the Extended search mode.
    • The search feature does not function when the attachment name or attachment content is searched.
  • Limitation and boundaries for optimal recovery and search:
    • Usage of AEGR Utility is optimal for datasets that do not exceed:
    • Database size: 2TB
    • Mailbox size: 100GB
    • Number of messages in the database: 2,000,000
    • Number of mailboxes in the database: 2,000
    • Number of messages in one mailbox: 100,000
  • Limitations for search in attachments content:
    • Search in attachments does not work for:

      Text contained in embedded OLE objects, WordArt, smart objects, charts, documents metadata (author, comments, tags, and others)

      Marker symbols in lists (numbered or bulleted)

      Text in a header/footer

      XLS/XLSX: number values

• Injection limitations
  • Archived mailboxes (and items from such mailboxes) are not exported to a live Exchange Server.
  • Photos of contacts are not exported to original live mailbox in Exchange Server 2007.
  • Emails with embedded images are displayed with an attachments icon after exporting to a live Exchange Server 2007.
  • Creation time and modified time are not restored.
  • Attached items inside attached messages are not restored to a live Exchange Server 2007.
  • Cross-domain export into original mailbox is not supported.
  • Contact groups and meeting requests cannot be exported to a live Exchange Server 2007 instances. Use export through PST for such items.
  • Missing sent date is exported as current date/time to a live Exchange Server.
  • Mailboxes cannot be created from AEGR, that is automatically at restore time. To restore a mailbox, an empty mailbox must be created in advance using the standard Exchange Server administration tools. In existing mailboxes folders and individual messages can be created without any additional administrative actions.
  • It is possible to rename/delete folders in the attached mailbox only within one program session.

Arcserve UDP Agent (Linux) Related

• When managing Arcserve UDP Agent (Linux) using the Arcserve UDP user interface, the following tasks are not supported:
  • Exclude volumes for individual nodes.

    Note: You can use global volume filters which apply to all nodes in a plan.

  • Simple backup schedule.

    Note: You can use advanced backup schedule.

  • Discover a node using a script.
  • Backup storage management and alerts.
  • Recovery set management on the backup server side.

    Note: You can still use recovery set management on the client side.

  • Command line d2djob --delete and d2djob --export.
• LVM (Logical Volume Manager) is not supported on SUSE Linux Enterprise Server (SLES) 10, but is supported on SLES 10 SP1 to SP4.
• The backup of instant VM/BMR is not supported when the auto recovery is not finished.

  If a backup job similar to this scenario is submitted, the job fails and does not report correct activity log with a message like The Linux kernel version is not supported.

• The RPS Jumpstart job does not support migrating data from CIFS or NFS to a data store. The Browse Linux Backup folder in the RPS Jumpstart wizard does not display any nodes or recovery points.

Backup Related

• File Backup Limitations:

  X64 - up to 370 million files

  X86 - up to 110 million files

  Note: For X86 users, if you have more than 110 million files to back up, use an X64 computer. For an alternate option, refer to the topic Catalog Job fails when backing up a large number of files on Windows 2003 X86 machine in the Arcserve UDP Agent for Windows User Guide v6.0.

• If the Arcserve UDP Agent (Windows) could not resolve the hostname of the Arcserve UDP Console server or the RPS server, or the RPS server could not resolve the hostname of the Arcserve UDP Consoler server, the backup job could not be submitted. The workaround is to configure the DNS server or add entries in the hosts file to verify the hostname could be resolved correctly.

Copy Recovery Point Related

Copy recovery point does not support copy to a data store with or without deduplication enabled. You can only copy a recovery point to a local/share folder.

BMR Related

If you are attempting to perform a BMR on a Generation 2 VM of Hyper-V 2012 r2 Server, create the BMR ISO using Windows ADK 8.1. Using Windows ADK 8 or Windows AIK to create the BMR ISO causes failure to accept input or failure for the BMR to start.

Copy to Tape Related

Arcserve Backup RAID group is not supported as the Copy to Tape destination.

Console Related

• Arcserve UDP cannot be installed on a server that has a non-English hostname.
• The Recent Events panel in the Arcserve UDP Console is not automatically refreshed after jobs are completed; the panel must be manually refreshed.

Dashboard Related

• Dashboard supports grouping jobs in a specified category and displaying detailed job information for all kinds of jobs except for a BMR job.
• The destination information which displays in the dashboard job detail table indicates the destination of the corresponding tasks which are configured in the plan at the time the job is being executed.
• For on demand jobs that are manually submitted from the Arcserve UDP Agent (Windows) user interface, for example, restore job, copy recovery point job, the corresponding plan name is displayed as N/A in the Dashboard. The job destination information is not shown in the Dashboard detail information pane. However, the job destination information for on demand catalog jobs are displayed in the Dashboard detail information pane under certain conditions.

Data Store Related

When deleting an unknown data store and adding it again, the UI displays the following message:

This name is already being used by another data store on the server. Please specify a different data store name.

File Attribute Related

The Arcserve UDP Agent (Windows) requires the file attribute "system" to convert the backup destination folder to the Arcserve UDP Recovery Point View. However, on some NAS filers, the file attribute "system" is not supported, therefore you cannot change the destination to the Arcserve UDP Recovery Point View.

Hardware Snapshot Related

If a Hyper-V server is not the active owner of the CSV volume, then the residues snapshots cannot be deleted using the SDCLI command line. This is a limitation of Netapp.

High Availability Related

Do not use multiple Arcserve UDP user interfaces to manage the same Arcserve Replication and High Availability control service. It will cause reports to be missing.

Host-Based VM Backup Related

• A VMware virtual machine backup fails when you add the virtual machine to the Console using HTTP. The reason is that Arcserve UDP Version 6.0 includes VMware Virtual Disk Development Kit (VDDK) 6.0 that does not support HTTP. (Refer the SSL certificate and thumbprint checking now mandatory section in VDDK 6.0 release notes.)

  If you have to use HTTP for any reason, download the latest version of VDDK 5.5.x and replace VDDK 6.0. For more information, see the Solutions Guide.

• For application granular level restore from recovery points backed up from Hyper-V VMs, only database file dump is supported. The other options such as Restore to original location, Restore to recovery database, and Restore to alternative location are not supported.
• When running multiple VMware backups simultaneously with transport mode as HOTADD, the backup job crashes. To resolve this issue, specify NBD or NBDSSL as the transport mode.
• When importing a VM from VCenter 5.5, and you select "HTTP" protocol to connect the VCenter, the VM infrastructure tree does not display any nodes.
• Restoring a Hyper-V virtual machine to an earlier version of the target Hyper-V server is not officially supported. Nevertheless, you can still continue to restore it. However, it is not guaranteed that the restored virtual machine will have full functionality due to the Hyper-V server compatibility.
• Anytime the hypervisor of the VM changes for either of the following reasons, if Arcserve UDP has the new hypervisor connection information already, the VM will be detected under the new hypervisor after the Update VM information is triggered.
  • The VM is moved to a different hypervisor (and retained VM Instance UUID).
  • The hypervisor hostname/IP is changed.

  Once that happens, you will have to redeploy the plan to the VM to continue backups.

• For a Host-based agentless backup of a Hyper-V VM with replication enabled:
  • The Host-based agentless backup supports backing up the VM from the Master (primary) site.
  • The Host-based agentless backup from the Replica site does not confirm data consistency and accuracy, and the completion of the backup job.
• After upgrading to Arcserve UDP Version 6.0, the first Hyper-V VM backup includes the full content of the disk (even if it is an Incremental Backup). The log may display the following message:

  The Change Block Tracking (CBT) feature has been upgraded. As a result, redundant data may be backed up.

• The following limitation is from Hyper-V, and not from Arcserve UDP. From Windows 2012 r2 onwards, there is a new feature of Hyper-V named shared VHD, The feature allows you to share the VHD(X) file among multiple VMs. (For more information about this feature, see this blog.) However, Hyper-V VSS Writer does not support this new feature. As a result, a Hyper-V agentless backup of VM containing the shared VHD feature will fail. To back up such VMs, perform an agent-based backup by installing Arcserve UDP Agent (Windows) on the VM.
• Arcserve UDP does not support the backup and restore operations of Hyper-V agentless VMs using SR-IOV.
• Host-based agentless backup does not support vCenter servers using VMware Linked mode. To protect VMs which reside in vCenter server instances in Linked Mode groups, add each VM individually from the vCenter server.
• VM recovery job may fail when the VM is backed up from a higher version ESX and restored to a lower version directly (not through vCenter). For example, you backup from ESXi 6.0 and restore to a lower version of ESXi, such as ESXi 5.5.

  Symptom

  If the VM is backed up from a higher version ESXi (like ESXi 6.0), when restoring it to a lower version ESXi (like ESXi 5.5) directly (not through vCenter), the VM recovery job may fail displaying the following error message:

  VM recovery job was unable to create the new virtual machine. The ESX/vCenter Server system reported the following error: com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Unexpected element tag "uptCompatibilityEnabled" seenwhile parsing serialized DataObject of type vim.vm.device.VirtualE1000 at line 1, column 5452while parsing property "device" of static type VirtualDevice

  Solution

  This is caused by compatibility problem of the VM created in different versions of ESXi. The VM property is introduced in the higher version ESXi but not supported by lower version ESXi. You can use one of the following workarounds:

  • Before backup remove the device which has the unsupported property. or
  • Restore the VM through vCenter which has the same version of ESXi (For example, in the above scenario use vCenter 6.0).
  • Manually create the VM on lower version of ESXi and restore the VM by BMR. This option is applicable only to VM with Windows Guest OS.

Restore Related

• The path addresses cannot be restored if the length of path is more than 514 characters.
• Do not restore small files (file size smaller than 100 bytes) from a recovery point to those special partitioned volumes, which are using cluster size equal to or bigger than 32KB. This limitation applies only to a recovery point, which has catalog generated.

  Note: This limitation does not apply when restoring files from a recovery point which has no catalog generated.

• The following limitation exists for catalog-less sessions:

  For some file attributes, if the restore destination is not supported, the restore job will fail. For example, some files have a security attribute, but only Windows NTFS is supported. If you restore it into a SAN, the restore job will fail.

• Restoring EFS (Encrypting File System) files to an alternate location fails with error "Access is denied".

  For catalog-less restores, you cannot restore EFS files, which is a limitation of the EFS feature.

  For more information see, the Microsoft Article 700811.

Virtual Standby Related

• In VMware ESX Server environments that are configured in a storage area network (SAN), the application copies only the first, full backup session to the ESX Server system using the SAN. For all subsequent full and incremental backups, the application copies the converted backup sessions using the LAN. The application behaves in this manner due to a VMware limitation. For more information, see the VMware website.
• Due to a VMware limitation, virtual standby cannot create virtual machines on ESXi Server systems using a free license. To create virtual machines, a purchased license is required.
• Due to a known VMware limitation, errors in the Activity Log appear in English when the Location is set to a non-English locale.
• Due to a Hyper-V limitation which does not support a virtual machine that uses the Unified Extensible Firmware Interface (UEFI), virtual standby cannot support the UEFI system. Therefore when you deploy a virtual standby task whose standby destination is Hyper-V server to a UEFI system, deployment fails. This is applicable when the Hyper-V server is 2008, 2008 r2 or 2012.

  If the destination Hyper-V server is 2012 r2 and the source node is a UEFI system, and is one of the following operating systems, it will be supported:

  • Windows Server 2012
  • Windows Server 2012 R2
  • 64-bit versions of Windows 8
  • 64-bit versions of Windows 8.1

Miscellaneous

• The interactions between the scenario properties are implemented (such as the rewind option with scheduled bookmarks). You can set the relative properties manually.
• Editing root directories of the full system Linux scenario is not supported.
• The Arcserve UDP solution does not support the Arcserve UDP Agent (Windows) integration scenario and the host-based VM backup integration scenario created from Arcserve Replication and High Availability.
• When the Arcserve UDP Server, Agent, or Recovery Point Server is running on machines with Intel 82574L network adapter or E1000e vNIC in virtual machines from VMware, the TCP Segmentation Offload (TSO) will be disabled when starting the Arcserve UDP Agent Service. This is because a data corruption problem may occur on such environments when TSO is enabled. You can also manually disable TSO or replace with another kind of network adapter to avoid this problem.

  For more information about this problem, see "Errata 17 - Tx Data Corruption When Using TCP Segmentation Offload" in the following Intel document:

  Intel 82574 Family Gigabit Ethernet Controller Specification Update

• Considering that there might be hundreds of data stores that are managed and used simultaneously on the same Arcserve UDP Console, the center pane of the RPS node page is refreshed every 15 minutes. The delay is to avoid high load while refreshing. Therefore, the most recent usage statistics values for the data stores might be delayed by 15 minutes.