Hello to everybody.
I've got this problem: I'm trying to restore an account on a D3/NT 7.5.2. It
is an account among others and I've done two file-save on two different
pseudo tapes on the windows box, the previous release was a 7.1.4. Both of
the saves verified ok.
I succeeded in restoring all of the accounts except one.
When I try to restore it in the FSI, D3 gives me a lot of errors and, if I
stop the process, in the dms I find item with an item-id named fsi:name,
afterwards, if I shutdown and restart D3 this item disappears.
As a second chance I tried to restore this account it in the VME on a 7.2 D3
with the "c" option, it looked as if it all went ok, but after a check I
noticed that some files were missing.
If I do a sel-restore of the missing files these go ok.
Now I'm thinking of restoring all the files one by one, but the files are
more than 30000.
Could anyone give me an help to resolve this problem ?
Thanks,
Alberto

Could you give an example of the errors? That might help.

Generally, if it was an FSI file to start with, it should go back into FSI
without a problem. If it was a VME file, it should go back into VME
automatically via restore. It could be restored into FSI by

account-restore fsi:name
account name on tape: original.acct.name

The (C) option is only for SAVEing, not for RESTOREing.

If the p-floppy tapes verified, they should restore, but that's a pretty
large jump, from 7.1 to 7.5. It's entirely possible that RD has changed
something "under the hood". Do these files have indexes?

But the real clue will be the error messages.


Mark Brown

"Alberto" <alberto_nospam (AT) tca (DOT) it> wrote

Hi Alberto
You can look to see if it got half started in the D3 windows Administration
program. You may find an Account DL/ID lying around. However what we
found on earlier releases is that a restore with the (o) for overwrite
option solved that or you can remove it with the D3 Admin tool.
Of course it is going back on a clean box isn't it. D3 7.5.2 will not
update 7.1.4 one must de-install and re-install. 3000 by hand seems awfully
disheartening.

Peter McMurray

"Alberto" <alberto_nospam (AT) tca (DOT) it> wrote

Thanks Mark,

this is the input and output of what's happening:


:t-rew
Block size: 500
[96] bot
:account-restore fsi:rogest (o4000 (I put the 'o' option as I
tried to do what excalibur suggested but nothing changed)
account name on tape:rogest
SQLDEMO
lwprnx
MODA.VMEBAK
PROG.AC
stuass
STUASSPRO
FsiDm
lwprn
dm
spooler
dmx
alborghetti
SQLDEMO.VMEBAK
SQL
SQL.VMEBAK
rogest this is the
name of the fsi account and here it is where it should start restoring it
1 > fsi:rogest 0,7
'fsi:rogest' is not a file name
1 > fsi:rogest > F.TERM 0,1
'F.TERM' is not a file name
1 > fsi:rogest > F.TERM > F.TERM 0,1
'F.TERM' is not a file name
1 > fsi:rogest > F.TERM > 41 0,5
'41' is not a file name

It keeps going on with this kind of messages.
After I stopped it with a break, I look at the list of accounts and, among
the others I see the following:

account name type account
....
fsi:rogest QS fsi:rogest
....

Yes, some of these files have indexes.
Hope this is what you asked.

Ciao,
Alberto

"Mark Brown" <mbrown (AT) drexelmgt (DOT) com> ha scritto nel messaggio
news:462fcc75$0$9880$4c368faf (AT) roadrunner (DOT) com...

As I have a copy of the preceeding D3Database folder, do you think I could
simply copy it in the new D3Database (after creating the fsi account) ?

"Mark Brown" <mbrown (AT) drexelmgt (DOT) com> ha scritto nel messaggio
news:462fcc75$0$9880$4c368faf (AT) roadrunner (DOT) com...

Alberto ha scritto:
and try again.
HTH
Stefano

This works well.

create-account fsi:rogest

and then copy the windows folder to your d3database. The contents of the
account come with it. Same with files.

Mark


"Albe" <coralbe_nospam (AT) email (DOT) it> wrote

I did it and it worked !
Thanks to everybody.

"Mark Brown" <mbrown (AT) drexelmgt (DOT) com> ha scritto nel messaggio
news:4630e426$0$5814$4c368faf (AT) roadrunner (DOT) com...

Hi
The space must be interesting now. The switch from 7.1 seems to indicate
that nothing has changed in the method of storage merely in the running of
programs to control the storage.
A related issue that you may need is to store some accounts on another
partition. We overcame this by creating the account on another partition
using the D3 Windows and then doing a restore with the O option. (TData
solution actually and saved us on a crowded disk)
Peter McMurray

"Alberto" <alberto_nospam (AT) tca (DOT) it> wrote