Hello,
i tested my restoration scenario but unfortunely i'v got an internal server
error
this is the entire log for the restore db
in fact, tsm mounts the good vitual volume with the good DB by it don't
want restore it
because tsm sees a db with 0 megabyte size :-(
do yo have an idea or i cancel the scenario and say to my customer : "err,
i'm sorry" :)
ANR0900I Processing options file dsmserv.opt.
ANR7811I Direct I/O will be used for all eligible disk files.
ANR8200I TCP/IP driver ready for connection with clients on port 1500.
ANR0200I Recovery log assigned capacity is 5120 megabytes.
ANR0201I Database assigned capacity is 20480 megabytes.
ANR4600I Processing volume history file
/usr/tivoli/tsm/server/bin/tsm1_vol_history.dsm.
ANR4620I Database backup series 1159 operation 0 device class DBB_OFFSITE.
ANR4622I Volume 1: DBB_OFFSITE.DBB.047533432.
ANR4634I Starting point-in-time database restore to date 03/13/03 23:59:59.
ANR0300I Recovery log format started; assigned capacity 5120 megabytes.
ANR0301I Recovery log format in progress; 4 megabytes of 5120.
ANR8340I SERVER volume DBB_OFFSITE.DBB.047533432 mounted.
ANR0301I Recovery log format in progress; 8 megabytes of 5120.
[...]
ANR0301I Recovery log format in progress; 220 megabytes of 5120.
ANR1363I Input volume DBB_OFFSITE.DBB.047533432 opened (sequence number 1).
ANR4646I Database capacity required for restore is 0 megabytes.
ANR4649I Reducing database assigned capacity to 0 megabytes.
ANR9999D icstream.c(1047): ThreadId<28> Invalid record header found in
input stream, magic=FFFFFFFF.
ANR9999D lvmrdu.c(457): ThreadId<0> Requested new capacity value is less
than 1 LVM partition.
ANR9999D icrest.c(2379): ThreadId<0> Rc=37 reducing db.
ANR1364I Input volume DBB_OFFSITE.DBB.047533432 closed.
ANR0301I Recovery log format in progress; 224 megabytes of 5120.
ANR2032E RESTORE DB: Command failed - internal server error detected.
thanks in advance for you help.
--
David Rigaudiere -+- Administration TSM -+-
Paris -+- 40, rue de Courcelles -+- 4e étage -+-
david.rigaudiere AT fr.abnamro DOT com -+- 01.5621.7802
|---------+--------------------------->
| | Remco Post |
| | <r.post AT SARA DOT NL>|
| | Sent by: "ADSM: |
| | Dist Stor |
| | Manager" |
| | <[email protected]|
| | T.EDU> |
| | |
| | |
| | 23/04/2003 16:22|
| | Please respond |
| | to "ADSM: Dist |
| | Stor Manager" |
| | |
|---------+--------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: ADSM-L AT VM.MARIST DOT EDU
|
| cc:
|
| Subject: Re: undelete volh type=dbb
|
>-------------------------------------------------------------------------------------------------------------------------------|
> hi remco post, thx for your answer.
> err no i do not have backup volh, but my volh file is ok and
> there is the
> DBBackups definitions inside of it.
> i've a copy of volh file in another place (simply a cp)
>
> q volh type=dbb returns only the dbbackup of the day, this
> morning 06:30.
>
> is it possible to restore the volh "db" from the volh file ?
>
>
> in fact i have to :
> 1 * restore the DB for the 2003/03/13,
Yes, in the dsmserver.opt file, you have a pointer to a volhist file,
that file is used to find the volhist, if the right dbbackup tape is in
there, you are save, aternatively, you could explicitly state the
volumenumber to retore the database from....
> 2 * export FS for the node FOOBAR
> 3 * restore the today's DB
> 4 * import node FOOBAR fs=exported_fs
>
Maybe (if you have enough resources, you could restore the db to a
testinstance of the server, do an export from there, so you don't have
to retore your production db....
> i launched dsmserv restore db todate=03/13/2003 source=dbb preview=yes
> and it found the good virtual volume on remote server.
>
> i think, for phase 1 and 2, "update volumes * access=reado"
> for not write
> on volumes which was in scratch state the 2003/03/13
> what do you think about it ?
>
> David
>
--
Remco
---------------------------------------------------------------------------
This message (including any attachments) is confidential and may be
privileged. If you have received it by mistake please notify the sender by
return e-mail and delete this message from your system. Any unauthorised
use or dissemination of this message in whole or in part is strictly
prohibited. Please note that e-mails are susceptible to change.
ABN AMRO Bank N.V. (including its group companies) shall not be liable for
the improper or incomplete transmission of the information contained in
this communication nor for any delay in its receipt or damage to your
system. ABN AMRO Bank N.V. (or its group companies) does not guarantee that
the integrity of this communication has been maintained nor that this
communication is free of viruses, interceptions or interference.
---------------------------------------------------------------------------
Le présent message (y compris tous les éléments attachés) est confidentiel
et est destiné aux seules personnes qu'il vise. Si vous l'avez reçu par
erreur, merci de l'indiquer à son expéditeur par retour et de procéder à sa
destruction dans vos systèmes. Toute utilisation ou diffusion non autorisée
de son contenu, dans sa totalité ou en partie, est strictement interdite.
Merci de noter que les e-mails sont susceptibles d'être altérés. ABN AMRO
Bank N.V. (et les entités membres du Groupe ABN AMRO) ne saurait être tenu
pour responsable ni de la transmission erronée ou incomplète des
informations contenues dans ce message, ni des délais de réception ou des
dommages causés à votre système. ABN AMRO Bank N.V. (et les entités membres
du Groupe ABN AMRO) ne garantit ni que l'intégrité de la communication ait
été maintenue ni que cette transmission soit exempte de virus,
d'interceptions ou d'interférences.
|
