feature request: backup exchange logs periodically

[frankive]

backup the sql transaction logs every 15 min. is very cool!
I would really like to see the same thing for exchange 2013/2016!

[frankive]

or am i missing something obvious here?

[Gostev]

No, you're not missing anything, Frank. We've had close to zero requests for this functionality in the past 8 years (unlike for SQL), which is why it is not available.

[andy51585]

+1

[Regnor]

Although it would be a grateful addition I would rather create a DAG or run backup jobs more often.

[mkretzer]

I also would like to have this as I think log backups would be more space efficient than image backups

[Mike Resseler]

But even if you would do log backups... You still need to take an image backup at a certain point in time to truncate the logs... So where do you see the space savings? (Or are you talking about taking less image based backups, like only once a day versus x a day...)

[mkretzer]

That's what I mean. And why should the log backup not truncate?

[JoshuaPostSAMC]

+1

[Mike Resseler]

MKretzer,

I am not sure if truncating the logs before you actually take a full backup of the database is a good practice. Maybe Exchange admins will tell me differently that this is perfectly possible. I will need to steal their brain on this one

[fja]

+1

[btanguay]

Since 2015, do this feature has been implemented? if not +1 for me

[veremin]

Nothing has changed in this regard. Priority has been given to more demanded features.

However, consider your voice counted.

[kubimike]

+1 I have slow storage, would be nice to do this as well. Whenever the snaps are removed (in VMware, not using storage integration) it freezes exchange randomly. Causing random user issues with outlook plugins.

[Gostev]

Actually, this feature won't remove the need for VM snapshot creation and removal... we still need to create the full image-level backup periodically, as it captures the state to which the logs that will be backed up periodically for the next day would be rolled onto.

[kubimike]

i figured, but I can do that image before and after working hours. I do that for SQL. As it stands now I backup exchange every 4 hours.

[Gostev]

Ah, got it thanks.

[kubimike]

Pretty please with cherries on top make that happ-captain. My users will thank you

[dropped91]

+1

[ralfwanninkhof]

+1

[lightsout]

+1 for me too!

[mkretzer]

+1

[ferrus]

We're just about to fully migrate from our previous Exchange backup software, and I assumed (incorrectly) that this was implemented the same as SQL logs.
Additional image backups are an option, but our Exchange merge takes up to 6 hours, and we're a long way off 2016/REFS.

So a definite +1 from me.

[awinkler77]

+1
For us a continuos Backup of Exchange Logfiles would be very nice in case the complete vm was crashed with all virtual disks (Disaster Recovery). We have same problems as kubimike that removing snapshots from vm will freeze the whole vm. Also using VMWare and not using storage integration. I think wenn only a snapshot from the logfile volume is taken, then the vm would not freeze at deleting this 1 snapshot. It's only 1 Snapshot-File that must be deleted.

I also see the need for a full image-level backup periodically and would do this at night time, in our case after 10pm.

[kubimike]

@awinkler77 I found a temporary work around. You might have had the same backup strategy I had. I was backing up exchange every 4 hours. This included the CAS Client access server. Remove that server from your job and schedule it to get backed up once a day. I'm doing mine around 2AM. If my users are awake working at that time its a sign they should go to bed . Although my storage speed hasn't changed, I no longer have the issue I was describing.