[Bacula-users] Job vs volume retention periods
Hi, I'm confused in regards to job retention vs volume retention. From the little bit I understand, if the volume retention period is passed and bacula is unable to find any other appendable volumes in the client's stoarge pool, it will delete all file and job records and then re-use that volume. However, how about if all the jobs in that volume have been pruned but the volume retention period hasn't passed yet (and of course recycling is enabled) Will bacula still re-use the volume since no more jobs remained after they've all been pruned? If it does, what's the purpose of having a volume retention period which is usually without a doubt longer than the job retention period? If it doesn't, what's the point of keeping a volume which doesn't contain jobIDs which can't be restored anymore? thanks in advance, Erik +-- |This was sent by erik.go...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Passing the current Storage to a Run Before Job script
Greetings!
I'm hopeful that someone can give us a little help. We currently run Bacula
2.4.4. We have backups run on two storage devices, and each device has its own
spool file directory. We've created a script that will check the spool
directory at the start of each job to make sure that it's empty, since we've
had a few issues with Bacula not deleting files due to crashes.
The issue comes in when we have to run a job on the other drive. For example,
twice a year we run full backups of all of our file sets to be stored offsite.
During this period, jobs that would normally run on our second tape drive are
manually run on the primary drive instead, so that the second drive can be
devoted to the offsite jobs. Unfortunately, the spool check script doesn't know
about the storage change, so it will end up clobbering a valid spool file for
the secondary drive, instead of checking the directory for the primary drive.
I've tried to find a variable to pass to the Run Before Job command to tell
it the actual current storage, but have had no luck (${Storage} doesn't expand
during the call). Does anyone know of a way to pass the storage to the script
(without using Python)?
Thank You,
Tom
+--
|This was sent by tomisom.s...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Release Drive0 no longer works (99% of time)
Has anyone else running Debian Lenny had/have this problem? Since upgrading from Debian Etch to Debian Lenny, I have found that release Drive0 does not unrelease the tape (DEC DLT single tape) in 99% of occassions. The message about drive waiting for sysop is still printed on the consol, but I now have to (99% of time) enter a unmount Drive0 command at the console, before it will unload the tape. InitiallyI thought it might have been related to replacing the adaptec scsi card with a qlogic scsi card, which occurred at the same time as the distribution upgrade, but the adaptec card has returned to this system and the problem still persists. Does anyone have any ideas of causes? I suspect that yet another righteous dabble has been carried out in some application in Debian and this lack of functionlity in the scsi system is the result. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Job vs volume retention periods
Hi Erik, volumes will only be reused after the volume retention period is reached. And the point of keeping a volume which doesn't contain jobIDs is that you could import the tape or recover data from it using btape since it still contains all files. Kind regards Julian -Ursprüngliche Nachricht- Von: phatrik [mailto:bacula-fo...@backupcentral.com] Gesendet: Mittwoch, 24. Juni 2009 03:46 An: bacula-users@lists.sourceforge.net Betreff: [Bacula-users] Job vs volume retention periods Hi, I'm confused in regards to job retention vs volume retention. From the little bit I understand, if the volume retention period is passed and bacula is unable to find any other appendable volumes in the client's stoarge pool, it will delete all file and job records and then re-use that volume. However, how about if all the jobs in that volume have been pruned but the volume retention period hasn't passed yet (and of course recycling is enabled) Will bacula still re-use the volume since no more jobs remained after they've all been pruned? If it does, what's the purpose of having a volume retention period which is usually without a doubt longer than the job retention period? If it doesn't, what's the point of keeping a volume which doesn't contain jobIDs which can't be restored anymore? thanks in advance, Erik +-- |This was sent by erik.go...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] File daemon at .... rejected Hello command
Hi, On Tue, 23 Jun 2009, Arno Lehmann wrote: and welcome here! I hope you find all the advice you need here - and I'm sure you'll be able to halp others, too! Thanks. I have so far :-) Gavin -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Restoring large directory does not work
On Tue, 23 Jun 2009 16:09:57 -0700, mehma sarja said: Did you wait till the cpu went back to low cpu usage? No, it stays high overnight and my patience runs out before cpu pegging does. I suggest attaching gdb to the bacula-dir process to see what it is doing, e.g. thread apply all bt Then detach gdb, let it run some more, and do the above again to see how it differs. You might need to build a debugging version of Bacula to get useful backtraces. __Martin -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] dir and sd hang
Silver Salonen wrote: On Tuesday 16 June 2009 15:08:29 Attila Fülöp wrote: Silver Salonen wrote: Hi. I use Bacula 3.0.0 on FreeBSD-6.3. The problem I have is that DIR and SD tend to hang often, and it seems one causes another, because they do it together mostly. Sometimes it happens between jobs, sometimes it happens before all the jobs. The only possibility unlock the processes is to kill them with -9 and start again. After that backups work usually a few days and then the processes hang again. Silver, not sure if you have already seen this: http://security.freebsd.org/advisories/FreeBSD-EN-09:04.fork.asc Maybe this patch will fix your problems with FreeBSD 7.0. Attila Anyone else experiencing this? I fixed thread related bacula 2.2.8 stability issues by moving from 6.3- RELEASE to 6.3-STABLE. It has a threadlib patch which 6.3-RELEASE has not. The issue was that concurrent backups would after a while result in a locked dir and sd. So your problem sounds related and you may give 6.3-STABLE a try. I would appreciate any feedback since we are planing to update to 3.0.x. Stability issues would of course change our modus operandi. HTH Attila Well, Bacula SD had a 'hang issue' in 2.4.4 too, but it got patched (and it was different..). After the patch it worked very well. About the issue in 3.0.0 - I actually see the same thing on FreeBSD-7.0 as well, so I guess moving the one server from 6.3-RELEASE to STABLE won't fix that. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Job vs volume retention periods
On Wed, 2009-06-24 at 09:14 +0200, Fahrer, Julian wrote:
Hi Erik,
volumes will only be reused after the volume retention period is reached.
And the point of keeping a volume which doesn't contain jobIDs is that you
could import the tape or recover data from it using btape since it still
contains all files.
Greetings
Julian is correct with exceptions.
Recycle Oldest Volume = yes
Recycle Current Volume = yes
PurgeOldestVolume = yes
Warning, the following description may not be perfect:
I use recycle oldest and purge oldest. This way, the job records can be
maintained in the catalog with an unresonably long job retention period.
When the director completes jobs, it will still perform pruning
operations pruning file records.
Then when the director goes to schedule a job, it will purge job records
from the volume and label it recycled if all jobs have had their file
records pruned. The volume chosen to recyle will be the one that has
not been written to for the longest period.
The status dir will show the recycled volume as the volume scheduled to
use.
For instance, I have a pool with two tapes for Tuesday and Thursday. I
want to use it four times then have it schedule using the othe tape
rotating every two weeks.
Pool {
Name = LTO_TueThu
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 16 Days
Volume Use Duration = 10 Days
Recycle Oldest Volume = yes
PurgeOldestVolume = yes
Storage = LTO
}
Set it up recently and it seems to work so far. Best of luck. The
documentation is awesome because there are so many possible parameters.
The one thing that may be missing is more recipes from current users.
Dirk
Kind regards
Julian
-Ursprüngliche Nachricht-
Von: phatrik [mailto:bacula-fo...@backupcentral.com]
Gesendet: Mittwoch, 24. Juni 2009 03:46
An: bacula-users@lists.sourceforge.net
Betreff: [Bacula-users] Job vs volume retention periods
Hi,
I'm confused in regards to job retention vs volume retention. From the
little bit I understand, if the volume retention period is passed and bacula
is unable to find any other appendable volumes in the client's stoarge pool,
it will delete all file and job records and then re-use that volume.
However, how about if all the jobs in that volume have been pruned but the
volume retention period hasn't passed yet (and of course recycling is
enabled) Will bacula still re-use the volume since no more jobs remained
after they've all been pruned? If it does, what's the purpose of having a
volume retention period which is usually without a doubt longer than the job
retention period? If it doesn't, what's the point of keeping a volume which
doesn't contain jobIDs which can't be restored anymore?
thanks in advance,
Erik
+--
|This was sent by erik.go...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Rewind permissions error in SD (UNCLASSIFIED)
Classification: UNCLASSIFIED Caveats: NONE I have installed Bacula on a Solaris 10 system using a StorEdge C2 tape jukebox. When I try to label a tape, I get the following error: Unable to open device SDLT1-Drive (/dev/rmt/0mbn): ERR=Permission denied Using the mt command (mt -f /dev/rmt/0mbn rewind), I can rewind the tape without errors. I ran the bacula-sd daemon in debug mode and got the output below. It appears that the rewind of the tape following the open fails due to permission problems (even though all 3 daemons are running as root and /dev/rmt/0mbn has 666 permissions). Line 441 in dev.c is after a d_ioctl() rewind call that apparently fails. backups-bge0-sd: dev.c:336-0 Close fd for mode change. backups-bge0-sd: dev.c:345-0 open dev: type=2 dev_name=SDLT-Drive (/dev/rmt/0mbn) vol=test118 mode=OPEN_READ_WRITE backups-bge0-sd: dev.c:394-0 Open dev: device is tape backups-bge0-sd: dev.c:409-0 Try open SDLT1-Drive (/dev/rmt/0mbn) mode=OPEN_READ_WRITE backups-bge0-sd: dev.c:431-0 Rewind after open backups-bge0-sd: dev.c:441-0 Rewind error on SDLT1-Drive (/dev/rmt/0mbn) close: ERR=Permission denied backups-bge0-sd: dev.c:475-0 dev.c:474 Unable to open device SDLT1-Drive (/dev/rmt/0mbn): ERR=Permission denied backups-bge0-sd: dev.c:483-0 open dev: tape -1 opened backups-bge0-sd: dev.c:358-0 preserve=0x0 fd=-1 backups-bge0-sd: dev.c:1892-0 Clear volhdr vol= backups-bge0-sd: vol_mgr.c:562-0 vol_unused: no vol on SDLT1-Drive (/dev/rmt/0mbn) Any ideas? Thanks, Andy Classification: UNCLASSIFIED Caveats: NONE -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Upgrading from bacula 2 to 3
Hello I am a newbie in bacula , I've inherited it from another admin . I saw the our version is an old version and i wanted to upgrade to the latest version , i looked at the bacula documentation to see if there is an upgrade procedure and couldn't find any . Is there an unofficial guide as to how to upgrade from version 2 to version 3 of bacula ? Thank you -- Assaf Flatto IMPORTANT . this email and the information in it may be confidential, legally privileged and/or protected by law. It is intended solely for the use of the person to whom it is addressed. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Please also delete all copies of this email and any attachments from your system. We cannot guarantee the security or confidentiality of email communications. We do not accept any liability for losses or damages that you may suffer as a result of your receipt of this email including but not limited to computer service or system failure, access delays or interruption, data non-delivery or mis-delivery, computer viruses or other harmful components. Copyright in this email and any attachments belong to Select Service Partner UK Limited. Should you communicate with anyone at Select Service Partner UK Limited by email, you consent to us monitoring and reading any such correspondence. Nothing in this email shall be taken or read as suggesting, proposing or relating to any agreement concerted practice or other practice that could infringe UK or EC competition legislation. Select Service Partner UK Limited is a company registered in England and Wales (company number 05687183) whose registered office is at 1 The Heights, Brooklands, Weybridge. Surrey. KT13 0NY -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Upgrading from bacula 2 to 3
On Wed, 2009-06-24 at 16:30 +, Assaf Flatto wrote: Hello I am a newbie in bacula , I've inherited it from another admin . I saw the our version is an old version and i wanted to upgrade to the latest version , i looked at the bacula documentation to see if there is an upgrade procedure and couldn't find any . First get a good catalog backup. Also make sure that you have a backup of the /etc/bacula as well. tar -czf /etc/bacula.tgz /etc/bacula just to have that easy to get to. http://www.bacula.org/manuals/en/install/install/Installing_Bacula.html#SECTION0032 Most all syntax of the config files will migrate. So that should not be a problem. There is usually just the update to the db schema. Dirk Is there an unofficial guide as to how to upgrade from version 2 to version 3 of bacula ? Thank you -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Upgrading from bacula 2 to 3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Assaf Flatto wrote: Hello I am a newbie in bacula , I've inherited it from another admin . I saw the our version is an old version and i wanted to upgrade to the latest version , i looked at the bacula documentation to see if there is an upgrade procedure and couldn't find any . Is there an unofficial guide as to how to upgrade from version 2 to version 3 of bacula ? You might want to check the release notes, especially the bit about the catalog format changes: http://sourceforge.net/project/shownotes.php?group_id=50727release_id=679402 Other than SQL schema changes, there's rarely something you have to modify, but watch out and double check your config files anyway, and of course monitor Bacula more closely after the upgrade. Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkpCYK0ACgkQ2Vs+MkscAyVDlACgsh0sFD9onspwSB82wwnb6JYr mmQAniIJIxt7e4ZiH7Y5AjBGhtiCfFOX =N++Y -END PGP SIGNATURE- -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Restoring large directory does not work
I got into gdb but know very little how to move around in there. I tried: [r...@lucifer ~]# gdb /usr/local/sbin/bacula-dir 27410 GNU gdb 6.1.1 [FreeBSD] This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... Attaching to program: /usr/local/sbin/bacula-dir, process 27410 Reading symbols from /usr/local/lib/libpq.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpq.so.5 Reading symbols from /lib/libcrypt.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.4 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. [New Thread 0x801a10300 (LWP 100334)] [New Thread 0x801902600 (LWP 100329)] [New Thread 0x801902480 (LWP 100192)] [New Thread 0x801902180 (LWP 100350)] Loaded symbols for /lib/libthr.so.3 Reading symbols from /usr/local/lib/libintl.so.8...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libintl.so.8 Reading symbols from /usr/lib/libwrap.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libwrap.so.5 Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /usr/lib/libssl.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libssl.so.5 Reading symbols from /lib/libcrypto.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypto.so.5 Reading symbols from /usr/lib/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 [Switching to Thread 0x801a10300 (LWP 100334)] 0x0040c043 in add_findex () -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Firewall fun
On Tue, 2009-06-23 at 21:52 +0200, Arno Lehmann wrote: Hi, 23.06.2009 17:04, Dirk Bartley wrote: Sure, iptables allows for connection based rules as well as the old ipchains style rules based rules. So your probably using connection based rules like : iptables -A INPUT -p tcp -m state --state ESTABLISHED -j ACCEPT iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -j ACCEPT just add something like iptables -A INPUT -p tcp --source fd_dmz_ipaddress --destination sd_internal_address --dport 9103 ACCEPT Yup. That should work. But back to your problem, Dirk: Have you tried the heartbeat interval setting? That should generate some traffic so that the pix doesn't time-out the seemingly stale connection. Tried 2 different things and on of them fixed it. Added heartbeat interval = 90 to the file daemon in the dmz and also added sysopt connection timewait to the firewall. One of the two fixed it, well at least I got a good full backup last night. Thanks for the suggesion! Dirk Arno -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Restoring large directory does not work
(gdb) thread apply all bt Thread 4 (Thread 0x801902180 (LWP 100350)): #0 0x0008016f98cc in nanosleep () from /lib/libc.so.7 #1 0x0008009078c5 in nanosleep () from /lib/libthr.so.3 #2 0x0044e21e in bmicrosleep () #3 0x0042408d in wait_for_next_job () #4 0x00408a3c in main () Thread 3 (Thread 0x801902480 (LWP 100192)): #0 0x000801715afc in select () from /lib/libc.so.7 #1 0x0008009074d4 in select () from /lib/libthr.so.3 #2 0x0044f9b2 in bnet_thread_server () #3 0x00438ba8 in connect_thread () #4 0x000800908a27 in pthread_getprio () from /lib/libthr.so.3 #5 0x in ?? () Error accessing memory address 0x7fbff000: Bad address. #0 0x0040c043 in add_findex () -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Upgrading from bacula 2 to 3
I am a newbie in bacula , I've inherited it from another admin . I saw the our version is an old version and i wanted to upgrade to the latest version , i looked at the bacula documentation to see if there is an upgrade procedure and couldn't find any . Is there an unofficial guide as to how to upgrade from version 2 to version 3 of bacula ? I may not be able to help much, but to get any more detailed advice, find out and provide this information: - on what OS your current Bacula server runs - more precisely, what version it is, like 2.0.x or 2.4.x - find out how it was installed: using some OS-spesific package manager (like rpm in Red Hat based systems), or was it possibly compiled on-site from a tarball - some gurus might want to know what database (like MySQL) is used If this is an install from eg. rpm-packages provided by Bacula developers, the upgrade could be very straightforward and automatic process. On the other side, some packages (like for Debian, AFAIK) may be built by OS packagers and not by Bacula developers at all, and in that case you'd better to search for information in OS-spesific forums too. -- TiN -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Restoring large directory does not work
On Wed, 24 Jun 2009 10:41:03 -0700, mehma sarja said: (gdb) thread apply all bt Thread 4 (Thread 0x801902180 (LWP 100350)): #0 0x0008016f98cc in nanosleep () from /lib/libc.so.7 #1 0x0008009078c5 in nanosleep () from /lib/libthr.so.3 #2 0x0044e21e in bmicrosleep () #3 0x0042408d in wait_for_next_job () #4 0x00408a3c in main () Thread 3 (Thread 0x801902480 (LWP 100192)): #0 0x000801715afc in select () from /lib/libc.so.7 #1 0x0008009074d4 in select () from /lib/libthr.so.3 #2 0x0044f9b2 in bnet_thread_server () #3 0x00438ba8 in connect_thread () #4 0x000800908a27 in pthread_getprio () from /lib/libthr.so.3 #5 0x in ?? () Error accessing memory address 0x7fbff000: Bad address. #0 0x0040c043 in add_findex () The function add_findex is interesting, but I think like your bacula-dir was compiled without debugging info so it is difficult to see what is happening. Try the following gdb commands (I assume you are running 64-bit FreeBSD): break *add_findex commands printf arguments: %x %x %x\n, $rdi, $rsi, $rdx end continue This sets a breakpoint at the start of the function add_findex to print the arguments and starts Bacula running again. It should stop in gdb when it reaches the beginning of add_findex again (with a message like Breakpoint 1...in add_findex...). When it stops, enter the continue command again and time how long it takes before it stops again. Do this a few times and post the results (including the arguments: output). __Martin -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Overriding Job and/or File Retention Periods?
Greetings! Is there any way, in Bacula 2.4.4, to override the File and/or Job retention period in either the Job, Schedule, or FileSet resource? The reason I ask is that we have a couple of filesets that are extremely large, but only on a handful of clients. We don't have the space to restore these sets except 'in-place', so we were looking for a way to keep the files/jobs for those jobs in the catalog until the volumes themselves were purged. Any ideas are appreciated :) Tom +-- |This was sent by tomisom.s...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Rewind permissions error in SD (UNCLASSIFIED)
Hi, 24.06.2009 16:57, Swartzbaugh, Richard A CTR DISA EUR wrote: Classification: UNCLASSIFIED Caveats: NONE I have installed Bacula on a Solaris 10 system using a StorEdge C2 tape jukebox. When I try to label a tape, I get the following error: Unable to open device SDLT1-Drive (/dev/rmt/0mbn): ERR=Permission denied Using the mt command (mt -f /dev/rmt/0mbn rewind), I can rewind the tape without errors. I ran the bacula-sd daemon in debug mode and got the output below. It appears that the rewind of the tape following the open fails due to permission problems (even though all 3 daemons are running as root and /dev/rmt/0mbn has 666 permissions). Hmm... I don't know this from Solaris, but with FreeBSD I recall something similar. In that case, a proper devfs.conf worked wonders! (Even though you would assume that root could access the device anyway...) Then, of course ACLs might prevent the SD from fully accessing the tape device - see getfacl et al. With Solaris, in addition to the automatic permission assignment at device detection, there is also role-based access control, which is managed with tools like ppriv, roleadd, usermod with -R option, and probably others - this is where my knowledge ends :-) Finally, Solaris is said to allow access to devices to only one user at a time - you can check which devices are in use by which user with list_devices. I guess it's possible that this feature might be the reason for your problems, too. No you've got some ideas - have fun with them! Arno Line 441 in dev.c is after a d_ioctl() rewind call that apparently fails. backups-bge0-sd: dev.c:336-0 Close fd for mode change. backups-bge0-sd: dev.c:345-0 open dev: type=2 dev_name=SDLT-Drive (/dev/rmt/0mbn) vol=test118 mode=OPEN_READ_WRITE backups-bge0-sd: dev.c:394-0 Open dev: device is tape backups-bge0-sd: dev.c:409-0 Try open SDLT1-Drive (/dev/rmt/0mbn) mode=OPEN_READ_WRITE backups-bge0-sd: dev.c:431-0 Rewind after open backups-bge0-sd: dev.c:441-0 Rewind error on SDLT1-Drive (/dev/rmt/0mbn) close: ERR=Permission denied backups-bge0-sd: dev.c:475-0 dev.c:474 Unable to open device SDLT1-Drive (/dev/rmt/0mbn): ERR=Permission denied backups-bge0-sd: dev.c:483-0 open dev: tape -1 opened backups-bge0-sd: dev.c:358-0 preserve=0x0 fd=-1 backups-bge0-sd: dev.c:1892-0 Clear volhdr vol= backups-bge0-sd: vol_mgr.c:562-0 vol_unused: no vol on SDLT1-Drive (/dev/rmt/0mbn) Any ideas? Thanks, Andy Classification: UNCLASSIFIED Caveats: NONE -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- Arno Lehmann IT-Service Lehmann Sandstr. 6, 49080 Osnabrück www.its-lehmann.de -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Restoring large directory does not work
Thanks for all your help you guys. I am impressed with the level of expertise here! Error accessing memory address 0x7fbff000: Bad address. #0 0x0040c043 in add_findex () The function add_findex is interesting, but I think like your bacula-dir was Try the following gdb commands (I assume you are running 64-bit FreeBSD): break *add_findex commands printf arguments: %x %x %x\n, $rdi, $rsi, $rdx end continue When it stops, enter the continue command again and time how long it takes before it stops again. Do this a few times and post the results (including the arguments: output). Yes, it is FreeBSD 64 bit. The continue command comes right back with these arguments: Breakpoint 1, 0x0040bfc0 in add_findex () arguments: 1b17068 a0 5fe00b arguments: 1b17068 a0 5fe00b arguments: 1b17068 a0 5fe00b arguments: 1b17068 a0 5fe00b (gdb) continue Continuing. Breakpoint 1, 0x0040bfc0 in add_findex () arguments: 1b17068 a0 5fe039 arguments: 1b17068 a0 5fe039 arguments: 1b17068 a0 5fe039 arguments: 1b17068 a0 5fe039 (gdb) continue Continuing. Breakpoint 1, 0x0040bfc0 in add_findex () arguments: 1b17068 a0 5fe055 arguments: 1b17068 a0 5fe055 arguments: 1b17068 a0 5fe055 arguments: 1b17068 a0 5fe055 (gdb) continue Continuing. Breakpoint 1, 0x0040bfc0 in add_findex () arguments: 1b17068 a0 5fe060 arguments: 1b17068 a0 5fe060 arguments: 1b17068 a0 5fe060 arguments: 1b17068 a0 5fe060 (gdb) continue Continuing. Breakpoint 1, 0x0040bfc0 in add_findex () arguments: 1b17068 a0 5fe071 arguments: 1b17068 a0 5fe071 arguments: 1b17068 a0 5fe071 arguments: 1b17068 a0 5fe071 (gdb) continue Continuing. Breakpoint 1, 0x0040bfc0 in add_findex () arguments: 1b17068 a0 5fe079 arguments: 1b17068 a0 5fe079 arguments: 1b17068 a0 5fe079 arguments: 1b17068 a0 5fe079 (gdb) continue Continuing. Breakpoint 1, 0x0040bfc0 in add_findex () arguments: 1b17068 a0 5fe0ac arguments: 1b17068 a0 5fe0ac arguments: 1b17068 a0 5fe0ac arguments: 1b17068 a0 5fe0ac -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Job vs volume retention periods
Dirk Bartley wrote:
On Wed, 2009-06-24 at 09:14 +0200, Fahrer, Julian wrote:
Hi Erik,
volumes will only be reused after the volume retention period is reached.
And the point of keeping a volume which doesn't contain jobIDs is that you
could import the tape or recover data from it using btape since it still
contains all files.
Greetings
Julian is correct with exceptions.
Recycle Oldest Volume = yes
Recycle Current Volume = yes
PurgeOldestVolume = yes
Warning, the following description may not be perfect:
I use recycle oldest and purge oldest. This way, the job records can be
maintained in the catalog with an unresonably long job retention period.
When the director completes jobs, it will still perform pruning
operations pruning file records.
Then when the director goes to schedule a job, it will purge job records
from the volume and label it recycled if all jobs have had their file
records pruned. The volume chosen to recyle will be the one that has
not been written to for the longest period.
The status dir will show the recycled volume as the volume scheduled to
use.
For instance, I have a pool with two tapes for Tuesday and Thursday. I
want to use it four times then have it schedule using the othe tape
rotating every two weeks.
Pool {
Name = LTO_TueThu
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 16 Days
Volume Use Duration = 10 Days
Recycle Oldest Volume = yes
PurgeOldestVolume = yes
Storage = LTO
}
Set it up recently and it seems to work so far. Best of luck. The
documentation is awesome because there are so many possible parameters.
The one thing that may be missing is more recipes from current users.
Dirk
Kind regards
Julian
-Ursprüngliche Nachricht-
Von: phatrik [mailto:bacula-forum at backupcentral.com]
Gesendet: Mittwoch, 24. Juni 2009 03:46
An: bacula-users at lists.sourceforge.net
Betreff: [Bacula-users] Job vs volume retention periods
Hi,
I'm confused in regards to job retention vs volume retention. From the
little bit I understand, if the volume retention period is passed and
bacula is unable to find any other appendable volumes in the client's
stoarge pool, it will delete all file and job records and then re-use that
volume. However, how about if all the jobs in that volume have been pruned
but the volume retention period hasn't passed yet (and of course recycling
is enabled) Will bacula still re-use the volume since no more jobs remained
after they've all been pruned? If it does, what's the purpose of having a
volume retention period which is usually without a doubt longer than the
job retention period? If it doesn't, what's the point of keeping a volume
which doesn't contain jobIDs which can't be restored anymore?
thanks in advance,
Erik
+--
|This was sent by erik.godin at gmail.com via Backup Central.
|Forward SPAM to abuse at backupcentral.com.
+--
--
___
Bacula-users mailing list
Bacula-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
___
Bacula-users mailing list
Bacula-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Hi,
Thanks for the help provided so far, it's very much appreciated. I do have a
few follow-up questions:
In a case where the client's storage pool would of reached it's maximum volume
limit (I use this combined with maximum volume bytes to control the size of
their allocated storage pools) and recycle oldest volume would be equal to
yes... If all the jobs have already passed their retention period, bacula would
recycle the oldest volume regardless of the volume retention period, is this
correct (on what date is this based btw, the date of the last written job?)
And that, as long as the volume wasn't recycled/overwritten, there's always
possibility to use bscan, re-write the catalogue and restore file-by-file? In
a case where the file records have expired but not the job records, can I
simply decide to restore an entire jobid instead of using bscan? How about
when a volume is purged? My understanding is, files can still be recovered,
however in this
[Bacula-users] Overriding Job and/or File Retention Periods?
Trying to work around the file/job retention question above, is it possible to set up multiple Client resources for a single client machine, without running multiple file daemons on the client? The way I read the manual, the name given to the client file daemon is what needs to be used for the client resource in the Director config. Is that true, or am I reading it incorrectly? Thanks for any help, Tom +-- |This was sent by tomisom.s...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Job vs volume retention periods
Thanks for the help provided so far, it's very much appreciated. I do have a few follow-up questions: In a case where the client's storage pool Pools don't belong to a client unless you set up the directors schedules that way and don't run any manually to the pool. would of reached it's maximum volume limit (I use this combined with maximum volume bytes to control the size of their allocated storage pools) and recycle oldest volume would be equal to yes... If all the jobs have already passed their retention period, bacula would recycle the oldest volume if recycle oldest is set yes. If you also set purge oldest, then it will purge the jobs as well regardless of the volume retention period, recycle oldest respects retention of files and jobs. is this correct (on what date is this based btw, the date of the last written job?) I think first written, not totally sure And that, as long as the volume wasn't recycled/overwritten, there's always possibility to use bscan, re-write the catalogue and restore file-by-file? In a case where the file records have expired but not the job records, can I simply decide to restore an entire jobid instead of using bscan? yes, restoring the entire job is always an option if the job record exists with purged files. How about when a volume is purged? If the volume is purged, then there will be no knowledge of the job or where it is on the tape, so bscan would be required. My understanding is, files can still be recovered, however in this case I'm presuming using bscan isn't optional? bscan required is my understanding. Dirk I think this should be the last of my question :) Bacula is pretty flexible. I had to read the pool directives, try some stuff for a bit, then read it again to fully appreciate what it took to get the results I wanted. Heck, I'm still not sure if I'm quite there yet. Thanks in advance, Erik -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Overriding Job and/or File Retention Periods?
If your serious about it, you could always script your way out of it. Set the file and job retention to the higher of the two desired values, then conjure up an sql statment that select the jobs that you want to have the lower retention periods and purge the records desired in a script. You could use the scripting language you feel most comfortable. Then run the script in cron or run after job. Here is an example of a sql statement SELECT Job.JobId FROM job JOIN JobMedia ON JobMedia.JobId=Job.JobId JOIN Media ON JobMedia.MediaId=Media.MediaId WHERE media.volumename IN ($medialist) ORDER BY Job.EndTime Limit 1 ; ; But you could have it select jobs of a certain jobname or client that are older than a certain age then purge files from those jobs. It only takes a bit to set up. Dirk On Wed, 2009-06-24 at 21:29 -0400, teksupptom wrote: Trying to work around the file/job retention question above, is it possible to set up multiple Client resources for a single client machine, without running multiple file daemons on the client? The way I read the manual, the name given to the client file daemon is what needs to be used for the client resource in the Director config. Is that true, or am I reading it incorrectly? Thanks for any help, Tom +-- |This was sent by tomisom.s...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
