I recently installed a new Ec2 instance and setup the system for a web service. At some point, I rebooted the instance and noticed that I could not connect to the web service via the Public IP address assigned to it. Upon investigation I discovered that the public DNS address had changed hence service not accessible. To avoid this in future, Amazon has a built in feature to allow one to associate a static DNS IP address to an Instance so in the event of instance reboot, it does not get assigned a new DNS address but rather maintains the previously assigned address.
In this post, I will be showing you how to spin-up a Windows Server machine on Amazon Elastic Compute Cloud (EC2). This post will get you started on how to use Amazon Elastic Compute Cloud (Amazon EC2) Windows instances. Step 1: Launch Instance – Sign into the AWS Management Console at https://console.aws.amazon.com and click on EC2 – Click on ‘Launch Instance’ – Select ‘Quick Launch Wizard’ → Enter Instance Name → Select your Public/Private key pairs (Checkout my post on how to create a key pair) → Scroll down and click on ‘Microsoft Windows Server 2012 Base‘ which is the base image I will be using for this post → Click Continue – Review your settings → then click Launch to launch the instance Note: The default security group created authorizes all IP addresses to access your instance over the specified ports (i.
In this post I will work you through on how to add new disk as a resource and dependency to an existing cluster group. Key requirement will be to ensure that a new disk/LUN had been provisioned and added as new drives to the SQL servers. Also ensure that the disk is formatted with the appropriate Allocation Unit Size. Refer to this Post for more details. Installation Steps – Log in to the active cluster node - Open the Failover Cluster Manager - Navigate down to Storage - Right-click on Storage and click Add a disk – On Add Disks to a Cluster - Ensure the new disk is selected - click OK – The cluster manager will add the new disk and bring it online – When the disk is added, you will notice under Available Storage the newly added disk.
This post will be focused on how to add additional SQL instance to an existing SQL Server 2008 R2 Cluster. At first I was a little confused about the concept of Active/Active and Active/Passive and its relationship with SQL failover clustering. In a multi failover cluster instances, these terms can be seen as ambiguous when used to describe the configuration of the SQL Server instances and the nodes they are running on.
In our quest to deliver a secured SQL Server 2008 R2 cluster solution, I will continue from my last post Part3 with the installation of SQL Server 2008 R2 SP1. Please note that when installing SQL server 2008 service pack in a cluster, this needs to be installed on the Passive node at any point in time. If this is installed on the Active node, then SQL will require a reboot thereby defeating the purpose of clustering.