Re: Cobol .DAT backup solution
- From: "Richard" <riplin@xxxxxxxxxxxx>
- Date: 14 Sep 2006 19:48:51 -0700
James J. Gavan wrote:
Richard - his original question was, elsewhere, how can he handle
backups when he has RETAIL applications (POS) working 24/7 ?
I am well aware of what the question was.
Cast your
mind back to ICL and Singer days - given you had 24/7 back then, how
would you have handled it.
20 years ago 24/7 online systems were not common. I did do some work
with SuperMarket 20 that ran on special DRS20 systems (which were sort
of Singer based, they replaced the Cogar/Singer 1500 and could run an
AP1 card that emulated a 1500). These machines used 2 DRS20s linked by
a special channel with a 1MByte buffer (this was early 80s). Backup was
continuous from the live machine to the standby machine via complete
transactions in the buffer.
It could do auto-fallover and then recover to the primary machine when
it was fixed.
The point I was making is that a set of MF ISAM files on a Windows
server is unlikely to be a good place to start to build a reliable 24/7
operation. Whether it be POS or any other it is likely to require all
files to be taken together to ensure a consistent set is backed up. It
also requires that the system be designed to do this from the start and
it can't be 'bolted on' afterwards.
Does MF still do the 'fileshare' server system that puts all the file
access via a server ? This may overcome some of the problems as it
implements COMMIT and ROLLBACK and may even do journalising.
.
- References:
- Cobol .DAT backup solution
- From: cobol_rasurop
- Re: Cobol .DAT backup solution
- From: James J. Gavan
- Cobol .DAT backup solution
- Prev by Date: Re: Cobol .DAT backup solution
- Next by Date: Re: Cobol .DAT backup solution
- Previous by thread: Re: Cobol .DAT backup solution
- Next by thread: Re: Cobol .DAT backup solution
- Index(es):
Relevant Pages
|