Re: using make_tape_recovery to clone a system

Hi Stevo,
I think you have a problem with tape on DR server. Have you tried to swap
tape from production server to DR server?
Make_tape_recovery it s ok. (usually I use make_tape_recovery -Av -a
device_files)
You can try to boot from a installation dvd or cd, Release C.6.1.44 is
availlable on dec 2004 of igniteux, and restore using disk as boot device
and tape for recover.
Check for hardware problem on your tape on DR server.


Regards

Antonio



"Stevo" <steven.robbins@xxxxxxxxx> ha scritto nel messaggio
news:1178862635.964245.89400@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 11, 3:34 pm, Stevo <steven.robb...@xxxxxxxxx> wrote:
Hi,

I'm not sure if I am using the right tool for this so any advice will
be appreciated.

Currently I have 2 x rp3440 one in production and the other to be used
as a DR. The production system is mirrored and the DR will not be.

I am trying to setup the DR server by doing the following:

- Take a system image of the current production server using
make_tape_recovery
- Load image onto DR server
- Dump and restore an informix database from the production to the DR
server

I am not able to boot off the DR server's disks after booting off the
tape.

What do I need to do to make the tape bootable?

Below is the output I get:

---------------------------

ngnems# make_tape_recovery -v -a /dev/rmt/1mn -x inc_entire=/dev/vg00
* Creating local directories for configuration files and
archive.

