Rapid Recovery Repository Volumes

I am using Rapid Recovery. 

My repository is currently made up of 4 6 TB volumes which are full. 

I am planning to triple the size of my storage and want to expand my repository. 

I was told that I could not simply add new volumes to the repository, as that would not balance the data from the currently full volumes, that I would need to archive the current repository,

Delete the current repository and recreate a larger repository. 

I have read that best practice is to use 6 TB volumes. 

Is there a limit to how many 6TB volumes I can use. 

What is the downside of using 10 TB volumes? 

Thank you, 

Lawrence 

  • There's a difference between 'you can't' and 'perhaps it isn't the best idea.'

    You can keep extending your repo, however if you are moving to difference storage mediums, or different speed of disks, it's best to not do that. Even if they aren't 'bad' disks, or bad storage, if they are noticeably different speeds/caliber, not the best idea. For an example, probably not best to have a repo that spans a QNAP with 5.4k disks, then crosses to a EQL with 7.2k disks, and then extends to an all flash Nimble. Can it work? yes. Best idea? no. 

    I have a couple questions, or 1 really. Are these volumes tied together in a RAID and you have a repo that sits on this 1 volume that you've exposed to the core? Or do you have 1 repo, but it sits on a number of extents (different volumes)? Either way, the 'best' thing you could do is have 1 great big volume, and put your repo on it, rather than have 2,4,10 different volumes all attached to make up a repo. 

    RR does not 'balance' the repo across disks no. You tell RR 'here is a 4TB disk' it consumes the whole thing from the get go. Regardless of reason, that is how it works. 

    You asked about repo limits as far as disks are concerned, I think the limit of extents is something like 256, assuming they are mounted disks (not unc/cifs paths). Again, no one one would recommend you doing that, but the core would let you (going back to the first line of this reply, you can do it, but should you). As long as the 'new' volumes are mounted volumes and not cifs shares you can extend the repo yes (unless RR now does allow you to extend to cifs shares, which if it does, I would HIGHLY not recommend you doing that): support.quest.com/.../how-to-extend-a-dvm-repository

    As for using 10TB disks over 6TB, I'd always go bigger as having too much storage is better than not having enough. I have literally dozens of cores using Seagate EXOS 16TB disks, they are perfectly fine. 

    If you have the luxury of using a temporary VM, or another workstation/server as a core, your best bet in moving from 1 repo to another (if it's a full move and you can have both online at the same time) is to temporarily set up a 2nd core, put the 'new' repo on the 2nd core, and replicate the data from the original core to the new one (make sure you specify the same retention policy). Then, once the replication is in-sync, shut down the core services and remove the old repo, and attach the new one to the old core, and march on. This again, is if you are moving from old to new storage and they are entirely different.