I don't think so... I looked in the event log and didn't see anything about
that.
2010/9/29 John Drescher
> On Wed, Sep 29, 2010 at 5:12 PM, Alípio Luiz
> wrote:
> > I changed the TCP KeepAlive (60) of the server, and I configured
> Heartbeat
> > Interval to 10 in:
> > - bacula-dir (director se
On Wed, Sep 29, 2010 at 5:12 PM, Alípio Luiz wrote:
> I changed the TCP KeepAlive (60) of the server, and I configured Heartbeat
> Interval to 10 in:
> - bacula-dir (director section, client section and storage section)
> - bacula-sd
> - bacula-fd
>
> Now, I'm getting the following error:
>
> 29-S
I changed the TCP KeepAlive (60) of the server, and I configured Heartbeat
Interval to 10 in:
- bacula-dir (director section, client section and storage section)
- bacula-sd
- bacula-fd
Now, I'm getting the following error:
29-Sep 14:38 SEC.srvarq09 JobId 1106: Generate VSS snapshots. Driver="VSS
>Does this (network timeout) happen randomly or is it predictable?
Randomly for me,
Sometimes Fulls or Diffs fail at different points and sometimes they don't even
start transferring data, just sit in never-ever land until they timeout... Once
and
a while they screw with me and just finish:)
It'
On Tue, Sep 28, 2010 at 3:20 PM, Joseph L. Casale
wrote:
>>Are you spooling? Try a 5GB spool file.
>
> Doubt that's the issue, I am writing to a raid array w/ max jobs=1, not
> tapes, so it would
> be merely redundant for me and I am also having the issue.
>
> I recall Kern suggesting the VSS cod
>Are you spooling? Try a 5GB spool file.
Doubt that's the issue, I am writing to a raid array w/ max jobs=1, not tapes,
so it would
be merely redundant for me and I am also having the issue.
I recall Kern suggesting the VSS code was very old, so I tried running for a
week w/o vss
and it didn't
2010/9/28 Alípio Luiz :
> Hello folks.
> I have the Director and Storage Server located in a network. Some clients
> (FD) are located in the same network and the backup process of those are
> very well.
> However, I have two clients located in another network. The both are running
> Windows Server
>May you help me with any suggestion?
>Thanks in advance.
Follow my post of 59 minutes ago:)
Seriously, I am having the same issues and they are to intermittent on
my end to say for sure which level they appear on. Hit and miss...
--
Hello folks.
I have the Director and Storage Server located in a network. Some clients
(FD) are located in the same network and the backup process of those are
very well.
However, I have two clients located in another network. The both are running
Windows Server 2008 R2. One of them is a Domain Con
I tried it, but it work fine only one time, when I run it manually!!
Tomorrow I return on bacula.. so I can check if the problem is the same
Ciao
CARLO
2010/1/4 Peter Allgeyer
> Am Mittwoch, den 30.12.2009, 14:56 +0100 schrieb Carlo Filippetto:
>
> > I have a job running on windows 2008 64bi
Am Mittwoch, den 30.12.2009, 14:56 +0100 schrieb Carlo Filippetto:
> I have a job running on windows 2008 64bit, mine bacula director is
> 3.0.3 on Linux server.
> On the client I installed the new 64bit version, but I can't undertand
> why the job goes well since the and where say
>
> "Network
Hi all,
I have a job running on windows 2008 64bit, mine bacula director is 3.0.3 on
Linux server.
On the client I installed the new 64bit version, but I can't undertand why
the job goes well since the and where say
"Network error with FD during Backup: ERR=Connection timed out"
***
12 matches
Mail list logo
