Operating System - HP-UX
1834640 Members
3151 Online
110069 Solutions
New Discussion

make_recovery on non local tape drive

 
SOLVED
Go to solution
Franky Leeuwerck_2
Super Advisor

make_recovery on non local tape drive

Hi,

Only on the 1st of my 2 hp-ux systems there is a tape drive attached.

Can I make an Ignite make_recovery tape of system 2 using the tape drive on system 1 ?

Thanks in advance,
Franky
19 REPLIES 19
MarkSyder
Honored Contributor
Solution

Re: make_recovery on non local tape drive

No.

If you have sufficient disc space you can do a make_net_recovery, but ignite cannot write to remote tape drives.

Mark Syder (like the drink but spelt different)
The triumph of evil requires only that good men do nothing
Pete Randall
Outstanding Contributor

Re: make_recovery on non local tape drive

As Mark says, Ignite can not write to a remote tape drive. You can do a make_net_recovery and then dump that to tape. See Chapter 10 of the Ignite Administration Guide:

http://www.docs.hp.com/en/B2355-90997/ch10.html


Pete

Pete
Franky Leeuwerck_2
Super Advisor

Re: make_recovery on non local tape drive

Hi,


This is my diskspace on /var:
/dev/vg00/lvol8 2097152 1668536 425360 80% /var
/dev/vg00/lvol10 4194304 17496 3915765 0% /var/adm/crash

Because I am not sure how much space I need I try to use the mounted filesystem /osbu.
But as you see, there are errors.

# hostname
myHost
# make_net_recovery -s myHost -a myHost:/osbu
* Creating NFS mount directories for configuration files.
nfs mount: get_fh: myHost:: RPC: Program not registered
nfs mount: get_fh: myHost:: RPC: Program not registered
nfs mount: retry: retrying(1) for: /var/opt/ignite/recovery/client_mnt after 5 seconds
nfs mount: retry: giving up on: /var/opt/ignite/recovery/client_mnt
ERROR: Could not NFS mount directory /var/opt/ignite/clients on cnjinux2. The
exports file on myHost should contain the entry
"/var/opt/ignite/clients -anon=2". Ensure that /var/opt/ignite/clients
has been exported using the "exportfs -av" command.
ERROR: Failed mounting directory /var/opt/ignite/recovery/client_mnt:/No such
file or directory (errno = 2)
ERROR: Failed to create NFS mount directories for configuration files.

======= 09/27/06 16:02:00 EAT make_net_recovery completed unsuccessfully


Franky
MarkSyder
Honored Contributor

Re: make_recovery on non local tape drive

1. What size is the OS disc on the system you want to backup?

2. How much free space do you have on the other system? Preferably not on an OS disc - I have dedicated discs for network backups.

Mark
The triumph of evil requires only that good men do nothing
Franky Leeuwerck_2
Super Advisor

Re: make_recovery on non local tape drive

So, this are my further questions :

1) How many diskspace do I need for a make_net_recovery ?

2) Can I run it from the same server with the archive on a mounted file system ?

Franky
Franky Leeuwerck_2
Super Advisor

Re: make_recovery on non local tape drive

Hi Mark,

The vg00 contains about 10 GB :
# bdf | grep vg00
/dev/vg00/lvol3 524288 221392 300552 42% /
/dev/vg00/lvol1 524288 128200 393040 25% /stand
/dev/vg00/lvol8 2097152 1668496 425400 80% /var
/dev/vg00/lvol10 4194304 17496 3915765 0% /var/adm/crash
/dev/vg00/lvol7 5242880 2636240 2586344 50% /usr
/dev/vg00/lvol4 1048576 696536 349352 67% /tmp
/dev/vg00/lvol6 5242880 3454872 1774088 66% /opt
/dev/vg00/lvol5 1048576 19560 1020984 2% /home
#

The mounted /osbu can handle 48 GB.

Franky
MarkSyder
Honored Contributor

Re: make_recovery on non local tape drive

That should be enough to take an ignite backup of the other system. I would recommend the following:

1. Create a dedicated lvol for the backup. 10Gb will be enough if you only want to store a single backup of the other system; make it larger if you want two copies (e.g. at monthly intervals) or if there are other systems.

2. Export the new filesystem to the other system.

3. You will probably find the GUI version of ignite more user-friendly. It should be self-explanatory, but if you need any more help just ask.

Mark
The triumph of evil requires only that good men do nothing
Franky Leeuwerck_2
Super Advisor

Re: make_recovery on non local tape drive

Hi Mark,

The thing is, I don't have another system.
Can't I make the archive on a non vg00 file system that I can mount from a SAN ?

Franky
MarkSyder
Honored Contributor

Re: make_recovery on non local tape drive

Doesn't your first post refer to two systems?

If you only have one, you will need to find a tape drive to attach to it. It cannot do a make_net_recovery to itself: you would be unable to access the backup if the OS disc went down. And the OS disc going down is precisely the time you would need the backup.

Mark
The triumph of evil requires only that good men do nothing
Franky Leeuwerck_2
Super Advisor

Re: make_recovery on non local tape drive

Mark,

Thanks for the inputs.
The 1st system I referred too doesn't sufficient diskspace too.

