Step wise how to guide for Ignite tape backup. Includes media check commands, backup log analysis and troubleshooting steps.
Ignite is OS backup solution for HPUX. This tool is developed by HP and available under brand name Ignite-UX. Its used to take system backup like ghost image in case of Windows. Complete OS can be restored using ignite backup solution in case of any system failure. Ignite offers network backup solution and tape backup solution. In network backup, OS backup is stored on ignite server over network and in case of restore its restored over network only (System should be booted with PXE boot). In tape backup, OS backed up in locally connected tape drive and restoration happens by booting system through bootable tape.
One needs to install this utility since its not native to HPUX. You can check if its installed or not using below command :
# /usr/sbin/swlist -l product |grep -i ignite Ignite-UX C.7.12.519 HP-UX System Installation Services
If not installed, you need to purchase it and install on your HPUX machine.
In this post we will see how to take ignite tape backup along with its logs, troubleshooting and media check commands.
Media check :
Before starting your backup on tape you need to check if tape drive and media is functioning properly. After connecting your tape drive to system and powering it on, you can identify it using ioscan -fnCtape & insf -e command. Its device name should be something like /dev/rmt/0mn . Once you identify device name for tape you can check its status wit mt command:
# mt -t /dev/rmt/0mn status Drive: HP Ultrium 2-SCSI Format: Status:  BOT online compression immediate-report-mode File: 0 Block: 0
Once you are able to get status of media means tape drive is functioning properly and correctly identified in kernel. Now you can go ahead with backup procedure.
Taking ignite tape backup :
Ignite tape backup can be run using command make_tape_recovery. This binary resides in /opt/ignite/bin. This command supports list of options but we are seeing here most used ones :
- -A : Checks disks/volme group and adds files in backup which are specified for backup inclusion
- -v : Verbose mode
- -I : Cause the system recovery process to be interactive when booting from the tape.
- -x : Extra options (include=file|dir, exclude=file|dir, inc_entire=VG or Disk) define inclusion/exclusion of file/dir/vg/disk
- -a : tape drive address
- -d : Description which will be displayed for archive
- -i : Interactive execution
Since ignite is aimed at OS backup, normally we take VG00 i.e. root volume group’s backup only in Ignite tape backup. Lets see one example :
# /opt/ignite/bin/make_tape_recovery -AvI -x inc_entire=vg00 -a /dev/rmt/0mn -x exclude=/data ======= 12/27/16 03:00:00 EDT Started /opt/ignite/bin/make_tape_recovery. (Tue Dec 27 03:00:00 EDT 2016) @(#) Ignite-UX Revision B.4.4.12 @(#) net_recovery (opt) $Revision: 10.611 $ * Testing pax for needed patch * Passed pax tests. ----- output clipped -----
In above example, we have started ignite backup with all VG00 included (-x inc_entire=vg00), excluding /data mount point which is part of vg00 (-x exclude=/data), on tape drive at 0mn (-a /dev/rmt/0mn) with interactive boot menu in backup (-I). Verbose mode (-v) starts printing all outputs on terminal screen like shown above.
It takes normally half and hour or more to complete backup depending on size of your files included in backup. If your terminal timeout is short value then you can put this command in background (with below command) so that it wont get killed when your terminal timed out and disconnect.
# /opt/ignite/bin/make_tape_recovery -AvI -x inc_entire=vg00 -a /dev/rmt/0mn -x exclude=/data >/dev/null 2>&1
Dont worry all outputs are being logged to log file so that you can analyze it later. Last few lines of output are as below which
declares backups has been completed successfully.
----- output clipped ----- /var/tmp/ign_configure/make_sys_image.log /var/spool/cron/tmp/croutFNOa01327 /var/spool/cron/tmp/croutBNOa01327 /var/spool/cron/tmp/croutGNOa01327 * Cleaning up old configuration file directories ======= 12/27/16 03:12:19 EDT make_tape_recovery completed successfully.
You can even schedule a Ignite backup in crontab on monthly, weekly or daily basis depending on your requirement.
Log files :
Your latest run output is saved under /var/opt/ignite/recovery/latest/recovery.log. All other run’s details are saved under /var/opt/ignite/recovery directory. Whenever command runs it links latest directory to current run’s directory. See below output to get an idea.
# ll /var/opt/ignite/recovery total 14240 drwxr-xr-x 2 root root 8192 Nov 27 03:12 2016-11-27,03:00 drwxr-xr-x 2 root root 8192 Dec 27 03:12 2016-12-27,03:00 lrwxr-xr-x 1 root sys 16 Dec 27 03:00 latest -> 2016-12-27,03:00 ----- output clipped -----
If ignite fails then recovery.log is the first place to look for an reason of failure.
This part is really hard to cover since there can be numerous reason why Ignite fails. But let me cover few common reason here –
- Tape media is faulty (check EMS logs, syslog) Solution : mediareplacement
- Tape drive is faulty (check ioscan status, EMs, syslog) Solution : hardware replacement
- One or more VG exist in /etc/lvmtab but not active on system (verify /etc/lvmtab with bdf) Solution : Remove inactive VG from lvmtab or made them active on system
- One or more LVOLs exist in /etc/lvmtab but not active on system (verify /etc/lvmtab with bdf) Solution : Remove inactive lvol from lvmtab or mount them on system
- ERROR: /opt/ignite/bin/save_config failed : One of the system attached disk/lun is faulty. Solution : check hardware and replace.