Moving o365 backups to a new disk

[unsichtbarre]

Howdy!

I need to migrate my Veeam Backup for o365 from an old disk to a new disk. Unfortunately, there are several very large jobs (2400 users/mailboxes) and it is about 15TB of data that I need to move. Right now, I am planning on using: Move-VBOEntityData but I am wondering if I need to disable the o365 job(s) first? It doesn't seem to be specified in: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=50

Are there any other tools to move the data efficiently?

THX,
-JB

[Mike Resseler]

JB,

I think this will help you: https://www.veeam.com/kb2649

[unsichtbarre]

Hi Mike,
Thanks for the reply. I am not migrating the o365 server, only the repository. The Move-VBOEntityData is what's been suggested.

[Mike Resseler]

John,

For: I am planning on using: Move-VBOEntityData but I am wondering if I need to disable the o365 job(s) first?
-> Yes, the backup job cannot run while this is running
For: Repository
-> See here also: veeam-backup-for-office-365-f47/moved-e ... 65119.html
There is another way, might be better (faster) depending on the size of your current repository. But also see that getting assistance from support can be handy

[unsichtbarre]

Thanks for the advice Mike;
Unfortunately we started with Move-VBOEntityData weeks ago and the process is painfully slow.

I WISH has started with Robocopy as that would have taken 24-48 hours at most. We are following up with support, I will add the case number when it is available.

Is there any way to transition the process from Move-VBOEntityData to Robocopy or are we stuck since about 33% of the data is moved?

THX,
-JB

[unsichtbarre]

Case number: 04904368

[nielsengelen]

Hi John,

If you aren't using Move-VBOEntityData anymore at the moment, u should be able to stop that process and use Robocopy. After that use Move-VBOEntityData again and point it to the copied repository.

[unsichtbarre]

Thanks nielsengelen!
Unfortunately support (Case number: 04904368) is somewhat unfamiliar with Move-VBOEntityData and providing information contradictory to what we already know/have proven to be the case.

Can you describe the process of using Robocopy after about 33% of mailboxes moved with Move-VBOEntityData?

[unsichtbarre]

I'm sorry I need to rant just a little. We are simply not getting the support we need. It took escalation to management to get the original case engineer to call us back and now after receiving notification that the case was being escalated, it has been 24 hours and no responses. And I have again requested management intervene.

In order for Veeam to expect us to use severity correctly in categorizing cases, Veeam also needs to respect the SLA of the assigned severity. This is severity 2 and we have been multiple 24 hour windows without replies (after we have supplied the requested information).

The issue is that Veeam just isn't moving data from Microsoft and/or between repositories.

[nielsengelen]

Hi John,

I'm sorry for the late reply. I must have missed your follow-up comment on the request.

Normally, moving data can be done using Move-VBOEntityData which will ensure the move of the data to another repository. Why this takes so much time for you is hard to tell. Now as you stated, you canceled this task after 33%.
What you can do is somewhat follow the procedure listed on the move KB.

1. Disable all backup jobs related to the repository you want to move.
2. Stop all the Veeam Backup for Microsoft Office 365 services before moving any data.
3. Copy the backup repository data to the backup repository location on the new repository location (using robocopy for example).
4. Start the Veeam Backup for Microsoft Office 365 services.
5. Add the new repository with the moved data.
6. Open backup job settings and specify to use the new repository.

This should allow you to open the restore points by right-clicking the corresponding organization. For the other data which you have moved, you should then be able to use Move-VBOEntityData to move it from the current repository into the new repository.

[unsichtbarre]

Hi nielsengelen,

Thanks for the reply. Your information is directly contradictory to information provided by Veeam Support on our ticket. I would estimate 24-36 hours move time for the entirety of the data using Robocopy - and I would love to proceed with this method.

Are you saying that even after using Move-VBOEntityData for 33% or so of the data, we can still use robocopy? How will that not totally mess up the data that has been moved so far? Right now Veeam for o365 seems to be completely stuck, so we are waiting for our escalation engineer at 16:00 this afternoon.

THX,
-JB

[nielsengelen]

Hi John,

I don't know exactly what has already been done via support but I just had an update on this topic and the case is actively being worked on. You should receive a call later today on the topic.

It sounds like this is the best option for now to assure consistency.