The New RTFM

Most of you who come here know that I post A LOT about the #vCommunity. What you may not know is that I actually have a day job. Who would have thought? In between being a dad, and a husband, and a VMUG Leader in NYC, I’m also a Solutions Engineer for Zerto. I’ve been in this role for over a year and I love it. I really enjoy speaking to customers and learning different and innovative ways of doing things.

As part of this totally awesome gig, I get to talk to a lot of customers and prospective customers about their disaster recovery (DR) and business continuity (BC) plans and approaches. One of my favorite questions to ask is this:

“How many people went into IT to become a DR admin?”

I usually get crickets. Not because it’s a bad thing to be in BC/DR (I make a great living from it), but because it’s not a sexy job. It’s usually a task that gets dumped in your lap for legal or compliance reasons and it takes you away from the things that you WANT to do. It usually involved getting a whole bunch of different teams (Virtualization, Storage, Networking, DBAs, App/Dev, etc) involved and spending a few weeks (usually a few months) preparing for a test that is almost always done during a (holiday) weekend. Who the hell wants to work on the weekend? I sure don’t, that’s why I made the move to the vendor side but that’s a whole other story.

There’s one other component that I haven’t mentioned yet. Runbooks. Ugh. Just the thought of those things make me cringe. Who remembers or still uses those huge loose-leaf binders with hundreds of pages of step by step instructions that were written (and probably not updated) years ago. Once a year you would have to dust them off for instructions on how to recover your environment in the event of a disaster. Then you would have to go page by page with a bunch of other team members and hope that the system matches what is on the page.

You know what is really helpful with this kind of situation? The simple acronym RTFM. I come from the military and this acronym had a very simple meaning

READ

THE

F*ING

MANUAL

That however, is the old RTFM.

Since working at Zerto, I’ve come up with a new meaning.

.

.

.

.

.

.

.

RECOVER

TEST

FAILOVER

MOVE

 

These are some of the essential functions that any IT Resiliency Platform should be able to provide you. By performing these functions, you’ll ensure that your workloads are protected, your data is intact, and your processes are valid. Let’s take a quick look at each of these functions:

 

RECOVER

This is the ability to restore your data. It could be restoring, or as we like to say resuming your VMs or applications. Or it could mean restoring files or folders from a point in time before a disruption.

 

TEST

Testing is probably one of the most important but also most overlooked operations when it comes to IT Resilience. Testing is how you know with great confidence that your systems will work when you attempt to get them back up and running. It’s a way to recover your VMs or applications in practice before having to do the real thing.

 

FAILOVER

Failover is a misleading term. This is actually recovering your VMs or applications at the target site. Think of this as initiating your DR plan in a live scenario. If your production site becomes unavailable for whatever reason, this is how you recover your workloads and make your users happy again. Simply put, when you’re down, get yourself back up and running.

 

MOVE

Zerto has a function called Move VPG which provides you with Application Mobility by migrating a Virtual Protection Group (VPG) to another location. (NOTE: A VPG is comprised of the VMs you are protecting) This could be moving to another storage platform, or another datacenter, moving from one hypervisor to another or even moving to, from or between cloud providers.

 

In order to have a complete IT Resilience platform, I believe you need to be able to perform all of these functions simply and consistently. Stay tuned as I will dive into each operation a bit more and how Zerto specifically performs each function.

 

VMUG Whiteboard Meetings #VMUGWB

Recently, I was afforded the opportunity along with Mike Martino (@wildcard78), and Ariel Sanchez (@arielsanchezmor) to present on the latest VMUG Leader call. We were speaking about a topic near and dear to our hearts, that being Whiteboard Meetings. This is something that we started at the NYC VMUG with tremendous support from Niran Even-Chen (@NiranEC) and Prabhu Barathi (@prabhu_b) from VMware as well as Azarya Shaulov (@az_ny) from Touro College. Azarya was gracious enough to provide us with the space free of charge.

I’m sure that your next question must be, “What the heck is a Whiteboard Meeting?”. Well, I’m glad you asked.

This meeting is designed to be:

Picture3

  • An informal and intimate technical meeting of NYC VMUG members with an emphasis on the QUALITY of the content.
  • A place where we could get together and share ideas about technology, projects, issues and learn from one another on the best way to move forward.
  • An opportunity to get in front of a room and work on your presentation skills. Not everyone is comfortable with public speaking and this gives our members a judgement-free forum to do so. We’re here to encourage one another
  • A safe zone free of sponsors or being bombarded by sales guys (We love you sales guys, we just need a little space). We welcome anyone to these meetings no matter where you come from as long as you are there to share ideas in a positive manner.
  • Most importantly, it’s not about free food or giveaways or anything like that, it’s about geeks being geeks and embracing the vCommunity.

