cancel
Showing results for 
Search instead for 
Did you mean: 

Backup & ACL

 
SOLVED
Go to solution

Backup & ACL

Is there a way to retain a file's ACL information in a backup/restore operation?

I get the impression that a file's ACL information is not saved during a backup operation and hence during a restore, the ACL info is lost.

Your comments would be greatly appreciated.

Regards,

Petran Bisschops
7 REPLIES
Daniel Fernandez Illan
Trusted Contributor

Re: Backup & ACL

Hi
I had tested backup/restore on files with ACL information and info is not lost.
Saludos.
Daniel.
Volker Halle
Honored Contributor

Re: Backup & ACL

Petran,

using the /INTERCHANGE qualifier would explicitly ask backup to NOT copy/save ACLs.

There was a recent discussion of the behaviour of BACKUP and ACLs in ITRC:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=960236

Volker.
Uwe Zessin
Honored Contributor

Re: Backup & ACL

I think BACKUP 'forgets' to save the ACL of the top-level directory. What I always do is something like this:

$ backup DISK1:[000000]DIR1.DIR;, [DIR1... and so on.
.

Re: Backup & ACL

Hi,

I investigated a bit more...

It was a Top directory so Uwe's comment could apply.

I think that the Restore action did someting that I did not expect - the file extracted from the backup had no acl attached but the directory the file was extracted to, had an ACL that defined that new files should by default get an ACL. However the extracted file did not inherrit te ACL.

If I copy a file to this directory or create a new file in this directory, these files will inherrit the ACL.

So I conclude that backup behaves differently from copy.

However, it still leaves me with the problem that a file with no ACL, that is extracted from a backup into a directory that should by default propagate an ACL, does not do so.

Petran.
Jan van den Ende
Honored Contributor

Re: Backup & ACL

Petran,

BACKUP does NOT retain ACLs, except:
BACKUP/IMAGE (does an exact restore)
and
BACKUP /OWN=ORIGINAL

But, like UWE indicated, this does NOT apply for toplevel directories.

For toplevel directories the best way is to use Uwe's workaround, or, as per John Gillings:

$ BACKUP :[000000...]/OWN=ORIG.

But, in my experience, all too often the construct with [000000...] is also used as INPUT specifier, and now you create a REAL 000000.DIR
The second time around that creates :[000000.000000...] , and now you are in trouble.

All in all, I prefer Uwe's method over John's.

hth

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Jan van den Ende
Honored Contributor
Solution

Re: Backup & ACL

Petran,

your extra info crossed my reply.

To have backup use the OPTION=DEFAULT ACL, you specify

BACKUP /OWN=PARENT

There is some logic involved: by default the process doing the restore becomes the owner, making ACLs potentially conflicting. Now, the parent dir as owner removes this potential conflict, and assosicating the ownership with the parent dir probably implies the wish to copy all of the security. (which is implemented)

Success

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.

Re: Backup & ACL

Dear all,

Thanks for your response.