Hi guys,
Is it about time the Office 365 product started auto-updating as a countermeasure to the constant changing of APIs at Microsoft?
I think a lot of people (myself included) would rather Veeam automatically pushed out the response to API changes as they are happening so frequently.
Obviously switchable so people have the choice whether or not to enable the automatic update.
On a side-note.. I only found out about the most recent API change from Gostev's forum digest email. Maybe o365 customers should get email notifications in the future each time Microsoft does a breaking change on their end. At least until we have an automatic update feature?
-
- Veteran
- Posts: 636
- Liked: 100 times
- Joined: Mar 23, 2018 4:43 pm
- Full Name: EJ
- Location: London
- Contact:
-
- Veeam Software
- Posts: 3195
- Liked: 774 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: API changes
Hi EJ,
Taking proactive measures is not always possible, because there's no single source (yet?) to track API changes in advance before they affect VBO work.
VBO is already providing an auto-update feature that is used to deliver the latest cumulative patches as well as new versions. The main challenge at the moment is the time required for testing each patch before rolling it out, and that's why it's sometimes faster to get the hotfix directly from support rather than be updated immediately by the product itself. There's some room for improvement, of course.
Taking proactive measures is not always possible, because there's no single source (yet?) to track API changes in advance before they affect VBO work.
VBO is already providing an auto-update feature that is used to deliver the latest cumulative patches as well as new versions. The main challenge at the moment is the time required for testing each patch before rolling it out, and that's why it's sometimes faster to get the hotfix directly from support rather than be updated immediately by the product itself. There's some room for improvement, of course.
-
- Veteran
- Posts: 636
- Liked: 100 times
- Joined: Mar 23, 2018 4:43 pm
- Full Name: EJ
- Location: London
- Contact:
Re: API changes
Maybe I'm being too specific.
What I'm hinting at is the idea of removing the human factor from the success or failure of o365 backups when everything else is available to make them work.
i.e. if you have a deployable hotfix but the user is on holiday instead of failing for two weeks until the user returns the software could install the hotfix itself and start backing up without the user having to intervene and correct the problem manually.
I'm not sure if it makes more sense phrased like that?
What I'm hinting at is the idea of removing the human factor from the success or failure of o365 backups when everything else is available to make them work.
i.e. if you have a deployable hotfix but the user is on holiday instead of failing for two weeks until the user returns the software could install the hotfix itself and start backing up without the user having to intervene and correct the problem manually.
I'm not sure if it makes more sense phrased like that?
Who is online
Users browsing this forum: No registered users and 28 guests