Request a demo
Menu
Request a demo

Virtiant Cloud versus Co-location

by Team Virtiant, on Apr 15, 2019 2:09:30 PM

When physical space becomes an issue, many SMBs begin to consider the option of co-location for their DR solution. They soon discover that a loss of proximity and scalability leads to increases in capital and operating expenditures. In this ongoing series of articles, we will continue to compare the power and simplicity of Recovery Site In the Cloud to other options in the marketplace. Let’s take a look at 4 sizable challenges when it comes to co-location disaster recovery solutions.

Proximity

The primary reason that any organization turns to a co-location scenario for their disaster recovery needs is a lack of available data center space. It may be that they lack the space in their existing facilities or that they need to locate their DR solution a significant distance away from their primary site. Regardless of the reason, the first sacrifice that SMBs will make when opting to co-locate is proximity.

The very essence of co-location means that IT Pros will no longer have the convenience of having localized staff support their DR solution. Instead, they will either have to spend additional funds to travel their teams to the co-location site or pay for ‘smart hands’ staff to handle these tasks. While there may be some value in this type of scenario in the event of a significant natural disaster, it far from convenient if you need to failover only small portions of your production infrastructure. Keep in mind that not every downtime event is a significant event. In fact, most are everyday issues related to equipment or human failure. These situations can often lead SMBs to experience a loss of control when it comes to supporting their DR environment in a co-location scenario.

With Recovery Site in the Cloud, you will be able to access all the network, compute, and storage components of your DR solution from the convenience of your primary location. Your limited IT staff can enjoy the same level of control they have today with their production environment, without the hassle of travel.

Capex Increases

Funding additional floor space in someone else’s data center is only the beginning of the capital expenditures required to stand up a co-located DR solution. In addition to leasing the floor space, SMBs will still need to procure hardware, software, and network equipment needed to mirror their production environment. Once purchased, you will also incur the time and expense to dispatch your limited IT resources to the co-location site to stand up the environment.

An additional consideration is the time and expense spent looking for an appropriate co-location facility that meets all your needs. Not all of these facilities are created equal. Your teams will need to travel to these sites, inspect the facility, evaluate its security and negotiate the appropriate amount of space to support your environment. These expenses must be factored into any cost analysis of a co-location DR scenario.

Virtiant understands the financial challenges that SMBs face. This is why Recovery Site in the Cloud does not require you to purchase extra hardware and software. Plus their industry-leading tools make configuring your new DR solution a breeze.

Opex Increases

Increased capital expenditures aren’t the only cost increases you can expect with a co-location solution. Your operating expenses relative to supporting a remote location are going to increase as well. For starters, you will need to pay maintenance fees on the hardware and software deployed at the co-location site. You will also have additional ongoing licensing fees. Whether you choose smart hands or travel for your existing IT staff, you will be hit with the labor costs of keeping the DR equipment patched and maintained as well. Let’s not forget the additional cost of connectivity between your primary site and the remote site so that you have enough bandwidth in the event of a failover.

Virtiant makes the maintenance of your DR solution ridiculously easy. With their easy to use interface, IT Pros can perform a one-click failover and when the disaster is averted, Recovery Site in the Cloud makes hot migration back to production smooth and seamless.

Scalability Challenges

As if the previous three issues were not significant enough to prevent most SMBs from utilizing a co-location option for DR, we next need to factor in the challenges around scalability. Your DR solution needs to be able to grow as your production environment does. In the case of co-location, you will be required to spend additional time and money to upgrade the DR solution when you make expansions to your production site. You will again need to purchase duplicate hardware and software in addition to sending your IT staff onsite to handle the deployments. You also better hope that this expansion does not require more floor space at the co-location site because you will be paying for that as well.

Scalability and flexibility are the very foundations of Recovery Site in the Cloud. IT Pros can easily scale up or down the needed VMs to support your production. This is especially valuable when you need to support the testing of small portions of your overall production site.

For more in-depth comparisons of Recovery Site In the Cloud, check out these articles covering RSIC’s advantages over on-premise, public cloud, and competitors solutions such as Datto. They will help you discover just how Virtiant can provide the ridiculously easy infrastructure resilience your SMB needs and deserves.

Schedule A Demo

 

 

Topics:business continuityDisaster Recovery

Comments