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

Best Practice To Free Up Space Post Upgrade

Hi All,

I just upgraded a file server and obviously RR took a new snapshot. My question is what is the recommended method for gaining some space back on the repository? I have another protected server to upgrade soon and I need the room for yet another new snapshot.

Do I shorten the retention period temporarily? I use the default retention schedule. If I delete my original snapshot won't it kill the whole old chain?

Thanks

Parents
  • If you delete a base, it will also delete every INC from the base forward to the next base. So not a good option. You could archive the base and its INC before deleting but due to performance issues, this is not something I would typically conciser 

    Shortening the retention may buy you a little space, but probably not enough.

    We go through this a lot and here are my thoughts. Everything you can think of is a band aid to try and fix a broken aspect of the product. There is really only 1 option in my mind

    Add more space to the Repo. This could be either a new repo or add an existing extent to the current repo. 

Reply
  • If you delete a base, it will also delete every INC from the base forward to the next base. So not a good option. You could archive the base and its INC before deleting but due to performance issues, this is not something I would typically conciser 

    Shortening the retention may buy you a little space, but probably not enough.

    We go through this a lot and here are my thoughts. Everything you can think of is a band aid to try and fix a broken aspect of the product. There is really only 1 option in my mind

    Add more space to the Repo. This could be either a new repo or add an existing extent to the current repo. 

Children
  • I have another repo that replicates from this one. If I wipe out the base on one repo would it leave the other one alone? One would have all new points and the other all the old.

  • The recovery point chains on the two cores can be different. As long as the replication is in sync currently, deleting the old base image and incrementals from one core would not remove it from the other.

    The only way it could cause an issue is if you break replication after the delete and reconfigure it. In that case if the core with the old base image chain is the source core, it will try to replicate all the missing data over to the target core so that both have the same data. But as long as you leave the replication configured it won't be an issue.