hi there, my experience with move-vboentityData, onPremis from one Jet to another also was very bad... the time it takes is one thing... another was that some objects couldn't be moved at all... and next one is, that the Destination JET DB is "corrupted" what the size of the objects in there is regarding... ah Repository that took like 17TB before now shows around 30 or 50TB and also grow unexpectedly faster then all other... strangest thing about this issue is, that the JetDB Files still only consume 17TB on disk...
another customer with around 60TB on Disk, according to the Powershell Commands from VB365 consumes 6600TB of repos...
you can imagine what ah hassle this is to get the customers ah correct bill for the used space (vb365-as-a-service)... obvisously we can't charge for the 6600TB eventhough i would like to and get ah big bonus of it each month..![🤯]()
my learnings are, don't use the move-vboentitiydata command!
i hope the V8 move will get better....
right now we start with fresh S3 Buckets for our customers and we just gift the customers the space we need for this double retentionholding![:(]( "Sad")
another customer with around 60TB on Disk, according to the Powershell Commands from VB365 consumes 6600TB of repos...
you can imagine what ah hassle this is to get the customers ah correct bill for the used space (vb365-as-a-service)... obvisously we can't charge for the 6600TB eventhough i would like to and get ah big bonus of it each month..
my learnings are, don't use the move-vboentitiydata command!
i hope the V8 move will get better....
right now we start with fresh S3 Buckets for our customers and we just gift the customers the space we need for this double retentionholding
Statistics: Posted by DaStivi — Jan 23, 2024 11:44 am
