When I issue the command, it will prompt the CLEAN-LEVEL message(the first NOTE in the attachment) and hang, I wait for a while and issue CTRL-C, it will display the DISALLOW message(the second NOTE ) and start to work, but it will never end. In the vg00, there is a application installation SRC file system which has been exclued by adding a line in the EXCLUDE portion of /tmp/make_sys_image file. e.g. /app_install_src/* , is it the suggested way to exclude it? Here is the related info I have posted before: http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1254867714409+28353475&threadId=1374412
Thanks,
Stan
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
From your previous post it appears that you are using make_sys_image to create a tape on a different server from the one you are actually igniting. I would have said that it would be a far better thing to do to create the server with the tape drive into an ignite server and run make_net_recovery on all the servers you need to ignite backup, onto the server with the tape drive. This can then be used to recreate the servers in case of any crashes etc.
If this is not possble, I would be interested in seeing the actual command you input to start your make_sys_image.
/cdrom is just a mountpoint of a separate file system. I want to backup the system thru make_sys_image script. At first I tried to backup it by make_net_recovery but not succeeded. There is another file system (mounted at /app_install_src) in vg00 which is only the installation source of the application, we want to exclude it during the OS backup as it has no relationship with it.
The complete command is /tmp/make_sys_image -s local -d /cdrom
it is also listed in the attachment. At first I tried to place the image in the Ignite server by -s IP_of_IUX_Server, it completed with error because there wasn't enough space in NFS exported FS in the server. So I changed to place it in local FS and excluded a FS which isn't necessary for system recovery. It is strange that this command is always hanging.
It looks like putting /app_install_src/* in the LEVEL2_NO_ARCHIVE section of the script is supposed to work.
Not sure why the hang.
Just wondering why you are running 'make_sys_image' directly, most folks prefer 'make_net_recovery' to archive a client.
Things to try: - make_net_recovery instead - adding the -v option, see if you can find out what it is doing when it hangs - could unmount /app_install_src instead, see if better - make sure /cdrom really is a writable filesystem, the name sounds like media
It is true that I have placed EXCLUDE_FILES in LEVEL2_NO_ARCHIVE section. At the beginning I tried the make_net_recovery but failed for some reason. From yesterday we start to seek the possibility to backup the system thru any one of the following: 1. make_net_recovery, 2. Write to USB DVD 3. make_sys_image
BTW, I once tried the debug mode(added a line "set -x" into make_sys_image script), we have the command running in the background so that it it possible to monitor it even if it hang as we deliver the support by remote dial-in. Here is the complete command: /tmp/make_sys_image -s local -d /cdrom -v âL âw /cdrom/ig.txt &
this command will quit after the following message, the first portion of it were omitted:
+ (( LIF_BKUP_ONLY )) + backup_lif * LIF disk /dev/disk/disk1_p2 found, with contents: volume ISL10 data size 7984 directory size 8 09/01/11 13:49:28 filename type start size implement created =============================================================== ISL -12800 584 242 0 09/01/11 13:49:28 AUTO -12289 832 1 0 09/01/11 13:49:28 HPUX -12928 840 1024 0 09/01/11 13:49:28 PAD -12290 1864 1468 0 09/01/11 13:49:28 LABEL BIN 3336 8 0 09/07/15 03:23:25 + exit 0 + restore_keepsafe
Printable version
