Subject | Re: Backing up / Restoring large databases |
---|---|
Author | Aage Johansen |
Post date | 2003-04-03T19:23:26Z |
Rodbracher wrote:
quite seldom (once a year, maybe twice) except for restores which are just
for testing the validity of the backup. It seems your backups are faster
than mine!
Maybe replicating data to a hot (or lukewarm) standby could be an option?
There has been talk about incremental backups, but not much more (than talk).
separate processors should help some.
--
Aage J.
> We are at a point where a number of our customer Firebird v1.0 GDBsHow often do you restore? Even though gbak runs every night, restores are
> are 1 - 2 GB in size. The backups take +-40 min and restores even longer.
> The growth rate is fair and I expect the GDB size to be 6 - 8 gb in a
> couple of years. Is this going to mean a backup/restore cycle of near 8
> hours ? A lot of these operations are near 24/7 - 8 hours is a lot of
> down time.
quite seldom (once a year, maybe twice) except for restores which are just
for testing the validity of the backup. It seems your backups are faster
than mine!
Maybe replicating data to a hot (or lukewarm) standby could be an option?
There has been talk about incremental backups, but not much more (than talk).
> Does anyone know if multi-processors dramatically improve backup/restoreWouldn't think so. But, having the gbak and the IB engine run on a
> time ?
separate processors should help some.
--
Aage J.