copying data with rights and protection intact accross remote nodes?

[Uwe Zessin]

Most of what BACKUP does (ownership, protection, ACL), but the ACL (Access Control List), which is part of the file header, stores the binary information of an identifier while RIGHTSLIST.DAT stores the name-to-value mapping.

[Clayton_12]

IS the qualifier /by_owner the one that captures and restores the file and directory protection, owner, and ACL information?

Thx
Clayton

[Uwe Zessin]

Ownership and protection are always saved. /BY_OWNER can be used as an input qualifier to select a sub-set of files to be saved.

/BY_OWNER as an output qualifier is a silly name (IMO), because it changes the ownership of all files created.

I say silly, because, prior to VAX/VMS V5.0 we had the /OWNER qualifier with the same functionality.

[Ian Miller.]

" IS the qualifier /by_owner the one that captures and restores the file and directory protection, owner, and ACL information? "

No /BY_OWNER is a file selection qualifier.

Backup always preserves the security info in the backup saveset.

[Clayton_12]

Thx for responses.

Does the security permissions automatically restore or is there a switch or qualifier that will do it?

[Uwe Zessin]

Use /BY_OWNER=ORIGINAL as an output qualifier.

[Clayton_12]

everthing is looking good except there is
One little quirk!

I backup from the 6.2 system:

backup /verify /record /ignore=(interlock) device:[*...] userdata:[username]file.bck /saveset

I copy the file to the 8.2 system then restore the data:

device:[backups]file.bck.bck/saveset device:[newdir...] /by_owner=original

All the files and and directories retain there ownership and the ACLS
EXCEPT!
All the directories at the root of newdir.
All device:[newdir.*] retain ownership but not the ACLS. All device[newdir.*.*] do have ACLs retained, all files have ACLs retained?


ANy ideas?

[Uwe Zessin · Accepted solution]

Right, that's a problem with BACKUP - use:

$ backup disk:[000000]dir1.DIR;1,[dir1...]*.*;* -
saveset.bck/SAVE_SET

or something like this.

[Clayton_12]

The way I see it now , the best solution is to first backup the root directory into one saveset , restore without [...] output specification

And then restore data saveset with the [...]
output specification:



backup /verify /record /ignore=(interlock) device:[000000]*.dir userdata:[username]rootdirfile.bck /saveset
backup /verify /record /ignore=(interlock) device:[*...] userdata:[username]file.bck /saveset

I copy the file to the 8.2 system then restore the data:


then first restore the root tree structure:
device:[backups]rootdirfile.bck.bck/saveset device:[newdir] /by_owner=original

This gives the root directories with ACLS

then restore all files by command:
device:[backups]file.bck.bck/saveset device:[newdir...] /by_owner=original

IS the the best solution?

Thx
Clayton

[Jan van den Ende]

Clayton,



IS the the best solution?


I don't know if it is THE best solution, but it sure is a GOOD solution, and it is straightforward.

Success!

Proost.

Have one on me.

jpe