Private Server and Physical Server Backup and Restoration:

Transcription

1 Technical Document Series Number 014 Private Server and Physical Server Backup and Restoration: A Technical Guide for ISP/HSP Administrator Covers Ensim ServerXchange 2.5 and Earlier Date: September 25, 2001 Version 1.1

2 by Seth Hak Important Notice This document contains proprietary information of Ensim and its receipt or possession does not convey any rights to reproduce, disclose its contents, manufacture, use, or sell anything it may describe. Reproduction, disclosure, or use without Ensim's specific written authorization is strictly forbidden. Ensim Corporation makes no representations or warranties with respect to the contents or use of this document. It also reserves the right to revise this publication and make changes to the content at any time without the obligation to notify any person or entity of such revisions or changes. ServerXchange and WEBppliance are trademarks of Ensim Corporation. Netscape is a registered trademark of Netscape Communications Corporation. Windows is a registered trademark of Microsoft Corporation. Java, Solaris, SPARC are registered trademarks of Sun Microsystems. Linux is a registered trademark of Linus Torvalds. All other trademarks and copyrights are the property of their respective owners. Copyright Ensim Corporation. All rights reserved. Ensim Corporation 1366 Borregas Avenue Sunnyvale, CA (408) , 2000, 2001 Ensim Corporation. All rights reserved. Ensim is a trademark. All other trademarks are the property of their respective owners. Product information is subject to change without notice.

3 Contents Private Server and Physical Server Backup and Restoration 1 Introduction 1 Purpose 1 Document Conventions 2 The `vklookup` Command 2 Listing Private Servers and Services on a Physical Server 3 Commands 3 Physical Server Directory Structure 4 Backing Up Private Servers 6 Options for Private Server Backups 7 Options 7 Backup Private Servers With REOBack 10 Frequently Asked Questions 13 Important Notes 15 Backing Up Physical Servers and All Its Private Servers 17 Full Backup of a Physical Server 17 Selective Backup of Physical Server 17 Recovering from a Physical Server Failure 19 Recovering Physical Servers With All Private Servers 20 Full Restore From Full Backup 20 Restore From Selective Backup 20 Example of a Physical and Private Server Recovery 21 For Further Reading 22 Private Server and Physical Server Backup and Restoration - PPS c i

4 ii Private Server and Physical Server Backup and Restoration - PPS c

5 Private Server and Physical Server Backup and Restoration Introduction Purpose Introduction To ensure proper recovery, you need to develop a good backup strategy. This guide suggests possible methods of backup that can work within your current disaster recovery implementation. You must be able to recover from the following scenarios. 1 Loss of a physical server due to: File system corruption Hardware failure Operator error 2 Loss of a private server due to: Private server file system corruption Operator error This section presents some introductory material on Ensim command line and directory structure. Private Server and Physical Server Backup and Restoration - PPS c 1

