Backup of Virtual Partitions


Backup of Virtual Partitions takes place in almost the same manner as in non-vPars systems. The primary difference is that rather than run one backup on a physical system, you'll have to run a backup of every Virtual Partition that exists on your physical system. You'll also want to run a make_net_recovery on every Virtual Partition as well. This will create a bootable recovery archive for the Virtual Partition. This is covered in the Ignite/UX Chapter 9.

We'll perform a backup of the first vPar on a system that has the tape drive configured as one of its components (this is a backup to a local tape drive). We'll then perform a backup of a second vPar on the same computer to the tape drive that is configured on the first vPar (this is a backup to a remote tape drive). The tape drive is remote to the second vPar because it does not have the tape drive configured as one of its I/O components . Since the two vPars are distinct and independent systems, the tape drive on the first vPar is remote to the second vPar.

Backup to a Tape Drive on the Local Virtual Partition

Let's now backup a vPar called cable1 to the local DDS drive at path 0.0.1.0.3.0. This is a backup of a vPar to a local tape drive, meaning that the tape drive resource is tied to the vPar for which the backup will be performed. The following vparstatus shows that the Local Bus Adapter (LBA) at 0.0 is dedicated to cable1 :

 #  vparstatus -p cable1 -v  [Virtual Partition Details] Name:         cable1 State:        Up Attributes:   Dynamic,Manual Kernel Path:  /stand/vmunix Boot Opts: [CPU Details] Min/Max:  1/3 Bound by User [Path]: Bound by Monitor [Path]:  33 Unbound [Path]:  97 [IO Details]    0.0  <-- path of Core I/O card  0.0.0.0    0.0.1.1.2.0  BOOT    0.0.4.0  CONSOLE [Memory Details] Specified [Base  /Range]:           (bytes) (MB) Total Memory (MB):  1024 # 

Although the tape drive at 0.0.1.0.3.0 does not appear in this vparstatus -v output, the tape drive is connected to the Core I/O card at 0.0 and is therefore accessible to cable1 to use as a backup device.

As a side note, if the tape interface were not on the Core I/O card, which is devoted to cable1 , we could move the interface from cable1 to a second vPar on the same computer called cable2 , confirm that the driver is in /stand/system , and then backup cable2

Since there are many devices that you may want to move among the vPars running on your system you want to make sure that you have all of the device drivers required to support these devices in your kernel.

Let's now run fbackup with u to update the backup database, for a full backup, f to specify the file to which we want to write the backup, g to specify our graph file, I to specify the name of the index file, and finally, we'll redirect messages to a file that will contain the backup log. We'll add the date and time to the end of the index and backup log files.

The following example shows the fbackup command issued:

  fbackup -0u -f /dev/rmt/0m -g /tmp/backupgraph -I   /tmp/backupindex.`date '+%y%m%d.%H:M'` 2>   /tmp/backuplog.`date '+%y%m%d.%H:%M'`  

Graph files are used to specify the files to be included in the backup. Index files contain a list of files produced as part of the backup. The graph file contains the files we wish to include ( i ) or exclude ( e ) as part of the backup. In our case the file contains only the following line:

 i /var/tmp 

Let's now see what files were produced as a result of having issued this command. First let's look at the backup index and backup log files:

[View full width]
 
[View full width]
# ls -l /tmp/backup* -rw-rw-rw- 1 root sys 11 Aug 29 14:45 backupgraph -rw------- 1 root sys 778 Aug 29 15:08 backupindex.010829.15:08 -rw-rw-rw- 1 root sys 521 Aug 29 15:08 backuplog.010829.15:08 # # cat /tmp/backupindex.010829.15:08 1024 1 / 1024 1 /var 1024 1 /var/tmp 108 1 /var/tmp/aaaa04686 1241 1 /var/tmp/ems_inittab.old 28 1 /var/tmp/envd.action2 28 1 /var/tmp/envd.action5 4106 1 /var/tmp/inetd.conf.old 96 1 /var/tmp/ntp 0 1 /var/tmp/rdskUBAa02185 0 1 /var/tmp/rdskWAAa01840 310 1 /var/tmp/sh1649.1 343 1 /var/tmp/sh1649.2 166 1 /var/tmp/sh1649.3 440 1 /var/tmp/sh1649.4 611 1 /var/tmp/swagent.log 0 1 /var/tmp/sysstat_em.fmt 22734848 1 /var/tmp/vmunix.noreloc # # cat /tmp/backupgraph i/var/tmp # # cat /tmp/backuplog.010829.15:08 fbackup(1417): cannot open the dates file /var/adm/fbackupfiles/dates for reading fbackup(1004): session begins on Wed Aug 29 15:08:10 2001 fbackup(3203): volume 1 has been used 1 time(s) fbackup(3024): writing volume 1 to the output file /dev/rmt/0m fbackup(1423): WARNING: could not open the dates file /var/adm/fbackupfiles/dates for graphics/ccc.gif writing fbackup(1030): warnings encountered during backup fbackup(3055): total file blocks read for backup: 44432 #

