Question about migrating to S3 from Jet DB

[kevin.boddy]

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

[mjr.epicfail]

Hi Kevin,

What numbers are we talking about here?
Do you now count of objects and total size of a single repository?

[kevin.boddy]

Hi,

The repository size is 60TB. I don't know how many objects but over a thousand users.
I have seen mention other service providers experiences being it takes about 14 days to migrate 20TB from Jet DB to S3.
Unfortunately, the customer cannot afford that kind of downtime for their backup.

Thanks
Kevin

[Polina]

Hi Kevin,

The high-level plan is to copy data from the source to the target and let the existing jobs continue running to the source repository during the migration. However, as the migration functionality mentioned by Fabian has not been released yet, it's too early to talk about it in details.

Thanks!