I found out today that a `backup volrestore' operation doesn't work
for volumes that are missing a dump from the dump hierarchy, i.e.
either are not on a full backup or are missing from any incremental
backup. This example shows the problem for a volume that was added
last friday and doesn't exist on a previous backup:
backup> volinfo user.phc.tonyh.backup
DumpID lvl parentID creation date clone date tape name
733471832 4 732894476 03/30/93 07:09 03/30/93 03:15 user.4.2.1
backup> volrestore idun.phc.chalmers.se g user.phc.tonyh.backup -n
backup> backup: index to iterator function is out of range Can't find tapes for volume
user.phc.tonyh.backup (in dump 728635770)
The response is the same without the -n flag.
The backup command ident's as
$Header: /afs/transarc.com/project/fs/dev/afs/rcs/bucoord/RCS/main.c,v
1.36 1992/06/11 16:06:57 dws Exp $
So, while restoring the volumes that can be restored, I need to find a
workaround for the rest. One way is to manually read the dump files
>From tape to disk and do a `vos restore'. However, unlike the old
vol-restore utility, `vos restore' doesn't handle incremental dump
files, although `vos dump' can produce such files. This merge,
however, can be done in other ways.
Any corrections or other ideas?
-- H}kan
--
H}kan Torbj{r : Dept. of Computer Engineering : qui me amat,
[EMAIL PROTECTED] : Chalmers Univ. of Technology : amat et
(+46) 031-772 16 66 : 412 96 G\TEBORG, Sweden. : canem meam
