• State Suggested Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 10335 views
  • Users 0 members are here
Options
Related
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

Deferred Delete / Repo space

Emte
over 6 years ago

Does anyone from RR have any insight into the Deferred Delete Process and/ or managing full repo's?

 

1) Deferred Delete

I cant find a lot of info on deferred delete past https://support.quest.com/rapid-recovery/kb/198715/understanding-deferred-delete-in-nightly-jobs

- How is it different than the normal deleting rpfs index file jobs? Does it just run after a delete is performed vs waiting till the nightly?

- Is there any reason not to enable this (and if not, why is it not the default) 

- If we upgrade to v6 and enable deferred delete (or the normal nightly job) Will this clean up v5 repos that were affected with several bugs from v5 repos, such as the ones documented here

support.quest.com/.../understanding-0-compression-in-an-appassure-rapid-recovery-repository

 

2) Full Repo's

I wish you guys would take a look at this entire repo situation. We constantly have sites call us with full repo's and it is a pain to deal with. The Cores are always in this catch 22 where you need space to free up space and we always seem to end up doing something we don't want to do just in order to get it running again and each time, what we have to do seems different. These types of posts go back years without any change, the forum suggested 2 of them as "solutions" to me when I was creating this one

Some idea's

- Have the Repo reserve some space for performing jobs that clear up space, like deletes, rollup etc. Make it so this space can not be consumed long term, EVER

- Have the Core stop backup when the repo reaches a certain % full or even better a % of the total size. So a working % is stored if the repo is 500GB or 50TB, make this configurable

- Have some sort of external space that can be used for jobs like rollup, RP deletes. Even if we had to add a storage location to the repo that was used for this process ONLY. so we could add it, delete data, run rollup and then DELETE the storage location from the repo (long shot, probably)

 

Or maybe I am missing something that is already there? If so, I would love a bit of guidance

 

Thanks in advance

Parents
  • 0 over 6 years ago
    First of all, the old PMs don't work here anymore. So we have a new PM. I have faith you're going to see things change going forward. I know you have heard that like every other month since you started working with us, but honestly, this is the first time I've had hope in a long time. So that should tell you something.

    Second, the new PM is digging through the backlog of ideas and updating it as quickly as he can. It takes time to go through 200 odd items, but he's working at it and you should start seeing updates. Also, I'm not sure how much public changes have been done yet. Public feedback is important and the goal is to get there as quickly as we can.

    Third, the feature request you pointed out about replication defines how replication already works for the most part. It's very similar to what is outlined there. So the reply should have been "we already do this". I am happy to explain how replication works in another post when I have more time if you want to hear it.

    Fourth, the alerts for a repository filling up start at 80%. The notification for a full repository occurs at 98% which is when the repo is basically full. So RR-I-223 is only partially accurate.

    I'm providing you with information regarding the tools we are going to be using going forward. This ideas portal is what we are going to use. If you open a support case and ask to add a feature request, support will point you there.
Reply
  • 0 over 6 years ago
    First of all, the old PMs don't work here anymore. So we have a new PM. I have faith you're going to see things change going forward. I know you have heard that like every other month since you started working with us, but honestly, this is the first time I've had hope in a long time. So that should tell you something.

    Second, the new PM is digging through the backlog of ideas and updating it as quickly as he can. It takes time to go through 200 odd items, but he's working at it and you should start seeing updates. Also, I'm not sure how much public changes have been done yet. Public feedback is important and the goal is to get there as quickly as we can.

    Third, the feature request you pointed out about replication defines how replication already works for the most part. It's very similar to what is outlined there. So the reply should have been "we already do this". I am happy to explain how replication works in another post when I have more time if you want to hear it.

    Fourth, the alerts for a repository filling up start at 80%. The notification for a full repository occurs at 98% which is when the repo is basically full. So RR-I-223 is only partially accurate.

    I'm providing you with information regarding the tools we are going to be using going forward. This ideas portal is what we are going to use. If you open a support case and ask to add a feature request, support will point you there.
Children
No Data