Top 10 things all new Simplivity admins must know

I'd like to comment on most of these points:

1: This is b.s. or at least it was in my experience. We bought CN3000s which were advertised in all documentation as having 412GB of RAM. They actually had 512, with 100 being reserved for the OVC. This sounds like a demo unit that wasn't properly communicated to the reviewer.

2: The OVC VM is physically tied to its host ESXi server and can't be vMotioned off. That's why putting the server into Maintenance Mode requires shutting down the OVC manually. It's a function of how vSphere works.

3 and 4: are true and are due solely (from what I hear) due to the requirement to run the Arbiter (a Windows app) on the same server as vCenter. Last spring I heard a rumor that they were working on removing this requirement, but haven't heard anything since.

5: Is this still true? I could have sworn that our original vCenter install was made using simple mode (as it was our only server), and yet installing the second vCenter server and linking it to the original was a piece of cake.

6: The biggest bummer for me regarding SimpliVity clones is that they're made on the same host as the original, because that's where the data resides. This is arguably a bigger issue when you have 10 servers than when you have 2. It would be nice if the GUI allowed you to specify a server to stand it up on as well as the SimpliVity datastore, with the caveat that your clone operation will take quite a bit longer than 5 seconds if you want it to reside on a different host.

8: I saw a technical demo of the SimpliVity management pieces being run from the Web client at VMworld. I suspect that this will be released with version 3.1 in 2016, though I prefer the vSphere client myself anyway.

9: I'm glad SimpliVity sells the cloud connector for this reason. We haven't jumped on it yet, but are considering replicating to AWS as a long-term storage option.

10: Speaking as someone who's spent the 5 of the last 8 days upgrading one OVC per day with support, this is unfortunately true still. They're slowly moving towards self-service upgrades, but it's not here yet.

Is it a requirement to have vCenter running in both the Production and the DR/recovery sites? Or would I be able to have my production vCenter server replicated to DR and recover there when necessary?