Hi,
I tried the Beta for Office 365 backup and noticed that the archive mailbox is not being backed up. I noticed this when trying a test restore I was not given the archive in the mailbox tree.
Did I do something wrong or is this not supported in the beta?
I have also noticed that you need an account with a license assigned to it in-order to connect to an organization.
As SMB would have it, they would usually pay for the mailboxes they actively use only and not for their subcontracted IT admin team
Is that a limit of O365 or do I need to enable some special permissions in on the account I am using?
BriFar wrote:I tried the Beta for Office 365 backup and noticed that the archive mailbox is not being backed up. I noticed this when trying a test restore I was not given the archive in the mailbox tree.
Did I do something wrong or is this not supported in the beta?
Hi Brian, this is a limitation of the beta build. It will be supported in the GA version.
BriFar wrote:I have also noticed that you need an account with a license assigned to it in-order to connect to an organization.
As SMB would have it, they would usually pay for the mailboxes they actively use only and not for their subcontracted IT admin team
Is that a limit of O365 or do I need to enable some special permissions in on the account I am using?
Brian, you don't need a license assigned to that account, just checked, it just works. But you might be hitting known issue: when a new account is created in Office 365 with password containing symbols like "~" or "#", then it cannot run a PS cmdlets up to the first password change. You can even change it to exacly the same password. Then it works as expected.
Hi Kostya,
thanks for the replies.
Re account, i tested with other accounts where we do not have a mailbox and it worked.
I seem to have one of the test domains for whom I am getting the error when i tries to connect to EWS:
30/09/2016 20:34:11 4 (2720) Failed to connect to Exchange Web Services.
30/09/2016 20:34:11 4 (2720) Error: Mailbox does not exist.
The subsequent operations are successful.
This happens when I try to add the Org.
The password does not have any special characters. The domain has a "-" in it like "domain-name.com"
Could that be causing an issue?
I will open a support case just in case.
Brian
Hi Kostya,
thanks for willing to assist. As mentioned in the PM, the issue seems to be resolved by itself.
Tried connecting again this morning and it connected to the organization without issues.
I'm running the GA version 2.0.0.594 and am running into the same problem as the person that started the thread; online archive mailboxes are not being backed up.
The error message is :
10/26/2018 2:41:36 AM :: Processing archive mailbox user@MyDomain.com failed with error: Cannot access mailbox.. Failed to synchronize item changes in folder: Inbox.. Mailbox move in progress. Try again later., Cannot open mailbox. :: 0:27:13
I receive this same error for all archive mailboxes (about 20 of them). I am not conducting any other processes at the same time so the "Mailbox move in progress." statement seems to be out of place.
Mailbox move potentially could be performed as a background process inside the O365 infrastructure. So, it still makes sense to run Get-MoveRequest and see the results. If everything is ok and you still can access those mailboxes in Outlook, it'd be best to re-run the backup again (I know that the similar issues have resolved naturally in some cases). If there's still no success in the next couple of days, please create a support case (and provide you case ID here).
As suggested I waited and the problem eventually cleared up without any action on my part. Each backup retry knocked a few of the failing mailboxes of the list until they were all captured by the 5th attempt. I did check to see if any moves were in the queue; it was empty.
Thank you
Thank you for getting back on this. I'll share the results with our support and R&D teams. There were a few more similar cases among our customers, which also have resolved naturally. We'll continue to investigate how to overcome such issues.
But you might be hitting known issue: when a new account is created in Office 365 with password containing symbols like "~" or "#", then it cannot run a PS cmdlets up to the first password change. You can even change it to exacly the same password. Then it works as expected.