Re: Disaster recovery [1405]

Better: Use the ALARMPROGRAM for logical log backup then as soon as that log archive is completed ship the file to the backup and apply it (ie keep ontape -r running constantly waiting for the next logical log file and then just reply 'Y' once the new file shows up. (You can use an expect script to monitor the arrival of new files and reply to the ontape prompts.) Then if the primary goes down just reply 'N' to the ontape (build into the expect script a method to tell it to say 'N') and let the recovery complete. Of course you could just use HDR (High availability Data Replication) which will do this for you automatically and seamlessly. ;0) Art S. Kagel ----- Original Message ----- From: Preetinder .... <preetinder.dhaliwal@dhl.com> At: 6/19 23:37 > Hi, > > We plan to implement a simple recovery mechanism. > > We have primary and secondary( has same instance ) machine. Both > with same versions of IDS. > > We plan to enable logical log backups on primary machine to a file > and then enable rsync for this log backup file to remote file ( > secondary machine). > > With level 0 backups twice in a week ( is small database - 2gb with > few changes) and a copy of logical logs on secondary machine too, will > we be able to recover in all scenarios?? ( i mean crash of instance on > primary or crash of primary machine ). > > We will make this log backup file on primary zero after every level > 0 and before starting log backup with ontape -c. > > > > Rgds > Preetinder sending to informix-list