Recovering from Lost User Rights after Running DSMaint
Novell Cool Solutions: Trench
By David Sayers
Digg This -
Posted: 11 May 2004
We lost user rights after performing a DSMaint procedure from one NetWare 5.x box to another 5.x box.
After performing back-up using Arcserve 7, then performing DSMaint procedure, followed by data restore, no file rights or long file names were carried across.
Reverse the DSMaint procedure and use a temporary server (wimps method) to store data whilst DSMaint is re-performed in order to ensure files, rights and file names are maintained, by using Novell Consolidation Utility to move data between old server > temp server > new server.
If you don't have another server to hand, you'll need to re-run the backup jobs. But ensure that Long File Name support and file DS rights options are set correctly in the backup software, before performing the DSMaint procedure again.
- You're going to need a DOS boot disk with CD support and a CD-write on your workstation.
- Server A = The server you originally performed DSMaint on. (The one you're retiring.)
- Server B = The new server you wish to eventually replace Server A with.
- TEMP server = Temporary NetWare 5.1 box placed in tree with enough disk space to accommodate files.
First perform an NDS Health Check to ensure all replicas and time are in sync.
Then proceed as follows:
- Perform DSMaint on Server B (get the NDS backup file), so the server locks its database for hardware upgrade. Unplug Nic cable so the IP address is free for Server A to come back online.
- Build a temporary NetWare box with the correct SP level for the NetWare Server Consolidation Utility and volume types. Insert it into the tree with a temporary name. You also want to ensure no replicas are going to be placed automatically on the TEMP server.
- Burn your NDS copy to a CD-ROM keeping the file and folder name.
- Boot Server A with the boot disk and copy the NDS file from the CD to C: before running the server command.
- Once Server A is back up, follow DSMaint again to restore DS after upgrade, pointing the path to the C: (copy of Server B DS). This should now bring Server A back online and ready to be used.
- Check that file rights are still OK, and perform another DS health check.
- Using the NetWare Server Consolidation Utility, schedule a data transfer of your required data from Server A to TEMP server. Once underway you can check straight away that data is moving correctly.
- Take a break.
- Once you have all your Data and File Rights on the TEMP server, you can now do a forward DSMaint from Server A to Server B. (But remember, you're going to need the NDS on CD again to restore Server B back into the tree. And Server A needs its Nic cable removed or shut down.)
- Once Server B is back up and Server A is offline, schedule another Consolidation to move the Data from TEMP server to Server B. Once completed you should have a nice, fully working, Server B with files, names and rights. Once you're happy and the NDS is calm, you can then remove the TEMP server from the tree.
If you have any questions you may contact David at email@example.com