Moving sysuaf, rightslist, net$proxy, netproxy, etc

[John A. Beard]

Hi folks... I need your expert advice

We are in the process of building a new ES47 based on the contents of an older 2100. Both boxes are running VMS 7.3-2.

Although the new server have been up and running for a couple of months now for testing, we are now ready to move all the final bits and pieces across from the original box.

We need to bring across (NOT merge) all the related uaf files from the old environment and replace the files that currently exist on the new box. The primary area of concern is the uaf entries (usernames, passwords, home dirs reference), and their associated rights and proxy entries. The 'old' profiles (logical home dirs, etc) should work fine in the new environment, as the build of the new disks and directory names are the same as the old ones.

Q1. What files need to come across... sysuaf.dat, rightslist.dat.. both net$proxy and netproxy.dat files ?) others ???.

Q2. If I can simply copy the necessary files across, will an immediate reboot capture all the information from the old system's files.

[Jan van den Ende · Accepted solution]

John,

provided that you copied the home-dirs etc. _INCLUDING THE OWNERSHIPS_, basically that can "just" be done.

Only one thing - do NOT copy the files (they are likely "locked by another user" anyway), and do NOT use BACKUP/IGNORE=INTERLOCK either.
In the words of Hoff: that option is named incorrectly. The real meaning is /ALLOW=CORRUPTION.

For each file (and you probably want to add QMAN$MASTER, although I also can envision you wishing to start with a "clean" start for that) do a ANA?RMS/FDL/OUTP=
Then, CONVERT/SHARE /FDL= .

Move the various to your new system with the correct names, and you are done,

-- for proxies, this assumes unchanged remote systems. Any additions will of course still have to be applied.

Any of the above conditions not met, or unsure, please, come again! Things are (then also) not too difficult, but you had better execute the correct changes!

hth.

Success!

Proost.

Have one on me.

jpe

[John A. Beard]

Thanks Jan... as advised, I "ignored" the /IGNORE

Clean copies of the nexessary files went across to the new server.. thanks

[Hoff]

The rightslist identifiers will have to be synchronized. This is not difficult, but it's a little work. These binary values can be associated with most any object on OpenVMS -- file ownerships, directory ownerships for server-related directories, within access control list entries, on batch queues, etc -- these can be and often are written most everywhere, and you will have to manage these identifier values.

You may (will?) probably have to merge at least some of these values.

If you should skip this step, you will have overlapping values, and this can cause cases where access is incorrectly allowed, or access is incorrectly denied. Biggest typically area here are likely the server-related and pre-created usernames, and related directories, files and such. The node-specific identifer, too. These don't necessarily receive the same binary values across systems.

Unfortunately, there are some structures that are tough(er) to scan for automatically and to get at. Most of the biggest and most commonly tweaked bunches of objects can be scanned for, files and devices and queues.

Stephen Hoffman
HoffmanLabs