checking the status of ignite backup

[Swetha Lakshmi]

Hi,

Could anyone help me out, how to check that the ignite backup got successfully completed ?

Thanks in advance

[VK2COT · Accepted solution]

Hello,

Some of options:

a) Log files in /var/opt/ignite/...
directories are always the simplest
option.

b) Refer to the following commands:

check_tape_recovery
check_net_recovery

c) In reality, the paranoid ones go for
full test restore as well.

Cheers,

VK2COT

[Swetha Lakshmi]

Thanks for your response.

I followed the same which u guided me but i found in those logs like

======= 12/30/08 12:19:01 IST make_tape_recovery completed unsuccessfully

being created will be incomplete. As result, the archive cannot
be used for recovering the system. If running this command in the
unstable network connection, you may consider running it in the
background using nohup (1M) to allow it to continue to completion
even if your network connection drops.

Could you pls help me, for that reason this backup got failed..

[Sagar Sirdesai]

Hi,
Please provide entire log file.
Then we can let you why it failed

Sagar

[sujit kumar singh]

Hi,


Shweta it seems that there had been a network failure of something that does with the connectivity of the Ignite server with the client.

seems that u had tried doing a network archive using make_net_recovery.

U can again try doing the same that by making another archive as it is evident that the current archive is not useful that is u woont be able to use this archive for restoration.

u can do the same with the GUI of ignite or u can give the following commands.

1) for making a network archive:
give this command on the Client that is the machine u want to take an ignite backup of.
#make_net_recovery -v -x inc_entire=vg00 -s -d &

make sure that the Directory on the ignite server that u give in the above command is NFS exported by the IGnite server and has got the permiossions for the client to write.

make cross entries for the clients entries in /etc/hosts and /.rhosts files.

edit the /etc/exports file properly on the Ignite server with the proper rights for the client or u can simply put in /etc/exports as

/var/opt/ignite/clients -anon=2
/var/opt/ignite/archives -anon=2

and export the same before executing the make_net_recovery from the client or executing the net recovery for the client from the IG-UX GUI on the Ignite server.
2)for making a Tape archive u can use
#make_tape_recovery -v -x inc_enitre=vg00 -a /dev/rmt/0mn &

note:
1)/dev/rmt/0mn is the Device file of the Tape Drive in ur system which u can get using ioscan -fnCtape
2)the & in both the commands tells the Ignite backup to work in the background that is even if the terminal from which u run the command gets closed the backup shall continue to run in the background.

all the logs for the Ignite activities for a local archiving can be found in the file /var/opt/ignite/recovery/archives/latest for a client and that on the ignite server as /var/opt/ignite/clients/0xLLA/recovery/ directory.

[VK2COT]

Hello,

Sujit KUmar gave you a nice response.

Either your make_net_recovery command
was interrupted by some network problem,
or someone killed it accidentally?

Check your network performance (just in case)
and then repeat the Ignite command. It is simple and it should work.

By the way, do you have any network
errors or collisions. Run:

netstat -in

Are your network interfaces running at
correct speed, duplex mode and negotiation?

Finally, do the same on your remote
Ignite server and check NFS performance as well. Remember, Ignite uses NFS when make_net_recovery is run...

Cheers,

VK2COT

[Swetha Lakshmi]

Thanks for all for spending ur precious time to solve this.