Hi,
I saw back in Feb this year on this thread
veeam-backup-for-microsoft-365-f47/obje ... 87494.html
Fabian mentioned "we will release a new cmdlet for Jet DB to object storage migrations, which will allow the migration of backups while backup jobs can run"
Does that mean backups not targeting the backup repository can still run or all backups can continue to run including the one being migrated?
What happens if we stop the migration part way through because it's taking too long to migrate, can we still use the source Jet DB repository again or is the data being moved out of the Jet DB to the S3 repository?
Thanks
Kevin
I saw back in Feb this year on this thread
veeam-backup-for-microsoft-365-f47/obje ... 87494.html
Fabian mentioned "we will release a new cmdlet for Jet DB to object storage migrations, which will allow the migration of backups while backup jobs can run"
Does that mean backups not targeting the backup repository can still run or all backups can continue to run including the one being migrated?
What happens if we stop the migration part way through because it's taking too long to migrate, can we still use the source Jet DB repository again or is the data being moved out of the Jet DB to the S3 repository?
Thanks
Kevin
Statistics: Posted by kevin.boddy — Apr 03, 2025 1:22 pm







