I have been trieing to restore data from a azure blob witch holds a archive from a custommer. The corresponding tennant is deleted a long time ago and the blob holds backup for (legal) archive purposes.
True a restore will not work because the tennant does not exists, but as far as our own investigation goes it is currently not possible to restore (or .pst export) O365 data stored from a tennant that does not exists anymore.
The use case is that this customer has a archive azure blob (cold not archive).
The original Veeam backup VM does not exists anymore.
Some data is needed for regulatory purposes from the archive.
After installing a new VM and adding the old Azure blob data the machine will start the import & index.
The repo shows in this example about 14TB of data present.
However it is not possible to access the data or start a restore session because the tennant is not in place.
example: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=80
After some digging the powershell does show the data is present on the blob. We have used the following commands:
# Get-VBORepository
# $archiverepo = Get-VBORepository -Name "Veeam365"
# Get-VBORestorePoint -Repository $archiverepo
This does give a long list of backups
We can also get some details:
# Get-VBOEntityData -Repository $archiverepo -Type Mailbox -Name "SomeUser"
Now the problem.
It does not seem to be possible to restore anything because the organization does not exists.
Also it is not possible to start the BackupExplorer, also the powershell does not allow this with the SessionID.
#Im Not Allone, I have found this in the fora:
veeam-backup-for-microsoft-365-f47/how- ... 90723.html
What is the procedure to recover (or export) data from AzureBlob if the original tennant does not exists anymore?
Corresponding: Case # 07587858 - Restore Azure blob data from deleted tennant
last response:
I can immagine more people has a archive somwere in the belief it is ready for restore.Unfortunately, we would not be able to read the data as they are orphaned, and it is not possible to re-index the same without configuring the organization.
As of today, this is limitation with Veeam backup for Microsoft 365. We will work with the RnD team to have this addressed in the future.