Repository Full - Second Repository has more storage available

Question

Hello, 
 I have an interesting problem. My Repository is currently full. I tried to delete some recovery points to free up space, and change retention policies, which helped to free up space, but, my FileServer decided it wants to take a new Base Image, which I don't have enough space to allow it to happen. I know I could kill all Recovery points from my file server, and let it start again, but I'm hoping to avoid this, as I have a better option. 
 We have an Outgoing Replication Rapid Recovery server set up that is in the same datacenter (same rack even). The intention was to put the second server at a second Data Center and have backups replicate...but it never happened. We have roughly 4 more TB of space on this second server. I think I want to make this the primary server, but am not really sure how to do it. I didn't want to do anything drastic, as I'd be curious if there's a really easy way to do it since it's backing up and replicating. I'm going to try to do some more research, my preliminary research has not found much, and I figured I'd get the question asked, and then I'll post an answer if I find it.

tom simanovich · Accepted Answer

As I do each machine, I'll force a backup as you had recommended. I just did the first small machine, and it seems like it's all set. I guess maybe a better way to phrase it (and I think you answered it), Is this: If I leave the replication from current core turned on and only pause it each time I'm working with a virtual machine (or do I not need to keep Pausing Outbound Replication?), will this work? I am trying to avoid new base images for most of them, my file server I can't avoid, but there's some other machines that I'd like to not have them take a new base. My fileserver currently is trying to take a new base image which is causing the space issues.

Tim Seymour · Answer

It's pretty simple to switch from using one to using the other as the primary. 
 
 Pause protection on the source core and ensure replication is caught up 
 Delete replication from both cores but keep the recovery points. All the machines on the replication core should become recovery points only. 
 Protect all the machines on the target core (do not remove them from protection on the original source core becuase that will trigger a new base image for all machines) 
 Once protected, force a backup and make sure an incremental is taken 
 Once you confirm that backups are working properly, remove the machines from protection on the old source core 
 Configure replication from your new source core back to the other core 
 
 I'd recommend doing these steps for one small agent to start with to make sure you understand them and that they work as you expect. Then once you have the steps down, do all of them in bulk.

Repository Full - Second Repository has more storage available

Top Replies