| 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, 0 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 logfiles: # 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 /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/fbackup- files/dates for 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. |