Keith T wrote (2014/11/21):
> BTW, any advise/references of tuning "DB dir inserting" faster? Thanks
> in advance!
MySQL: MyISAM & delay_key_write = ALL
and either do not do unexpected power offs (not so hard today), or when
the disaster happens, run "repair table ..." for all tables in bacula
da
Hi Heitor,
Many thanks! But tried to recreate a new database and catalog since I stuck
there for some times. Now, the backup job was running and doing volume 3 data
backup. Hope it will be accomplished in this weekend.
BTW, any advise/references of tuning "DB dir inserting" faster? Thanks in
a
Keith,
Did you check this?
It's for MySQL, but for PgSQL I think would be the same logic.
Fixing table 'bacula.batch' doesn't exist
Newer versions of Bacula create a temporary working table in order to do batch
inserts, which can greatly speed up inserting attributes into the catalog.
Unfo
Keith,
Did you check this?
It's for MySQL, but for PgSQL I think would be the same logic.
Fixing table 'bacula.batch' doesn't exist
Newer versions of Bacula create a temporary working table in order to do batch
inserts, which can greatly speed up inserting attributes into the catalog.
Unfo
Hi Heitor,
Thanks for your kind reply! No upgrade had done in those few months for
Bacula. If DB got error, just query why volume 1 has no problem but always
stuck at volume 2? Is it able to check/repair the DB comes with bacula? Or
shall I check postgresql manual? I ran the job again after rep
10-Nov 01:12 bacula-fd JobId 1105: Error: bsock.c:429 Write error sending 29424
bytes to Storage daemon:localhost:910
3: ERR=Connection reset by peer
10-Nov 01:12 bacula-fd JobId 1105: Fatal error: backup.c:1200 Network send
error to SD. ERR=Connection reset by peer
10-Nov 01:45 bacula-dir Jo