6 Introduction Document Conventions Table 1. List of Terms Terms CLI $vkid $vkname $disksize $vps_install_location Definitions Command Line Interface, a set of command line scripts provided by Ensim. The numeric ID of the private server recorded in the ControlCenter Database. You can use the vklookup utility to find the $vkid or $vkname of a given private server. The name of the private server, the FQDN (Fully Qualified Domain Name, i.e., The size of the loopback disk of a private server. This can be found in /ServerXchange/vpses/$vkid/ info/disksize.conf. The install location specified when a private server is created. The `vklookup` Command Each Private Server has its own internal ID number that you can sometimes see in pathnames or process listings. This is the ID of the private server in the ControlCenter database. To convert between the ID number and the name of the Private Server, use the vklookup command. Vklookup provides a detailed listing of the private server properties. % Usage: /usr/bin/vklookup -n VKhostname (longname) /usr/bin/vklookup -i Vkid Use n to search using the FQDN of the private server or I to search using the $VKID of the private server. [root@ps20 /root]# vklookup -i 15 vk="15" installdir="/<install-dir>" dns2=" " Private Server and Physical Server Backup and Restoration - PPS c 2

7 Introduction processquota="256" extnetmask=" " netquota="5" memquota="128" extdomain="<domain-name>" extipaddr=" " name="<client-name>" diskquota="1000" cpuquota="5" dns1=" " gateway=" " version=" " Listing Private Servers and Services on a Physical Server You can execute the following commands as root on a solaris or linux workstation using the CLI to determine the set of private servers, services and their properties. Refer to the ServerXchange Users Guide for more information on the CLI. Commands list_private.pl - This command gives you a list of private servers on a particular physical server. query_private.pl - This command gives you a list of properties including QOS values for a private server. list_service.pl - This command gives you a list of services installed on a particular private server. Private Server and Physical Server Backup and Restoration - PPS c 3

8 Physical Server Directory Structure Introduction You can access the private servers files and configurations directly from the physical server. The base directory where everything is stored is /ServerXchange/. Even if you specify an install location of /home/vps, or /vps, or nfsserver:/export/vps all private servers are linked through the /ServerXchange/ base directory. Table 2 lists some ServerXchange subdirectories and their descriptions. Table 2. ServerXchange Subdirectories Subdirectory filesys/ ps_upgrades/ rollback/ services/ templates/ vkman/ vpses/ Description filesys/ is where all named install locations are linked. So if you specify multiple install locations during private server creations they will all be linked here. ps_upgrades/ is where private server upgrade information is stored (when there is an upgrade available). rollback/ is where the private server configuration is stored during an upgrade. This is used to revert a failed upgrade back to it s the state before the upgrade. services/ is where all the services installed on the private servers are cached. We cache the services to reduce installation times and network traffic. templates/ is currently not used. vkman/ is where Ensim stores relevant scripts, code and programs to manage private servers. vpses/ is where all private servers are linked by $vkid. This is your entry point. In /ServerXchange/vpses you will see numbered links to /ServerXchange/filesys/ $vps_install_location 39/ 41/ 42/ Private Server and Physical Server Backup and Restoration - PPS c 4

9 Introduction Each /ServerXchange/vpses/$vkid link has a set of directories. Table 3 lists these directories and their descriptions. Table 3. ServerXchange/vpses/$vkid Link Subdirectories Subdirectory info/ Description info/ is where the private server configuration files are stored. All these of these files are updated from the ControlCenter. They are basically copies of the information that is stored on the ControlCenter s database. Changing the values in these files will NOT be preserved between reboots and will not propagate to the ControlCenter. services/ treeroot/ vnkbuilt/ disks/ services/ is where a list of installed services on the private server treeroot/ is the private server root `/`. So as you can see, when you list treeroot it is just the contents of the root directory of the Private Server. vnkbuilt/ is a place holder file. Do not attempt to remove or modify this file. disks/ is where the loopback image is stored (if there are any) You can see where the private servers are mounted by using the mount command. The file systems are actually mounted to $vps_install_location/vpses/$vkid/treeroot as shown below. [root@ps20 15]# mount /dev/hda5 on / type ext2 (rw) none on /proc type proc (rw) /dev/hda1 on /boot type ext2 (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) Private Server and Physical Server Backup and Restoration - PPS c 5

10 Backing Up Private Servers /ServerXchange/vkman/data/fsimage on /mnt/fsimage type ext2 (ro,loop=/dev/loop0) /ensim/vpses/2/disks/disk1 on /ensim/vpses/2/treeroot type ext2 (rw,loop=/dev/loop1) /ensim/vpses/3/disks/disk1 on /ensim/vpses/3/treeroot type ext2 (rw,loop=/dev/loop2) /ensim/vpses/4/disks/disk1 on /ensim/vpses/4/treeroot type ext2 (rw,loop=/dev/loop3) /ensim/vpses/15/disks/disk1 on /ensim/vpses/15/treeroot type ext2 (rw,loop=/dev/loop4) server.ensim.com:/export/dev/adjunct/daily/current on /ensim/vpses/15/treeroot/mnt type nfs (rw,addr= ) server.ensim.com:/export/dev/adjunct/daily/current on /ensim/vpses/15/treeroot/mnt/adjunct type nfs (rw,addr= ) Backing Up Private Servers There are several options for backing up private servers. We will discuss some generic solutions, which you can use with your current backup procedures. Private servers are not bound to a particular physical server. However, private servers are bound to a particular ControlCenter. Think of physical servers as being disposable containers where the private servers reside. There are no special requirements for backing up Local Solaris Private Servers, since Local Solaris Private Servers do not use loop-back filesystems. Private Server and Physical Server Backup and Restoration - PPS c 6

11 Options for Private Server Backups Backing Up Private Servers There are two basic backup options. For both options we highly recommend that you maintain separate volumes for each Private Server as if you were backing up any other server. Options 1 Backup each private server with your favorite backup system. Install a client on each private server. Each private server does a backup as if it were a real server with its own volume. You can then follow your routine backup policy. Follow these steps: a b Install your favorite backup agent on each private server. Set your server to backup each private server at a specified time. Pros: Simple, fits within your existing backup policy Cons: Expensive, requires an agent on every private server 2 Backup all or selected private servers on a given physical server from the physical server. Follow these steps: a b c Backup from /ServerXchange/vpses/$vkid/treeroot. Give each PS it s own volume and name it with a distinct name such as the private servers domain name and the backup date. To reduce the backup size of a WEBppliance PS use a backup client that preserves hard-links (e.g. the cpio utility preserves hard-link information). Pros: Less expensive. Requires only one agent on the physical server Cons: More complicated, requires special backup archives for each private server In either case it is important that you tell your backup software to: 1 Preserve or maintain hard/soft Links 2 Not backup the following: /proc /tmp /mnt Private Server and Physical Server Backup and Restoration - PPS c 7

12 Backing Up Private Servers Example Here is an example script that will backup a Physical Server. #Performs a backup of a physical server #!/bin/sh cd /Backup # Get the filesystems df -hp > /Backup/physical<name>.df.sh df -hp grep treeroot sed "s/m / /g" awk '{print "/ServerExchange/vkman/bin/create_filesys "$6,$2" /home" }'/ Back up/mk.physical6.fs.sh #get the physical server config tar cvzf /Backup/Phys6.conf.tgz -C / \ /Backup/*.sh /Backup/scripts \ /etc/ssh2/hostkey \ /etc/ssh2/hostkey.pub \ /etc/serverxchange \ /var/log/vkman.log \ /var/log/serverxchange \ /ServerXchange/vpses \ /ServerXchange/filesys/home \ /home/pool \ /home/alreadymounted \ /home/vpses/*/info \ /home/vpses/*/vnkbuilt #Performs a backup of a Private server #!/bin/sh tar cvzf /Backup/Phys$2.Priv$1.tgz -C / \ /ServerXchange/filesys/home/vpses/$1/treeroot \ Private Server and Physical Server Backup and Restoration - PPS c 8

13 Backup Private Servers With REOBack --exclude /ServerXchange/filesys/home/vpses/$1/treeroot/proc \ --exclude /ServerXchange/filesys/home/vpses/$1/treeroot/tmp Backup Private Servers With REOBack REOBack (pronounced "ray-o-back") is a backup solution designed for Linux users and system administrators. Designed to be simple to set up, it is easy to use and it is great as a quick solution for those who may not be able to do regular backups. It supports the automatic full/incremental backups of files you define, remote backups via NFS or FTP, as well as auto deletion of old backups. You can read the documents dealing with how to configure local (default), FTP or NFS backups. For more information, point your browser to for REOback Version = 1.1 Download the REOBack tar ball from: reoback-1.0_r2.tar.gz Download perl-libnet and install the rpm. This is needed for FTP backups. ftp:// contrib.redhat.com/pub/contrib/noarch/noarch/perl-libnet noarch.rpm Caution: The RPM only works with RPM 4 or better. You will need to manually setup REOBACK or use the following code to place the files. I ve asked the REOBack maintainer for a source RPM to help us build our own. #!/bin/sh #config-reoback.sh cd /tmp /bin/tar -zxvf reoback-1.0_r2.tar.gz echo "placing files in proper directories" echo " " echo " " cp -R /tmp/reoback-1.0/conf/ /etc/reoback/ mkdir -p /usr/local/reoback/data cp /tmp/reoback-1.0/reoback.pl /usr/local/reoback cp /tmp/reoback-1.0/run_reoback.sh /usr/local/reoback cp /tmp/reoback-1.0/docs/man/* /usr/man/man1 Private Server and Physical Server Backup and Restoration - PPS c 9

14 Backup Private Servers With REOBack echo " " echo " " echo "Done with reoback install" echo "make sure you setup /etc/reoback/settings.conf" echo "make sure you setup /etc/reoback/files.conf" echo "make sure you set the cron to run /usr/local/reoback/ run_reoback.sh" echo "read the docs in /tmp/reoback-1.0/docs" echo "or type 'man reoback'" When this is done you have to configure REOback. Edit the /etc/reoback/settings.conf for the server, everything is well documented. Use the following script to create the files.conf for the private servers. #!/bin/sh #make-files.sh VPSLIST="`/bin/ls /ServerXchange/vpses`" REOCONF=/etc/reoback/files.conf HOSTNAME="`/bin/hostname`" #echo $vpsroot echo "#Auto Generated by $0" > $REOCONF echo "">>$REOCONF echo "">>$REOCONF echo "File: $HOSTNAME-BOX" >> $REOCONF echo "/etc/ssh2/hostkey" >> $REOCONF echo "/etc/ssh2/hostkey.pub" >> $REOCONF echo "/etc/serverxchange" >> $REOCONF echo "/var/log/vkman.log" >> $REOCONF echo "/var/log/serverxchange" >> $REOCONF echo "/vps/vpses/pool" >> $REOCONF echo "/vps/vpses/alreadymounted" >> $REOCONF echo "/vps/vpses/*/info" >> $REOCONF Private Server and Physical Server Backup and Restoration - PPS c 10

15 Backup Private Servers With REOBack echo "/vps/vpses/*/vnkbuil" >> $REOCONF echo "">>$REOCONF echo "">>$REOCONF for VPSID in $VPSLIST do VPSINFO="`/usr/bin/vklookup -i $VPSID 2> /dev/null`" VPS="`echo $VPSINFO awk '{ print $10,$8 }' cut -f2,4 - d'\"' sed 's/\"/\./'`" echo "File: $VPS" >> $REOCONF echo "">>$REOCONF echo "/ServerXchange/vpses/$VPSID/treeroot" >> $REOCONF echo "">>$REOCONF echo "Skip: /ServerXchange/vpses/$VPSID/treeroot/proc" >> $REOCONF echo "Skip: /ServerXchange/vpses/$VPSID/treeroot/dev" >> $REOCONF echo "Skip: /ServerXchange/vpses/$VPSID/treeroot/tmp" >> $REOCONF echo "Skip: /ServerXchange/vpses/$VPSID/treeroot/mnt" >> $REOCONF echo "">>$REOCONF echo "">>$REOCONF done Caution: There maybe a bug in ServerXchange, it does not insert the vk=n in the /ServerXchange/vpses/1/info/vk.conf file. You will need to insert as the very first line vk= 1 in the vk.conf for VKID 1.\ Your file should look something like this. It is easy to customize, just list the files, directories you want to backup or Skip. #Auto Generated by make-file.sh File: rh001-box /etc/ssh2/hostkey Private Server and Physical Server Backup and Restoration - PPS c 11

16 Backup Private Servers With REOBack /etc/ssh2/hostkey.pub /etc/serverxchange /var/log/vkman.log /var/log/serverxchange /vps/vpses/pool /vps/vpses/alreadymounted /vps/vpses/*/info /vps/vpses/*/vnkbuil File: rh001-1.remarkablehosting.com /ServerXchange/vpses/1/treeroot Skip: /ServerXchange/vpses/1/treeroot/proc Skip: /ServerXchange/vpses/1/treeroot/dev Skip: /ServerXchange/vpses/1/treeroot/tmp File: rh001-2.remarkablehosting.com /ServerXchange/vpses/2/treeroot Skip: /ServerXchange/vpses/2/treeroot/proc Skip: /ServerXchange/vpses/2/treeroot/dev Skip: /ServerXchange/vpses/2/treeroot/tmp File: rh001-3.remarkablehosting.com /ServerXchange/vpses/3/treeroot Skip: /ServerXchange/vpses/3/treeroot/proc Skip: /ServerXchange/vpses/3/treeroot/dev Skip: /ServerXchange/vpses/3/treeroot/tmp Frequently Asked Questions Table 4 on page -13 lists a sampling of the most commonly asked questions regarding backup with REOback. Private Server and Physical Server Backup and Restoration - PPS c 12

17 Backup Private Servers With REOBack Table 4. Frequently Asked Questions (Sheet 1 of 2) Question How do I force a full backup? When doing a local or NFS backup it says, Performing incremental backup via FTP. Why is that? How do I process a backup of individual directories without a files.conf? Answer Delete files in /usr/local/reoback/data/. This is a bug that will be fixed in the next release. There is a hidden feature of REOBack to allow backup of individual directories outside the files.conf. This is hard-coded in the reoback.pl. 1 Look for a line in the reoback.pl that looks like: #&backupdir("/home/sforge/ reoback", "Reoback", 1); 2 Change it to: &backupdir ("/usr/local/ www/", "rh001", 1); Note: You can repeat the same line of code for other directories that you want to archive in a similar fashion. What about the hard link issue? See html_mono/tar.html#sec120 Private Server and Physical Server Backup and Restoration - PPS c 13

18 Backup Private Servers With REOBack Table 4. Frequently Asked Questions (Sheet 2 of 2) Question How do I restore? Answer tar xpvfz DARKSTAR- myfiles-full am.1.tgz <dir or file(s)> To restore only the home directory in the private server: tar --directory=/ -zxpvf rh001-rh001-2.remarkablehosting.comfull am.1.tgz Important Notes I have not tested the scenario of removing the private server and building a new one. The caveat here is that the $VKID must remain the same or you will have to somehow restore to the new ID. I have not tested the scenario of rebuilding a complete physical server, we need to make sure the right information is backed up. It may be best to manually backup the physical server configuration like the original backup document states. Backup times to the local device are slow if you have a slow IDE Disk. The creation of the backup file eats IO. A workaround to using their NFS (which creates a local file and then moves it to NFS) is to mount a partition somewhere and set that mount point as the localbackup directory in settings.conf. As far as I can tell ALL hard links are maintained. [root@rh001-3 /]# ls -li /home/virtual/filesystemtemplate/ bin/zcat rwxr-xr-x 4 root root Mar [root@rh001-3 /]# ls -li /home/virtual/rh1/bin/zcat rwxr-xr-x 4 root root Mar Available space is approximately the same, 500K difference, maybe log files? Before disaster Private Server and Physical Server Backup and Restoration - PPS c 14

19 Backing Up Physical Servers and All Its Private Servers /]# df -k Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda % / After disaster i.e. rm -rf /home [root@rh001-3 /]# df -k Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda % / After restore [root@rh001-3 /]# df -k Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda % / After Reboot [root@rh001-3 /]# df -k Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda % / Adding sites did not work. For some reason the files dev/null and dev/ptmx dev/tty are not restored. You can restore them this way: # /bin/mknod -m 0666 /home/virtual/filesystemtemplate/dev/ null c 1 3 # /bin/mknod -m 0666 /home/virtual/filesystemtemplate/dev/ tty c 5 0 # /bin/mknod -m 0664 /home/virtual/filesystemtemplate/dev/ ptmx c 5 2 Backing Up Physical Servers and All Its Private Servers There are two options we can use to perform a backup and restore of a physical server and all private servers on that server. These are: 1 Full backup 2 Selective backup Private Server and Physical Server Backup and Restoration - PPS c 15

