[Info-vax] VAXCluster vs. VMSCluster?

[AdeV]

Bob Gezelter may or may not have intoned:
> On Jan 8, 5:16 am, AdeV <s... at solutionengineers.com> wrote:
> > H Vlems may or may not have intoned:
> >
> >
> >
> > > On 7 jan, 18:03, AdeV <s... at solutionengineers.com> wrote:
> > > > AdeV may or may not have intoned:
> >
> > > > > AdeV may or may not have intoned:
> >
> > > > > [snippage]
> >
> > > > > Hmm, thought I'd see what would happen if I just added it in anyway....
> > > > > and it booted, hurrah!
> >
> > > > > Mounted the CDROM, which seems to be quite readable; it's currently in
> > > > > the process of restoring vms073.b/save_set; hopefully, I can then unplug
> > > > > it from the network & have it boot standalone.....
> >
> > > > Nope, it didn't like that - ?42 NOSUCHFILE
> >
> > > > Back to the old drawing board...
> >
> > > > --
> > > > Cheers!
> > > > Ade.
> >
> > > Ade,
> > > try the backup command again and add the /VERIFY qualifier. That way
> > > you'll know whether the on disk structure
> > > on the target disk is valid. There's no need to run WRITEBOOT,
> > > restoring the .B saveset produces a bootable disk.
> > > The error ?42 NOSUCHFILE seems to indicate that you either boot from
> > > the wrong volume or that the volume is bad.
> > > Boot the 3100 again in the cluster and run ANALYSE/DISK on the
> > > intended boot device.
> > > The backup command you used was:  $ BACKUP/IMAGE DKA500:[000000]
> > > VMS073.B/SAVE $3$DKA100:
> > > Or something similar? When you boot the 3100 in the cluster, run a
> > > directory of  [000000] just to check that there's not just
> > > a copy of the .B saveset sitting there...
> >
> > I wasn't able to use the /IMAGE parameter, as DKA0 (the hard disk) is
> > not mounted as foreign. As it's in use (page file), I can't unmount &
> > re-mount it...
> >
> > I do have a second HDD handy, I will try adding that to the system later
> > today, maybe I can restore onto that instead, then change it to be the
> > boot drive...
> 
> Ade,
> 
> For historical reasons, licensing still uses the name VAXCLUSTER
> (Verified against HOBBYIST PAK collection issued recently for an Alpha
> system).

Thanks Bob, that might explain why it doesn't work, then; I definitely 
got a licence for "VMSCLUSTER", not "VAXCLUSTER"...


-- 
Cheers!
Ade.