User guide

Known problems and limitations
EMC Avamar 7.0 Release Notes 39
Microsoft Windows client
The following table lists known problems for this release of the Avamar Client for
Windows.
Table 10 Windows backup client known problems (page 1 of 2)
ID Description
26326 Hard links are not preserved by default
To successfully back up and restore hard links on Windows clients, add the
--x18=1048576 option to the dataset for scheduled group backups or to the Backup
Command Line Options dialog box for on-demand backups. You should also always
back up and restore the hardlink file and target file together.
26348 Restoring a large number of SIS links may be very slow
When restoring a large number of Single-instance Storage (SIS) link files, SIS
architecture reports that for every SIS link, the corresponding common store file must
be restored. This may result in the common store file needing to be restored multiple
times for each SIS link and therefore may result in a longer restore time.
26802 Corrupted Office XML files may need special flag to restore correctly
If you back up a corrupted Office XML file (.docx, .xlsx), then an error message
similar to the following may appear when you restore the file and open it:
Excel cannot open the file 'Spreadsheet.xlsx' because the file format
or file extension is not valid...
or
The Office Open XML file filename.docx cannot be opened because there
are problems with the contents, Word found unreadable content in
documentfile.docx. Do you want to recover the contents of this
document? If you trust the source, click Yes.
If you open the file anyway, the file may be empty or unusable. When this occurs, rerun
the restore using the --deflateofficexml=false flag in the Restore Command
Line Options dialog box. After restore, when you open the corrupted file you may get
the same Office error message, but if you click OK to open the file anyway, the file
should open correctly.
54642 Unable to ping DNS addresses in a mixed IPv4/IPv4 environment when Bare Metal
Recover wizard is used to configure the addresses
When using the Bare Metal Recover wizard to configure a system with two NICs, one
using IPv4 and the other using IPv6, the DNS addresses are unpingable. The interim
solution to this problem is to disable the NIC that is on the IPv4 network, using the
following commend:
netsh interface set interface "Ethernet 2" disable
N/A Interaction with Samba mounts
Restores of network mounted drives across Samba to UNIX might not result in the
proper file user and group permissions.
N/A Incompatibility with Venturi Wireless client
If the SSL encryption option is enabled when you back up Windows clients, then the
backup sporadically fails with older versions of the Venturi Wireless client. To resolve
the incompatibility, upgrade the Venturi Wireless client to version 3.1.4 or later.