HP-UX B.11.23 Itanium Ignite server restore file system issue.

[HP-UX TIM OSP]

I have an Itanium Ignite server(B.11.23) that I setup and used make_sys_image and created file .gz of another HP-UX Itanium B.11.23(client). When I used the ignite server to restore the image it created all the essential file systems( /, /usr,/var, etc...) except for the one file system that is not a standard one. It created a directory under root instead of creating the file system. How do I get the ignite server to create this file system during the restore and do I have to redo the make_sys_image again?
Thanks in advance.

[Mike Shilladay]

Hi Saptaji,

The ignite/UX will create all the filesystems it was instructed to do. If you have another non-standard filesystem you can always create a new lvol for it and create another ignite image (use the "-x inc_entire=vg00") to copy all the volume group.

To get Ignite/UX to recover this data as a filesystem you will you need to interact with Ignite, and select the filesystems tab, you can create a new filesystem, providing the data is on the image and you mount the filesystem as the directory it would be loaded it should load up with the extra non-standard filesystem.

Hope that helps,

Mike.

[HP-UX TIM OSP]

Mike

The -x inc_entire=vg00 option is only for make_net_recovery? Or can you use it for make_sys_image also?

[Fabian Briseño]

Hello saptaji.

Ignite Recommends you to backup only OS filesystems. If you need to backup other filesystems you can use fbackup, Also there is a "-x exclude=file|directory" if you want to avoid this problem in the future.

[HP-UX TIM OSP]

The filesystem has nothing in it just the filesystem, but is needed for operations. I just wanted the restore to create the filesystem so I don't have to do manually after every time I restore it.

[Mike Shilladay · Accepted solution]

Hi Saptaji,

The -x option is for both tape and network ignite types.

If your extra filesystem is in vg00, then just use the switch:

-x inc_entire=vg00

If your filesystem is in another volume group, the switch you may want to consider is:

-x inc_entire=vg00 -x inc_entire=vg01

Either way, once you have created the filesystem, providing that you tell ignite what you wish to back up, then any new ignite images will reflect the extra filesystem. If the filesystem was in another Volume Group, it will select the disk that formed part/all of that volume.

Mike.

[HP-UX TIM OSP]

Using command make_net_recovery, instead of make_sys_image to create an image of the client server.