Shadow dissolve

[Matthias Foerster]

What is the command to tell a disk that it is
no longer a member of a shadow set, so that it
can be used as system disk for a non-shadow system?

- Shadow set: DSA0: with $10$dka0: and $10$dka100: (ALPHA XP1000 OVMS 8.3)
- dism $10$dka100:
- mou/over=(shadow,id) $10$dka100:
- back/image/ini dka100: dkb200:
- booting from dkb200: >>> still marked as
shadow-set-member (why ??? and how to kill
this mark)
- mc sysmen
SYSMAN> par set alloclass 0
SYSMAN> par set shadow 0
SYSMAN> par write ......
- CRASH when rebooting because DKB200: still
marked as shadow set member and alocation
class undefined

[Wim Van den Wyngaert · Accepted solution]

boot minimal and set shaodw_sysdisk to 0.
Then continue.

Wim

[Jon Pinkley]

As Wim hinted, the problem is the sysgen parameters. Although I believe he meant "conversational boot" instead of "minimal boot".

You have made a clone of the system disk, and any system that boots from the disk will assume the role of the system root it is booted from. If this new system is on a LAN that is visible to the original node, you will probably need to be changing more than just the shadow configuration.

The procedure is described in the VMS installation and upgrade manual, since upgrades of a shadowed system disk are not supported.

Here's a link to the relevant section in the 8.3 manual.

http://h71000.www7.hp.com/doc/83final/ba322_90045/ch04s08.html

However, that is only for the shadowing portion. You may need to change other parameters as well to prevent interference with other nodes, especially if the system disk/root was part of a VMSCluster.

A bit more info about what the purpose of the copy is would help readers make appropriate recommendations.

Jon

[Wim Van den Wyngaert]

Thank you for the correction Jon. Indeed conversational boot.

Wim

[Matthias Foerster]

Thank you all for fast answers. I tried setting
the shadow_sys_disk - parameter setting to 0
and the booting was OK. Moreover I put
$ set shadow /force_removal
and I had the impression that the shadow-set-member mark was killed.

So my problem is solved and I will close the inquiry. Thank You very much for helping.

Matthias

p.s.: The purpose of creating a copy of the system was: For testing a warm-stand-by-application I need a system disk
for a second node with the same OVMS and Oracle-RDB version as the one of the shadow
set and want to avoid building up a new system.

[Matthias Foerster]

Thank You