On 09/09/2014 02:34 AM, Kenny Noe wrote:
> Kern,
>
> I tried this tonight. Marked the mail.tar file only and redid the
> restore. It failed again with the same error.
>
> Any other suggestions?
Yes, I probably should have mentioned to remove all runbefore scripts
and any other thing that you ma
Hi Kenny,
Have you checked permissions for writing the specified directory? Take a
look at the error time:
08-Sep 11:51 BS01-SD1 JobId 12897: Forward spacing Volume
"mail-0386" to file:block 0:219.
08-Sep 12:14 BS01-SD1 JobId 12897: End of Volume at file 2
Kern,
I tried this tonight. Marked the mail.tar file only and redid the
restore. It failed again with the same error.
Any other suggestions?
---Kenny
On Mon, Sep 8, 2014 at 5:46 PM, Kern Sibbald wrote:
> Hello,
>
> It looks to me from the name /fifo/ and the error you are getting that you
>
Kenny,
Ok. Lets move on: I really recommend you to upgrade your client from
5.0.3-1 to a 5.2.x (not bigger than director). We had a major release
between your director and client version.
Regards,
On Mon, Sep 8, 2014 at 4:53 PM, Kenny Noe wrote:
> Heitor,
>
> Yes, I did change to local (/tmp)
Heitor,
Yes, I did change to local (/tmp) this past attempt.
*restore
First you select one or more JobIds that contain files
to be restored. You will be presented several methods
of specifying the JobIds. Then you will be allowed to
select which files from those JobIds are to be restored.
To se
Kenny,
Again it looks like you haven't change the Where variable to a local server
directory and kept using: /nas/users/admin/
Could you please try any other directory? E. g.: /tmp?
NAS can be tricky and its a whole different ACL system. Trying to restore
files directly on a mount point may lead y
I've tried all day to restore this file. Ran 12 restores today. All
have the same result. I get an empty file.
This worked once 3 months ago when I completed a restore of this file to
the original server, but now that server is gone I can't restore the file!
Sorry to vent my frustration but
Heitor,
/nas/bacula/bluewhale is a path on besc-bs01. This is where the Bacula
backup are put. mail-0386 is the bacula volume I'm trying to restore.
I'll try a local location to restore.
Thanks--Kenny
On Mon, Sep 8, 2014 at 3:24 PM, Heitor Faria wrote:
> Kenny,
>
> Is this path (/nas/b
Kenny,
Is this path (/nas/bacula/bluewhale) a path to a NAS mount point in besc-bs01
client? If yes, this might be the cause of the writing error.
Did you try to restore to a local client directory? E. g.: /tmp?
On Mon, Sep 8, 2014 at 4:12 PM, Kenny Noe wrote:
> Sorry, failed to include the l
Sorry, failed to include the list...
---Kenny
-- Forwarded message --
From: Kenny Noe
Date: Mon, Sep 8, 2014 at 1:25 PM
Subject: Re: [Bacula-users] Restore from dead client
To: Dan Langille
Gents Following instructions.
Appreciate your time...
--Kenny
Kenny:
Please run the restore job again and then copy/paste the entire session from
bcsonole. Thank you.
On Sep 8, 2014, at 1:15 PM, Heitor Faria wrote:
> Kenny,
>
> Ok. Sorry for the confusion about the bluewhale client. This is why we need
> your full restore command, to see exactly what
>
> You should not change your Backup Client at the restore, even if the
> *CLIENT* is dead.
>
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version contr
Kenny,
Ok. Sorry for the confusion about the bluewhale client. This is why we need
your full restore command, to see exactly what's happening..
You should not change your Backup Client at the restore, even if the
restore is dead. You should change your Restore Client. It would be nice to
inform it
Heitor,
Pardon my ignorance, but i don't follow your questions...
My original client "bluewhale" experienced a terrible HD failure thus the
need to recover. I have been changing the "client" and "where" parameters
when walking thru the restore procedure. When the restore process runs it
create
Hello Martin,
See below ...
On 09/08/2014 06:12 PM, Martin Simmons wrote:
> Thanks, I just didn't want to OSX binaries to go down the path of the Windows
> binaries.
No, OSX has no particular code written by Bacula Systems that is not in
the community version, whereas for Windows Bacula Systems
Kenny,
1. Could you reproduce the input you used at the restore submission?
2. Can you tell the client bluewhale version?
Regards,
On Mon, Sep 8, 2014 at 1:48 PM, Kenny Noe wrote:
> Heitor,
>
> Hi! Thanks for the reply I'm utilizing a console and the Bacula
> console and executing a "re
Heitor,
Hi! Thanks for the reply I'm utilizing a console and the Bacula
console and executing a "restore" command then walking thru the prompts
given. What is this "run" command? Yes, I believe I'm trying to restore
the same file, but it's not working.
Thoughts?
Thanks--Kenny
On M
Kenny,
First of all, are you using the "run" command to submit a prior configured
Restore Job? I think this is not advisable, since there are several restore
variables that only the "restore" command can fetch.
Did you try to restore the same file with the restore command?
Regards,
On Mon, Sep
Dan,
Thanks for the reply. I tried this this morning and still failed the
restore. I see during the Status Storage - Storage_Bluewhale where the
"Running Jobs section shows Files=0, Bytes=0 Bytes/sec=0. However in the
Device Status section, Device "File_bluewhale" is mounted and the Total
Byt
Thanks, I just didn't want to OSX binaries to go down the path of the Windows
binaries.
There is a new Xcode command productbuild, but I've not explored how to use it
yet.
__Martin
> On Mon, 08 Sep 2014 15:46:26 +0200, Kern Sibbald said:
>
> Hello Martin,
>
> Have you been talking to Dimi
Mr. Bacula Users,
Just FYI, I've created two VPS with Bacula Enterprise (Trial) / Community,
BWEB / WEBACULA demos, if you ever need a environment for demonstration:
http://www.bacula.com.br/?page_id=2093
You may also use bconsole / BAT and ask me in PVT for root credentials if
you need to make te
Hello Robert,
Thanks for the tips.
Best regards,
Kern
On 09/08/2014 04:16 PM, Robert Oschwald wrote:
> You can use MacPorts to build Bacula 7.0.4 (client by default, also supports
> MySQL-, PostgreSQL- and SQLite3 Server variants)
>
> Install macports (macports.org), then perform
> „sudo port
You can use MacPorts to build Bacula 7.0.4 (client by default, also supports
MySQL-, PostgreSQL- and SQLite3 Server variants)
Install macports (macports.org), then perform
„sudo port install bacula“
This by default installs the client fd.
Configure the client in /opt/local/etc/bacula/bacula-fd
Hi Simone,
Thank you for this suggestion. We're going to try your backport repository,
although I have some questions concerning our case:
I forgot to mention that we use webacula frontend to give a web access to
some users, and it adds some tables to the database. Will the upgrade from
your repos
Hello Martin,
Have you been talking to Dimitri? :-)
Bacula Systems has no secret script for building Mac OS. It is done
using the scripts in /platforms/osx with only some trivial name
changes that I personally made (e.g. Bacula -> Bacula Enterprise, ...).
All Bacula Systems low level script
Hello,
On 8 September 2014 15:27, José Vicente Mondejar wrote:
> Thank you for this suggestion. We're going to try your backport
> repository, although I have some questions concerning our case:
> I forgot to mention that we use webacula frontend to give a web access to
> some users, and it adds
Unfortunately the cake is rotten now :-) PackageMaker is no longer supported
by Apple so the script doesn't work on OSX 10.9.
Please encourage Bacula Systems to contribute a fix to this script back to the
community version and build its binaries from that, rather than using a secret
cake recipe.
27 matches
Mail list logo
