Restore Data - IRIX File System iDataAgent - Full System Restore

Topics | How To | Full System Restore | Related Topics

Overview

Perform a Full System Restore

Overview

The difference between a normal restore and a full system restore is the severity of the problem. Normally, if data is lost or removed, it is recovered from the archives using the normal restore procedures. However, when a normal restore operation cannot correct a software and/or hardware corruption problem, some additional changes may be required.

When the root file system is lost, a full system restore is required.

Perform a Full System Restore

Before You Begin

This procedure includes the following general steps to create and test a bootable disk for a full system restore. Detailed instructions are provided in the following section.

  1. Create a system (bootable) disk from IRIX.
  2. Create and mount a root file system on the system that you want to restore.
  3. Use the IRIX File System iDataAgent to restore your data.
  4. Verify that the restore has successfully completed.
  5. Test the system disk that you created; ensure that the IRIX File System iDataAgent is installed on this disk.
  6. From this disk, use the IRIX File System iDataAgent to restore your data.

  • Try to avoid the unconditional overwrite of the root directory on a live file system. This is a mechanism that allows an unconditional overwrite of open files in the root directory (/) on a live file system. Performing such a restore can result in an inconsistent system that may also fail to boot. Use this option AT YOUR OWN RISK.

  • For information on creating a system disk from IRIX, see IRIX 6.5: Administration Guide – Performing Disk Administration.

To perform a full system restore:

  1. To start creating a system disk from IRIX, issue the hinv command to determine the controller and drive address of the disk to be converted to a system disk. For example:

    # hinv -c disk

    Integral SCSI controller 0: Version QL1040B (rev. 2), single ended
      Disk drive: unit 1 on SCSI controller 0
      Disk drive: unit 3 on SCSI controller 0
    Integral SCSI controller 1: Version QL1040B (rev. 2), single ended
      Disk drive: unit 2 on SCSI controller 1
  2. Issue the fx command in the expert mode to create bootinfo, repartition the disk (e.g., replicate the partitions on the original root drive) and label the new disk.
    This procedure destroys all data on the disk.

    Answer the prompts with the correct controller number and drive address for the disk you are converting and 0 for the Logical Unit Number (LUN).

    The following example shows you how to create a new system disk located on controller 0, drive 3, LUN 0.

    # fx -x 'dksc(0,3,0)'      [Enter]

    fx version 6.5, Oct 10, 2002
    ...opening dksc(0,3,0)
    ...drive selftest...OK
    Scsi drive type == SEAGATE ST32171W SUN2.1G7462

    ----- please choose one (? for help, .. to quit this menu)-----
    [exi]t             [d]ebug/           [l]abel/           [a]uto
    [b]adblock/        [exe]rcise/        [r]epartition/
    fx> l/cr/a    [Enter]

    ...creating default bootinfo
    ...created default partitions, use /repartition menu to change ...creating default sgiinfo
    ...creating default volume directory

    ----- please choose one (? for help, .. to quit this menu)-----
    [exi]t             [d]ebug/           [l]abel/           [a]uto
    [b]adblock/        [exe]rcise/        [r]epartition/
    fx> r/o       [Enter]

    fx/repartition/optiondrive: type of data partition = (xfs) [Enter]
    Warning: you will need to re-install all software and restore user data from backups after changing the partition layout.  Changing partitions will cause all data on the drive to be lost.  Be sure you have the drive backed up if it contains any user data.  Continue? Yes  [Enter]

    ----- please choose one (? for help, .. to quit this menu)-----
    [exi]t             [d]ebug/           [l]abel/           [a]uto
    [b]adblock/        [exe]rcise/        [r]epartition/
    fx> r/e       [Enter]

    Enter .. when done
    fx/repartition/expert: change partition = (0) 8 [Enter]
    before:  type volhdr     block       0,         0 MB
                             len:     4096 blks,    2 MB
    fx/repartition/expert: partition type = (volhdr) [Enter]
    fx/repartition/expert: base in megabytes = (0) [Enter]
    fx/repartition/expert: size in megabytes (max 2030) = (2)32   [Enter]
     after:  type volhdr     block       0,         0 MB
                             len:    65536 blks,   32 MB

    Continue the repartitioning of the disk until it is complete. The following fx command will display the defined partitions.

    fx> l/sh/part 

    ----- partitions-----
    part  type        blocks            Megabytes   (base+size)
      0: xfs      131072 + 4026129       64 + 1966
      1: raw       65536 + 131072        32 + 64  
      8: volhdr        0 + 65536          0 + 32  
     10: volume        0 + 4157201        0 + 2030

    ----- please choose one (? for help, .. to quit this menu)-----
    [exi]t             [d]ebug/           [l]abel/           [a]uto
    [b]adblock/        [exe]rcise/        [r]epartition/
    fx>
    fx> exi       [Enter]
    label info has changed for disk dksc(0,3,0).  write out changes? (yes)      [Enter]
     

  3. Issue the dvhtool command to examine the contents of the volume header of the disk to be converted.  Then add the stand-alone shell (sash) to its volume header if it is not there already. 

    # dvhtool -v list /dev/rdsk/dks0d3vh 

    Current contents:
            File name        Length     Block #
            sgilabel            512           2
            mr             18688000           3
            sash             266240       36503
            sashARCS         343040       37023

     

    To add the stand-alone shell (sash), use the dvhtool command and the Unix prompt:

    # dvhtool -v add /stand/sash sash /dev/rdsk/dks0d3vh        [Enter]

     

    We now have a disk that is bootable.
     

  4. To start creating the data partition disk, make a root filesystem on the root partition of the disk you are converting.  For example:

    mkfs /dev/dsk/<DriveID>
     

    Where <DriveID> is the Drive Identifier of the partition containing the root file system.
     

  5. Mount the new root file system at /mnt by entering the following command:

    mount /dev/dsk/<DriveID> /mnt
     

    Where <DriveID> is the Drive Identifier of the partition containing the root file system.
     

  6. From the CommCell Console, right-click the backup set that contains the backup data of the root file system, click All Tasks, click Restore, and type / as the path to restore from.
    Do not select Unconditional Overwrite from the Restore Options dialog box.
  7. Write to the newly created disk (e.g.,  /mnt).
  8. When restoring encrypted data, refer to Data Encryption.
  9. Start the restore operation.
  10. Verify that the restore operation has completed successfully.
  11. To start testing the new system disk, begin by shutting down the system to the PROM Monitor.
  12. Bring up the Command Monitor by choosing the fifth item on the System Maintenance menu.
  13. Boot the system on the new disk as described in this example:

    >> boot –f dksc(0,3,8)sash [Enter]
    # boot –f dksc(0,3,0)unix root=dks0d3s0     [Enter]
     
  14. If the IRIX File System iDataAgent is not part of the new disk, or if it is not installed on another disk on your system, be sure to install the IRIX File System iDataAgent from the installation disc. 
    Whenever you install the IRIX File System iDataAgent on a new disk, you must first DeConfigure your iDataAgent from the CommServe in order to release the license that is still consumed from the original install. You must also install the iDataAgent with the exact client information that was used originally. If you do not do this, the old backups will not be available to the new client.
  15. Use the IRIX File System iDataAgent to restore your data.

 

Back To Top