Re: BACKUP weirdness

What if I just do the WRITEBOOT, and then do an "upgrade" installation
from CD? Would that repair the VMS$COMMON issues?

Peter 'EPLAN' LANGSTOEGER wrote:
In article <1154347806.038256.238680@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, sampsal@xxxxxxxxx writes:
I recently backed up my system drive using the following command:

BACKUP DRA0:[000000...] DRA2:[000000]FULL.BCK/SAVESET

(I KNOW I should've used /IMAGE, but unfortunately I was in a rush and
didn't :( )

So you ended without information about your aliases in the saveset.
This is really not good with a system disk (where aliases are heavily used).

Anyway, if I try to restore the saveset (when booted up from the VMS
install CD) using a command like:

BACKUP DRA2:FULL.BCK/SAVESET DRA0:

then BACKUP just dumps all the files in the Master File Directory. If I
do a BACKUP/LIST on the FULL.BCK saveset, it show that the correct
directory structures are in fact in place.

Can someone tell me how to restore these files into their correct
locations?

$ BACKUP DRA2:FULL.BCK/SAVESET DRA0:[*...]/OWN=ORIG

and then check the various [SYS*.SYSCOMMON...] trees which are all
copies of [VMS$COMMON...] but should be aliases instead.
This means you could repair them by hand with something like

$ RENAME [SYS0]SYSCOMMON.DIR SYSCOMMON_OLD.DIR
$ SET FILE/ENTER=[SYS0]SYSCOMMON.DIR [000000]VMS$COMMON.DIR
and so on

Good luck
--
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail peter@xxxxxxxxxxxxxx
A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

.

Relevant Pages