Can't get Move-VBOEntityData to work

[pufferdude]

I'm trying to follow the Example 1 "Moving User Data" here https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=50 but not getting very far.

I seem to not be able to get the user in the Get-VBOEntityData command, which then causes the Move-VBOEntityData command to fail.

Specifically, I can run:

$repository = Get-VBORepository -Name "O365 Backup 2yr" (then print $repository and see the correct repo's info)

$destination = Get-VBORepository -Name "O365 Archive" (then print $destination and see the correct repo's info)

$user = Get-VBOEntityData -Type User -Repository $repository -Name "Firstname Lastname" (when I print $user, I get nothing returned here)

Then when I try the move via:
Move-VBOEntityData -From $repository -To $destination -User $user -Mailbox -ArchiveMailbox -OneDrive -Sites

I get this error, presumably because I don't have a user from the prior step:

Move-VBOEntityData : Cannot validate argument on parameter 'User'. The argument is null. Provide a valid value for the
argument, and then try running the command again.

Can anyone tell me where I'm going wrong? Are the Example instructions wrong or incomplete? I've tried multiple user names of ones I want to move (all accurate) with same results.

[nielsengelen]

Do you get any users as output when you just run "Get-VBOEntityData -Type User -Repository $repository"?

[pufferdude]

Doh, I'm an idiot. I was pointing at the wrong source repo, which didn't have these no-longer-in-O365 users I was trying to move. Just got confused as to what repo I was trying to move from. Sorry to waste your time!

[pufferdude]

Ah, but stuck again. The move doesn't throw an error now, but doesn't actually move anything. I think it's because I have a source repo with users in it that are no longer in O365 (they were deleted long ago). Seems I can't move the backups of said users from old repo to new one (because the new repo can't find those users in O365?) Sigh.

[nielsengelen]

It could be that the backup file retention was already reached and the data is already deleted. What is the retention for the source repository and how long ago did those users get deleted from M365?

[pufferdude]

Thanks. I don't think it's retention, as the source repo's retention is 7yr and the destination is never... and we've only been using VBO for 3yr

I went ahead and tried a move from our primary repo on a user that DOES exist in O365, and that move fails as well... no error, the Move-VBOEntityData command just prompts with the "Y" to proceed, and when I do, I see some blue text flash at the top and the command is over within a second or two... and nothing at all is moved to the destination repo.

All I did was create a new destination repo with never expire... is there something else I should have done? Is it possible VBO can't move users to this repo because nothing has ever been written to it via a normal backup? (That would seem to defeat the purpose of the move command, if so). If that's not it, I must be missing something else. As it stands, no move I've tried works, but no errors are thrown, either.

[nielsengelen]

Unfortunately, at this stage, I am unable to tell what could be the cause and I suggest you to open a support case to understand what is going on. Some insight will be needed in your setup and repositories.

Could you open a case and let us know the case ID for future reference?

[Polina]

Hi Jim,

Do both repositories have the same type of retention?
Also, the move operation is independent of the user state in O365. It simply moves backup data between repositories. The check for an O365 license of a user will be performed when you run a backup job containing this user and targeted to the new repository.
Last but not least, have you already checked our KB describing how to move your backup data the right way: https://www.veeam.com/kb3067 ?

[pufferdude]

Both repositories have the same TYPE of retention (Snapshot) but the source repo has 2yr retention and the destination repo has forever.

Thanks for the link to that KB and script. I will try that and see what happens (above I was just running the commands manually)

[pufferdude]

Doh. This all came down to the jobs still being active! That KB gave me the clue that move jobs can be seen in the UI under History | Data Management, and when I looked THERE I could see my move attempts failing with "Repository is used by a restore session. Stop the session and try again." error.

While I was NOT doing any "restores", on a hunch I just disabled the jobs and voila... move worked perfectly. That Move-VBOEntityData command needs some seriously better error reporting

Thanks all for the help, I finally got it working and that's what matters!

[Polina]

Hi Jim,

Glad it finally worked for you )
And thanks for the feedback - I'll take a closer look at the error reporting there.