ured use duration exceeded. Marking Volume "Media3" as Used.
WOOHOO!Here's a gotcha though. All previously created volumes will have to have the Volume Use Duration set manually to 23h. Do this using the "update" command.Good luck.>>> Kumaran Babu <
[EMAIL PROTECTED]&
IP @ www.itsyourip.com
On 12/20/05, Kumaran Babu <[EMAIL PROTECTED]> wrote:
Hello All,
I still have a problem with the Bacula backup software waiting for me enter STATUS 1 and then UNMOUNT and MOUNT to start the backup everyday.
The Volume Retention Period and Use Period is set for 5
Is Volume Retention is same as VolumeRetention (A space in between?)
Kumaran
On 12/20/05, Kumaran Babu <[EMAIL PROTECTED]> wrote:
Hello All,
I still have a problem with the Bacula backup software waiting for me enter STATUS 1 and then UNMOUNT and MOUNT to start the backup everyday.
Hello All,
I still have a problem with the Bacula backup software waiting for me enter STATUS 1 and then UNMOUNT and MOUNT to start the backup everyday.
The Volume Retention Period and Use Period is set for 5 days (for daily backups - 6 tapes in rotation) and 18 days for Weekly backups (3 tape
wrote:
My best guess is that you did not read either the Bacula rescue manual chapteror the README in the rescue source, and hence you failed to run the
configuration prior to trying to run make.On Friday 02 December 2005 10:50, Kumaran Babu wrote:> I'm <bacula-users@lists.sourcefor
I'm trying to create a Rescue disk for Bacula 1.38 on a Centos 4.0 OS but it throws error at "make bacula" part of it where it runs in a loop with the following message on the screen:
collecting system info ...Done collecting info.Begin creating scripts ...Done making partitioning scriptsBe
Hi,
I've installed Bacula on my Debian Server thro' apt-get and hence there is no Rescue folder setup. Whats the best way to go about setting up Disaster recovery on my server. I know I can download the Rescue source from
Sorceforge.net. But, I need to know, if there is any specific procedure t
Thanks for that... I've enabled the Run before script and as said earlier changed the retention period to 5 days. Things look fine for now and I shall keep the forum posted on this.
Kumaran
On 10/25/05, Arno Lehmann <[EMAIL PROTECTED]> wrote:
Hello,On 25.10.2005 10:00, Kumaran Babu
I'm experiencing the same problem with
1. The backup will sit and wait for a MOUNT command to start a backup.
2. Sta 2/3/4 will not bring up what it does when you type STA and then 1/2/3/4
I do not run a RUN before script. I have a daily full backup as in this case and a seperate Pool with 1 volu
