A tale of two products (don’t expect Dickens)

At Re:Invent and just after, AWS released several new products. Included in those were AWS FSx Windows and AWS Backup. Both of these products had a lot of interest for me, for various reasons, so I thought I’d give them a try. None of my experience was under work conditions, but the following are my experiences. Note: Both are only in a small number of regions, currently.

AWS FSx Windows

Pros:

  • Easy setup (by itself)
  • Fully compatible Windows file server
  • DFS support
  • Has backups
  • Works as expected

Cons:

  • Requires AWS Microsoft AD in each VPC
  • Can’t change file share size
  • Some features can only be changed from CLI
  • Throughput can only be changed through restore
  • Minimum share size is 300GB

First out of the box, and released at Re:Invent is AWS FSx Windows.… [Keep reading] “A tale of two products (don’t expect Dickens)”

Backups? Doesn’t Amazon handle that?

For many, the cloud is a magical place where servers just appear and your cloud provider looks after everything, or, if they at least have a concept of the servers, they just assume that the provider will also back them up. Lots of people never bothered to think about protection in a VMware environment, so why start now?

Unfortunately, while your cloud provider probably supplies the tools, you still need to do the configuration and management.… [Keep reading] “Backups? Doesn’t Amazon handle that?”

Disk Space Reporting through Lamba Functions- Windows servers

Solution Objective:

The solution provides detailed report related to hard disk space for all the Windows Ec2 instances in the AWS environment.

Requirements:

Mentioned below are the requirements the solution should be able to fulfil.

  • Gather information related to all mount points in all the Windows EC2 instances in the environment.
  • Able to generate cumulative report based on all instances in the environment.

3. Assumptions:

The following assumptions are considered

  • All the EC2 instances have SSM agent installed.
[Keep reading] “Disk Space Reporting through Lamba Functions- Windows servers”

IT Service Management (ITSM) & Operations – Overview of the Availability Management Process

Background

In many cases ITSM Availability Management Process is overlooked due to other frontline processes such as incident, problem and change management. I have provided a summary of this availability management process and significance below. I hope that the information is useful for your organisation in order to define and implement the process.
Objectives:

  • Availability management has to ensure that the delivered availability levels for all services comply with or exceed the agreed requirements in a cost-effective way and enables the business to satisfy its objectives.
[Keep reading] “IT Service Management (ITSM) & Operations – Overview of the Availability Management Process”

The Present [and Future] Landscape of Data Migrations

A rite of passage for the majority of us in the tech consultancy world is being a part of a medium to large scale data migration at some stage in our careers. No, I don’t mean dragging files from a PC to a USB drive, though this may have very well factored into the equation for some us. What I’m referencing is a planned piece of work where the objective is to move an entire data set from a legacy storage system to a target storage.… [Keep reading] “The Present [and Future] Landscape of Data Migrations”

Querying against an Azure SQL Database using Azure Automation Part 1

What if you wanted to leverage Azure automation to analyse database entries and send some statistics or even reports on a daily or weekly basis?
Well why would you want to do that?

  • On demand compute:
    • You may not have access to a physical server. Or your computer isn’t powerful enough to handle huge data processing. Or you would definitely do not want to wait in the office for the task to complete before leaving on a Friday evening.
[Keep reading] “Querying against an Azure SQL Database using Azure Automation Part 1”

Major Incident Management – Inputs and Outputs

Definition

A major incident is an incident that results in significant disruption to the business and demands a response beyond the routine incident management process.
The Major Incident Management Process applies globally to all Customers and includes Incidents resulting in a service outage.  This process is triggered by Incidents directly raised by Users or via referral from the Event Management Process, which are classified as Major Incidents in the Incident Management Process by the Service Desk.… [Keep reading] “Major Incident Management – Inputs and Outputs”

Cloud Operations Model and Project Stream – Considerations

Background

Cloud operations stream is responsible for designing and operation of the cloud model for the project and BAU activities. This stream is primarily responsible for people, process, tools and information. The model can change as the organisation’s requirements and type of business.  

Aspects Cloud Operations Model

Below is an example of key aspects that we need to consider when defining Cloud Operations Model.
aspects 2.jpg

Cloud Operations Stream  – High Level Approach

Below is an example model for how to track a cloud program operationally.… [Keep reading] “Cloud Operations Model and Project Stream – Considerations”

ITSM – Service Catalogue – Summary

Definition

  • The Service Catalogue represents a trusted record of the services provided by Information Technology (IT), its default capabilities, measures and primary means of access and provision.
  • It is the means by which we articulate WHAT we manage and measure. It is the hidden power of how we set the customer’s expectations and exceed them.
  • It can provide an essential medium for communication and coordination among IT and its customers, and should distinguish between Business Customers (the ones paying for the service) and End Users (the recipient of the service).
[Keep reading] “ITSM – Service Catalogue – Summary”

ITSM – Continual Service Improvement (CSI) – All you need to know

Why Continual Service Improvement (CSI) is Required?

  • The goal of Continual Service Improvement (CSI) is to align and realign IT Services to changing business needs by identifying and implementing improvements to the IT services that support Business Processes.
  • The perspective of CSI on improvement is the business perspective of service quality, even though CSI aims to improve process effectiveness, efficiency and cost effectiveness of the IT processes through the whole life-cycle.
  • To manage improvement, CSI should clearly define what should be controlled and measured.
[Keep reading] “ITSM – Continual Service Improvement (CSI) – All you need to know”