Shortly after VMware announced its EVO Rail initiative, whereby hardware partners could start delivering a very dense compute, storage, and networking solution within a wholly-contained appliance – I started exploring the data protection aspects of an EVO Rail solution. The nice folks in ESG’s video studio have produced a whole series on this … in two-minute increments.
In the earlier video capsules, we looked at the protection of EVO Rail systems in production. For part 6 in the series, let’s look at EVO RAIL as perhaps the ideal BC/DR infrastructure.
After all, it has everything you need for a second site … so why not drop one in an alternate location (or co-lo site) and start replicating to it? And for DRaaS providers, perhaps a self-contained EVO might be an interesting option over a shared infrastructure for some clients? Check out the video for more details:
Please feel free to check out the earlier installments in the series:
DP considerations for EVO Rail – part 1 – an overview of EVO RAIL and its data protection ramifications
DP considerations for EVO Rail – part 2 – VMware’s own data protection options
DP considerations for EVO Rail – part 3 – EMC’s EVO RAIL and its data protection possibilities
DP considerations for EVO Rail – part 4 – Dell’s EVO RAIL and its data protection possibilities
DP considerations for EVO Rail – part 5 – HP’s EVO RAIL and its data protection possibilities
In the next few weeks, I will be releasing the last of the seven segments … on channel partner considerations for EVO RAIL systems. As always, thanks for watching.
— jason
Originally posted on my personal self-managed blog while at ESG (TechnicalOptimist.com), reposted on DPM for archival reference. Broken links are likely due to ESG content being dropped between its acquisition by TechTarget and their acquisition by Omdia.