But I could mount that SAN volume too it.
Would that work ?

How do I start make_net_recovery interactively ?

Thanks for the help.
Franky
NB : I am a DBA, not a unix sysadmin.
Franky Leeuwerck_2
Super Advisor

Re: make_recovery on non local tape drive

Mark,

Let me rephrase the question.

I would like to make a make_net_recovery archive of vg00 of system 2.

On system 1, I mounted a filesystem (from the SAN) for placing the archive file there.

Can you tell me what the command could like like for making that archive and from which machine should I run it : system 1 or system 2 ?

Franky
MarkSyder
Honored Contributor

Re: make_recovery on non local tape drive

If you want to backup system 2 you will run make_net_recovery from system 1. You should be able to backup to a SAN.

Login to system 1 and write a shell script consisting of the following:

DISPLAY=xx.xx.xx.xx:0.0
export DISPLAY
ignite

where xx.xx.xx.xx is the ip address of your PC (I'm assuming you're sitting at your PC to do this job). Run the script. It will give you the GUI version of ignite, which is very easy to follow and will guide you through what needs to be done - it is definitely better to use the GUI version if you are not a sys admin. Why make life difficult for yourself? The GUI version is made for people like you (and me!).

Good luck - and just ask if you have any more questions.

Mark
The triumph of evil requires only that good men do nothing
Franky Leeuwerck_2
Super Advisor

Re: make_recovery on non local tape drive

Mark,

Can we proceed with the command version ?
The interactive Ignite session might not be a good idea. My systems are about 10000 miles away from and the connection is not too well.

I want to backup System2.

I have mounted a SAN filesystem /osbu on System1.

I have created an archive directory on the latter filesystem :
# mkdir -p /osbu/recovery/archives/System2
# chown bin:bin /osbu/recovery/archives/System2/

On System1, I have exported the filesystem (as described in MAN) in a new exportfs file :
# cat /etc/exports
cat: Cannot open /etc/exports: No such file or directory
# vi /etc/exports
"/etc/exports" [New file] 1 line, 57 characters
# cat /etc/exports
/osbu/recovery/archives/System2 -anon=2,access=System2
# /usr/sbin/exportfs -av

Can you tell me what the following commands are for starting the make_net_recovery ?
I suppose these must be submitted on System1

Thanks,
Franky
MarkSyder
Honored Contributor

Re: make_recovery on non local tape drive

On system 2:

make_net_recovery -s System1 -a /osbu -x inc_entire=vg00

I've never used the command line version, but this is correct according to the man page.

Mark
The triumph of evil requires only that good men do nothing
Franky Leeuwerck_2
Super Advisor

Re: make_recovery on non local tape drive

Mark,

I launched the command on System2 and this is the result :
# make_net_recovery -s cnjinux1 -a cnjinux1:/osbu -x inc_entire=vg00
* Creating NFS mount directories for configuration files.
nfs mount: get_fh: System1:: RPC: Program not registered
nfs mount: get_fh: System1:: RPC: Program not registered
nfs mount: retry: retrying(1) for: /var/opt/ignite/recovery/client_mnt after 5 seconds
nfs mount: retry: giving up on: /var/opt/ignite/recovery/client_mnt
ERROR: Could not NFS mount directory /var/opt/ignite/clients on cnjinux1. The
exports file on System1 should contain the entry
"/var/opt/ignite/clients -anon=2". Ensure that /var/opt/ignite/clients
has been exported using the "exportfs -av" command.
ERROR: Failed mounting directory /var/opt/ignite/recovery/client_mnt:/Error 0
(errno = 0)
ERROR: Failed to create NFS mount directories for configuration files.

======= 09/27/06 18:28:18 EAT make_net_recovery completed unsuccessfully
#

I see the command is looking for a directory /var/opt/ignite/recovery/... .
Is there something missing ?

Franky
MarkSyder
Honored Contributor

Re: make_recovery on non local tape drive

You should have a directory called /var/opt/ignite/recovery on System1. Make sure it is included in /etc/exports in the form shown in the error message then run exportfs -av. You should be able to see the directory being exported.

Mark
The triumph of evil requires only that good men do nothing
Franky Leeuwerck_2
Super Advisor

Re: make_recovery on non local tape drive

Mark,

There was already an recovery directory on the system.
I exported it :
# cat /etc/exports
/osbu/recovery/archives/System2 -anon=2,access=System2
/var/opt/ignite/recovery -anon=2
#

I get the same errors when running the make_net_recovery on System2.
Is there something like a mount action that I should do ?
Franky
MarkSyder
Honored Contributor

Re: make_recovery on non local tape drive

I think we've exhausted my knowledge now. It might be best to raise a new thread for the NFS mount, cross-referring to this one: I suspect people with more ignite/NFS knowledge than I have may not have read this thread because there was a bunny alongside it. I always award points after a fault is fixed, for that very reason.

Mark
The triumph of evil requires only that good men do nothing
Franky Leeuwerck_2
Super Advisor

Re: make_recovery on non local tape drive

Hi Mark,

I understand the situation.
Thanks anyway .. I learned at least some new stuff.

Regards,
Franky