VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
First things first, you should test this in the latest version, which is currently VB365 v7, there’ve been many breaking changes over the years. If you can test in a supported version that the issue still occurs and if the error changes that’ll be the best first step please. I’ve just now had a chance to install a trial of version 7, and yup, that works no problem.Cheers!
Hopefully I only need to confirm my auth once per session - going to https://microsoft.com/devicelogin won’t be much use in a loop :) Booo! You have to continually re-authenticate. I’ll have to find a new solution.
It looks this was a modern authentication issue. I followed the app registration example in #6 and that seems to have worked.Hopefully I only need to confirm my auth once per session - going to https://microsoft.com/devicelogin won’t be much use in a loop :)
Right, I think that I’ve resolved it. I checked out“C:\ProgramData\Veeam\Backup365\Logs\Veeam.Archiver.Service_2023_07_07_09_54_54.log”and, from my guesswork, it seems that the actual deletion happened instantly, but it triggered a full sync of the job. Is that right:07/07/2023 14:26:12 Deleting job: Remove user: Some User...07/07/2023 14:26:12 Deleted07/07/2023 14:26:13 Checking identity of the request from 127...07/07/2023 14:26:13 Identity check passed07/07/2023 14:26:13 Adding full synchronization action to queue07/07/2023 14:26:13 Preparing full synchronization07/07/2023 14:26:13 Starting proxy configuration synchronization: serverIf so, that would be a nightmare to remove 8 users from a job that contains 200.I returned to the Remove-VBOEntityData cmdlet and see a -RunAsync switch which “Indicates that the command returns immediately without waiting for the task to complete.”. That sounded perfect, so I amended my script, and the jobs ran through immediately.I don’t know if
oh ok, thanks. Will do. EDIT - I can’t create an account there at the moment, they must be having issues. So, for now, I’ll carry on here.I’ve had a look in the logs at C:\ProgramData\Veeam\Backup365\Logs\Veeam.Archiver.PowerShell_2023_07_07_12_01_05.log Here is the end of it:07/07/2023 12:10:49 13 (7600) Processing Veeam PowerShell cmdlet: Get-VBORepository...07/07/2023 12:10:49 13 (7600) Cmdlet script name: C:\Users\KWCork\Remove-VeeamUserDataAndLicence.ps1 (line number: 12, offset: 15)07/07/2023 12:10:49 13 (7600) Cmdlet pipeline length: 1 (position: 1)07/07/2023 12:10:49 13 (7600) Cmdlet parameters:07/07/2023 12:10:49 13 (7600) Name: My_M365Repository07/07/2023 12:10:49 13 (7600) Cmdlet execution completed: Get-VBORepository07/07/2023 12:10:49 13 (7600) Processing Veeam PowerShell cmdlet: Get-VBOEntityData...07/07/2023 12:10:49 13 (7600) Cmdlet script name: C:\Users\KWCork\Remove-VeeamUserDataAndLicence.ps1 (line number: 16, offset: 17)07/07/2023 12:10:49 13 (76
As @DChiavari said, retention policy for VBM365 can be confusing and can cause storage issues if not configured correctly. I find this blog very useful for explaining the difference between item level and snapshot level retention. https://www.veeam.com/blog/office-365-backup-retention-explained.html I’d like to see this, but it always times out. “Generating Protected Mailboxes report…. Please wait...” for quite a few minutes and then times out.It’s a pity that there is no -job switch as it does the whole organization without restriction. Thanks for the link though.
Just as an additional suggestion / heads-up: check the Retention Policy setting at the Repository level. “Item-Level” retention can be sometimes confusing, since the retention setting does not only impact how long data is kept - it also impacts which data is backed up in the first place. For example: if you select 1 year, only items not older than 1 year are backed up, and then kept for 1 year. Wow, I think you just saved my bacon there. I assumed it meant “keep this for a year” and as I’m using this as a temp backup before a migration, 1 year is all I set… :-|I’ll change that right now and hopefully it’ll append the missing data. Otherwise I’ll re-create from scratch. Thanks for the tip!EDIT: Yup, it’s adding the missing data now.
Yeah, I’d like to get those licences over the next few days though. Looks like support will be the only option.
Yeah, I was worried that might be the case. You live and leearn. :) Thanks.
Yup, the whole repository has been blitzed and doesn’t show up with Get-VBORepository. Still can’t remove the licences though.
OK thanks for the reply. I'm using this to assist merging about 50 accounts this weekend so having to mess about with zip files is a pain when I could automate the whole thing otherwise.50 is doable, but I've to do the same with about 300 accounts in July so in the meantime I'll have a play with the OneNote API you mentioned. :-) Cheers
"if something you are trying to do is not supported." You make it sound like I'm using your product to do something it was never intended to do. I only want to restore files that are backed up and there is now no way to do that. It's truer to say that your product is not fit for purpose, and what annoys me most is that version 7 came out after EWS was discontinued.
Thanks for the suggestion. I’ve actually got it working in the meantime by testing the backup in the GUI. Once I did that, the PS version worked fine.So, I guess Veeam “couldn’t see” my target user, for want of a better word? Is there something I should do to ensure that? This morning I used Get-VEODUser to check the account and I could query it without issue. Any suggestions?Cheers again.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
