Maintain control of your Microsoft 365 data
Post Reply
FrankCl2
Service Provider
Posts: 73
Liked: 10 times
Joined: Sep 19, 2018 12:11 pm
Full Name: Frank Wijmans
Location: The Netherlands
Contact:

Exit strategy

Post by FrankCl2 »

Hi folks,

Currently, having a exit strategy is a hot topic for us.
Which is something we don't have in place when it comes to M365 backups.

Are there supported or unsupported procedures we could use to export backup data for example to USB disks? Which our (former) customers could use to restore data when in need?

Anybody with experience on this subject?

Thanks,

Frank
Mildur
Product Manager
Posts: 8979
Liked: 2375 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Exit strategy

Post by Mildur » 1 person likes this post

Hi Frank

You can export the data:
- Export Mailboxes to PST
- Saving SharePoint and OneDrive Files as Zip Files or directly as content
- Saving Team Posts as MSG Files
https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=70
A lot of those exports can be scripted by PowerShell or RestAPI.

In case you have jet db based repositories, you can provide your former customers with the jet db files. They can add those files as a repository to their own VB365 installation.
Same goes for Object Storage based repositories, if you have used object storage buckets which were controlled by the customer itself. Simply remove the bucket in your service and let them configure the bucket in their own VB365 server. They must add the original M365 organization to their VB365 server to be able to restore from such backup data.
bucket

Best,
Fabian
Product Management Analyst @ Veeam Software
FrankCl2
Service Provider
Posts: 73
Liked: 10 times
Joined: Sep 19, 2018 12:11 pm
Full Name: Frank Wijmans
Location: The Netherlands
Contact:

Re: Exit strategy

Post by FrankCl2 »

Hi Fabian,

Thanks for your input, much appreciated!

We currently have jet db based repositories for this customer in place. So in theory we could copy this to a disk and have the customer do their thing.
Do we have to consider any limitations or requirements as to how they could add those files to a new VB365 installation? For example, when backed up with version 5, is it possible to add those files to a version 6 installation, or a 6.0 vs 6.1 version etc?
chrisflyckelen
Service Provider
Posts: 63
Liked: 8 times
Joined: Oct 15, 2019 7:51 am
Contact:

Re: Exit strategy

Post by chrisflyckelen » 1 person likes this post

Hi Frank,

another approach would be to provide the customer with their backup repository. The customer can always make a restore even without a license.
So the only thing to do is, installing the application, adding the repository and the customer should be able to export what is needed to restore.

If the customer switches to another backup solution, the backed up data could be deleted after the retention period expires.

Greets,
Chris
Mildur
Product Manager
Posts: 8979
Liked: 2375 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Exit strategy

Post by Mildur » 1 person likes this post

Hi @chrisflyckelen
That's one of my suggestions ;)

Hi @FrankCl2
Yes. Your customer must make sure that the original M365 organization is added to the new VB365 server.
The build must be the same or higher version as the one where you have disconnected the repository.

For added repositories from earlier versions, VB365 will ask for an update of the repository:
https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=70
Updates to V7 can be done from V5 and later builds.
https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=70

Image

Best,
Fabian
Product Management Analyst @ Veeam Software
chrisflyckelen
Service Provider
Posts: 63
Liked: 8 times
Joined: Oct 15, 2019 7:51 am
Contact:

Re: Exit strategy

Post by chrisflyckelen »

@mildur
Oops... Late night forum post seems not to be a good idea :D
Post Reply

Who is online

Users browsing this forum: No registered users and 7 guests