want a way to recover, right?
Create standalone BACKUP kits for the OpenVMS VAX systems, and create or acquire bootable BACKUP kits for the OpenVMS Alpha systems. Use CLUSTER_CONFIG or CLUSTER_CONFIG_LAN to remove the various system roots and to shut off boot services and VMScluster settings. Create as many architecture-specific copies of the system disks as required. Realize that the new systems will all likely be booting through root SYS0-if you have any system-specific files in any other roots, save them. Relocate the copies of the VMScluster common files onto each of the new system disks. Reset the console parameters and boot flags on each system for use on a standalone node. Reset the VAXCLUSTER and NISCS_LOAD_PEA0 parameters to 0 in SYSGEN and in MODPARAMS.DAT. Clobber the VMScluster group ID and password using SYSMAN. Reboot the systems seperately, and run AUTOGEN on each. Shut off MOP services via NCP or LANCP on the boot server nodes. Permanent seperation also requires the duplication of shared files. For
Related Questions
- How does our association protect its legal right to recover past due assessments from our member owners?
- Might I have a legal right to recover for unanticipated negative side effects from Accutane use?
- I’ve been athletic all my life, but right now I’m suffering from injuries. Can Yoga help me recover?
