news about move-VboEntityData enhancements with v8 ?

[karsten123]

we already migrated all of our JET repositories to S3. It was such a pain in the a**.

[DaStivi]

just to cross-reference this... currently there is a bug after moving jet-2-S3 ... restorepoints before the move aren't visible with the restore portal, and only when dooing restores via the organization object, and not through the job object any more..

veeam-backup-for-microsoft-365-f47/poin ... 97927.html

[karsten123]

experienced a upload cap of round about 200 Mbit/s to S3 repository. What is the reason for that?

[Polina]

Hi Karsten,

Potentially it could be some network constraints or throttling on the storage side, or possibly some local system limits...

[karsten123]

you are right for sure. is it possible to check it in the move job logs?

[Polina]

It's very unlikely, we are only logging events produced by the product itself or relevant for the product.

[sandsturm]

Is it possible to use the "new" mechnic only for Jet to Object migrations or also for Objectstorage to Objectstorage migrations?

thx,
sandsturm

[Polina]

@sandsturm

Nothing new has been released yet. We will provide all the related information when the feature is ready and available.

[DanielJ]

We are weeks away from having a new S3 platform up and running. We will then want to migrate off the old one as soon as possible. Any chance of there being a supported method for doing that in the near future?

[DaStivi]

If you follow the posts from Polina, not eta for the new logic/script (or whatever it will be)...

Only way right now, stop and disable job/schedule and then run the script with the move-vboentitiy cmdlets. It's working this way okeyish... Sometimes there are a few issues... Anotherthing I noticed sometimes there are groups moved, with the groups the member mailboxes are moved ,likewise in the backup there is a dependency... Afterwards when the user is moved (or vice versa) the move job generate a warning because either the object is currently still moved or it might be finished moving I ln the other move job and then it's complaining it doesn't find the object any more...

One more thing I did, after the move Jobe finished , I manually checked the jet repo with the get-vboentity cmdlets to see if there are any objects left in the repo! Happened once or twice that some objects where still in the jet according to the cmdlets..

Another important thing, don't run the job unless all move jobs are finished!

Also check the issue that arise with using the cmd, right now the moved restore points are not displaying in the (web) restore Portal...

[DanielJ]

Not looking for an ETA. I just want some reassurance that this sorely needed feature is coming. I don't know how it was possible to ever start recommending SP's and others to move to S3 without even a supported method of migrating between S3 platforms.

[DaStivi]

S3 to S3 most probably isn't supported when the new logic is released at first... This has also been already communicated...

Right now S3 to S3 I would recommend to use something like "S3 explorer" and copy the content , then re-import it into VB365

[sandsturm]

Exporting and importing the content will work for 1-2 TB or so. In my case, I have about 170 TB to move and during the time of this move, i have to stop the backupjobs and that is almost a no-go beacuse the import and export will take too much time. Therefore I (and it seems a lot of other persons) need an option to "migrate" the data independent of active backup jobs....

[DaStivi]

i understand the issues but still you need to see how to get around without relying to veeam...
either your storage can provide such a feature, for example in Netapp Ontap S3 there is a S3-Bucket Snapmirror you can "clone" the s3 bucket to a new storage in the background and only need minimal downtime...

and you can still try S3-Browser (s3browser.com) there is a "folder-sync" option where at least in theory you can choose 2 s3 buckets... i didn't tested this just saw the docs and saw the option in real life its there and you can choose booth folders to be s3..
https://s3browser.com/amazon-s3-folder-sync.aspx



you'll need to check also propagete deletes..


for me that sounds like it could work (like a robocopy /mir )

[karsten123]

if „get-vboentitydata -repository $repo -type organization“ is null for migrated JET repos, is it save to delete them? or should i wait for the retention to expire?

[DaStivi]

I specifically queried against each "type"..

Code: Select all

Get-VBOEntityData -Repository $repo -Type 
Group         Mailbox       OneDrive      Organization  Site          Team          User

[karsten123]

if organization is null, all other types will also be null

[DaStivi]

i've deleted the jet repos after the get-vboentitiydata didn't listed anything anymore... hopefully everthing has been moved.. and the jet dbs contained only whitespace... size isn't shrinked of these files... you would have todo a offline database reorg to see the change reflected...

you might can remove the jet-repos from vb365 and try to restore some old data out of the moved s3 repos hopefully this is a legitimate way to test availability of restore points..