Posted by Andrea Mauro on June 7, 2017
Design a ROBO infrastructure. Part 4: HCI solutions

2-nodes hyperconverged solution

As written in the previous post, for ROBO scenario the most interesting HCI (Hyper-Converged Infrastructure) configuration is a two nodes configuration, considering that two nodes could be enough to run dozen VMs (or also more).

For this reason, not all hyperconverged solutions could be suitable for this case (for example Nutanix or Simplivity need at least 3 nodes). And is not simple scale down an enterprise solution to a small size, due to the architecture constraints.

Actually, there are some interesting products specific for HCI in ROBO scenario:

  • VMware Virtual SAN in a 2 nodes clusters
  • StarWind Virtual Storage Appliance
  • StorMagic SvSAN

StarWind Virtual SAN overall architecture

Learn More

Posted by Andrea Mauro on March 30, 2017
Design a ROBO infrastructure (Part 3): Infrastructure at remote office side

Design a ROBO scenario must match finally the reality of the customers’ needs, its constraints but also the type of workload and the possible availability solutions of them.

Logical design of a ROBO scenario

When can found the different type of approaches:

  • No server(s) at
  • Few servers (that maybe can fail)
  • Some servers with “relaxed” availability requirements
  • Some servers with reasonable availability

Let’s analyze each of them.

Design a ROBO scenario must match finally the reality of the customers’ needs, its constraints but also the type of workload and the possible availability solutions of them.

Hyper-Converged Infrastructure structure

Learn More

Posted by Andrea Mauro on February 24, 2017
Design a ROBO infrastructure (Part 2): Design areas and technologies

In the previous post, we have explained and described business requirements and constraints in order to support design and implementation decisions suited for mission-critical applications, considering also how risk can affect design decisions.

Now we will match the following technology aspects to satisfy design requirements:

  • Availability
  • Manageability
  • Performance and scaling
  • Recoverability
  • Security
  • Risk and budget management

ROBO Design areas and technologies

Learn More

Posted by Andrea Mauro on January 25, 2017
Design a ROBO (Part 1): Introduction and high-level design

What is a ROBO scenario?

A Remote Office / Branch Office (ROBO) is an office located in a different site or a remote geographical area from another office (usually the headquarter or the main office). Several organizations have one (or more) main office, as well as remote offices in another city, country or continent.

Many organizations today have in each remote office some local IT infrastructure, usually for data locality, but also for service local services.

ROBO scenario

Learn More

Posted by Mike Preston on January 17, 2017
PowerShell ROBO

Picture this – you are a systems administrator working at a major banking institution.   The security team walks into your office and lets you know that a major update needs to be applied to all of the servers within the institution – not a problem for most organizations, but in the case of a bank, you could have hundreds if not thousands of remote and branch offices.  Sure, we can write scripts to copy out the update files and even execute them remotely from our head office – but the problem most ROBO scenarios are ever-changing – with new offices being created and others closing down all the time.  Keeping track of server names, IP schemes, etc. can be quite a time-consuming process.  Naturally, we want the same updates, patches, and fixes to be deployed everywhere, in the same manner, in order to provide consistency – so having this up to date list available when we need it is key to driving success within our environment.

cmdlet run

Learn More