Summary: Cloning DUNIX System

From: <KAPLANSKYM_at_NCCCOT.AGR.CA>
Date: Sun, 19 Apr 1998 12:57:33 -0400 (EDT)

I had posted a question regarding copying an Alpha 1000 running Digital
Unix V3.2C to create a cloned development/test platform on a DEC 3000
Model 600.

Thanks to those who replied.

--------------------------------------------------------------------------------
Dr. Tom Blinn of Digital has done this several times. He suggests
making the device names identical to make life simpler as no changes
would be required in the fstab. Use dump and restore to copy the file
systems, since I am using UFS. An alternative is to set up one system
to be an RIS server and then boot the other over the network and use
standalone mode to load the image copies.

The network configuration files will also have to be changed, of course.
 Once the backups are done, a new kernel may have to be built, so boot
/genvmunix and follow the usual procedures.
--------------------------------------------------------------------------------

George Guethlein of Giant Food, Inc provided detailed instructions for
the vdump and vrestore parts. He says that this approach "**should**"
work, although more time than expected may have to be spent configuring
files to compensate for the host specific information (ie. /etc/hosts,
/etc/services, /etc/rc.config, etc.).

Use "vdump"to take a complete backup of the critical system files (ie,
"/", "/usr", and "/var"), it works for UFS and AdvFS filesystems.

The following commands should do it :

1.) mt -f /dev/rmt0h rewind
2.) /sbin/vdump -0 -N -C -u -F 64 -f /dev/nrmt0h /
3.) /sbin/vdump -0 -N -C -u -F 64 -f /dev/nrmt0h /usr

Use "vrestore" to put the filesystems back down on the new disks.

1.) Boot the 3000 from the Unix install CD (same version as production).
2.) Make the device files or the two disks ( I calculate the device
     address to be DKA300 = "rz3" and DKB400 = "rz12"), as follows :
a.) cd /dev
b.) .MAKEDEV rz3
c.) .MAKEDEV rz12
3.) Verify the filesystems partition location on the 1000 and make sure
     that the partitions are at least the same size on the 3000.
4.) Mount the correct partitions :
a.) mount /dev/rz3a /
b.) mount /dev/rz12? /usr
5.) vrestore the filesystems. Check the vrestore man page for the
     correct command.

When the system files are restored, you may have to boot from the
"genvmunix" kernel to autodetect the NEW disks. Then, you MAY have to
rebuild the kernel with any of your site specific modifications. This
should resolve the major device id considerations. However, if you use
LSM (and possibly other software) you will have more work. The devices
are known in the LSM configuration database.

--------------------------------------------------------------------------------


Marvin Kaplansky
Agriculture Canada
kaplanskym_at_ncccot.agr.ca
Received on Sun Apr 19 1998 - 18:58:40 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:37 NZDT