Holikar, Sachin (ext) wrote:
>
> You are right Alan.
> It's a database dump file.
> So you mean to say that I can compress the current file and rename it. So
> that next time
> Mysql will start writing onto new bacula.sql file?
Yes, but see Bruno's post on this - which also shows you how to c
On 10/18/10 08:08, Damian Ge;bicki wrote:
> Phil Stracchino wrote:
>> On 10/18/10 07:21, Holikar, Sachin (ext) wrote:
>>
>> Well, without seeing the script, we're somewhat guessing. Personally, I
>> keep my catalog dumps around because if something crashes my database,
>> it's faster to just reload
Phil Stracchino wrote:
> On 10/18/10 07:21, Holikar, Sachin (ext) wrote:
>
> Well, without seeing the script, we're somewhat guessing. Personally, I
> keep my catalog dumps around because if something crashes my database,
> it's faster to just reload the last database than to do a bscan.
> However
On 10/18/10 07:21, Holikar, Sachin (ext) wrote:
>
> Hi Bruno,
>
> You hit the bullz eye!!
>
> I read both the scripts
>
> make_catalog_backup & delete_catalog_backup.
>
> Found that previous admin has modified this script.
>
> After the statement ,
>
> mysqldump -u ${2}${MYSQLPASSWORD}${MYS
o:br...@ioda-net.ch]
Sent: Montag, 18. Oktober 2010 12:59
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Bacula mysql cleanup
On 10/18/2010 11:06 AM, Holikar, Sachin (ext) wrote:
> Hello,
>
> We have a Bacula Version: 2.2.7 installed on SuSE 9 Linux. The database is
>
Alan Brown wrote:
> Damian Ge;bicki wrote:
>>
>> The bacula.sql, if I good remember, it's your main CatalgoDB - sqlite.
>
> The original poster is using mysql, not sqlite.
>
> bacula.sql is his database dump - it's a plain ascii text file.
>
> It can be compressed with gzip, bzip2, etc etc and y
Brown [mailto:a...@mssl.ucl.ac.uk]
Sent: Montag, 18. Oktober 2010 12:55
To: Damian Ge;bicki
Cc: Holikar, Sachin (ext); bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Bacula mysql cleanup
Damian Ge;bicki wrote:
>
> The bacula.sql, if I good remember, it's your main CatalgoD
On 10/18/2010 11:06 AM, Holikar, Sachin (ext) wrote:
> Hello,
>
> We have a Bacula Version: 2.2.7 installed on SuSE 9 Linux. The database is
> mysql Ver 14.7.
>
> Bacula has been running since couple of years now. We noticed that the mysql
> partition where "Write Bootstrap" files (*.bsr) are
Damian Ge;bicki wrote:
>
> The bacula.sql, if I good remember, it's your main CatalgoDB - sqlite.
The original poster is using mysql, not sqlite.
bacula.sql is his database dump - it's a plain ascii text file.
It can be compressed with gzip, bzip2, etc etc and you should keep
multiple copies ar
Holikar, Sachin (ext) wrote:
> Hello,
>
> I agree if I rename just the file name in bacula-dir.conf , it will
start to write in a new file.
> But the point is the file which has grown in size is "bacula.sql".
> So this is the actual file in question. Can we do something about
this file?
>
al Message-
From: Damian Ge;bicki [mailto:dami...@wasko.pl]
Sent: Montag, 18. Oktober 2010 11:26
To: Holikar, Sachin (ext)
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Bacula mysql cleanup
Holikar, Sachin (ext) wrote:
> Hello,
>
> We have a Bacula Version: 2.2.7 instal
Holikar, Sachin (ext) wrote:
> Hello,
>
> We have a Bacula Version: 2.2.7 installed on SuSE 9 Linux. The database
> is mysql Ver 14.7.
>
> Bacula has been running since couple of years now. We noticed that the
> mysql partition where "Write Bootstrap" files (*.bsr) are stored is
> increase
Hello,
We have a Bacula Version: 2.2.7 installed on SuSE 9 Linux. The database is
mysql Ver 14.7.
Bacula has been running since couple of years now. We noticed that the mysql
partition where "Write Bootstrap" files (*.bsr) are stored is increased alot.
Particularly "bacula.sql" file is grown
13 matches
Mail list logo