On Wed, Oct 5, 2011 at 11:05 PM, James Harper
wrote:
>> > In Exchange 2010, circular logging is the default.
>> >
>> >
>>
>> Circular logging is NOT the default in Exchange 2010
>>
>
> I think that's not true for Small Business Server 2011 (which includes
> Exchange 2010). I'm pretty sure that by
> > In Exchange 2010, circular logging is the default.
> >
> >
>
> Circular logging is NOT the default in Exchange 2010
>
I think that's not true for Small Business Server 2011 (which includes
Exchange 2010). I'm pretty sure that by default it is on for SBS 2008
too (Exchange 2007). This means y
On 10/05/11 15:54, Ben Walton wrote:
> What mysql are you building against? The included one? More to the
> point, which compiler was it built with?
MySQL 5.5.8, Solaris 10 package from Oracle. Need to update that actually.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71
Excerpts from Phil Stracchino's message of Wed Oct 05 15:26:06 -0400 2011:
> I've been trying, but have yet to succeed. I think it would
> probably be a lot simpler if Solaris 10 came in all-32-bit and
> all-64-bit flavors, instead of the hybrid mixture of 32-bit and
> 64-bit it is at present. I
Hi All,
I'm going to be adding a new pair of boxes to the network shortly.
One box will be a primary server and the other a hot standby. The hot
standby will sync the live system nightly.
As I see it, I've got a few options for backup here:
1. Backup both boxes, pay the heavy price of duplicat
On 10/05/11 15:14, Ben Walton wrote:
> Excerpts from Phil Stracchino's message of Wed Oct 05 14:51:57 -0400 2011:
>
> Hi Phil,
>
>> Side note: It was unreasonably difficult to get it built correctly
>> on Solaris 10. I couldn't get a working 64-bit build at all, either
>> with gcc or with Sun St
Excerpts from Phil Stracchino's message of Wed Oct 05 14:51:57 -0400 2011:
Hi Phil,
> Side note: It was unreasonably difficult to get it built correctly
> on Solaris 10. I couldn't get a working 64-bit build at all, either
> with gcc or with Sun Studio, and the only way I could get a
> correctly
On Wed, Oct 5, 2011 at 1:32 AM, Kevin Keane wrote:
> On 10/4/2011 3:49 PM, James Harper wrote:
>>> I have this error backing up Exchange on a Windows 2008 Standard 64
>> bit
>>> system.
>>> "HrESEBackupSetup" seems to be a Windows call. Bacula reports the
>> error
>>> and yet seems to back up the
On 10/05/11 09:37, Rory Campbell-Lange wrote:
> I've been using non-batch insertion with postgres (following your dare,
> I think, Phil) for about a year. Backups are only about 8TB, but it
> works extremely well for us.
So, I just built bacula-5.1.14 from git, with batch disabled. And we'll
see
On Wed, Oct 5, 2011 at 12:04 PM, tscollins
wrote:
> So I checked what bconsole reports and here it is:
>
> Terminated Jobs:
> JobId Level Files Bytes Status Finished Name
> ==
> 3 Full 72,805 7.660
So I checked what bconsole reports and here it is:
Terminated Jobs:
JobId LevelFiles Bytes Status FinishedName
==
3 Full 72,8057.660 G OK 04-Oct-11 13:51
Technology1s-iMac-backup
On 10/5/2011 4:13 AM, Jeremy Maes wrote:
> Op 5/10/2011 9:47, Roy Sigurd Karlsbakk schreef:
>> Hi all
>>
>> I have setup Bacula and we're currently backing up three networks, the
>> private LAN, the DMZ and a remote observatory - Birkenes. The latter is
>> connected to a 1Mbps SHDSL link. There's
On 10/05/11 10:25, Uwe Schuerkamp wrote:
> On Wed, Oct 05, 2011 at 02:37:37PM +0100, Rory Campbell-Lange wrote:
>>
>> I've been using non-batch insertion with postgres (following your dare, I
>> think, Phil) for about a year. Backups are only about 8TB, but it works
>> extremely well for us.
>>
On Wed, Oct 05, 2011 at 02:37:37PM +0100, Rory Campbell-Lange wrote:
>
> I've been using non-batch insertion with postgres (following your dare, I
> think, Phil) for about a year. Backups are only about 8TB, but it works
> extremely well for us.
>
Hi folks,
thanks for your recommendations an
On 5 Oct 2011, at 14:23, Phil Stracchino wrote:
> On 10/05/11 05:07, Uwe Schuerkamp wrote:
>> Hi folks,
>>
>> I'm wondering about the best mysql settings for our new bacula
>> installation which will be taking over from an older setup.
>>
>> Current bacula db size is 55G, we have around 14TB
On 10/05/11 05:07, Uwe Schuerkamp wrote:
> Hi folks,
>
> I'm wondering about the best mysql settings for our new bacula
> installation which will be taking over from an older setup.
>
> Current bacula db size is 55G, we have around 14TB backup data from
> ca. 100 clients on disk storage ATM but
> On Tue, 04 Oct 2011 20:32:55 -0700, Randy Katz said:
>
> Hello Esteemed Bacula People!
>
> I have backups on a 90-120 day cycles with full/diff/incr from a pool of
> machines to
> a Director machine. The pool of machines also has a local script backup
> to secondary
> hard drive space whi
Hi folks,
I'm wondering about the best mysql settings for our new bacula
installation which will be taking over from an older setup.
Current bacula db size is 55G, we have around 14TB backup data from
ca. 100 clients on disk storage ATM but this is expected to double in
the next year or so. the
Op 5/10/2011 9:47, Roy Sigurd Karlsbakk schreef:
> Hi all
>
> I have setup Bacula and we're currently backing up three networks, the
> private LAN, the DMZ and a remote observatory - Birkenes. The latter is
> connected to a 1Mbps SHDSL link. There's a central Director with the
> PostgreSQL datab
Hi all
I have setup Bacula and we're currently backing up three networks, the private
LAN, the DMZ and a remote observatory - Birkenes. The latter is connected to a
1Mbps SHDSL link. There's a central Director with the PostgreSQL database. Each
of the networks have a private SD.
Now, backing u
Op 4/10/2011 18:52, Mark Yarbrough schreef:
I am running bacula w/vchanger on Debian and backing up several
machines successfully, however my largest file store (which takes a
few days to run) is crashing after it has written the entire library
to disk/tape. I am not completely sure what to
> > What error is Bacula giving? What errors are in the event logs?
> >
> > One thing - if Exchange is set to 'circular logging' then you will
> > have problems backing up.
> Not really. All circular logging means is that the old database log
files will be
> deleted before the next backup. In norma
22 matches
Mail list logo
