Hello.
Danie Theron wrote:
Hi Jo ,
Yes , I am using different Pools for my onsite and offsite backups , however I tested this and because of the backups being quite large , it does take ample time to do a double backup of the same client. The other problem I have is defining the same client more than 2 times in the bacula-dir.conf. Basically I want to have different volumes for different filesets of the same client , but bacula doesn't allow that it seems (?) (see my bacula-dir.conf below). This will ensure my volumes are more logically managed , and also bcopy'ing the volumes to offsite will take less time.
Perhaps you could set up your mailer to break lines around column 70?
And no, you can't define a client twice. How do you expact the director to determine which setup to use? Still, to my knowledge you can use different volumes for different filesets, simply put them in different Pools or, if you don't like that, give them different Media Types. With file storage, media types onsite and offsite sound reasonable.
...
# VerpaktShare Fileset Definitions
FileSet {
Name = "verpaktshare Set"
Include = compression=GZIP9 {
"d:/VerpaktShares"
}
Exclude = { *.exe *.mp3 *.tmp *.pst *.mov *.mpg *.avi *.qts *.rm *.mpeg *.asf
*.wmv *.ogg }
}
This one only as an example: You really should use the new, supported fileset syntax. The old one might work, but Kern discourages it and it will probably vanish soon.
# VerpaktShare Client Definitions
Client {
Name = mercury-fd
Maximum Concurrent Jobs = 2
Address = mercury.verpakt.com
FDPort = 9102
Catalog = MyCatalog
Password = ""
Autoprune = yes
Job Retention = 6 months
File Retention = 60 days
}
# VerpaktShare offsite1 Client Definitions
Client {
Name = mercury-fd
Maximum Concurrent Jobs = 2
Address = mercury.verpakt.com
FDPort = 9102
Catalog = MyCatalog
Password = ""
Autoprune = yes
Job Retention = 6 months
File Retention = 60 days
}
Sorry, I will not go through all that configuration.
What you try seems to be... nonsense.
Sorry if this sounds rude, though.
My hints:
Define clients,
define storage,
define filesets,
define pools for onsite storage, probably putting something like ONSITE in their names,
and define the jobs you want.
First, for onsite storage only.
Apply all necessary schedules.
If all this works I'd continue by
adding storage and pools for offsite storage,
and modifying the schedules to start the necessary jobs for offsite storage, using job override statements in the run clauses.
If you want to copy your onsite volumes for offsite storage that should be quite simple using file storage only: Simply copy the volume files to some removable media. Or, of course, wait until "proper" migration is one of baculas features...
Arno
-- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
