[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference forty2::x500

Title:X.500 Directory Services
Notice:Sprt: FORTY2::X500_SUPPORT, Kits: 216.*, try dir/titl=OFFICIAL
Moderator:FORTY2::PULLEN
Created:Tue Jan 30 1990
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1016
Total number of notes:4299

998.0. "Moving a X.500 to another system disk." by NNTPD::"[email protected]" (Torben Sorensen) Thu Apr 24 1997 11:55

My customer have made a new system disk with dec unix 3.2g
Previous the system runs 3.2 clean. Instead of doing an upgrade,
he choosed to do a new installation on a new and bigger system disk.

And now the question. Is there a easy way to move x.500 data
including DSA information as naming context and all that sthuf,
to the new system disk, without doing it all from scratch????

The system is also running MAILbus 400 and MAILbus monitor.


/Torben

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
998.1a-107.tunnel.crl.dec.com::FORTY2::PALKAAndrew Palka Altavista DirectoryThu Apr 24 1997 15:1921
The easiest way is probably 
1) install X.500 on the new system 
2) examine the new presentation address of the dsa
3) shutdown the dsa
4) copy all of /var/dxd to the new system
5) start up the dsa

By doing a fresh installation you can be sure that all the system
files that are needed will be present. 
Copying /var/dxd will take the database and schema files.

If the presentation address of the dsa has changed then you
will need to set the new address in the dsa. In that case you will
have to set the new one in dua_defaults.dat, and in any subordinate
references, consumer access points etc. that are in this or other
dsas (That could be a big task !).

Andrew
998.2What about DSA Naming ContextNNTPD::"[email protected]"Torben SorensenMon Apr 28 1997 08:5217
Thanks for you answer.!

Just an other question:

Do I have to create Naming Context's in the new system, or
can I move that information also from the old system.
The customer have a replication setup to an other dec.X500
system.

About copying the /var/dxd files... The old system was running
a 2.02 version. The new is a 3. system. What do I need to do
to the files when they are copyed to the new system?


/Torben

[Posted by WWW Notes gateway]
998.3a-101.tunnel.crl.dec.com::FORTY2::PALKAAndrew Palka Altavista DirectoryMon Apr 28 1997 11:1517
The Naming contexts are part of the database, so they will exist
when you reload it.

If you are upgrading from V2 then you have an additional problem.
A V3 DSA can load a database created by a V2 system with no problem,
but the default schema is different with V3.

You will have to use the V3 schema files from /var/dxd (I.e.
you only copy the old database files DSA-*).
If you have a customised schema with the old database then you
will have to recustomize the V3 schema (edit and compile it).

You will also have to tell the dsa to load the snapshot files
(ncl> create dsa from snapshot), otherwise it will reload the
memory image files created during installation.

Andrew