Am Thu, 11 Feb 2010 07:08:28 -0500 schrieb Dan Langille:
> JanJaap Scholing wrote:
>> Thanks for all the input.
>>
>> I think a lvm snapshot is the best way to go for us.
>
> Be aware of the potential risks of backing up a database at the file
> system level. What you may be backing up is a data
On 02/11/10 01:08 PM, Dan Langille wrote:
> JanJaap Scholing wrote:
>> Thanks for all the input.
>>
>> I think a lvm snapshot is the best way to go for us.
>
> Be aware of the potential risks of backing up a database at the file
> system level. What you may be backing up is a database in an
> incon
JanJaap Scholing wrote:
> Thanks for all the input.
>
> I think a lvm snapshot is the best way to go for us.
Be aware of the potential risks of backing up a database at the file
system level. What you may be backing up is a database in an
inconsistent state (e.g. part way through a transaction)
+0100
Subject: [Bacula-users] How to backup the catalog
Hi List,
One
question, how to backup the catalog.
We are
using MySQL for the bacula catalog. This database is approximately 46 Gb in
size.
When we use
the backup script make_catalog_backup (supplied with bacula) to dump the
Hey,
for innodb should mysqldump with the --single-transaction option work.
http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html#option_mysqldump_s
ingle-transaction
Kinds regards
Julian
--
SOLARIS 10 is the OS for D
Heitor Medrado de Faria wrote:
> If you use Postgresql, you could put database in backup mode for hot
> backup = http://www.postgresql.org/docs/8.1/static/backup-online.html.
I just use pg_dump without doing anything special
--
Hi,
On 02/10/10 04:52 PM, JanJaap Scholing wrote:
> Hi List,
>
> One question, how to backup the catalog.
>
> We are using MySQL for the bacula catalog. This database is
> approximately 46 Gb in size.
Are you using MyISAM or InnoDB ? Backup procedures can vary according to
the MySQL storage engi
Mike Ruskai wrote:
> On 2/10/2010 10:52 AM, JanJaap Scholing wrote:
>>
>> Hi List,
>>
>>
>> One question, how to backup the catalog.
>>
>>
>> We are using MySQL for the bacula catalog. This database is
>> approximately 46 Gb in size.
>>
>> When we use the backup script make_catalog_backup (supplie
On 2/10/2010 10:52 AM, JanJaap Scholing wrote:
Hi List,
One question, how to backup the catalog.
We are using MySQL for the bacula catalog. This database is
approximately 46 Gb in size.
When we use the backup script make_catalog_backup (supplied with
bacula) to dump the database, bacula
Am Wed, 10 Feb 2010 16:52:54 +0100 schrieb JanJaap Scholing:
> Hi List,
>
>
> One
> question, how to backup the catalog.
>
>
> We are
> using MySQL for the bacula catalog. This database is approximately 46 Gb
> in size.
>
> When we use
> the backup script make_catalog_backup (supplied with ba
> One question, how to backup the catalog.
>
> We are using MySQL for the bacula catalog. This database is approximately 46
> Gb in size.
>
> When we use the backup script make_catalog_backup (supplied with bacula) to
> dump the database, bacula is not usable during the mysqldump process due to
> l
Hi List,
One
question, how to backup the catalog.
We are
using MySQL for the bacula catalog. This database is approximately 46 Gb in
size.
When we use
the backup script make_catalog_backup (supplied with bacula) to dump the
database, bacula is not usable during the mysqldump process due to
12 matches
Mail list logo
