Hi Raoul,
from the docs:
The recovery history file helps you locate information once you have
performed a backup.
For example, it helps you determine the location of a backup,
or in which backup a DB2 object can be found. If a backup is moved to
different media,
say from disk to tape, this file can be updated to keep track of the new
location of the backup.
Every DB2 backup made contains a copy of this file, and it can be restored
from any backup.
If you choose to restore it, use caution to avoid overwriting the
database's existing history file.
Although the recovery history file is an ASCII file,
manually editing the file should be done only at your own risk and is not
recommended.
db2 '? restore'
RESTORE DATABASE source-database-alias { restore-options | CONTINUE | ABORT
}
restore-options:
[USER username [USING password]] [{TABLESPACE [ONLINE] |
TABLESPACE (tblspace-name [ {,tblspace-name} ... ]) [ONLINE] |
HISTORY FILE [ONLINE]}] [INCREMENTAL [AUTOMATIC | ABORT]]
[{USE {TSM | XBSA} [OPEN num-sess SESSIONS] |
FROM dir/dev [ {,dir/dev} ... ] | LOAD shared-lib
[OPEN num-sess SESSIONS]}] [TAKEN AT date-time] [TO target-directory]
[INTO target-database-alias] [NEWLOGPATH directory]
[WITH num-buff BUFFERS] [BUFFER buffer-size]
[DLREPORT file-name] [REPLACE EXISTING] [REDIRECT] [PARALLELISM n]
[WITHOUT ROLLING FORWARD] [WITHOUT DATALINK] [WITHOUT PROMPTING]
You can destroy an create a new instance, and than create a new DB like
'create db dummy'.
After that you can take your backup and do a restore with the INTO, REPLACE
EXISTING option.
Mit freundlichen Gr��en
Joachim M�ller
--
DOUGLAS Informatik & Service GmbH
Datenbankmanagement
Douglas Holding AG, Kabeler Str. 4, 58099 Hagen
Tel.:+49-2331-690-249,Fax:+49-2331-690-78-249
Mobile: +49-170-2221-249
--------------------------------+----------------------------------------------------------------------------
[EMAIL PROTECTED]|
nair.com| An: [EMAIL PROTECTED], [EMAIL
PROTECTED]
Gesendet von:| Kopie:
[EMAIL PROTECTED]| Thema: [DB2EUG]
rg|
|
|
25.02.2003 09:24|
Bitte antworten an|
Raoul.Joemman|
|
--------------------------------+----------------------------------------------------------------------------
We are planning a desaster recovery procedure for a database on DB2 v7.2 on
AIX.
We use TSM for the database backup.
I noticed when we make a database backup to TSM and then destroy and
recreate the
instance, it is not possible to restore the database anymore. I think this
is because of the
missing history information for the backup. I mean the history you see with
the command
"db2 list history all backup for database x".
If I am correct, is it then possible to recreate this historical
information?
Or do I have to backup this information also to the TSM server?
What kind of procedures do you use?
Best regards
Raoul Joemman
*****************************************************************
This e-mail and any attachment may contain confidential
and privileged material intended for the addressee only.
If you are not the addressee, you are notified that no part of
the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail
or attachment is strictly prohibited, and may be unlawful.
If you have received this e-mail by error, please notify the
sender immediately by return e-mail, and delete this message.
Martinair Holland N.V., its subsidiaries and/or its employees
shall not be liable for the incorrect or incomplete transmission
of this e-mail or any attachments, nor responsible for any
delay in receipt.
*****************************************************************
-
::: When replying to the list, please use 'Reply-All' and make sure
::: a copy goes to the list ([EMAIL PROTECTED]).
*** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
*** For more information, check http://www.db2eug.uni.cc
-
::: When replying to the list, please use 'Reply-All' and make sure
::: a copy goes to the list ([EMAIL PROTECTED]).
*** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
*** For more information, check http://www.db2eug.uni.cc