20 Full Backup of a Physical Server Backing Up Physical Servers and All Its Private Servers In this option you create a complete file system backup of the physical server. You can use this method regardless of customizations you made after the server is brought under management by ServerXchange. However, Your recovery servers need to be completely identical to the production server. Backup the entire physical server file system with these exceptions. Do not follow symbolic links Do not backup /proc Do not backup /tmp Do not backup /mnt Do not backup mounted file systems, only the local ones Now perform private server backups as described in Backing Up Private Servers on page -6. Selective Backup of Physical Server This option allows you to backup size and backup times by reducing the amount of data that is backed up. Caution: You should NOT follow or modify this process if you have made any customization to the base OS, beyond those made by Ensim. If you have not modified the base OS distribution you need to only backup the following: /etc/ssh2/hostkey and /etc/ssh2/hostkey.pub /etc/serverxchange /var/log/vkman.log /ServerXchange/vpses/* - Do not follow symbolic linksidentify each private server local install root, and do not follow symbolic links: Next, identify each private server local install root, and again do not follow symbolic links: /ServerXchange/filesys/<local_install_root> /ServerXchange/filesys/<local_install_root>/alreadyMounted /ServerXchange/filesys/<local_install_root>/pool Private Server and Physical Server Backup and Restoration - PPS c 16

21 Backing Up Physical Servers and All Its Private Servers /ServerXchange/filesys/<local_install_root>/vpses/*/vnkBuilt /ServerXchange/filesys/<local_install_root>/vpses/*/info/* /ServerXchange/filesys/<local_install_root>/vpses/*/treeroot/* It is also possible to find the local_install_root by examining the output of ls la/ ServerXchange/vpses. If possible, set the backup software to not cross filesystem boundaries, and be sure to exclude the following directories from the backup: /proc /tmp /var/spool Physical server backup examples On a physical server, we have two local private servers 61 and 62 as well as two NFS private servers 63 and 64 installed. For the local private servers, we assume the installation directory of /usr/ensim. Here are the commands we can use with tar to backup the servers: # TAR THE BASE SERVERXCHANGE FILES # tar cvzf sxbase-backup.tgz -C / /etc/ssh2/hostkey /etc/ ssh2/hostkey.pub /etc/serverxchange /var/log/vkman.log \ /var/log/serverxchange /ServerXchange/vpses /ServerXchange/ filesys/usrensim \ /usr/ensim/pool /usr/ensim/alreadymounted /usr/ensim/vpses/ */info \ /usr/ensim/vpses/*/vnkbuilt # TAR EACH PRIVATE SERVER FILE SYSTEM # tar czvlf vps-62-backup.tgz -C / /usr/ensim/vpses/62/ treeroot # tar czvlf vps-61-backup.tgz -C / /usr/ensim/vpses/61/ treeroot Or, you can also use the following to tar all the private server file system: # tar czvlf vps-backup.tgz -C / /usr/ensim/vpses/*/treeroot Private Server and Physical Server Backup and Restoration - PPS c 17

