Il giorno gio, 05/07/2012 alle 13.58 +0200, Uwe Schuerkamp ha scritto:
> If the copy job finishes successfully, I'd simply ignore the "starting
> full backup" job message
> ;-)
Ok, but this is not an answer :)
I would like to know why bacula is telling me that a new full backup
is being made in c
On Tue, Jul 03, 2012 at 07:14:36PM +0200, Gandalf Corvotempesta wrote:
>
> The full client backup is not run, as far as I can see.
> A full backup will take many many hours and actually the copy jobs
> ends in a couple of minutes.
If the copy job finishes successfully, I'd simply ignore the "star
Il giorno mar, 03/07/2012 alle 15.30 +0200, Uwe Schuerkamp ha scritto:
> can you post your copy job definition?
Job {
Name = "myclient-TapeCopyFull"
Type = Copy
Pool = myclient-FullPool
#Level = Full
Client = myclient-fd
Fileset = None
Priority = 11
SpoolData = No
Selection Type
On Tue, Jul 03, 2012 at 03:06:48PM +0200, Gandalf Corvotempesta wrote:
> I'm still having issue with a copy job.
> I'm trying to copy a job using this selection query:
>
Hello Gandalf,
can you post your copy job definition? Have you checked if a full
*client* backup is started after that message
I'm still having issue with a copy job.
I'm trying to copy a job using this selection query:
SELECT * FROM Job WHERE (EndTime BETWEEN NOW() - INTERVAL 40 DAY AND
NOW()) AND Type = 'B' AND Level = 'F' AND (JobStatus = 'e' OR JobStatus
= 'T') AND Name = 'myclient-job' GROUP BY Name;
This query seem
I'm getting far too tired to follow this one... :)
I noticed that a Copy to Tape job was putting my incremental backups
into a full pool. That is, the original job was level = incremental.
The copy to tape was run at level = full.
I wasn't sure why, but I think I've found it.
This is the orig
