SRDB ID   Synopsis   Date
18060   How to backup and restore Alternate Pathing databases   18 Sep 2001

Status Issued

Description
When creating backup tapes for a full system disaster recovery on
a machine that has Alternate Pathing installed, it is not clear how
the AP databases can be backed up and recovered, as they reside on raw
disk slices.  There will be multiple copies (at least 3) of the databases.
Each one is unique and must be copied back to its original slice
upon the restore.  This is because each database holds data about its own 
location and the locations of all other copies. 
SOLUTION SUMMARY:
The following is a tested procedure that can be used to backup and
restore the AP databases.

Procedure
---------

Create the off-site disaster recovery backups. (at regular intervals)
----------------------------------------------
  o   shutdown applications and unmount all disks
      except the boot disk.
  	
  o  Create a directory on the boot disk: /backup
  
  o  In the /backup directory, make copies of /etc/vfstab, 
     /etc/system, VTOCs of all disk etc.
     
     Output of apconfig -D (database layout)
     
     Output of apconfig -S and -N (disk and network setup)
     
     Print out hard copies as well.
     
  o  Copy each AP data base into a file in this directory using dd.
      
     Each database is different, even when they are in sync,
     as they contain info about which slice they are in, and
     each one must be copied back to its original location.
     
     Example:  cd /backup
               dd if=/dev/rdsk/c0t0d0s4 of=apdb-c0t0d0s4
               
        GOTCHA ALERT: Don't use any slice 0 for apdb's and
        don't use huge slices!
       
               
  o  If there are AP network devices, rename the hostname.XX to
     be a real active interface.
     
     Example:
     	 mv hostname.mqe0 hostname.qe0
     	 
  o  Take the boot disk out of AP using the "apboot" command
     This modifies the /etc/system file and the vfstab (even takes care of swap) 
    
  o  Reboot (to be sure you can).
  
  o  Shutdown to single user.
  
  o  Backup all the file systems with a level 0 ufsdump.
  
  o  When finished, boot up to multi-user.
  
  o  Run apboot to AP the boot disk again.
  
  o  Move back hostname.xxx files.
  
  o  Uncomment the vfstab.
  
  o  Reboot.
  

Recovery
--------
  o  Perform the ufsrestores.
     
AP recovery
-----------
  o  copy back the apdb's to their proper location.
  
       Example:  cd /backup
       		 dd if=apdb-c0t0d0s4 of=/dev/rdsk/c0t0d0s4       		 
       		 
  o  reboot
  
  o  Check all is OK with acponfig -D etc.
  
  o  Move back hostname.xxx files.
  
  o  Uncomment the vfstab.
  
  o  Reboot.
  

If it all goes horribly wrong the system should be usable without
AP; just edit the vfstab is so that real devices are mounted.
Then AP can be set up again from scratch.

The disks that are being restored to must be identical in geometry to the 
originals for this procedure to work. If the disk are not identical then 
AP must be set up again from scratch after the recovery.

SUBMITTER: Christopher Maughan APPLIES TO: Hardware/Ultra Enterprise/Servers/Enterprise 10000, Operating Systems/Solaris/Solaris 2.x ATTACHMENTS:


Copyright (c) 1997-2003 Sun Microsystems, Inc.