MSL Device Path change after recover from tape

[Jason Ng Teng Po]

Hi all,

I have one rx6600(A) and one attached MSL2024. I have change the device path for the MSL2024 to 130m,131m,132m and 133m. I create a make_tape_recovery for this rx6600(A) machine.

I take the tape and recover it to another rx6600(B) machine with MSL2024 attached. After recovery finish, I get the MSL2024 tape device path as 0m,1m,3m and 4m.


My question is why the rx6600(B) did not follow the rx6600(A)?

[Steven E. Protter]

Shalom,

You didn't report the OS in your post.

It is possible to change the paths using ioinit and clearing out the /etc/ioinit file.

If the system is cold installed with all hardware in place, then recovered using Ignite it should come out with the same paths.

What generally happens in real life is that the system is installed and then hardware is added later,and this can lead to this situation.

If you want to fix it here is a post to assist:
http://docs.hp.com/en/B2355-60130/ioinit.1M.html

http://docs.hp.com/en/5992-4174/ch04s07.html

SEP

[Jason Ng Teng Po]

Sorry my UX is 11.31 September release.

The thing is, I know how to change it using IOINIT method. But my customer know nuts about HP-UX. So I don't want to go there and everytime do a IOINIT after recovering from the tape. I just want the tape take care of it.

For the first set of rx6600 and MSL2024, previously it was detected as 0m,1m,2m,3m so I change it to 130m,131m,132m and 133m. After that I did a

make_tape_recovery -x inc_entire=vg00 -a /dev/rmt/?mn on the first set.

Once completed I take the tape and recover it on the 2nd set of rx6600 and MSL2024 that has already attached.


But comes out that I have to do IOINIT again.

[Ganesan R]

Hi Jason,

The reason is that, system will assign the device files according to the instance numbers. On rx6600(B) system will assign the instance numbers for the tape devices starting from 0 and it will not look the customised device files. That is the reason why you are getting the device files starting from 0m, 1m, 2m and so on.

If you need to stick with customised device files, what you need to do is create link files 130m, 131m, 132m and link to 0m,1m,2m on source server and then take ignite image.

Or just create the link files on destination server only whenever you are recovering.

[Jason Ng Teng Po]

So that means rx6600(A) and rx6600(B) will never be persistent on the device path?

For example both rx6600(A) and rx6600(B) will have different device path.

rx6600(A)
0m, 1m, 2m, 5m,

rx6600(B)
1m, 3m, 4m, 5m

Because I have one set of HP-UX serviceguard where both node have different device path. So I need to make it same (using IOINIT) for DP to scan the device properly. If not I have to use a softlink to link them to /dev/mydrive.