I'd like to export our company's main NDS database to a former workstation that I turned into a nw5.1 server. This is going to be part of our lab and I'd like it to resemble our setup as much as possible. If I backup the NDS database in mwconfig...is it possible to import it on to the new server? This server already has nds installed, I'm guessig I would have to remove directory services? Thanks
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
copy NDS database?
- Thread starter summoner
- Start date
- Thread starter
- #3
Not sure if it's in your version of DS, but try executing DSREPAIR -$DU on your test server. You should get more options than just backup DS. Do a restore with out verification (so nothing gets in the way), and point it to the directory your DIB set is backed up to. The extention on the backup file should have a $DU to give you a hint if this will work or not. (been a while since I have used 8.5, this option is avilable in 8.6.2).
Another way you can do it is to use NWCONFIG, go into DS options and do a backup of DS before a hardware upgrade. You will want to do this after hours since it will close and lock the DS database. After you create the backup on your production server, turn around and restore it in the same menu, this will unloack the DS database on your production server. Then, take the file it created and transport it to your test server. Name your test server the same exact name as the production server, and also the same exact internal IPX number. Then using NWCONFIG, go into the DS options on the test server and do a restore DS after hardware upgrade.
You will not be able to have both servers on teh same physical network using either option.
There is one more way to do this, but you need to be very familure with DS to do it. You need to know how to sync, and how to repair DS when servers go down. Basicly, install the test server to the production tree. Then take it off the network. When the test server is on it's own network, promote it to master and remove the production server from the replica ring. Then on the production server, remove the test server from the replica ring. Go into ConsoleOne on both servers, clean up DS. Install PKI services on the test server, and clean up DS. DO NOT go this way unless you feel bold or are familure DS clean up and repair.
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Provogeek
CNE Network+ Experience
Certified nut case
Another way you can do it is to use NWCONFIG, go into DS options and do a backup of DS before a hardware upgrade. You will want to do this after hours since it will close and lock the DS database. After you create the backup on your production server, turn around and restore it in the same menu, this will unloack the DS database on your production server. Then, take the file it created and transport it to your test server. Name your test server the same exact name as the production server, and also the same exact internal IPX number. Then using NWCONFIG, go into the DS options on the test server and do a restore DS after hardware upgrade.
You will not be able to have both servers on teh same physical network using either option.
There is one more way to do this, but you need to be very familure with DS to do it. You need to know how to sync, and how to repair DS when servers go down. Basicly, install the test server to the production tree. Then take it off the network. When the test server is on it's own network, promote it to master and remove the production server from the replica ring. Then on the production server, remove the test server from the replica ring. Go into ConsoleOne on both servers, clean up DS. Install PKI services on the test server, and clean up DS. DO NOT go this way unless you feel bold or are familure DS clean up and repair.
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Provogeek
CNE Network+ Experience
Certified nut case
- Thread starter
- #5
Thanks for the answer provogeek.
I'd like some clarification on your instructions please. I'm talking about the option in nwconfig "Save local NDS information before hardware upgrade" You say: After you create the backup on your production server, turn around and restore it in the same menu, this will unloack the DS database on your production server.
I've backed up NDS this way, but I've never had to restore it like you mention. The server was still running and able to process logins etc... after the upgrade. Is this restore necessary? Please clarify...thanks.
I'd like some clarification on your instructions please. I'm talking about the option in nwconfig "Save local NDS information before hardware upgrade" You say: After you create the backup on your production server, turn around and restore it in the same menu, this will unloack the DS database on your production server.
I've backed up NDS this way, but I've never had to restore it like you mention. The server was still running and able to process logins etc... after the upgrade. Is this restore necessary? Please clarify...thanks.
Hi Summoner,
I believe what Provo meant is that once you perform this procedure NDS is locked. You need to restore it again to get it back to it's original condition.
In the mean time you would copy the exported file and import it into the other server.
I have used this procedure during a NW6 to NW6 hardware migration and NDS was locked when I did it.
Good Luck
Lou
I believe what Provo meant is that once you perform this procedure NDS is locked. You need to restore it again to get it back to it's original condition.
In the mean time you would copy the exported file and import it into the other server.
I have used this procedure during a NW6 to NW6 hardware migration and NDS was locked when I did it.
Good Luck
Lou
this is really a backup method in the true sense of the word
it effectively removes the ds into a nice convient file so that you can restore it to say for example new hardware (if you search for tids on dsmaint it will explain).
you are doing the restore on the same server so that you are putting it back to original condition but you have the file to use on the test system - which as said before you will need to keep seperate
this method is quick and easy but not without risk
(i have used this before numerous time and never had any probs) -just verify ds and time in sync before hand and you havent any user requiring access
i've never tried other way although suspect it may be better - will need to go and read about it
it effectively removes the ds into a nice convient file so that you can restore it to say for example new hardware (if you search for tids on dsmaint it will explain).
you are doing the restore on the same server so that you are putting it back to original condition but you have the file to use on the test system - which as said before you will need to keep seperate
this method is quick and easy but not without risk
(i have used this before numerous time and never had any probs) -just verify ds and time in sync before hand and you havent any user requiring access
i've never tried other way although suspect it may be better - will need to go and read about it
- Status
Similar threads
- Locked
- Question