Hi,
On 1/24/2006 7:19 PM, Dan Langille wrote:
I started a new thread, because we've gone onto a new topic. Catalog
backup, not just catalogs.
On 24 Jan 2006 at 20:11, Timo Neuvonen wrote:
Is there a possibililty that it will hold 5 years worth of data?
It is. Note that 5 years of data for backing up one computer is
quite different from that used to backup 1000 computers. Indeed, it
depends greatly upon how many *files* you are backing up, and not
such much on the size of the data.
If the system to be backed up is relatively stable (only a few files change
between incremental bacups) and the catalog is included in the backup, the
catalog itself may be a significant amount of data that will be put into
every (even incremental) backup. This is one thing to consider, if catalog
size gets big. This may put a practical limit to the timeframe that is kept
in the catalog in full.
The catalog, when backed up, is just one file. At least it should be.
If you're using mysqldump or pg_dump, you'll have just one ASCII
file. For SQLite, I don't know.
I do not recommend backing up the raw database files as a backup
method. The ASCII file is always The Right Thing To Do.
What Timo meant, I suppose, was that the catalog itself might grow to
become the biggest part of your stored data. Which is correct in my
experience, but also, I observe that the catalog backup usually doesn't
grow beyond something reasonable in terms of available storage.
Of course, there is no such thing as a "normal" system in the sense that
its data size, amount of data changed between backups, and catalog size
can be used to extrapolate to other setups. Nonetheless, the backup
setups I know do have the "right" relation of storage space to data
stored so that the catalog backup sizes aren't what breaks the setup.
Usually, though, I store the catalog backups only for a very limited
time, typically in the pool used for incremental backups, where they
quickly expire. Catalog backups are most of the time between 2/3 to 1/4
of the daily amount of data.
Given these experiences, I never saw a reason to inestigate into
differential database backups using the transaction logs, for example.
One question to you all - How do you handle catalog backups, especially
retention of the corresponding volumes?
I decided I wouldn't have to keep the catalog for very long, because
it's mainly needed for desaster recovery, where I won't need to go back
in time but rather restore the most current system state.
Thanks,
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