22 Backing Up Physical Servers and All Its Private Servers Now perform one of the private server backup methods described in Backing Up Private Servers on page -6. Recovering from a Physical Server Failure Assume registered and installed physical server A has failed. Install and register (via OpCenter) new physical server B. Change the physical server B network information to match physical server A. In other words, change the IP address and hostname to match A. This must be done manually (netconf), not through the ControlCenter. Restore the base files backed up from physical server A onto physical server B. Run the script located in the physical server to create the loopback file systems and restore the private server file systems (see example below). Restart physical server B. If the physical server B was registered and installed from the ControlCenter, you must use OpCenter to disable the physical server and then remove it from the ControlCenter. Since the network information on the physical server was already changed, this effectively does nothing beyond cleaning the ControlCenter's database. Private Server and Physical Server Backup and Restoration - PPS c 18

23 Recovering Physical Servers With All Private Servers Question: How does this handle the box ID in the database? Answer: It is in /etc/serverxchange/box.id which is already tar-ed in sxbase-backup.tgz. Recovering Physical Servers With All Private Servers If, for any reason a physical server fails follow these steps to recover. Full Restore From Full Backup Use the following method when you have recovery hardware identical to the production server and your backup method is from Full Backup of a Physical Server on page -16. Restore your complete backup on the recovery server, and reboot. Restore individual private servers from the private server backup volumes created in Options for Private Server Backups on page -7. Note: Make sure your failed server remains off line or you will have conflicting IP addresses. Restore From Selective Backup Use this method of restore when you have followed the backup procedure in Full Backup of a Physical Server on page -16. To help create this scenario, assume that registered and installed physical server A has failed. Install and register a new physical server B. Change the physical server B network information to match physical server A. In other words, change the IP address and hostname to match A. This must be done manually (netconf), not through the ControlCenter. Restore the base files backed up from physical server A onto physical server B. Run the script located in the physical server to create the loopback file systems and restore the private server file systems (see example below). Restart physical server B. It will not assume the identity of physical server A. Private Server and Physical Server Backup and Restoration - PPS c 19