So, how did it start? To quote Ariel, “At a bar, of course!

Picture2

We were having a typical discussion about the VMUG Meeting we just had. You know what I’m talking about. After the meeting ends, there is that group of people that just can’t get enough and are super excited to talk to people who speak their language. They were just so blown away by the topic that they never want the discussion to end. Our conversation then morphed into how great the discussion we were having was. We said, “You know what? We should have more meetings like THIS!” In a nutshell, that’s how this idea began.

What’s next?

What do you need to get started with your own Whiteboard meetings?

Picture5

  • A (few) Whiteboard(s) and dry erase markers. Duh.
  • A space that can hold 12 to 15 people. We try to keep these meetings a little smaller so that everyone has the ability to participate. If you can use a classroom-type space, even better.
  • Local product experts who would like join is usually very valuable for members who are looking for answers and insight. Having local VCDXs, VCAP, VMUG Leaders, vExperts, etc. participate is very helpful.
  • Someone to break the ice (a VMUG Leader, typically) and some relevant topics to discuss. (Current Technologies, New Product Releases, Home Labs, Automation examples, etc.)
  • If there is money available in your budget, try to order some take out for the group. A couple of pizzas is usually sufficient.

 

What advice can I give you?

  • Invite people that you think would appreciate it. This doesn’t have to be limited to virtualization admins. Bring co-workers. I’ve personally brought one of my network architects out and now he’s more involved with virtualization than ever before.
  • Be outgoing. Don’t be afraid to make a mistake. Remember, this is a judgement free zone where we are all trying to improve.
  • Do not limit conversation to just VMware, these meetings are about technology in general. VMware is usually the focus but related technologies are often discussed. We’ve spoken about networking, Public Cloud, AD, Email, Backups & Replication, you name it, it’s probably come up in some form or fashion.
  • Try to capture the session to a blog post with pictures to help promote the individuals presenting on social media and future vExpert applications. That usually helps bring more people to future meetings. We post under the hashtag #VMUGWB.
  • Try to have breakout Whiteboard Meeting at UserCons, or sponsor-driven VMUG Meetings
  • Have topic focused Whiteboard Meetings. Have a meeting around NSX, vSAN, VMware Cloud on AWS, you can even poll your members for topics that they’d like to talk about. Try to get your local VMware SEs to attend as well. You may even be able to catch a traveling SME if they are in town.
  • If you have the ability to do a video conference or a WebEx of some sort, go for it. I’ve actually taken advantage of this myself after the birth of one of my kids.

Picture1

  • Try to really have an understanding of what people are looking to learn and why they are there. Make it as collaborative as possible. Try to bring in an expert on a particular subject if you keep hearing about it.
  • Keep the conversation going after the meeting ends. Go grab a beer and a bite afterward. Sometimes the shy ones that don’t get up and present will open up a bit more after a few cold ones.

With that said, I hope you try this out in your area. It tends to have a really positive impact on those who attend.

Here’s some feedback that we received from one of our attendees:

“The whiteboard sessions hosting by NYCVMUG community have been an excellent forum for engineering and architecture discussions.  Unlike larger conferences, the whiteboard sessions are small and each participant has an opportunity to present something – anything – to the room.

For myself, the WB sessions have been a great opportunity to accelerate VMware training, an opportunity to work through complex problems regarding production issues, lab infrastructures and vetting/sounding out future plans. 

Another big aspect for me personally is the ability to practice presenting in of itself.  Being small & unrelated to employers or vendors in combination with great community members, the sessions have help increase my overall confidence when standing before peers & colleagues.

Overall the WB sessions are a great experience. I look forward to attending more and seeing the concept grow beyond NYC.”

-Brendan Peterson (@petes_revenge)

I’m looking forward to hearing about Whiteboard Meetings all over the world. Hopefully, this catches fire and the vCommunity continues to grow.

If you have questions, we’re here to help. Feel free to reach out to any of us if you want more info. Our contact info is listed below. We can be reached through the vExpert Slack as well.

If you think that this could be helpful, let your local VMUG leaders know! We always announce these

A special thanks to Mike, Ariel, Niran, Prabhu, Azarya, Brendan and the whole NYC VMUG Whiteboard crew for building an awesome vCommunity and helping to make this such a success.