Windows Fileserver - file recover to original location mess the permissions/ownership

[Steppan]

Hi all,

We have a fileserver with 8Tb of deduped data (windows dedup). All files has been backeup last weekend using both Accelerator and Optimized backup for windows deduped volumes turned ON. We just checked the entire partition and let it go. Everything done within 48h. Pretty nice.

When we try to restore some files and folders to their original location it restores nicely but when we try to open the folder it says we don't have permission. I had to re-own that folder and replace all ACLs to make it acessible for the users, what a mess!

Even restoring to alternate location we got this error. If during restore I check the option "restore without access control attributes" it restores and the folder gets accessible but it receives ACLs from it's parent object, losing the purpose to restore it to original location.

The netbackup user we created as service account for everything has high level permissions within the file server (it is in the fileserveradmin adgroup and have write/read permissions on everything).

Tested restore with our legacy Data Protector and the same folder has been restored flawless.

Anyone?

[Thiago_Ribeiro]

Hi,

Please confirm us did you already check this?

About restoring thefiles that have Access Control Lists (ACLs) An Access Control List (ACL) is a table that conveys the access rights users need to a file or directory. Each file or directory can have a security attribute that extends or restricts users’ access. By default, the nbtar (/usr/openv/netbackup/bin/nbtar) restores ACLs along with file and directory data.
However, in some situations the ACLs cannot be restored to the file data, as follows:
■ Where the restore is cross-platform. (Examples: An AIX ACLrestored to a Solaris client or a Windows ACL restored to an HP client.)
■ When a restore utility (tar) other than nbtar is used to restore files. In these instances, NetBackup stores the ACL information in a series of generated files in the root directory using the following naming form: .SeCuRiTy.nnnn
These files can be deleted or can be read and the ACLs regenerated by hand. Note: If performing an alternate restore where the original directory was ACL-enabled, the alternate restore directory must also be ACL-enabled. If the alternate restore directory is not ACL-enabled, the restore is not successful. Restoring files without restoring ACLs The NetBackup client interface on Windows is available to administrators to restore data without restoring the ACLs. Both the destination client and the source of the backup must be Windows systems. To restore files without restoring ACLs, the following conditions must be met:
■ The policy that backed up the client is of policy type MS-Windows.
■ An administrator performs the restore and is logged into a NetBackup server (Windows or UNIX).
The option is set at the server by using the client interface. The option is unavailable on standalone clients (clients that do not contain the NetBackup server software). ■ The destination client and the source of the backup must both be systems running supported Windows OS levels. The option is disabled on UNIX clients. Use the following procedure to restore files without restoring ACLs. To restore files without restoring ACLs
1 Log onto the NetBackup server as administrator.
2 Open the Backup, Archive, and Restore client interface.
3 From the client interface, initiate a restore.
4 Select the files to be restored, then select Actions > Start Restore of Marked Files.
5 In the Restore Marked Files dialog box,place a check in the Restore without access-control attributes check box.
6 Make any other selections for the restore job.
7 ClickStart Restore.

Regards

Thiago