Most likely you have a level override in your schedule
On Tuesday 21 June 2005 23:29, Grant wrote:
Kern,
I realize that the level is catalog and not full, but here is my job
definition...
# Backup the catalog database (after the nightly save)
Job {
Name = BackupCatalog
JobDefs =
Kern,
You were right. Although the syntax I was using was correct, I am
assuming this because my other Schedule definitions are working properly,
that was the problem.
Here is what I had before in the config;
Schedule {
Name = WeeklyCycleAfterBackup
Run = Full Pool = Catalog sun-sat at 3:10
}
Here is the successful job.
21-Jun 08:16 ganymede-dir: Start Backup JobId 109,
Job=BackupCatalog.2005-06-21_08.15.24
21-Jun 08:17 ganymede-sd: 3301 Issuing autochanger loaded drive 0 command.
21-Jun 08:17 ganymede-sd: 3302 Autochanger loaded drive 0, result is Slot 3.
21-Jun 08:17 ganymede-sd:
On 21 Jun 2005 at 13:20, [EMAIL PROTECTED] wrote:
Hello,
I have been getting this error over the last week or so and I can not
figure out what is wrong.
When I run the catalog backup manually from the bconsole it runs fine, I do
not change any of the settings.
You have pasted us the failed
Hello,
I have been getting this error over the last week or so and I can not
figure out what is wrong.
When I run the catalog backup manually from the bconsole it runs fine, I do
not change any of the settings.
Below is the output from the director. Any suggestions would be
appreciated
You should be using Level=Full not Level=Catalog
On Tuesday 21 June 2005 19:20, [EMAIL PROTECTED] wrote:
Hello,
I have been getting this error over the last week or so and I can not
figure out what is wrong.
When I run the catalog backup manually from the bconsole it runs fine, I do
not
Kern,
I realize that the level is catalog and not full, but here is my job
definition...
# Backup the catalog database (after the nightly save)
Job {
Name = BackupCatalog
JobDefs = DefaultJob
Level = Full
FileSet=Catalog
Schedule = WeeklyCycleAfterBackup
# This creates an ASCII copy of
