Inode license management

[Charles Fear]

Scenario:
Upgrading mirrored system disks from 4 GB to 9 GB.
Process:
1. Omniback bakup of DBs and other application data.
2. Create make_recovery DLT tape
3. Switch disks
4. Restore from tapes created in step 2.
5. Restore data and DBs from step 1.

All of this works just fine... here's the dillema....

Apparently one of the business applications has a license model that uses the files system inode the license file allocates. Not sure I understand how or why they would do this because I cannot see how you would recover from a failed disk or a disaster without intervention.

Can anyone advise how {or if} a file can be restored to a specific inode?

[Steven E. Protter]

There is no way to go except for having the license re-authorization as part of your DR procedure.

We have the same problem with our print spooler.

You also should stop using make_recovery and use make_tape_recovery

The former is obsolete and the newer product might do a better backup and get you around this.

SEP

[Charles Fear]

Thanks for the quick reply... I said make_recovery but only for reference... we do use the make_tape_recovery....

Again Thanks for the input

[Mark Grant]

I haven't tried this but I guess if you put the license file on a tiny filesystem and backed it up buy using "dd" on the logical volume, I would guess that after a restore using "dd" the inode would be the same.

It's worth a try.

[T G Manikandan]

The best option would be to transfer the license to the new setup!

Are there any options of that tool using the network card address/easier way of having the host information.

I assume it would definitely have such option .

[T G Manikandan]

transfer the license, I meant return and get new licenses.
Out of curiosity,what is that tool?