24 Recovering Physical Servers With All Private Servers If physical server B was registered and installed from the ControlCenter, you must use OpCenter to disable and remove physical server B from the ControlCenter. Since the network information on the physical server was already changed, this effectively does nothing beyond cleaning the ControlCenter s database. Example of a Physical and Private Server Recovery After you have completed the steps listed in section 3 (the first 3 steps), and assuming we have separate.tar files for each private server and have copied them to the physical server, here is what you do: # UNTAR THE BASE SERVERXCHANGE FILES # tar xzvpf sxbase-backup.tgz -C / # CREATE THE TREEROOT DIRECTORY FOR THE CREATE_FILESYS SCRIPT # mkdir /usr/ensim/vpses/61/treeroot # CREATE AND MOUNT THE PRIVATE SERVER FILE SYSTEM # /ServerXchange/vkman/bin/create_filesys /usr/ensim/vpses/ /usr/ensim # UNTAR THE PRIVATE SERVER FILES INTO THE NEW FILE SYSTEM # tar xzvpf vps-61-backup.tgz -C / usr/ensim/vpses/61/ treeroot/ # CREATE THE TREEROOT DIRECTORY FOR THE CREATE_FILESYS SCRIPT # mkdir /usr/ensim/vpses/62/treeroot # CREATE AND MOUNT THE PRIVATE SERVER FILE SYSTEM # /ServerXchange/vkman/bin/create_filesys /usr/ensim/vpses/ /usr/ensim # UNTAR THE PRIVATE SERVER FILES INTO THE NEW FILE SYSTEM # tar xzvpf vps-62-backup.tgz -C / usr/ensim/vpses/62/ treeroot/ # RESTORE PRIVATE SERVER INFO FILES # tar xzvpf sxbase-backup.tgz -C / usr/ensim/vpses/61/info # tar xzvpf sxbase-backup.tgz -C / usr/ensim/vpses/62/info # shutdown -r now Private Server and Physical Server Backup and Restoration - PPS c 20

25 For Further Reading For Further Reading Download the Ensim CLI for Linux or Solaris from your ControlCenter Administration GUI. Refer to the ServerXchange Users Guide chapter entitled: Using Command Line Interfaces. Ensim Support Site You need an Account ID and password to access the following documents at: ServerXchange Users Guide Using the CLI ServerXchange Physical Server Technical Guide Automating ServerXchange Processes Ensim WEBppliance Forums Ultimate.cgi?action=intro Publications Private Server and Physical Server Backup and Restoration - PPS c 21