- Posts: 9
- Liked: never
- Joined: Sep 15, 2009 1:06 pm
- Full Name: Michael Berg
I have the following questions regarding backing up of a Microsoft Exchange Server. In an agent-based way, the backup agent flushes the LOG files after a succesful, so that we keep storage for LOG files at a minimum. LOG files are also used in a restore situation to minimize a potential data loss.
Since Veeam doesn’t flush LOG files, how should a customer approach this? I’m aware of the fact that Veeam do a VSS-integrated backup of Exchange, so that all data is consistent. But the point of having databases and log files, is to control the amount of data that we could potentially loose…
So – let’s say we do a backup of the exchange system at 1 PM. Next backup occurs at 4PM. In between here, we lose the datastore on which the database are stored upon. Normally I would restore the datastore and commit LOG files that is still available on the Exchange server because they are stored on another datastore. This ensures that my data loss is at a minimum or next to nothing.
But since Veeam doesn’t (in my understanding) flush the LOG files, I would have an inconsistent system or?
- SVP, Product Management
- Posts: 29323
- Liked: 5456 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
Hi, actually we do, since version 2.0 released back in 2008. If you take a look at user interface controls on the Guest Processing step of backup job wizard carefully, you will even see the corresponding controls that allow you to modify logs flushing behavior.dr.bergs wrote:Since Veeam doesn’t flush LOG files
Users browsing this forum: No registered users and 29 guests