Disk Information

An additional precautionary step to help you recover from loss of critical data: before a disaster strikes is to find out how each disk on your network is partitioned and formatted and print and save this information. If a disk is damaged or destroyed during a disaster, use the disk information to recreate the disk exactly as it was prior to the disk crash. Do the same for each system Backup backs up, unless the systems are consistent in disk and filesystem layout.

Caution - When you recreate your disk configuration, you need to have partitions large enough to hold all the recovered data. Make the partitions at least as large as they were before to the crash.

Use the dfcommand to find out how the Backup server disks are partitioned and mounted. Use the appropriate operating system command to print disk partitioning information. Do the same for any Backup clients that have local hard disks. For example, the df -kinformation looks similar to this:

Filesystemkbytesusedavail capacityMounted on
/dev/dsk/c0t3d0s086567862402015509880%/
/dev/dsk/c0t1d0s62658071987294049883%/usr
/dev/dsk/c0t1d0s496103574682902566%/var
swap10775681077480%/tmp The following dkinfocommand examples give you information about how each disk is partitioned for a SunOS system:

% dkinfo sd0a
SCSI CCS controller at addr f8800000, unit # 24
1151 cylinders 9 heads 80 sectors/track
33120 sectors (46 cyls)
starting cylinder 0
% dkinfo sd0b
1151 cylinders 9 heads 80 sectors/track
197280 sectors (274 cyls)
starting cylinder 46

Solstice Backup 5.1 Disaster Recovery Guide

*April 1998

6