======= 05/11/07 13:04:15 EST Started make_tape_recovery. (Fri May
11
13:04:15 EST 2007)
@(#) Ignite-UX Revision C.6.1.44
@(#) net_recovery (opt) $Revision: 10.672 $

* Testing for necessary pax patch.
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/1mn

* Number of Archives to Save = 2

* Pax type = tar

In? dsk/vg name minor# Associated
disks/mountpoints
2 v /dev/vg00 0x00 /dev/dsk/
c4t0d0 /dev/dsk/c5t0d0
/dev/vg00/stand /
stand 2
/dev/vg00/swap
/dev/vg00/
root / 2
/dev/vg00/home /
home 2
/dev/vg00/opt /
opt 2
/dev/vg00/tmp /
tmp 2
/dev/vg00/usr /
usr 2
/dev/vg00/var /
var 2
0 v /dev/vg01 0x01 /dev/dsk/
c4t2d0 /dev/dsk/c5t2d0
/dev/vg01/ems /
ems 0
/dev/vg01/tools /
tools 0
/dev/vg01/
reports /reports0
/dev/vg01/data /
data 0
/dev/vg01/DBdbspe1_1G
/dev/vg01/DBdbsp2_1G
/dev/vg01/pmsp1_2G
/dev/vg01/pmsp2_2G
/dev/vg01/pmsp3_2G
/dev/vg01/pmsp4_2G
/dev/vg01/pmsp5_2G
/dev/vg01/pmsp6_2G
/dev/vg01/pmsp7_2G
0 v /dev/vg02 0x02 /dev/dsk/
c4t1d0 /dev/dsk/c5t1d0
/dev/vg02/DBdbsp1_1G
/dev/vg02/pmsp8_2G
/dev/vg02/pmsp9_2G
/dev/vg02/pmsp10_2G
/dev/vg02/pmsp11_2G
/dev/vg02/pmsp12_2G
/dev/vg02/pmsp13_2G
/dev/vg02/pmsp14_2G
/dev/vg02/DBdbsp3_1G
/dev/vg02/pmsp15_2G
/dev/vg02/pmsp16_2G
/dev/vg02/pmsp17_2G
/dev/vg02/pmsp18_2G
/dev/vg02/pmsp19_2G
/dev/vg02/pmsp20_2G
/dev/vg02/pmsp21_2G
0 v /dev/vg03 0x03 /dev/dsk/
c4t3d0 /dev/dsk/c5t3d0
/dev/vg03/DBdbsp4_1G
/dev/vg03/DBdbspe2_2G
/dev/vg03/pmsp22_2G
/dev/vg03/pmsp23_2G
/dev/vg03/pmsp24_2G
/dev/vg03/pmsp25_2G
/dev/vg03/pmsp26_2G
/dev/vg03/pmsp27_2G
/dev/vg03/pmsp28_2G
/dev/vg03/DBdbsp5_2G
/dev/vg03/dump /var/
adm/crash 0
/dev/vg03/DBnbsp1_2G

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in
the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2007-05-11,13:04/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

* Backing Up Volume Group /dev/vg01
* /usr/sbin/vgcfgbackup /dev/vg01
* Creating Map Files for Volume Group /dev/vg01
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg01.mapfile /dev/vg01

* Backing Up Volume Group /dev/vg02
* /usr/sbin/vgcfgbackup /dev/vg02
* Creating Map Files for Volume Group /dev/vg02
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg02.mapfile /dev/vg02

* Backing Up Volume Group /dev/vg03
* /usr/sbin/vgcfgbackup /dev/vg03
* Creating Map Files for Volume Group /dev/vg03
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg03.mapfile /dev/vg03

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/bin/make_arch_config -c
/var/opt/ignite/recovery/2007-05-11,13:04/archive_cfg -g
/var/opt/ignite/recovery/2007-05-11,13:04/flist -n
2007-05-11,13:04 -r
64 -d Recovery\ Archive -t -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
* Checking configuration file for Syntax
Adding /opt/ignite/Version file to LIF.
* Writing boot LIF to tape
48215+0 records in
48215+0 records out
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/1mn -
t n -s
local -n 2007-05-11,13:04 -m t -w
/var/opt/ignite/recovery/2007-05-11,13:04/recovery.log -u -R -
g
/var/opt/ignite/recovery/2007-05-11,13:04/flist -a 2772590

* Preparing to create a system archive.

* Archiving contents of ngnems via tar image to local device/
dev/rmt/1mn.
* Creation of system archive complete.
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the backup:
/var/opt/osiam/mbx/FTR24889
/var/opt/osiam/mbx/FTR24694
/var/tmp/ign_configure/make_sys_image.log

* Cleaning up old configuration file directories

======= 05/11/07 13:14:05 EST make_tape_recovery completed
successfully!
ngnems# mt -f /dev/rmt/1mn rewind

-------------------------------------------------------------------------------
Below is the boot from tape and then it cannot find a bootable drive
-------------------------------------------------------------------------------

Configuration Menu: Enter command > bo p7
Interact with IPL (Y, N, or Cancel)?> n

Booting...
Boot IO Dependent Code (IODC) revision 3

HARD Booted.

ISL Revision A.00.44 Mar 12, 2003

ISL booting hpux (;0):INSTALL

Boot
: tape(0/4/1/1.1.0.0.0.0.0;0):WINSTALL
11751424 + 1970264 + 2631464 start 0x200d68

alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3e900000.
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: nfs3_link(): File system was registered at index 4.
NOTICE: autofs_link(): File system was registered at index 6.
NOTICE: cachefs_link(): File system was registered at index 7.
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0
iether1: INITIALIZING HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-
T Adapter
at hardware path 0/3/1/0/4/0
iether2: INITIALIZING HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-
T Adapter
at hardware path 0/3/1/0/4/1
iether3: INITIALIZING HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-
T Adapter
at hardware path 0/3/1/0/6/0
iether4: INITIALIZING HP AB545-60001 PCI/PCI-X 1000Base-T 4-port 1000B-
T Adapter
at hardware path 0/3/1/0/6/1

System Console is on the Built-In Serial Interface
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - no room
WARNING: no swap device configured, so dump cannot be defaulted to
primary swap.
WARNING: No dump devices are configured. Dump is disabled.
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors:
CUPI80_BL2000_1108 -c 'V
w for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108
'CUPI80_BL2000_1108' Wed
Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 6289408 Kbytes, lockable: 4776588 Kbytes, available:
5504796 Kbyte
s

======= 05/10/07 10:27:07 EDT HP-UX Installation Initialization.
(Thu May 10
10:27:07 EDT 2007)
@(#) Ignite-UX Revision C.6.1.44
@(#) install/init (opt) $Revision: 10.303 $
* Scanning system for IO devices...
* Querying disk device: 0/4/1/0.0.0 ...
* Querying disk device: 0/4/1/0.1.0 ...
* Querying disk device: 0/4/1/0.2.0 ...
* Querying disk device: 0/4/1/0.3.0 ...
* Querying disk device: 0/4/1/0.4.0 ...
* Querying disk device: 0/4/1/0.5.0 ...

-------------------------------------------------------------------------------

In addition to the last capture I recieve the following message:

ERROR: Cannot open source device: /dev/rmt/0m: No such device or
address
(errno = 6).

Not sure why this is not visible.



.

Relevant Pages

  • using make_tape_recovery to clone a system
    ... The production system is mirrored and the DR will not be. ... What do I need to do to make the tape bootable? ... Number of Archives to Save = 2 ... Creating System Configuration. ...
    (comp.sys.hp.hpux)
  • Re: using make_tape_recovery to clone a system
    ... The production system is mirrored and the DR will not be. ... What do I need to do to make the tape bootable? ... Number of Archives to Save = 2 ... Creating System Configuration. ...
    (comp.sys.hp.hpux)
  • Re: backup tool
    ... that I have to restore the tape to an almost-the-same server ... configuration. ... My server is 3 years old now and it is not on the ...
    (microsoft.public.exchange.admin)
  • ntbackup bug between 2003 and XP Pro
    ... I'm new to the list so I hope we can also post XP/2003 Server issues ... If you try to use a tape created in 2003 Server RTM in XP Pro SP1 it will ... Verify the data is there by doing a test restore. ...
    (NT-Bugtraq)
  • Re: Disaster Recovery Plan
    ... preferable to restoring a master tape, ... Server and a HP tape drive. ... Attend a course taught by an expert instructor with years of in-the-field ...
    (Security-Basics)