protection lost on root-level directories during restore

[BoyeDav]

We installed a new RAID controller and had to restore our system and data volumes as part of that. Almost everything is working fine, however we lost the protection on the root-level directories on both our system (dka0) and data (dka1) volumes.

What I mean is, any directory immediately under [000000] didn't retain their protection as part of the backup/restore. Any subdirectories under them as well as all the files on the system did restore with the proper protection, just not the highest level directories under [000000].

We're on OpenVMS 8.3, IA64, latest patches as of June 2007 consolidated ECOs, on Integrity rx3600.

Is there something I did wrong in the backup/restore that would affect the protection on just the top-level directories? I'm in the process of restoring both volumes to alternate locations to see what I can about the protection. Any suggestions/comments?

Thanks!

[Steven Schweda]

> Is there something I did wrong [...]

Most likely. /IMAGE would have been good.
After that, as I recall, there is some fine
print involving [000000...] v. [*...], or some
such detail.

[BoyeDav]

It's only the top level directories, so it's not a huge deal. I can fix that manually. Can anyone tell me what the default protection is on the "standard" VMS directories, like VMS$COMMON, SYS0, etc.?

Thanks again.

[Jan van den Ende]

Boye,

Nothing new in IA64, nor in 8.3
That has been the case (and annoying) since at least 6.2
It is the same on disk-to-disk BACKUP with /OWN=ORIG: you first have to do the top level directory(s) separately.
Disk-to-disk, it just is a nuisance, but tape-to-disk, it _IS_ rather more than that! :-(
(ISTR, but no hard fact on that, that in Vax 5.x things worked as expected).

Sorry, no better news.

Proost.

Have one on me.

jpe

[Jan van den Ende · Accepted solution]

>>>
Can anyone tell me what the default protection is on the "standard" VMS directories, like VMS$COMMON, SYS0, etc.?
<<<

Oops!! Do you mean you migrated the _SYSTEM DISK_ without /IMAGE ??
That means you also lost all aliasses!!

Oh, I see. Is this the same disk as your previous question:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1144893 ?

Well, mount a distro CD and look how it is there.
That is the vanilla version.

Proost.

Have one on me.

jpe

[BoyeDav]

Thanks, I will do that :)

[John Gillings]

>After that, as I recall, there is some fine
>print involving [000000...] v. [*...],

Steven is correct. There's a subtle distinction between:

$ BACKUP disk:[*...]*.*;*

and

$ BACKUP disk:[000000...]*.*;*

the former doesn't explicitly include the top level directories. So, although the restore can infer their existence, and must create them, because the directories themselves weren't saved, all other information (protection, ACL, etc...) is lost.

To save all information about all files, use [000000...] rather than [*...].

[BoyeDav]

Our ACLs and protection on the sub directories and files all survived, so all that really need to be fixed was the protection on the top-level directories.

I changed my backups per the above suggestions.

Thanks!

[Hoff]

BACKUP /IMAGE is your friend when you're working with the whole disk.