make_sys_image

[Jacques Carriere]

Q1 - How dangerous is to run the "make_sys_image" command on a client to create the image.
Q2 - is it better to run the command to dump the image directly on my ignite server.
eg.
On client:
#make_sys_image -s local
or
#make_sys_image -s Ignite_server
-d /var/opt/ignite/archives/Rel.11.11

Q3-If I run make_net_recovery on the client to create an image on the Ignite server, can this iamge be used to boot the client using
boot lan.IP_of_Ignite_server

thanks

Jacques

[Steven E. Protter · Accepted solution]

Shalom,

1) On an active, production system its extremely dangerou because it makes key networking files and /etc/passwd disappear while in progress. However if called with make_tape_recovery or make_net_recovery its perfectly benign.
2) I use a combination of the commands, with a -s and -d in the single command line. This is possible but can definitely cause the issue I mentioned in item 1 above.
3) Yes. There are conditions necessary to make it work and it won't work well or at all taking say an rx2620 server and trying to restore it to an rx6660 box.

SEP

[Jacques Carriere]

In Q2 only the client is affected and not the Ignite server, correct?

[IT_2007]

1. It is ok as long as you won't interrupt the process. It will replace network and other key files during backup and will be restored once process is completed.

2. Always safe to run locally and then copy to Ignite server. Because for any reason, process gets hung, you don't have choice to kill it and which will cause losing server (client) network and other key files.

3. Yes. You can use it as long as you properly configured Ignite server.

[Jacques Carriere]

In Q2, with Ignite server specified , only the production client is affected and not the Ignite server, correct?

[Jacques Carriere]

With make_net_recovery, the image is copied to the Ignite server in /ignite/S1/207-01-08,07:36 (where S1 is the client server).

Q4- Can this image be converted to the same format created by "make_sys_image".
eg. S1.gz

[IT_2007]

In Q2, with Ignite server specified , only the production client is affected and not the Ignite server, correct?

yes. correct.

[IT_2007]

With make_net_recovery, the image is copied to the Ignite server in /ignite/S1/207-01-08,07:36 (where S1 is the client server).

Q4- Can this image be converted to the same format created by "make_sys_image".
eg. S1.gz

No. It won't convert to zipped format. Even if you convert manually, then it won't work during recover process.

[Jacques Carriere]

thanks