Post by Excalibur21Post by Frank WinansIt sure would be handy to have an option flag to let you do a full file
restore that stops after the first account on tape.
HI
I do set this up on each site so that I can quickly something that has
screwed up the work space such as a big power fail with everyone
logged on. It is a trick Mike Raffaele of TData showed me.
I use D3 Windows but I assume that Linux works the same.
Of course all my work is in the FSI. If for some reason you have work
elsewhere then create your list manually.
My way creates a tape with MDS, DM and Spooler.
dev-make -t tape -a "d:\d3backups\basesys,p"
set-device x
select mds with a1 "d]"
file-save
Then using the Windows D3 Device Manager create the save as
a tape device
When necessary run d3vme.exe in the usual way and select your
new tape.
Peter McMurray
a) I was rather hoping for something in future releases that lets you
get back to work when, in all the excitement of doing a full file-save
followed by full file restore, you _forget_ the simple precaution of
_First_ cutting a file-save tape of just the dm account {OK, dm and
spooler is ok too.} Usually the first part of a tape is just fine, and
dm account gets forced to be first account on tape. It is a royal pain
to nit-pick your site-specific changes to factory-supplied dm account
to merge them into the dm/spooler/sqldemo 'file-save' tape that comes
from the installation of d3 {not to mention if you've got any abs
patches,
that 'tape' will have the wrong checksums in dm,abs, file.} On top of
that you essentially cannot account-restore the tape dm account as
new disk account dm.tape without it ditching all your system files like
USERS and PIBS and DEVICES in favor of simple qpointers to the
disk DM account, so you have to laboriously sel-restore those by file#.
b) Note you need to select mds,dm, "dm" "spooler"
or mds,, "dm""spooler" -- you wrote just mds,dm by
mistake...
c) Also note dev-make will only let you create new pseudo-floppy tapes
on d3/nt, if you are on d3/linux you have to just change some existing
tape to reflect your preferred filename. I think that's the dev-chg
verb.
d) but back to the original problem; aside from any insane intricacies of
d3/nt having an fsi:,
even on d3/linux if, say, your third account on tape has a massive
file,
say 500 items of 3 megabytes each, and as a result your restore does
a segdump there, well at that point your full file restore is dead in
the
water. You have a mostly-empty mds "account" master dictionary,
{ it may only have one item -- a d-pointer in mds,, called "DM"},
but it will be missing
all the account qpointers you had before, like SYSPROG
all the other non-dpointer items like the
attribute-defining
item "SYSPRIV"}
You will need to manually sel-restore all those non-Dpointer items
from mds,, file by file# off your tape, if you decide to try and limp
along without reverting to the factory-supplied
dm/spooler/sqldemo 'file-save' tape. { Say, I just noticed
that
d3/linux 7.5.0 lets you do count mds,md, without having an
"md" item in the mds,, "file." I could have sworn I saw the "md"
item was required in mds,, just like you need it in all account
master dicts, << for example in 'file' dm,, >> on earlier
d3/linux
releases... seems like it is optional now though.}
{even after patching up mds,, that way, you still won't be healthy
enough to be generating file-of-file items during saves until after
you've done yet _another_ file-save of that semi-working
pick filesystem and done a full-file restore. This time, since the
full file restore concluded normally, it will hopefully run whatever
patch-up programs it normally does after having sucked each account
each account from a tape, and that will make fof work ok again.
Erm, before you repopulate mds,, even the create-account verb
is too impaired to work.