Dell EMC Avamar for Windows Servers 19.7 User Guide

Restoring over corrupted SIS links

An SIS volume restore may fail because the SIS Groveler service is running and prevents the restore process from correctly restoring some files. In the log file for the restore, the error for the failed restore appears similar to the following example, and the size of the restored file is set to zero:

Error "avtar Error <5737>: I/O error: Unable to write(4) "path to file" (code 38: Reached the end of the file)."

To correct this error, delete the corrupted SIS links from the restored server, and then use Avamar to select and restore the links from the backup set.

Restore of folders or files with many Access Control Entries may fail

Restore of folders or files with 1,820 Access Control Entries ( ACEs ) may fail with one of the following error messages:

• File '%s' is unable to be restored due to Avamar having improper permissions to restore the security information for that file. If you wish to restore the file, either provide proper rights to Avamar or use the --ignoreacls option.

• I/O error: Unable to BackupWrite(4) ...(code 87: The parameter is incorrect).

Perform one of the following steps to resolve this issue:

• Add the --ignoreacls attribute to the Restore Command Line Options dialog box before you restore.
• Remove ACEs from the folders and the files so that there are fewer than 1,820 entries.

A full disk restore operation does not restore ACLs of a root disk

A full disk (disk to disk) restore operation by using the avtar command restores files, folders, and ACLs of files and folders, but not ACLs of a root disk. To restore ACLs of a root disk, specify the --existing-dir-aclrestore=true option in the avtar command. The option resets ACLs of files, folders, and root disk, and then replaces them with new ACLs from a backup.

To restore only ACLs, specify the --restore-acls-only=true and --existing-dir-aclrestore=true options in the avtar command.

Sometimes Office XML files need a special option to correctly restore

If you back up an 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 option in the Restore Command Line Options dialog box. After restore, when you open the file, sometimes you get the same MS Office error message, but if you click OK to open the file anyway, the file should correctly open.