Backup Exchange 2013

[Delando]

Hello

Is it possible to backup Exchange 2013 with veem if you choose to close the exchange services before starting the backup? (Untill the support for 2013 is released)

Regards

/Andreas

[Vitaliy S.]

Yes, sure, why not? Though I believe AAIP should also work...

[Delando]

So ordinary backup with vss is suported for Exhange 2013?

[Gostev]

Yes, it is supported.

[Delando]

It worked, Do i need to do fullbackup every time?
Did a backup again. But its still yesterdays date on last backup when i look in Exchange.

[Vitaliy S.]

It worked, Do i need to do fullbackup every time?

No, you shouldn't, just treat this VM as any other production critical VM. Btw, what backup mode are you using? Forward or reversed incremental?

Did a backup again. But its still yesterdays date on last backup when i look in Exchange.

Do you mean that you do not see any new backup completion events in the Application event log?

[Delando]

Im using default incremental.

In the Exchange gui you can check when you database was backed up. I can see the one from yesterday, But the one i ran today dont seem to register.

[Vitaliy S.]

And what about Windows event log? Do you have any events about successful backup there? Do you have "truncate transaction logs" checkbox enabled in the advanced settings of the AAIM processing option?

[Delando]

Yes VSS is on, Got some Exchange VSS errors in the eventlog
"Failed with error 80131516 when preparing for backup, Failed preparing for snapshot, Failed when freezing the databases. and some more.
I will try doing one full again.

Same error when im doing Fullbackup....

[Delando]

Here are the vss errors!

Code: Select all

The Microsoft Exchange Replication service VSS Writer (Instance 823d0bf2-8947-4828-b743-8e54494f355d) failed with error 80131516 when preparing for a backup.

The Microsoft Exchange Replication service VSS Writer (Instance 823d0bf2-8947-4828-b743-8e54494f355d) failed with error 800423F3 when preparing for snapshot.

Microsoft Exchange Replication service VSS Writer instance 823d0bf2-8947-4828-b743-8e54494f355d failed when freezing the databases.

Microsoft Exchange Replication service VSS Writer instance 823d0bf2-8947-4828-b743-8e54494f355d failed when thawing the databases.

The Microsoft Exchange Replication service VSS Writer encountered an exception in function Microsoft::Exchange::Cluster::ReplicaVssWriter::CReplicaVssWriterInterop::PostSnapshot. HResult -2146232969. Exception System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.PostSnapshot(IVssWriterComponents* pComponents).

[Delando]

Have the same problem with the built in Windows Backup, Seems that others are experience the same problems.

[Delando]

it seems to be a bug that should be fixed in CU1.

[Vitaliy S.]

Ok, thanks for the update. I believe once you resolve VSS issues, your database backup stamp should also be updated.

[Delando]

Exchange 2013 CU1 installed and veeam backup works fine

/Andreas

[infused]

Just confirming that I need CU1 installed for 6.5 to be able to truncate logs? If not, does anyone know why it's not truncating my logs?

[Vitaliy S.]

Based on post from Andreas, CU1 should do the trick.

[infused]

Cheers.

Any reason why it doesn't backup without CU1?

[Delando]

Yes. CU1 fixed my problems with the logs.

[infused]

Anyone know why though? It was working...



I've just done some testing, the DAG needs to be first in the list of VMs or it will not truncate logs.



Full active backup after this change and it's finally backing up again. I think it's because the CAS servers were being backed up first.

I don't have CU1 installed (And don't want to after reading all the bugs...)

[benthomas]

Has anyone confirmed being able to restore exchange 2013 mailstores using Veeam 6.5?
I assume you aren't able to restore individual mail items though until Exchange Explorer v7 is out?

[veremin]

I assume you aren't able to restore individual mail items though until Exchange Explorer v7 is out?

Why not? Just get the public beta of the new version of Veeam Explorer for Exchange that extends support to Microsoft Exchange 2013.

Hope this helps.
Thanks.