Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
Notice: | Welcome to the Digital UNIX Conference |
Moderator: | SMURF::DENHAM |
Created: | Thu Mar 16 1995 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 10068 |
Total number of notes: | 35879 |
My customer has an AS2000 padestal server with an SWX800 cabinet. HSZ40 is used and there are 30 disks installed. There is another AS41000 pedestal server with only 6 disks. The idea is how much work will be involved if we would like to swap the servers, i.e. the AS4000 will be connected to the SWX800 with HSZ40 controller and 30 disks, and the AS2000 will have 6 disks. The AS2000 runs Unix, and the AS4000 runns NT. Is it just a swap of server and rebuilding of the kernel, or has to backup all the data in the 30 disks and restore them back once the HSZ40 controller is installed ? Rgds.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
9123.1 | Keep the names the same... | SSDEVO::ROLLOW | Dr. File System's Home for Wayward Inodes. | Wed Mar 12 1997 10:53 | 19 |
Is the goal to have the AS2000 running NT after the swap and the AS4100 running UNIX? If so, that's pretty easy. Move the system disk and boot from the generic kernel. Mount the local file systems and build a configuration specific kernel. Edit /etc/rc.config as necessary if the name of the network adapter changed. If you can manage to keep the system disk having the same name in the move between systems, you save yourself a little extra work. If not, you need to be sure that the special files for the new system disk exist before the move. This sort of shuffle is very easy with UFS. It may take a bit more work of changing links for AdvFS. It may be even harder if LSM is involved. With a bootable system disk you can worry about the remaining storage. If you keep all the device names the same, you just move the cables. If the names change, it gets harder. |