• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 27 subscribers
  • Views 3670 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

Quest vs Dell compression

lbuck
over 6 years ago

We have a couple of DL appliances that we've had for 3 years.  For the last year and half everything has been good with it with the same number of protected machines and retention rate settings so that it was close to max capacity.  Earlier this year I upgraded from the Dell to the Quest version.  Since then, I've had to remove 5 protected machines and reduce drastically the retention settings and even then, I'm constantly getting warnings about the Repository being full and when it hits the max, no new recovery points get saved.  Is the compression or deduplication or whatever it is, that much worse with the new Quest version?  Is it a matter of waiting it out till all the Dell recovery points are gone?

Parents
  • 0 over 6 years ago
    Thanks for your reply and suggestion. While it wasn't the issue, the cores are not busy and there is a lot of times when no events are running, it did make me look through the event logs for the protected machines looking for when rollups were happening and I didn't find any. I then took a closer look at the retention policy and the exiting recovery points and realized that the retention policy isn't being followed. To my limited knowledge, it looks like no rollups or deletes have been done since Feb when I upgraded to Quest. I did a Force Rollup on one protected machine and it went from 13 pages of recovery points down to one.

    I attempted to do Force Rollups on the other machines and unfortunately it looks like half of them error out with
    •The given key was not present in the dictionary.
    •The remote slave core with the id '9b3968d5-86c0-4e7a-90b4-0e5cfe07aa8a' was not found

    I'm assuming it is trying to do the rollups but encounters this error and then doesn't attempt any other machines. So now I got to look at this.
Reply
  • 0 over 6 years ago
    Thanks for your reply and suggestion. While it wasn't the issue, the cores are not busy and there is a lot of times when no events are running, it did make me look through the event logs for the protected machines looking for when rollups were happening and I didn't find any. I then took a closer look at the retention policy and the exiting recovery points and realized that the retention policy isn't being followed. To my limited knowledge, it looks like no rollups or deletes have been done since Feb when I upgraded to Quest. I did a Force Rollup on one protected machine and it went from 13 pages of recovery points down to one.

    I attempted to do Force Rollups on the other machines and unfortunately it looks like half of them error out with
    •The given key was not present in the dictionary.
    •The remote slave core with the id '9b3968d5-86c0-4e7a-90b4-0e5cfe07aa8a' was not found

    I'm assuming it is trying to do the rollups but encounters this error and then doesn't attempt any other machines. So now I got to look at this.
Children
No Data