What are the features in the version 8 release of object storage that will fix this issue? We are facing a similar issue, we had a retention of 3 years (why, because when we started, I wasn't thinking about "the future"), that I reduced 2 two years to help decrease the space used, but as noted, this didn't do anything because as you mentioned above the JETDB doesn't relinquish it's territory. When is the expected release date of 8, and can you point to the "New & Improved" features that would aid with this issue?The Move-VBOEntityData function does not release unused space. Jet databases cannot be shrunk, although it may be possible with eseutil, it is a lengthy process and not supported. I do not recommend using it.
However, you can use the move command to transfer any remaining restore points to a new repository and then delete the old repository. Backup jobs will not run during this migration to a new repository.
Instead of performing this migration, I suggest waiting until version 8 is released and then considering a migration to object storage. The benefits of our upcoming version should make the migration to object storage worthwhile.
Best regards,
Fabian
Also, when I calculate our data in M365, it only comes to about 1.5TB, but in the JETDB, it says it's 3.9TB... this is from running the script you provided above. Soooooooooo.... what does that mean? Does that mean that there is 2.4TB of backup data that is just backup copies of the primary data objects, or snapshots, or whatever the correct term is?
Statistics: Posted by kshaeta — Jul 02, 2024 5:51 pm
