Subject Re: [ib-support] Re: maintenance strategie
Author Jason Chapman (JAC2)
Batch File
0) Delete last weeks offline copy
0.1) Delete last weeks output files
1) Stop services
2) Rename / move original
3) Start Services
4) Backup > output file
5) Restore > output file
6) Run an application to parse both output files, if exactly as expected
then rename / move restored version
You should be able to detect a good vs bad output file.
If there is any problem, users will not be able to login as DB will be
restored under a new name - this will prompt the support call.

my 2c.

JAC.


"Aage Johansen" <aagjohan@...> wrote in message
news:5.1.0.14.0.20020128215629.00b2f308@......
>
> >but I need to make those things as easy as possible for my customers.
> >Any idea to automate this ?
> >My db is not busy 24x7. The weekend is a good period to do this.
>
> You can automate it. You can use the Windows scheduler (AT) to run batch
> filles, or you can use a 3rd party program.
> HOWEVER, I don't think I would ever let a restore automaticaly
(unattended)
> overwrite the current database. It just might happen that the backup has
> errors. If the restore fails after overwriteing some of the database,
your
> users will not love you. You will have to be very careful.
> Consider giving the users a written procedure for doing the backup/restore
> including testing the restored db, and provide them with either complete
> batch-files with gabk (backup, and restore), or one of the free backup
> utilities (with parameters in place).
> As long as your db does not use multiple files you can freely copy
> databases around.
>
>
> Regards,
> Aage J.
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>