I am trying to back up a large disk that is greater than the size of the
disk that I save my data to (eventually it gets migrated to tape).
The issue is that I have it run for 16 hours at max, but when those 16
hours end, it marks the jobs canceled by user, and I cannot migrate it
to tape. Also when I run the job again, it starts over from scratch
instead of continuing from where it left off. Is there a way to change
this? I have a feeling that if I removed the time limit, I would hit
the same problem when the disk fills.
Dan
Here is the appropriate part of my director config:
Job {
Name = "file-server Backup"
Type = Backup
Level = Incremental
Client = file-server-fd
FileSet = "file-server Set"
Pool = 45tZFS
Messages = Standard
Max Run Time = 16h
}
Client {
Name = file-server-fd
Address = file-server.igb.illinois.edu
FDPort = 9102
Catalog = MyCatalog
Password = "xxxxxxxx" # password for FileDaemon 2
File Retention = 60 days # 60 days
Job Retention = 6 months # six months
AutoPrune = yes # Prune expired Jobs/Files
}
Parts of two job logs that show it starts over:
2016-04-13 14:28:58
bacula-dir
No prior Full backup Job record found.
No prior or suitable Full backup found in catalog. Doing FULL backup.
2016-04-14 08:09:46
bacula-dir
No prior Full backup Job record found.
No prior or suitable Full backup found in catalog. Doing FULL backup.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
