- Posts: 158
- Liked: 30 times
- Joined: Dec 05, 2010 9:29 am
- Full Name: Bob Eadie
I noticed one night that a particular Exchange 2010 server had failed direct SAN and failed over the Network, and the backup took about one quarter of the time it had been taking! From 3 and a half hours, to under one hour.
This particular server had always been reporting hundreds of 'Map Disk Region' while backup up, so perhaps this was slowing down the direct SAN??
I changed all my backup proxies to network (rather than automatic) and this server is still taking under an hour, though all the other backups are taking roughly the same time as they were before.
Is it worth my changing the other servers back to automatic selection . . . which is difficult, as the setting is per Proxy, rather than per job . . . or just leave them on on network. We have got a 10GB network between the production and backup infrastructure.
Thanks for any suggestions. In one sense, 'if it ain't broke, don't fix it' tempts me to leave well alone, as it is all working fine.
Computer Manager at Bedford School, UK (since 1999).
Veeam user since 2009.
- Veeam Software
- Posts: 18560
- Liked: 1607 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
Regarding "map disk region" errors, those are typical for direct SAN in some circumstances, though I'm not sure whether they could affect performance.
- Veeam Software
- Posts: 5815
- Liked: 1664 times
- Joined: Jul 26, 2009 3:39 pm
- Full Name: Luca Dell'Oca
- Location: Varese, Italy
As usual, the best maintenance activity to do is to run a storage vmotion so to remove the fragmentation of that disk. This helps regardless of the backup method that is used.
Principal EMEA Cloud Architect @ Veeam Software
vExpert 2011 -> 2019
Veeam VMCE #1
Users browsing this forum: No registered users and 9 guests