On Wed, Oct 5, 2011 at 1:32 AM, Kevin Keane <subscription AT kkeane DOT com>
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 proper amount of data though I cannot
>> access
>>> it since it is flagged as failed. Microsoft has an article about this
>> call which ties
>>> into the ntbackup. Article ID: 820272.
>>>
>>> The article is for Windows 2003, but it basically says that is the
>> Exchange data
>>> and the OS are on the same partition you will have problems. They
>>> recommend backing up the main server first and then the exchange data.
>> I
>>> am currently doing this and I will see what the results are.
>> Best practice says you shouldn't have them on the same partition, but it
>> shouldn't break anything if you do.
> The article refers to a problem specifically with NTBackup. You can have
> the Exchange database and the OS on the same partition, but you cannot
> back both up in the same job. I am not familiar enough with backing up
> Exchange in bacula; it may use similar underlying code, and thus have a
> similar problems.
>
> With NTBackup you have to back up just the SystemState, and then back up
> the Exchange database separately.
>
>> 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 normal operation, these
> old log files are never used anyway.
>
> The only reason somebody might want to keep them is to allow restoring
> the Exchange database to one particular point in time. Instead of the
> traditional "restore the last full backup, and then restore the
> incrementals" you would restore the full backup plus all the log files
> since then. Then you replay the log files until the exact point in time
> you want.
>
> In practical terms, most people never needed this capability, so
> circular logging actually is perfectly fine.
>
> In Exchange 2010, circular logging is the default.
>
>
Circular logging is NOT the default in Exchange 2010
http://technet.microsoft.com/en-us/library/bb331958.aspx
As per the reply from James Harper, circular logging is a "bad thing"
it means that ANY restores will have loss.
With circular logging disabled, it means that you will only have loss
from your last backup PAST the last good log. with it enabled, you
will only have your last backup, everything else is gone
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
