User guide

54 EMC Avamar 7.0 Release Notes
Known problems and limitations
Avamar Data Store Gen4
The following table lists known problems for Avamar Data Store Gen4.
N/A Proxy upgrades
Due to differences in the virtual machine operating systems, you cannot upgrade 6.1
proxies to version 7.0 or later. If you require version 7.0 or later functionality, you must
deploy new 7.0 proxies. If you need to upgrade a 6.1 proxy to a later version 6.1
software, use the instructions in the
EMC Avamar 6.1 for VMware Guide .
N/A Backup of .vmx and nvram files might fail because the ESX server has an exclusive lock
When using vCenter 4.1 U1 or earlier, backups of .vmx and nvram files might fail
because the ESX server maintains an exclusive lock on these files. If the vCenter
attempts to use an ESX server other than the one that has the exclusive lock on the file
to back up the files, then the server without the lock cannot read the .vmx and nvram
files to back them up. This issue is fixed in vCenter 4.1 U2.
To work around this issue, add the --x22=8192 option to the dataset for scheduled
group backups, or to the Backup Command Line Options dialog box for on-demand
backups. This allows the backup to complete even if the .vmx file is not backed up.
Because the .vmx file contains the VM configuration information, when restoring the
backup, you can select Restore to original virtual machine or Restore to existing virtual
machine, but you cannot select Restore to a new virtual machine. To restore to a new
virtual machine, you must manually create a VM with the same configuration as the
original VM, then use the Restore to existing virtual machine option to restore the
backup to the newly created VM. Restoring to a manually created VM issues new virtual
NIC MAC addresses and new virtual disk serial numbers, which may cause license
activation issues with VMs running Windows.
Table 26 Avamar with VMware known problems (page 2 of 2)
ID Description
Table 27 Avamar Data Store Gen4 known problems
ID Description
N/A Limitations when rerunning dpnnetutil
You cannot add or change replication and management parameters when rerunning
dpnnetutil on ADS Gen4 systems.
If you rerun dpnnetutil, the following prompt appears: Use existing
dpnnetutil configuration file? If you click Yes (the proper response), then
management and replication prompts are excluded in successive screens.
To work around this issue, delete the probe.xml file in the
/usr/local/avamar/var directory before you rerun dpnnetutil.
N/A Changing subnets is not allowed on single-node servers
You cannot use dpnnetutil to change subnets in a postinstallation single-node
server environment. The dpnnetutil utility initially allows you to change the subnet
IP address, but an error message appears later that directs you to return the
configuration to its original state. To work around this issue:
•Run a nodedb update if command in the following form:
nodedb update if --addr=old_ip_address --new-addr=new_ip_address
--new-nwgrp=network_id
• Manually update the configurations of network interfaces, such as
/etc/sysconfig/network/ifcfg-eth0.
• Manually edit the contents of /etc/hosts.
• Update the configurations of the Avamar subsystems (that is, gsan, mcs, ems).