- Posts: 1
- Liked: never
- Joined: Dec 16, 2016 3:40 pm
- Full Name: Florent THIESSET
Today, I have tested backup via veeam backup office365.
I have a problem with backup time, 8 Go in 1h45. (fiber)
My customers has 1,4 To saved. The time required would be 8-10 days.
Limitation of Office 365 ? A solution for the first backup ?
- Veeam Software
- Posts: 17222
- Liked: 1420 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Service Provider
- Posts: 42
- Liked: 8 times
- Joined: Jun 02, 2015 12:44 am
- Full Name: David
For example, if you query Google's for mail.office365.com it will normally return outlook-apacsouth.office365.com with an average ping of 110-120ms.
However, if you query any AU based DNS server (Internode or Telstra for example) it returns outlook-au.office365.com with an average ping of 2-4ms.
The speed difference between these two Office365 sites is also huge. I get 500KB/s-1MB/s via outlook-apacsouth vs 8-10MB/s vis outlook-au.
This suggestion is a complete guess because as Foggy says theres not much info to go on but this might save you a lot of time if it's the cause as it was for me.
- Veeam Software
- Posts: 5113
- Liked: 542 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
This is indeed one of the reasons. Theoretically, when you query O365 you would get the closest one to your area. Your request would go over the internal Azure network and still be very decent in speed. Their internal network is impressive.
However, some companies might query it from APAC but the proxy or router or whatever is located somewhere else which already causes the delay.
Last but not least, O365 has made throttling limitations which can only be lifted by contacting MSFT support. It is also described in our documentation
Users browsing this forum: No registered users and 1 guest