quick backup in order to free up exchange log

[mteamjpy]

Hi guys ,

need a quick help we are performing reverse incremental on our exchange server, i would like once to launch an incremental that i hope could be quicker.
How i could do that without getting a full for the first time if it's possible.
if not could you look for a quick backup option ?

[veremin]

Your goal is just to truncate Exchange logs, isn’t?

If so, I’m wondering why it can’t be done by the means of Exchange Management Console.

In case of VB&R, the fastest option which is likely to meet your expectations is to exclude all of VM disk from being processed and enable truncation log setting.

Hope this helps.
Thanks.

[mteamjpy]

indeed the but is too get these log in a backup if we need them .
that 'a a policy we can only trunc log if we got them on backup
for sure I would prefer to trunc log before backup that will increase backup speed , but what will happen if the backup fail and in the same time the exchange ?


regards

Jean-pol

[foggy]

indeed the but is too get these log in a backup if we need them .
that 'a a policy we can only trunc log if we got them on backup

So why not to backup this VM with the "Truncate logs on successful backup only" option then?

[Cokovic]

Hi guys ,

need a quick help we are performing reverse incremental on our exchange server, i would like once to launch an incremental that i hope could be quicker.
How i could do that without getting a full for the first time if it's possible.
if not could you look for a quick backup option ?

If i get it right you've setup a Reverse incremental job for your Exchange but never performed an initial Fullbackup so far right? Then there is no possibility to perform an Incremental as a previous Full is required.

There is a support document by Microsoft (http://support.microsoft.com/kb/240145/en-us) if you want to truncate logs manually but dont know if it is still applicable for Exchange 2007/2010 as they refer to Exchange 5.5 / 2000 / 2003.

So you were left with two options here in my opinion:

1. Perform a Full backup of your Exchange with "Truncate logs on successful backup only"
2. If it's urgent cause you are running out of space switch the database temporarily to circular logging. This would truncate the logs too but you would break your policy as you would lose the current logs. After logs were truncated disable circular logging again. But keep in mind that this would require a short downtime of your database as you have to unmount and remount the database for this change to take effect.

Anyway i think best would still be an initial Fullbackup run.

[mteamjpy]

Hi cokovic,

we have done a full backup in reverse incremental but i want to perform simple incremental job when it is needed
is it possible ?
regards

Jean-pol

[foggy]

What do you mean by "simple incremental"? Each subsequent job run after the full is incremental.

[mteamjpy]

so there is 2 kind of incremental in veeam
reverse incremental and old incremental job.
until now we are doing reverse incremental but like we got many issues i want to launch a quicker incremental so not a reverse

regards

Jean-pol

[foggy]

Ok, so you want just to switch to forward incremental mode for a while, don't you? You can do that by simply editing the corresponding option in the job properties, no need to create a full. However, note, that on switching back you will need to perform the full backup (will be automatically triggered at the next job run after switching).

[mteamjpy]

ok that's fair enough

many thanks
Jean-pol