Re: [Bacula-users] Imitate Veritas behaviour
Anybody?
Guy Zuercher wrote:
Hello List,
my company is using bacula for quite a while and we find it is a
really cool piece of software! So thanks to Kern and everybody else
involved.
I would like to know if anybody managed to imitate the behaviour of
Veritas as close as possible for the following scenario:
- Customers do full backups in multiple jobs every night
- Customers sometime forget to change the tape, so it shall be
overwritten in that case
- Sometimes customers take out the monthly tape and put it away
- Some customers have autochanger's, some just a normal TapeDrive
but i think that does not matter for this question
Now the behaviour of most commercial backup applications (like Veritas)
is to overwrite the tape in case it has been left in the drive from the
previous day. Only if the tape is overwritten, the records are being
purged from the database otherwise the configured retention periods apply.
I tried to imitate this behaviour with Bacula v1.36, v1.38 and v2.01
without success. Here is the relevant config of a simple DLT drive.
Pool {
Name = WeeklyPool
Pool Type = Backup
AutoPrune = yes
Volume Retention = 15h
Volume Use Duration = 15h
Recycle = yes
Recycle Current Volume = yes
Maximum Volumes = 0
}
This works nicely, but obviously the only gotcha is, that records are
being purged from the database every 15 hours (daily). But without
specifying Volume Retention AND Volume Use Duration together it does
not work either.
I thought of using Maximum Volume Jobs, but this is unhandy, since the
database has to be adjusted every time a job is added or deleted.
Another option would be to set AutoPrune to no and drop the records
manually. The best directive would probably be Use Volume Once, but
this is to be deprecated.
I am looking for some lean solution without helper scripts, cronjobs and
just one pool.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Imitate Veritas behaviour
I'm not sure this is possible without some kind of admin job that you
would run before the backups to see what tape is still in the drive.
Then your admin job would do the house keeping necessary to reuse the tape.
Another Vertias feature I like that bacula does not have is the append
period. This is a time window after the tape was last written to that
would allow another append.
brian-
Guy Zürcher wrote:
Anybody?
Guy Zuercher wrote:
Hello List,
my company is using bacula for quite a while and we find it is a
really cool piece of software! So thanks to Kern and everybody else
involved.
I would like to know if anybody managed to imitate the behaviour of
Veritas as close as possible for the following scenario:
- Customers do full backups in multiple jobs every night
- Customers sometime forget to change the tape, so it shall be
overwritten in that case
- Sometimes customers take out the monthly tape and put it away
- Some customers have autochanger's, some just a normal TapeDrive
but i think that does not matter for this question
Now the behaviour of most commercial backup applications (like Veritas)
is to overwrite the tape in case it has been left in the drive from the
previous day. Only if the tape is overwritten, the records are being
purged from the database otherwise the configured retention periods apply.
I tried to imitate this behaviour with Bacula v1.36, v1.38 and v2.01
without success. Here is the relevant config of a simple DLT drive.
Pool {
Name = WeeklyPool
Pool Type = Backup
AutoPrune = yes
Volume Retention = 15h
Volume Use Duration = 15h
Recycle = yes
Recycle Current Volume = yes
Maximum Volumes = 0
}
This works nicely, but obviously the only gotcha is, that records are
being purged from the database every 15 hours (daily). But without
specifying Volume Retention AND Volume Use Duration together it does
not work either.
I thought of using Maximum Volume Jobs, but this is unhandy, since the
database has to be adjusted every time a job is added or deleted.
Another option would be to set AutoPrune to no and drop the records
manually. The best directive would probably be Use Volume Once, but
this is to be deprecated.
I am looking for some lean solution without helper scripts, cronjobs and
just one pool.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Imitate Veritas behaviour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How is that different from VolumeUseDuration (are you saying only that
you wish the clock started counting from the end of the backup? if so,
that is sort of easily kludged around by adding the backup time to this
window). Or are you talking about the fact that this window does not get
pushed every time it is written to?
Brian Debelius wrote:
I'm not sure this is possible without some kind of admin job that you
would run before the backups to see what tape is still in the drive.
Then your admin job would do the house keeping necessary to reuse the tape.
Another Vertias feature I like that bacula does not have is the append
period. This is a time window after the tape was last written to that
would allow another append.
brian-
Guy Zürcher wrote:
Anybody?
Guy Zuercher wrote:
Hello List,
my company is using bacula for quite a while and we find it is a
really cool piece of software! So thanks to Kern and everybody else
involved.
I would like to know if anybody managed to imitate the behaviour of
Veritas as close as possible for the following scenario:
- Customers do full backups in multiple jobs every night
- Customers sometime forget to change the tape, so it shall be
overwritten in that case
- Sometimes customers take out the monthly tape and put it away
- Some customers have autochanger's, some just a normal TapeDrive
but i think that does not matter for this question
Now the behaviour of most commercial backup applications (like Veritas)
is to overwrite the tape in case it has been left in the drive from the
previous day. Only if the tape is overwritten, the records are being
purged from the database otherwise the configured retention periods apply.
I tried to imitate this behaviour with Bacula v1.36, v1.38 and v2.01
without success. Here is the relevant config of a simple DLT drive.
Pool {
Name = WeeklyPool
Pool Type = Backup
AutoPrune = yes
Volume Retention = 15h
Volume Use Duration = 15h
Recycle = yes
Recycle Current Volume = yes
Maximum Volumes = 0
}
This works nicely, but obviously the only gotcha is, that records are
being purged from the database every 15 hours (daily). But without
specifying Volume Retention AND Volume Use Duration together it does
not work either.
I thought of using Maximum Volume Jobs, but this is unhandy, since the
database has to be adjusted every time a job is added or deleted.
Another option would be to set AutoPrune to no and drop the records
manually. The best directive would probably be Use Volume Once, but
this is to be deprecated.
I am looking for some lean solution without helper scripts, cronjobs and
just one pool.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
- --
_ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III
|$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD4DBQFGm3s+mb+gadEcsb4RAguBAJMGJVyFN7SmcJ1jPnQGC1FdYO5tAKCBQkMq
djTPCj+ZNIHvVMez8aOv6A==
=qig4
-END PGP SIGNATURE-
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Imitate Veritas behaviour
Forget what I just said. I always get the overwrite period, and the
append period mixed up. I am talking about the overwrite period.
VolumeUseDuration starts the time window from the first write to the
tape. This is similar to the backup exec append period The
overwrite period in backup exec, starts the time window at the last
write to a tape. So if I had an infinite append period, and a 12 hour
overwrite period, then the tape could be appended to until 12 hours from
the last job, after which the tape could be recylced.
Ryan Novosielski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How is that different from VolumeUseDuration (are you saying only that
you wish the clock started counting from the end of the backup? if so,
that is sort of easily kludged around by adding the backup time to this
window). Or are you talking about the fact that this window does not get
pushed every time it is written to?
Brian Debelius wrote:
I'm not sure this is possible without some kind of admin job that you
would run before the backups to see what tape is still in the drive.
Then your admin job would do the house keeping necessary to reuse the tape.
Another Vertias feature I like that bacula does not have is the append
period. This is a time window after the tape was last written to that
would allow another append.
brian-
Guy Zürcher wrote:
Anybody?
Guy Zuercher wrote:
Hello List,
my company is using bacula for quite a while and we find it is a
really cool piece of software! So thanks to Kern and everybody else
involved.
I would like to know if anybody managed to imitate the behaviour of
Veritas as close as possible for the following scenario:
- Customers do full backups in multiple jobs every night
- Customers sometime forget to change the tape, so it shall be
overwritten in that case
- Sometimes customers take out the monthly tape and put it away
- Some customers have autochanger's, some just a normal TapeDrive
but i think that does not matter for this question
Now the behaviour of most commercial backup applications (like Veritas)
is to overwrite the tape in case it has been left in the drive from the
previous day. Only if the tape is overwritten, the records are being
purged from the database otherwise the configured retention periods apply.
I tried to imitate this behaviour with Bacula v1.36, v1.38 and v2.01
without success. Here is the relevant config of a simple DLT drive.
Pool {
Name = WeeklyPool
Pool Type = Backup
AutoPrune = yes
Volume Retention = 15h
Volume Use Duration = 15h
Recycle = yes
Recycle Current Volume = yes
Maximum Volumes = 0
}
This works nicely, but obviously the only gotcha is, that records are
being purged from the database every 15 hours (daily). But without
specifying Volume Retention AND Volume Use Duration together it does
not work either.
I thought of using Maximum Volume Jobs, but this is unhandy, since the
database has to be adjusted every time a job is added or deleted.
Another option would be to set AutoPrune to no and drop the records
manually. The best directive would probably be Use Volume Once, but
this is to be deprecated.
I am looking for some lean solution without helper scripts, cronjobs and
just one pool.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
- --
_ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III
|$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD4DBQFGm3s+mb+gadEcsb4RAguBAJMGJVyFN7SmcJ1jPnQGC1FdYO5tAKCBQkMq
djTPCj+ZNIHvVMez8aOv6A==
=qig4
-END PGP SIGNATURE-
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
