Checklist for Manually Cloning a Unix
Server
Here are the key items necessary to manually match the unix file server
configuration on one file server to another file server. Please
note that it is much easier and more reliable to use automated methods
of cloning server configuration such as HP's Ignite UX product, or
IBM's
Sysback product.
Guidelines:
- Always backup every file that is being changed by copying it to
the same filename with today's date as the extension
- cp /etc/hosts /etc/hosts.22june03
- Always test every change
1. Initial OS Installation
Create Filesystem
Install OS Files
Configure Basic Networking
- Hostname
- IP Address
- Subnet Mask
- Default Gateway
- DNS
- DHCP
- NTP
- NIS
2. User Configuration
Backup the important user configuration files:
- /etc/passwd
- /etc/group
- /etc/shadow
- /etc/profile
- /etc/PATH
- /etc/motd
- /etc/issue
- /.profile (roots .profile)
- /.rhosts (roots .rhosts)
Replace these files with copies from the source server
Copy/Import/Mount home directories as needed
Copy custom environmental files/profile files
3. NIS Configuration (if applicable)
Duplicate the NIS role of the server:
- NIS Master
- NIS Slave
- NIS Client
Verify the configuration files have been properly updated to use NIS:
- /etc/passwd
- /etc/hosts
- /etc/networks
- /etc/group
- /etc/protocols
- /etc/services
- /etc/rpc
- /etc/netgroup
4. Filesystem Configuration
Local Filesystem Configuration:
List the Filesystems and compare them with the existing filesystems:
( on HP-UX to list local filesystems: bdf
| sed 1d | xargs -n 6 | grep -v :/, to list NFS filesystems: bdf | sed 1d | xargs -n 6 | grep -c :/,
to list local filesystem type: grep -v :/ /etc/fstab | awk '{print $2 "\t"
$3}')
- Name
- Size
- Type
- Mount Points
- Mirroring or Striping
Create any filesystems that are missing on the new system
Change the size of existing filesystems on the new system as needed
NFS Filesystems:
- Make the required mount points for NFS Mounts
- Change ownership of the mount points
- Change the permissions of the mount points
- Copy the fileystem configuration files (edit as needed):
Move the data to the new system
- export the volume groups and reimport?
- image/clone?
- backup/restore or copy
- Mount the NFS filesystems
5. Startup/Shutdown Configuration
Startup scripts
Shutdown scripts
Link scripts to startup and shutdown
/sbin/init.d
/sbin/rc.*
/etc/inittab
6. Service Configuration
/etc/inetd.conf
/etc/services
7. Additional Networking Configuration
Change these parameters as needed to configure the networking
- Hostname - cannot be the same as the original server if the
original server is not shutdown
- IP Address - cannot be the same as the original server if the
original server is not shutdown
- Subnet Mask
- Default Gateway
- DNS
- Multiple Interfaces?
Copy the required networking configuration files from the original
server
- /etc/hosts - cannot be the same as the original server if the
original server is not shutdown
- /etc/rc.config.d - multiple files located here
- /etc/resolv.conf
- /etc/nsswitch.conf
- /etc/ntp.conf
8. Scheduling Configuration
Copy the configuration associated with crontab and at:
- crontab -l
- at -l
- /var/adm/cron
- /var/spool/cron
- cronjobs
- atjobs
9. Printing Configuration
Identify and configure (migrate configuration if possible from original
server):
- Local Printers
- Remote Printers
- Jet Direct Printers
10. System Logging Configuration
/etc/syslog.conf
11. OS Configuration
Version (uname -a)
Kernel Parameters (HP-UX "kmtune"
will list the tuning parameters)
Installed Patches/Maintenance Release Bundles
12. Application Software Configuration
Can it be copied/restored from tape, or does it require an installation?
License Keys
License Manager Processes
Hardware Dependancies
Application Patches/Updates
Locally Installed Software/Utilities/Scripts (/usr, /opt . . .)
Configuration Files
- /etc/sendmail.cf --> if running sendmail
13. NFS Export Configuration
What is going to be exported
Who can access
How will it be accessed - ro, rw
Who can be root
/etc/exports
exportfs
14. Apply Custom Procedures/Configuration
Security Hardening
15. Final Configuration if Replacing the Original Server
Hostname Change - original server must be shutdown
IP Address Change - original server must be shutdown
Copy /etc/hosts from the original server - original server must be
shutdown if this file is used