4 Cloud To-Dos Before Leaving on Vacation

Jul 30 2014 | by Eran Abramson

31 Flares Twitter 0 Facebook 0 LinkedIn 31 Email -- Filament.io 31 Flares ×

It’s inevitable! Your company’s cloud expert is bound to go on vacation sometime this summer. Wait! Before you start stressing, take a deep breath and realize – the show must go on. With a bit of pre-planning, you can set a few steps in motion to decrease any possibilities of peril and make sure deployment will function properly while Mr. Cloud Ninja takes a well earned break.

Pre-takeoff Checklist:

Let’s face it; no one knows and understands your cloud like the cloud expert running it day-in-and-day-out. As they constantly tend to it, they know all of the nuances of its configuration and deployment. They know what hiccups to expect, when, and are aware of possible storming skies forming before any others even catch a hint of any issues.

So how do you prepare?

1 – Contingency Plans:

While it is likely certain procedures are already in place, it is best to update them for common, and uncommon but possible disasters. Let’s call it contingency planning. Review and update best and worst case scenarios and each game plan for them. Consult with the cloud expert who knows how much and where the cloud can be pushed and document the best practices for each of the different possible scenarios.

2 – Alternate Backup:

Unless your IT changes their mind or delays their vacation, the optimal solution is to have a knowledgeable and capable backup alternate who gets trained by the cloud expert and can learn the duties, processes and procedures. This backup also enables the main cloud expert to have needed flexibility to do other projects, attend customer meetings, offsite business events, etc.

3- Alerts & Notifications:

To set the backup person up for success, a good idea is to introduce efficient alerts and notifications to get an early heads-up on warning signs before they become real problems. The alerts and notifications enable the alternate backup person to keep focus on key metrics and raise concerns and investigate if and when needed. This process will also provide useful peace-of-mind to the powers that be.

4 – Auto-pilot Tasks:

Any processes and tasks that may be automated and scheduled definitely should be. For example, if a resource goes down, another should be ready to immediately go up in its place. If a specific deployment isn’t running properly, it should be re-launched per each configuration, or if disk space is running low, additional storage should be waiting to be added, etc.

This allows the backup to focus on areas that cannot be automated, keeping track of critical areas which require much more attention.

הורד (2)Once your cloud IT ninja guy goes on vacation, steps must be taken to handle ongoing tasks and provision as issues arise. Thankfully, there are a growing number of cloud automation and optimization tools that can help out with much of this automation. Some of these tools, such as Cloudyn, won’t make the changes for you, but can assist with a wide array of customized alerts and notifications, continuous in-depth monitoring across the board to find and decrease inefficiencies, and provide actionable recommendations based on each company’s unique cloud usage footprint for improvement.

 

Login

Forgot Password?

No account yet? Register.

31 Flares Twitter 0 Facebook 0 LinkedIn 31 Email -- Filament.io 31 Flares ×