Backup replication site, getting around 2 TB limit

We're going to be replicating our off site backups to the cloud. We will be leveraging a service by a local data center. They will spin up a server for us (Virtual) and we can lease space in 1TB sizes, with a 2 TB max (my understanding is this is also a vmware limitation).

My question is.. what are some ways that we can get around this 2TB limit? Obviously the OS for the storage Server Client + the OS size will not be that large, but the location I will be storing the data, just to start will likely by around 6-7 TB. The good news is that we can point the Server Client to a mapped drive. So in theory, whatever is behind that UNC path for size is all that matters. however, is there a "good" way to manage this in Server 2008R2 or would I be better setting up storage pools in server 2012? Or do you have other suggestions
LVL 5
MetaltreeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Paul SolovyovskySenior IT AdvisorCommented:
The only way currently to go beyond a 2TB limit for a VMDK (keep in mind that you can have multiple 2TB VMDK per VM) is to use a physical RDM.  Or you can wait until vSphere 5.5 comes out and it will support 64TB VMDK (virtual disk size)
0
Paul SolovyovskySenior IT AdvisorCommented:
Forgot to mention, another way to do go around this is to use an iscsi initiator out of the VM attached to a LUN
0
MetaltreeAuthor Commented:
paulsolov,

So how it will work for us is they will in fact keep spinning up separate 2TB volumes for us.

So, my thought was to just keep adding those 2TB volumes to some type of storage pool in Server 2012 or perhaps someone has a better suggestion for 2008r2?
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Paul SolovyovskySenior IT AdvisorCommented:
You can create a VM with 2TB volumes, each one would be a separate virtual disk.

What are you trying to replicate and what methodology are you using to accomplish this task?
0
MetaltreeAuthor Commented:
Its simple.

Server:
It would be a basic OS (2008r2 or 2012) on the C.
the "D:\" would be the collection of 2TB volumes.

This server is a "replication" server. In other words, remote clients/servers just copy their data to this location.

My question is, what would be the "best" way to "pool" the volumes associated withe data drive.
0
Paul SolovyovskySenior IT AdvisorCommented:
you can't have D as "collection" of 2TB volumes.  It would have to be D,E,F, etc..

unless you span the volumes and you don't want to do that
0
MetaltreeAuthor Commented:
Why don't I want to span, or pool, the volumes? Its simply a repository for .vhd or .vmdk files
0
Paul SolovyovskySenior IT AdvisorCommented:
If you have data spanned across volumes and one volume fails you have more than 1 volume with corrupt data.  If you hard separate them into separate volume your SPOF (single point of failure) decreases.  If it's a VMware VMDK you can't pull them together unless you do this in windows as spanned volumes..vmware doesn't support virtual disks larger than 2TB at this tiem
0
MetaltreeAuthor Commented:
Keep in mind, these volumes would all be 2 TB volumes on a SAN. That LUN would attach as a datastore on the host and then that datastore would be the volume on the VM. would that make a difference?
0
Paul SolovyovskySenior IT AdvisorCommented:
If it's an RDM (LUN attached directly to the VM) and it's physical then it can be up to 64TB volume.  A datastore attached to the ESXi host can also be 64TB but the VMDKs inside of the datastore can only be 2TB max as virtual disks
0
MetaltreeAuthor Commented:
Ok, let me rephrase the question.... perhaps you can tell me why this is a really bad idea and offer a suggestion on a better solution...

For the sake of the actual question, lets assume its a physical server, not a VM.

So I have my clients which replicate to my datacenter.

In my datacenter. I have a physical server which is where my Server application for my backup software is installed. I can only keep attaching 2 TB storage to this server. Why is this a bad idea?
0
Paul SolovyovskySenior IT AdvisorCommented:
it is not a bad idea.  The gotcha is if you want all the 2TB volumes be presented as a single "D" drive
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.