In most circumstances it will be saved at the point the backup starts. That is
If the file is not there at the start then it will not be in the backup
If you started editing a file after the backup starts the backup will contain
your original (unedited file).
If you are writing a file when the ba
On three separate networks I have
TandbergData (I think they are NEOs now) T24 with 2 SAS LTO-5 drives
TandbergData StorageLoader with LTO-5 drive
Quantum LTO-3 standalone drive (obviously a lot less on that one)
Best wishes.
Dave Mattinson
Eng/Tech/Sci
This email and any attachments to it may b
I cannot see anywhere that status schedule is a valid command. I suspect it is
translated to something like 'status storage', but I may be wrong on that as my
status storage doesn't mention scheduled jobs. If you just want to know the
next scheduled jobs just do a 'status dir'. The first few
I would try Recycle = yes in pool definition or set one of the purged volumes
status to recycle and see if it will mount then.
Dave
Pool {
Name = Pool4
Pool Type = Backup
Recycle = no # Bacula can automatically recycle Volumes
AutoPrune = no # Pr
root@pisces:/usr/local/share/bacula# ./update_postgresql_tables
Looks like you are running it as root. Do it as the bacula user/role, normally
called bacula
su - bacula
/usr/local/share/bacula/ update_postgresql_tables
Or use the -c su option if your security doesn't allow above.
Dave
This em
I have just updated Bacula-2.2.8 to 3.0.1 and am having a little
trouble.
Running on Solaris 10 10/08, postgreSQL 8.3
When I try to update a volume using mediaID rather than volume name I
get an error.
Update volume
1 (status)
| 109 | DS.016 | Append| 1 | 629,992,129,536
Cody Building, Ively Road, Farnborough,
Hampshire, GU14 0LX, United Kingdom
http://www.qinetiq.com/home/notices/legal.html
Date: Wed, 13 May 2009 09:50:42 -0400
From: "K. M. Peterson"
Subject: Re: [Bacula-users] Delay between end of despool and spooling
again
To: Mattinson David
Cc
Hi
I have installed Bacula-3.0.1 (gcc 3.4.3) on a Solaris 10 10/08 Sun
T5420 server with a Quantum Superloader DLT-S4 attached. postgreSQL
database.
I use a spool area of 5GB and the backup always progresses to normal
completion & no btape issues.
The normal sequence of events for a local 360GB