Hi, I'm hoping someone can share their experience of using repozo, packing and backups to answer a couple of questions. I've googled around to confirm that packing means a full backup. Is there any way to carry out incremental backups and then pack the database, without carrying out a full backup each time - for example, can I continue to get nightly incremental backups if I pack nightly but retain the last 2 days' transaction history? (I transfer the increments to a backup server, and then rebuild the database, then take a nightly snapshot to tape, so I really don't need a full backup) I have an inkling this is not possible, but would be useful to confirm... TIA, Miles
On Mar 5, 2008, at 12:38 , Miles wrote:
Hi,
I'm hoping someone can share their experience of using repozo, packing and backups to answer a couple of questions.
I've googled around to confirm that packing means a full backup. Is there any way to carry out incremental backups and then pack the database, without carrying out a full backup each time - for example, can I continue to get nightly incremental backups if I pack nightly but retain the last 2 days' transaction history?
(I transfer the increments to a backup server, and then rebuild the database, then take a nightly snapshot to tape, so I really don't need a full backup)
I have an inkling this is not possible, but would be useful to confirm...
You're right, this is not possible. The only way to prevent full backups is to never pack the database. jens
Hi,
I've googled around to confirm that packing means a full backup. Is there any way to carry out incremental backups and then pack the database, without carrying out a full backup each time - for example, can I continue to get nightly incremental backups if I pack nightly but retain the last 2 days' transaction history?
(I transfer the increments to a backup server, and then rebuild the database, then take a nightly snapshot to tape, so I really don't need a full backup)
I have an inkling this is not possible, but would be useful to confirm...
You're right, this is not possible. The only way to prevent full backups is to never pack the database.
Thanks for confirming. One other question which I don't know enough zodb voodoo to answer: Say I record the transaction ID of the last transaction to be backed up each night, pack the database, then with my next backup, only back up transactions with an ID above that. Is there any reason why this wouldn't work as a strategy? Not sure I really want to be responsible for a completely custom backup strategy, but I would like to know a bit more... Thanks, Miles
Miles wrote at 2008-3-5 12:20 +0000:
.... Say I record the transaction ID of the last transaction to be backed up each night, pack the database, then with my next backup, only back up transactions with an ID above that. Is there any reason why this wouldn't work as a strategy?
Not sure I really want to be responsible for a completely custom backup strategy, but I would like to know a bit more...
Packing can change old transactions (by deleting no longer used object records). Also note that a FileStorage contains back references (references from one object record to a previous object record). Such back references make it difficult to sticht together a backup for transactions until a given tid and one for transaction from this tid onward -- when some packing has happened in between. -- Dieter
participants (3)
-
Dieter Maurer -
Jens Vagelpohl -
Miles