This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Compression 0%

Hello
I was having space problems in my repository, so to solve the problem, I paused all the jobs for more than 24 hours, so the rollups could complete, and it would not disrupt RPFS jobs in the background.
Today, my repository has more than 3TB of space, but the compression is still 0%. My doubt is. Is it necessary to complete RPFS jobs to start compression?
I ran a script now for more information.

QueuedFileVersions QueuedRPFSSize
134156 21.71TB

Do I need to wait to complete the compression?

Parents

0 Emte over 5 years ago

https://support.quest.com/rapid-recovery/kb/158029/understanding-0-compression-in-an-appassure-rapid-recovery-repository

Resolution

Once 0% compression occurs there is no solution to undo this. No matter which of the following workarounds you choose, the affected repository must be deleted and remade.
Cancel
Up 0 Down

Cancel
0 daniel.santiago over 5 years ago in reply to Emte

Check Respository, would solved?
Cancel
Up 0 Down

Cancel

Reply

0 daniel.santiago over 5 years ago in reply to Emte

Check Respository, would solved?
Cancel
Up 0 Down

Cancel

Children

0 Emte over 5 years ago in reply to daniel.santiago

If you are having the issue described in the article then it appears nothing will solve it short of deleting the repo. But if you are unsure, open a case with support
Cancel
Up 0 Down

Cancel

Compression 0%

Resolution