Subject: | |
From: | |
Reply To: | |
Date: | Thu, 12 Sep 1996 22:29:47 EDT |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Hi,
We are moving to a 24*7 operation on a HP3000/992-200 and are looking at HP's
TurboStore7*24 and Orbit's BackupPlus OnLine/XL. There are several large
Image data bases that use Image Logging with RollBack recovery enabled.
We also use ProAcive's BackChat product to mirror the log transactions to
another HP3000.
The problem is with the large numbers of Image logfiles and Dbrecov. In the
event of a System Failure and then the need to perform a Rollback Recovery.
Image logging will number the Log files from 001 to 999 and then restart the
numbering from 001 again. This can be catered for by purging the log files
after they have been stored so that a file name conflict does not occur. But
Dbrecov requires that you restore all the log files to perform a Rollback
recovery. We could restore the first 001 to 998 log file set and then wait
for the console request. Then restore the next log file set etc and continue.
This may be too time consuming.
Of course it would be preferable to get all the users off the system and
start a new Image logging cycle at some stage in order to limit the number of
log files. This seems to defeat the idea of 24*7 availability and is
difficult when your users are your customers. They do not log on and have a
normal session but instead talk to a process running on the HP3000. These
customer connections could be as high as 10,000.
I would appreciate any thoughts / comments from list users on methods to
handle this situation. Is anyone faced with a similar problem and have you
any wise knowledge to pass on ?. Also whether SIG-IMAGE has had any requests
for enhancements to Dbrecov so that it does not require the log files to be
restored.
TIA
Peter Dewar
CHEP Australia
|
|
|