The two files with the date appended ( 8/29/01 time 15:08 ) to the end of the filename were produced by the fbackup command issued earlier. The date appended to the end of the file can help in the organization of backup files. We could restore any or all of these files with frestore .

The backup of vPar cable1 to the local tape drive is a backup of the system with a hostname of cvhdcon3 . The other vPar running on this system, cable2 , was not included in the backup because its host, cvhdcon4, is viewed as a separate system. In the next section we'll see how we would backup cable2 to the tape drive dedicated to cable1 .

Backup to a Tape Drive on a Different Local Virtual Partition

The tape drive in the preceding section was connected to cable1 and used to backup cable1 . Let's now backup cable2 with the tape drive as part of the cable1 Virtual Partition. Keep in mind that vPar cable2 with its hostname cvhdcon4 is a separate system from cable1 and its host name cvhdcon3 . We will, therefore, have to backup vPar cable2 to a remote tape drive on cable1 .

We will backup to a remote tape, connected to cable1 , with fbackup by specifying the system name and tape drive, or file, to which we want to store the files. The following example uses fbackup options. We are connected to cable2 and specify that it is to be backed up to the tape drive on cable1 (hostname cvhdcon3 .) The fbackup command below will perform the backup to the remote tape drive:

 #  fbackup -f cvhdcon3:/dev/rmt/0m -i /var/tmp -v  fbackup(1004): session begins on Wed Aug 29 16:09:28 2001 fbackup(3307): volume 1 has been used 6 time(s) (maximum: 100) fbackup(3024): writing volume 1 to the output file cvhdcon3:/dev/rmt/0m     1: /     2: /tmp     3: /tmp/.AgentSockets     4: /tmp/.AgentSockets/A     5: /tmp/X11_newfonts.log     6: /tmp/install.vars     7: /tmp/llbdbase.dat     8: /tmp/lost+found     9: /tmp/portmap.file    10: /tmp/rpcbind.file    11: /tmp/sd_ipd_acl.1417    12: /tmp/services    13: /tmp/swlist    14: /tmp/typescript fbackup(1005): run time: 17 seconds fbackup(3055): total file blocks read for backup: 141 fbackup(3056): total blocks written to output file cvhdcon3:/dev/rmt/0m: 0 # 

It takes a little getting used to running fbackup to a remote device even when the device is physically connected to the computer on which you're working. Since the two vPars are different hosts , however, it makes sense that a tape drive used by a different vPar would indeed be remote.

The fbackup runs over the network from cable2 to cable1 . This is one of the many reasons that you want to have a network card for every vPar on your system.

We would issue other remote backup commands as well. The following example shows running cpio on cable2 to the tape drive on cable1 (host name cvhdcon3 :)

 #  find . -print  cpio -oBv  (   remsh cvhdcon3 dd of=/dev/rmt/0m)  . lost+found .AgentSockets Socket <.AgentSockets/A> not backed up typescript install.vars swlist X11_newfonts.log sd_ipd_acl.1417 services rpcbind.file portmap.file llbdbase.dat 140 blocks 140+0 records in 140+0 records out # 

This command performs the backup of /tmp on vPar cable2 by sending the files to the tape drive on system cvhdcon3 (vPar cable1 .)



HP-UX 11i Systems Administration Handbook and Toolkit
HP-UX 11i Systems Administration Handbook and Toolkit (2nd Edition)
ISBN: 0131018833
EAN: 2147483647
Year: 2003
Pages: 301

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net