Marc Huppert


After using the Cohesity Virtual Edition very successful for several months, I decided to implement another one inside my second datacenter within my HomeLab / HomeDC.

I upgraded a Lenovo P50 notebook with a second SSD and a 4TB HDD. This tiny system has now 4 CPU Cores 2,7 GHz (8 Threads) , 32GB RAM, 2 x 256 GB SSDs, 1 x 4TB HDD and 1GbE. It only consumes 43W per hour.

I deployed Cohesity Virtual Edition with a medium size to it. Here are the specifications:

It will be the only VM onto this system, so I attached all 4 CPUs to it, 24 of my 32GB RAM, 200GB Flash based vmdk, a 3,5TB HDD vmdk and 1GbE. I named that VE Cohesity Remote.

My main Cohesity Virtual Edition is slightly bigger configured:

16 vCPUs (Host has 32 Threads), 64GB RAM with all configured active, 400GB FusionIO ioDrive2 based vmdk, 7TB HDD Raid 1 and 10GbE. My plan is to use the Cohesity Remote only for replication from my main Cohesity Virtual Edition. This scenario is not officially supported, but it works very well…. If you know me, I always like to do things that are not officially supported…. 😎

After the initial configuration of my new Cohesity Remote appliance, it was time to configure the replication.

You must setup the replication first on the master system. Simply click on Register Remote Cluster.

You must enter the connection information of the Remote System. You can configure things like Distribute Load (only applicable for the Cohesity HW appliances), Encryption, Outbound Compression and Data Transfer Limits. I have not configured Encryption and Transfer Limits within my environment. I just want to replicate data from my main datacenter to my second datacenter at my house.

Last step on the primary system is configuring the View Box Pairing. Simply choose the ViewBox from Cohesity Virtual Edition and from the Cohesity Remote System.

Now we need to do the same on the other side, as well.

Congratulations, now we have configured the replication setup between two sides….

Next step is to configure Protection Policies that uses this replication.

You can modify your existing policies with the Edit option.

I have not modified these settings, it works well for my requirements.

Here is the option to replicate the backup data to the remote site. I configured the replication “After Every Backup Run” and only after a successful completed backup run.

After a successful run of a Protection Job, you can see these jobs on the Cohesity system at your remote site. You have now all your backups within two places. You can perform a restore or a failback of these Protection Jobs on the remote system. Very nice and easy to setup.

Here is a view of my Cohesity Remote Dashboard. My replications consume right now 1,18 TB. I really love this solution. Great job, Cohesity!!!!