Re: [Bacula-users] Bacula Enterprise Vmware Plugin Cases
Hello, 2014-09-04 19:33 GMT+02:00 Heitor Faria hei...@bacula.com.br: Hi there, I think this is kind of off-topic, but does anyone use Bacula Enterprice Vmware plugin and would be able to write a few lines about its features / usage to a potential client? Features: - requires vCenter for backup/restore operations - support for esx cluster - clientless solution (does not require Bacula FD installation at vmguest) - when using SAN transport - LANless solution, either - no need to install anything on ESX hosts - support for Full and Incremental (block level) backups with CBT (incremental based on VMware internal track of changed blocks) - perform a disk images and vmguest configuration backup - restore as the new (created) vmguest or local to the backup server as a files - no fear to overwrite original machine - you can select esx host and datastore where you want to restore It can be deployed in the new environment in a few minutes (I'm able to do it in this timeline). In my deployments I configure an automatic backup of new vmguests when they are created and disable a backup of deleted vmguests, so backup admin does not need to handle it manually. If you have additional questions, just ask. best regards -- Radosław Korzeniewski rados...@korzeniewski.net -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Restore from dead client
Just to update my plea for help. My Bacula server is hosted on a Ubuntu 11.10 server Bacula Version is 5.2.2 Problem - Unable to perform a restore of a backup to a different client / location The error given is : 05-Sep 09:48 BS01-DIR1 JobId 12852: Start Restore Job Restore_mail_bluewhale.2014-09-05_09.48.35_24 05-Sep 09:48 BS01-DIR1 JobId 12852: Using Device File_bluewhale 05-Sep 09:48 BS01-FD1 JobId 12852: shell command: run ClientRunBeforeJob /nas/users/admin/scripts/MailRestore.bash 05-Sep 09:48 BS01-FD1 JobId 12852: ClientRunBeforeJob: zimbra: unrecognized service 05-Sep 09:48 BS01-FD1 JobId 12852: ClientRunBeforeJob: zimbra: unrecognized service 05-Sep 09:48 BS01-SD1 JobId 12852: Ready to read from volume mail-0386 on device File_bluewhale (/nas/bacula/bluewhale). 05-Sep 09:48 BS01-SD1 JobId 12852: Forward spacing Volume mail-0386 to file:block 0:219. 05-Sep 10:11 BS01-SD1 JobId 12852: End of Volume at file 28 on device File_bluewhale (/nas/bacula/bluewhale), Volume mail-0386 05-Sep 10:11 BS01-SD1 JobId 12852: End of all volumes. 05-Sep 09:49 BS01-FD1 JobId 12852: Error: create_file.c:292 Could not open /nas/users/admin/backups/data/backups/mail/fifo/mail.tar: ERR=Interrupted system call 05-Sep 10:11 BS01-FD1 JobId 12852: shell command: run ClientAfterJob /nas/users/admin/scripts/MailCleanup.bash 05-Sep 10:11 BS01-FD1 JobId 12852: ClientAfterJob: zimbra: unrecognized service 05-Sep 10:11 BS01-DIR1 JobId 12852: Bacula BS01-DIR1 5.2.2 (26Nov11): Build OS: x86_64-unknown-linux-gnu ubuntu 11.10 JobId: 12852 Job:Restore_mail_bluewhale.2014-09-05_09.48.35_24 Restore Client: besc-bs01 Start time: 05-Sep-2014 09:48:37 End time: 05-Sep-2014 10:11:05 Files Expected: 1 Files Restored: 0 Bytes Restored: 0 Rate: 0.0 KB/s FD Errors: 1 FD termination status: OK SD termination status: OK Termination:Restore OK -- warning file count mismatch I get a zero size mail.tar file in the destination location, so I know the changes in location works. Should I post mf conf files?? Please advise... Thanks--kenny On Fri, Sep 5, 2014 at 10:48 AM, Kenny Noe knoe...@gmail.com wrote: Hi again Apologies for the late reply... I'm juggling several offices and am back to this now. Martin - Thanks for the reply. I have investigated the pre-process script and it does the following : Stop the Zimbra Mail service and runs the tar cmd to create the mail.tar file. Then Bacula uses fifo to backup the tar file into a volume in the SD Catalog. I've tried to restore to the local server and still get the same error. Any one have thoughts?? I REALLY need to get this file restored... Appreciate all the help. Sincerely, --Kenny On Thu, Aug 14, 2014 at 11:42 AM, Martin Simmons mar...@lispworks.com wrote: The error is 12-Aug 09:51 BS01-FD1 JobId 12560: Error: create_file.c:292 Could not open /nas/bacula/data/backups/mail/fifo/mail.tar: ERR=Interrupted system call which is strange. Is /nas/bacula/data/backups/mail/fifo/mail.tar a normal file or are you trying to restore into a FIFO? You could try restoring into a file on the local disk. __Martin On Tue, 12 Aug 2014 10:25:12 -0400, Kenny Noe said: Phil, Thanks for the reply. So now the job runs and reports successful but all I get is a empty file. Here is the output from the log file : 12-Aug 09:50 BS01-DIR1 JobId 12560: Start Restore Job Restore_mail_bluewhale.2014-08-12_09.50.07_59 12-Aug 09:50 BS01-DIR1 JobId 12560: Using Device File_bluewhale 12-Aug 09:50 BS01-FD1 JobId 12560: shell command: run ClientRunBeforeJob /nas/users/admin/scripts/MailRestore.bash 12-Aug 09:50 BS01-FD1 JobId 12560: ClientRunBeforeJob: zimbra: unrecognized service 12-Aug 09:50 BS01-FD1 JobId 12560: ClientRunBeforeJob: zimbra: unrecognized service 12-Aug 09:50 BS01-SD1 JobId 12560: Ready to read from volume mail-0386 on device File_bluewhale (/nas/bacula/bluewhale). 12-Aug 09:50 BS01-SD1 JobId 12560: Forward spacing Volume mail-0386 to file:block 0:219. 12-Aug 10:12 BS01-SD1 JobId 12560: End of Volume at file 28 on device File_bluewhale (/nas/bacula/bluewhale), Volume mail-0386 12-Aug 10:12 BS01-SD1 JobId 12560: End of all volumes. 12-Aug 09:51 BS01-FD1 JobId 12560: Error: create_file.c:292 Could not open /nas/bacula/data/backups/mail/fifo/mail.tar: ERR=Interrupted system call 12-Aug 10:12 BS01-FD1 JobId 12560: shell command: run ClientAfterJob /nas/users/admin/scripts/MailCleanup.bash 12-Aug 10:12 BS01-FD1 JobId 12560: ClientAfterJob: zimbra: unrecognized service 12-Aug 10:12 BS01-DIR1 JobId 12560: Bacula BS01-DIR1 5.2.2 (26Nov11): Build OS: x86_64-unknown-linux-gnu ubuntu 11.10 JobId: 12560 Job:Restore_mail_bluewhale.2014-08-12_09.50.07_59 Restore Client: besc-bs01 Start time:
[Bacula-users] Error: block.c:255 Write errors?
Hello, I sporadically get these types of alerts for one on my bacula tape libraries... 05-Sep 00:41 lawson-sd_L100_ JobId 389348: Error: block.c:255 Write error at 610:412 on device L100-Drive-0 (/dev/L100-Drive-0). ERR=Input/output error. Am I correct in assuming that this was indeed a tape write error, but that bacula will attempt a 2nd write of the same block of data and if that 2nd attempt succeeds proceed on and ultimately have a successfully run job (one that can be restored without issue)? In other words, should this error worry me if it doesn't happen often? It does consistently happen -- with 100's of jobs a night, it probably happens 3-4 times a week. thanks, Stephen -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
So 'update slots kicked' some sense into bacula-dir and it started writing. Summary: 1. You'd think media manipulation commands like delete volume would update bacula's inventory when done. You'd be wrong. You have to manually run 'update slots' every time. This might be documented someplace (don't ask me where). 2. Bacula's clever volume selection algorithm is completely unsuitable for vchanger. If you have multiple disk magazines online you probably want to fill up one disk, then the next. What bacula did here is pick a volume from the next disk when the current one's only 20% full. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
On 09/05/2014 11:59 AM, Dimitri Maziuk wrote: So 'update slots kicked' some sense into bacula-dir and it started writing. duh. 'update slots' kicked... -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
2. Bacula's clever volume selection algorithm is completely unsuitable for vchanger. If you have multiple disk magazines online you probably want to fill up one disk, then the next. What bacula did here is pick a volume from the next disk when the current one's only 20% full. There are several ways to control what volumes bacula use. Although I am uncertian how you got in the situation you were in. John -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
On 09/05/2014 12:16 PM, John Drescher wrote: There are several ways to control what volumes bacula use. Although I am uncertian how you got in the situation you were in. That makes two of us. I 1. deleted some volumes and didn't run 'update slots', 2. got an 'intervention needed' e-mail a day or so later. I'm beginning to think I'd be better off with a simple pre-job script that checks the disk and re-points a symlink to the next disk in the set. Or something along those lines. I've another bacula setup that writes to a single filesystem. It's been running with about zero problems (knock on wood) and zero maintenance for years: auto-labelling works, volume recycling works, the only problems are spinning rust and lsi's ugly raid manglement software. It seems once you step out of the ein drive, ein tape sandbox you're in the not intended for use case and all bets are off. Which is only fine if you don't care about your backups. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
There are several ways to control what volumes bacula use. Although I am uncertian how you got in the situation you were in. That makes two of us. I 1. deleted some volumes and didn't run 'update slots', I am curious to why you are deleting volumes. I mean for my vchanger usage (for 4+ years) I setup a fixed # of fixed sized volumes in each magazine (which is its own filesystem on a disk - only 1 magazine per disk). John -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
On 09/05/2014 12:52 PM, John Drescher wrote: There are several ways to control what volumes bacula use. Although I am uncertian how you got in the situation you were in. That makes two of us. I 1. deleted some volumes and didn't run 'update slots', I am curious to why you are deleting volumes. I mean for my vchanger usage (for 4+ years) I setup a fixed # of fixed sized volumes in each magazine (which is its own filesystem on a disk - only 1 magazine per disk). Spinning rust. I had a weird disk failure: it died after it was filled in and should've had no i/o going on for several days. So volumes that were on it were gone and I needed another backup of whatever was on them asap. (I have post-job rsync that makes a copy of the current disk, so if that dies I can replace it [hopefully] without getting bacula's knickers in a twist. So Murphy made sure the one that died wasn't the one I've a copy of.) -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
On 9/5/2014 1:48 PM, Dimitri Maziuk wrote: I've another bacula setup that writes to a single filesystem. It's been running with about zero problems (knock on wood) and zero maintenance for years: auto-labelling works, volume recycling works, the only problems are spinning rust and lsi's ugly raid manglement software. The whole point of vchanger is to use multiple filesystems as a single autochanger. For a single filesystem I would recommend Bacula's built-in disk autochanger capability or else Bacula's standard disk storage handling. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
On 09/05/2014 01:41 PM, Josh Fisher wrote: On 9/5/2014 1:48 PM, Dimitri Maziuk wrote: I've another bacula setup that writes to a single filesystem. It's been running with about zero problems (knock on wood) and zero maintenance for years: auto-labelling works, volume recycling works, the only problems are spinning rust and lsi's ugly raid manglement software. The whole point of vchanger is to use multiple filesystems as a single autochanger. For a single filesystem I would recommend Bacula's built-in disk autochanger capability or else Bacula's standard disk storage handling. Right, that's my point: when you use bacula's standard disk storage handling you get - automatic volume labeling, - automatic volume recycling, and generally near zero maintenance overhead. With vchanger I - have a job split over different disks, - need to manually fix the catalog every time I sneeze, - get into weird intervention needed loops where bacula mounts a volume it's just filled up and complains it couldn't write to some other volume it shouldn't have tried in the first place. Ergo, if you want to use multiple filesystems, the smart move would be to fake the standard disk storage over multiple filesystems. (As for built-in disk autochanger, Kern's explanation of it never made much sense to me: maybe it's useful for debugging or something...) -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error: block.c:255 Write errors?
Huh, maybe this is a misdiagnosis of the end of tape and a write error only in the sense that there is no tape left. 05-Sep 00:41 SD_L100_ JobId 389348: Error: block.c:255 Write error at 610:412 on device L100-Drive-0 (/dev/L100-Drive-0). ERR=Input/output error. 05-Sep 00:41 SD_L100_ JobId 389348: Re-read of last block succeeded. 05-Sep 00:41 SD_L100_ JobId 389348: End of medium on Volume IM0161 Bytes=1,090,307,051,520 Blocks=520,103 at 05-Sep-2014 00:41. On 09/05/2014 09:42 AM, Stephen Thompson wrote: Hello, I sporadically get these types of alerts for one on my bacula tape libraries... 05-Sep 00:41 lawson-sd_L100_ JobId 389348: Error: block.c:255 Write error at 610:412 on device L100-Drive-0 (/dev/L100-Drive-0). ERR=Input/output error. Am I correct in assuming that this was indeed a tape write error, but that bacula will attempt a 2nd write of the same block of data and if that 2nd attempt succeeds proceed on and ultimately have a successfully run job (one that can be restored without issue)? In other words, should this error worry me if it doesn't happen often? It does consistently happen -- with 100's of jobs a night, it probably happens 3-4 times a week. thanks, Stephen -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
On 9/5/2014 3:16 PM, Dimitri Maziuk wrote: On 09/05/2014 01:41 PM, Josh Fisher wrote: On 9/5/2014 1:48 PM, Dimitri Maziuk wrote: I've another bacula setup that writes to a single filesystem. It's been running with about zero problems (knock on wood) and zero maintenance for years: auto-labelling works, volume recycling works, the only problems are spinning rust and lsi's ugly raid manglement software. The whole point of vchanger is to use multiple filesystems as a single autochanger. For a single filesystem I would recommend Bacula's built-in disk autochanger capability or else Bacula's standard disk storage handling. Right, that's my point: when you use bacula's standard disk storage handling you get - automatic volume labeling, - automatic volume recycling, and generally near zero maintenance overhead. With vchanger I - have a job split over different disks, - need to manually fix the catalog every time I sneeze, Fix the catalog?? - get into weird intervention needed loops where bacula mounts a volume it's just filled up and complains it couldn't write to some other volume it shouldn't have tried in the first place. That is related to the 'update slots' not being issued when a change occurred. This problem also occurs if I forget to issue 'update slots' when I change tape cartridges in a tape autochanger, so I don't really consider that a huge disadvantage. Ergo, if you want to use multiple filesystems, the smart move would be to fake the standard disk storage over multiple filesystems. How? (As for built-in disk autochanger, Kern's explanation of it never made much sense to me: maybe it's useful for debugging or something...) Well, true, it is a [mostly] undocumented feature. I have tested it and it appears to work well, but I cannot say I have used it extensively in production. Kern has stated that it is used in production, though I don't know when/where. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error: block.c:255 Write errors?
Huh, maybe this is a misdiagnosis of the end of tape and a write error only in the sense that there is no tape left. It certainly could be that. John -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
On 09/05/2014 03:10 PM, Josh Fisher wrote: With vchanger I - need to manually fix the catalog every time I sneeze, Fix the catalog?? Run 'update slots' after 'delete volume'. My impression is cartridges in magazines are completely disconnected from volumes in the media catalog; every time you touch one you have to manually fix the other. That is related to the 'update slots' not being issued when a change occurred. This problem also occurs if I forget to issue 'update slots' when I change tape cartridges in a tape autochanger, so I don't really consider that a huge disadvantage. It is, however, quite inconvenient when a backup fails because you removed a full non-recyclable tape cartridge from a completely different magazine. Which is what happened here. I've used legato and tivoli and yes, you have to run inventory on the silo before you could use a new tape, but neither would fail on a missing tape until you actually tried to do some i/o on it. Ergo, if you want to use multiple filesystems, the smart move would be to fake the standard disk storage over multiple filesystems. How? Amanda does (or did last I looked) it by re-pointing a symlink. Presumably that is done at the right time with the right error handling. With bacula the options I can see are pre-job or post-job scripts, the former can at least abort the job on error. I suspect neither can guarantee proper timing. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula Status Report
Hello, I have posted a Bacula Status report to the www.bacula.org site. It discusses the following items: 1. Bacula Release Status 2. Windows Binaries 3. Bacula Enterprise 4. Vacation 5. Bareos The following is a link to the report. http://blog.bacula.org/bacula-status-report-30-august-2014/ Best regards, Kern -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Restore from dead client
Birre,
Thanks for the reply. I guess this is where I get lost...
The fifo is reading a file that was created in the pre-process called
mail.tar. The mail.tar is made from the following directories /opt/zimbra
and /var/mail/zimbra. This is where the Zimbra files and mailstore were
kept.
This pre-process is a script that has this :
*MailBackup.bash*
#!/bin/bash
exec /dev/null
MKDIR=/bin/mkdir
MKFIFO=/usr/bin/mkfifo
RM=/bin/rm
TAR=/bin/tar
DEFCODE=0
DUMPBASE=/data/backups
errCode=${DEFCODE}
mailDir=/var/mail/zimbra
zimbraDir=/opt/zimbra
Main()
{
service zimbra stop
RunMailRestore
service zimbra start
ExitScript ${errCode}
}
RunMailRestore()
{
EXTENSION=.tar
dumpDir=${DUMPBASE}/mail
fifoDir=${dumpDir}/fifo
RebuildFifoDir
${MKFIFO} ${fifoDir}/mail${EXTENSION}
${TAR} -xpf ${fifoDir}/mail${EXTENSION} 21 /dev/null
}
RebuildFifoDir()
{
if [ -d ${fifoDir} ]
then
${RM} -rf ${fifoDir}
fi
${MKDIR} -p ${fifoDir}
}
ExitScript()
{
exit ${1}
}
Main
The restore script simply does a tar xpf instead of a tar cpf.
Below is the *client config* for my mail server
#
# bluewhale
#
Client {
Name = bluewhale
Address= bluewhale.bnesystems.com
Catalog= BS01-Catalog
Password = xxx
FileRetention = 30 days
JobRetention = 30 days
AutoPrune = yes
MaximumConcurrentJobs = 1
}
Job {
Name = Backup_mail_bluewhale
Enabled= yes
Type = Backup
Level = Full
Accurate = yes
Client = bluewhale
FileSet= Full_mail_bluewhale
Messages = Standard
Pool = Pool_mail_bluewhale
Schedule = Schedule_mail_bluewhale
MaxRunTime = 6 hours
MaxStartDelay = 1 hour
ClientRunBeforeJob = /nas/users/admin/scripts/MailBackup.bash
ClientRunAfterJob = /nas/users/admin/scripts/MailCleanup.bash
AllowDuplicateJobs = no
CancelQueuedDuplicates = yes
RunScript {
Command=/nas/users/admin/scripts/MailCleanup.bash
RunsWhen=After
RunsOnFailure=yes
RunsOnClient=yes
RunsOnSuccess=no
}
}
Job {
Name = Restore_mail_bluewhale
FileSet= Full_mail_bluewhale
Type = Restore
Pool = Pool_mail_bluewhale
Client = bluewhale
Messages = Standard
ClientRunBeforeJob = /nas/users/admin/scripts/MailRestore.bash
ClientRunAfterJob = /nas/users/admin/scripts/MailCleanup.bash
RunScript {
Command=/nas/users/admin/scripts/MailCleanup.bash
RunsWhen=After
RunsOnFailure=yes
RunsOnClient=yes
RunsOnSuccess=no
}
}
Job {
Name = Backup_os_bluewhale
Enabled= yes
Type = Backup
Level = Full
Accurate = yes
Client = bluewhale
FileSet= Full_os_bluewhale
Messages = Standard
Pool = Pool_os_bluewhale
Schedule = Schedule_os_bluewhale
MaxRunTime = 6 hours
IncrementalMaxRunTime = 2 hours
DifferentialMaxRunTime = 4 hours
AllowDuplicateJobs = no
CancelQueuedDuplicates = yes
}
Job {
Name = Restore_os_bluewhale
FileSet= Full_os_bluewhale
Type = Restore
Pool = Pool_os_bluewhale
Client = bluewhale
Messages = Standard
}
Pool {
Name = Pool_mail_bluewhale
PoolType = Backup
Storage= Storage_bluewhale
MaximumVolumeJobs = 1
CatalogFiles = yes
AutoPrune = yes
VolumeRetention= 365 days
Recycle= yes
LabelFormat= mail-
}
Pool {
Name = Pool_os_bluewhale
PoolType = Backup
Storage= Storage_bluewhale
MaximumVolumeJobs = 1
CatalogFiles = yes
AutoPrune = yes
VolumeRetention= 365 days
Recycle= yes
LabelFormat= os-
}
Storage {
Name = Storage_bluewhale
Address= 10.10.10.199
SDPort
Re: [Bacula-users] Restore from dead client
Birre,
There are 2 scripts, one does a make backup and the other is a mail
restore. Both scripts are almost exactly the same with one completing
a tar cpf and the other a tar xpf
--Kenny
On Fri, Sep 5, 2014 at 8:33 PM, Birger Blixt bi...@virtualgate.org wrote:
2014-09-05 23:48, Kenny Noe skrev:
Birre,
Thanks for the reply. I guess this is where I get lost...
The fifo is reading a file that was created in the pre-process called
mail.tar. The mail.tar is made from the following directories
/opt/zimbra and /var/mail/zimbra. This is where the Zimbra files and
mailstore were kept.
This pre-process is a script that has this :
*_MailBackup.bash_*
#!/bin/bash
.
RunMailRestore()
{
${TAR} -xpf ${fifoDir}/mail${EXTENSION} 21 /dev/null
}
...
The restore script simply does a tar xpf instead of a tar cpf.
Was that really the contents of the backup script ?, it do a restore.
*_
_*/Birre
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
