ADSM-L

Recovery Log problems

1999-09-01 15:19:31
Subject: Recovery Log problems
From: malkit <malkit AT UDI.CO DOT IL>
Date: Wed, 1 Sep 1999 21:19:31 +0200
Hello,

I would like to discuss the following with you:

I recommended my customers to work with rollforward. Some of them even
have mirroring for their recovery log. The reason was - data integrity.

We usually fail to restore the DB to its most current state. The main
problem we encounter is that whenever we have a failure on ADSM DB -
usually hardware problem it effects the recovery log as well, and we
must run point in time backup.

Yesterday, one of our customer had a crash on one of the recovery log
disks. The recovery log was mirrored to another disk, but ADSM didn't
switch to the alternate volume.Both of the volume switched to offline
and ADSM crashed. Running 'dsmserv display logvol' we got a message that
these volumes are offline. We couldn't load ADSM back - we try extend
log, restore DB - which failed as well. Finally we run 'dsmserv format
....' and only then we were able to restore the DB.

I would like to ask you if any of you work SUCCESSFULLY with
rollforward. What is your experience with ADSM DB and RLOG.


--
Regards
Regards

Malkit Hayun , UDI
Storage Products Manager
IBM Certified Specialist-ADSM
Office: 972-3-9233440
Fax:    972-3-9233441
Mobile: 972-52-834575
Email: malkit AT udi.co DOT il