copying data with rights and protection intact accross remote nodes?

[Clayton_12]

I have a 6.2 system and a 8.2 sytem, separtate nodes non clustered.

IS it possible to copy files and structure from DIsk on 6.2 system with all protections and rightlist information intact onto the 8.2 system?

Is it possible to use BACKUP to backup disk from the 6.2 host into save-sets on the 8.2 host disks?

Thx
CLayton

[Uwe Zessin]

Yes, BACKUP is the right way. It will even retain the creation and revision dates on plain files. For directores, I use a hack of two command procedures and the good old FILE utility.

[David Jones_21]

Note that the rights identifiers in the ACLS will have the binary values, not the names so you have to manually reconcile the rightslist.dat files on the 2 systems.

[Arch_Muthiah]

Clyton,

you can try some related info here under the subtitle of
B.1 Building a Common SYSUAF.DAT File
B.2 Merging RIGHTSLIST.DAT Files

http://h71000.www7.hp.com/doc/731FINAL/4477/4477pro_023.html#build_uaf_upgrade


Archunan

[Arch_Muthiah]

Clayton,

"VMS guide to system security" says that BACKUP of RIGHTSLIST.database will not be correct even if we use /IGNORE=INTERLOCK qualifier in the backup command as RIGHTSLIST database is one of the VMS CORE files which should be open always.

And the manual says RIGHTSLIST database cannot be recovered from a BACKUP copy.

So better
1. CREATE RIGHTSLIST database
2. ADD/IDENTIFIER to generate UIC for each user in SYSUAF.database.
3, Redefine the holders of the identifiers with GRANT/IDENTIFIER commands.

I saw your couple posting on this same topic earlier, I guess this is best way as per the the manual.

Archunan

[Jan van den Ende]

Re: archuan:

A consistent copy of active SYSUAF.DAT and RIGHTSLIST.DAT (and other permanently opened files) can be made by
$ CONVERT/SHARE ,
and then copying temp-file.
(see the MANY postings on this and related subjects by Mr. RMS himself, Hein van den Heuvel)

Proost.

Have one on me.

Jpe

[Arch_Muthiah]

Clayton,

Yes, Jan. Clayton can use CONVERT/SHARE to a copy of rightslist file, and he already mentioned in his previous posting that he used COPY command and it worked for him.

I never tried BACKUP?, our docs also says backup/restore can't be the best way.

Archunan

[Bart Zorn_1]

How unreliable is a BACKUP/IGNORE=INTERLOCK of RIGHTSLIST.DAT really?

IMHO there is very little write/update activity on RIGHTSLIST on a normal system. So when you take this backup on a system which is not doing anything else, the chance that you wind up with an unusable RIGHTSLIST file is very slim.

OK, the documentation is correct. There is a chance that something goes wrong. In practice, if you know what you are doing, just do it!

Regards,

Bart Zorn

[Petr Spisek]

CLayton,
yes, BACKUP can save original owner-UIC of file (Did you mean this as "righlist information"?). The best solution is to use the same user with the same UIC on both systems for owner of the saved file. If user of orig. UIC doesn't exist, you'll see only UIC-num as owner of file. You can use parameter /BY_OWNER=ORIGINAL into your BACKUP comands for backup and restor (or /BY_OWNER=['actual_uic'] for restore command).
Petr

[Clayton_12]

I was looking to perserve both Owner information, protection information, and identifier (Rightlist??/) permisions on files and directories?


Thx
Clayton