SIOS SANless clusters

SIOS SANless clusters High-availability Machine Learning monitoring

  • Home
  • Products
    • SIOS DataKeeper for Windows
    • SIOS Protection Suite for Linux
  • News and Events
  • Clustering Simplified
  • Success Stories
  • Contact Us
  • English
  • 中文 (中国)
  • 中文 (台灣)
  • 한국어
  • Bahasa Indonesia
  • ไทย

Archives for February 2018

Clustering SQL Server 2012 On Windows Server 2012 with DataKeeper

February 9, 2018 by Jason Aw Leave a Comment

A Little Recap

In my previous post I walked through the process of building a 2-node cluster up to the point where we are ready to start clustering SQL Server 2012 on Windows Server 2012. If you have completed those steps, you are ready to move on and actually create your clustered application with my suggested SIOS Datakeeper Cluster Edition.

Next step, clustering SQL Server 2012

First up, we have SQL Server 2012. SQL Server 2012 cluster installation is pretty much identical to SQL 2008/2008 R2 cluster installations, so most of this will apply even if you are using SQL 2008/2008 R2. The terminology around SQL Server 2012 Clustering gets a little convoluted. You will hear mention of SQL Server AlwaysOn, which essentially could mean one of two different things: AlwaysOn Availability Groups or AlwaysOn Failover Cluster Instance. The confusion arises because both solutions require some level of integration with Windows Server Failover Clustering and it is even further confused by the fact that you can deploy a combination of AlwaysOn Availability Groups and AlwaysOn Failover Clustering, but that is a topic for another day!

Breaking It Down In Easy-To-Understand Terms

Essentially AlwaysOn Availability Groups is what used to be called Database Mirroring in SQL 2008 R2 and earlier. It has some new bells and whistles that overcome some of the limitations of earlier versions of database mirroring, so it is certainly worth checking it out. AlwaysOn Failover Cluster Instance is simply what used to be called a SQL Server Failover Cluster. This is the latest edition of the same clustering technology that has been available since early versions of SQL Server. One of the best new features of SQL Server 2012 AlwaysOn Failover Cluster Instance is the ability to have nodes in different subnets. This was a major limitation in earlier versions of SQL Server. In a previous blog entry I discussed some of the limitations of AlwaysOn Availability Groups, you should check that out before you make any decisions on which technology to deploy.

Let’s Start

With that said, this article is going to focus on the Step-by-Step instructions on deploying a SQL Server 2012 AlwaysOn Failover Cluster Instance.

Step 1

Make sure your cluster storage is ready. If you followed the instructions in my previous post, you will know that instead of a shared disk resource, we are going to use a replicated disk resource using the 3rd party software DataKeeper Cluster Edition. If you are using shared storage and have added the storage than you can skip right to Step 2 where we begin the SQL install. Otherwise, follow the steps below to configure the software to replicate the local disks for use in a SQL cluster.

Configuring DataKeeper Cluster Edition

  1. Install and configure DataKeeper Cluster Edition
    1. Run DK Setup
      Clustering SQL server 2012 with DataKeeper
    2. Go through the entire installation process selecting all of the default values.
      Clustering SQL server 2012 with DataKeeper
      Clustering SQL server 2012 with DataKeeper
      Clustering SQL server 2012 with DataKeeper
      Clustering SQL server 2012 with DataKeeper
      Clustering SQL server 2012 with DataKeeper
      Clustering SQL server 2012 with DataKeeper
      Clustering SQL server 2012 with DataKeeper
      Clustering SQL server 2012 with DataKeeper
      Clustering SQL server 2012 with DataKeeper
    3. Restart the computer after the installation completes as prompted and repeat the process on the SECONDARY server
    4. Launch the DataKeeper UI on PRIMARY and click Connect to Server. Connect to PRIMARY and then connect to SECONDARY
      Clustering SQL server 2012 with DataKeeper
      Clustering SQL server 2012 with DataKeeperClustering SQL server 2012 with DataKeeper
    5. Click on Create Job and walk through the Create Job wizard to create a mirror of the E drive
      Clustering SQL server 2012 with DataKeeper
      Clustering SQL server 2012 with DataKeeper
      Choose the source volume of the mirror and the IP address of the NIC that will carry the replication traffic.
      Clustering SQL server 2012 with DataKeeper
      Choose the target of the mirror and click Next
      Clustering SQL server 2012 with DataKeeper
      Here you will choose your mirror options:
      Compression – only enable for replication across a WAN
      Asynchronous – choose this for all WAN replication
      Synchronous – this is ideal for LAN replication
      Maximum bandwidth – used in WAN replication as a way to put a cap on the amount of bandwidth replication is allowed to use. Generally it should be left on 0, however for initial mirror creation you may want to limit the bandwidth so replication does not use all available bandwidth to do the initial synchronization
      Clustering SQL server 2012 with DataKeeper
      Once you click Done the mirror will be created.
      Clustering SQL server 2012 with DataKeeper
      Once the mirror is created you will be prompted to register the volume in Windows Server Failover Clustering (WSFC). Click Yes and a new DataKeeper Volume Resource will be registered in Available Storage (see picture in Step 2).
      Clustering SQL server 2012 with DataKeeper

Step 2

We are going to begin the installation of SQL Server 2012 on the first cluster node.

  1. Before we begin, make sure your storage appears in Failover Cluster Manager and is assigned to the Available Storage group as shown below
    Clustering SQL server 2012 with DataKeeper
  2. At this point we are going to launch the SQL Server 2012 setup and go to the Installation Tab and click New SQL Server failover cluster installation
    Clustering SQL server 2012 with DataKeeper
  3. Step through the installation as shown in the following screen shots.
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    The following error is expected if your servers are not connected to the internet. If you are connected to the internet you should go ahead and accept the updates it finds.
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    For Service Account best practices read the following: http://msdn.microsoft.com/en-us/library/ms143504.aspxFor our lab purposes I am just using the Administrator account
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Before you click next, click on the Data Directories tab and change the location of tempdb. With Windows Server 2012 tempdb no longer has to reside on the cluster storage. In our example we are moving tempdb to the C drive to avoid replicating unnecessary data.Clustering SQL server 2012 with DataKeeperClustering SQL server 2012 with DataKeeper

    At this point you will need to make sure to create the same tempdb directory on the SECONDARY server as advised by the warning.

    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper

    Congratulations, the 1st cluster node has been installed.

We are now ready to install SQL on the second node of the cluster.

  1. Go to the SECONDARY server and launch the SQL Server 2012 Setup and follow the wizard as shown in the following screen shots, starting with clicking on Add node to a SQL Server failover cluster.
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    The following error is expected if your servers are not connected to the internet. If you are connected to the internet you should go ahead and accept the updates it finds.
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
    Clustering SQL server 2012 with DataKeeper
  1. Congratulations – you have built a 2-node SQL Server 2012 AlwaysOn Failover Cluster Instance. Open up Failover Cluster Manager and you should see something that looks like this.Clustering SQL server 2012 with DataKeeperThis article “clustering SQL Server 2012 in a Windows Server 2012 cluster” was meant to be just a quick run through on how to install SQL 2012 in a Windows Server 2012 cluster. For additional reading start here and let Google be your friend!

Reproduced with permission from https://clusteringformeremortals.com/2013/01/05/clustering-sql-server-2012-on-windows-server-2012-step-by-step/

Filed Under: Clustering Simplified, Datakeeper Tagged With: AlwaysOn Availability Groups, DataKeeper, SIOS DataKeeper Cluster Edition, Windows Server 2012

Clustering Windows Server 2012 Step-By-Step

February 8, 2018 by Jason Aw Leave a Comment

Basic Steps Of Any Cluster

This article is the first in a series of articles on Clustering Windows Server 2012. This first article covers the basics first steps of any cluster, regardless of whether you are clustering Hyper-V, SQL Server Failover Clusters, File Servers, iSCSI Target Server or others. Future articles will cover more detailed instructions for each cluster resource type, but the following information is applicable to ALL clusters.

I’m assuming you know a little bit about clusters and why you would want to build one, so I won’t go into those details in this particular post. I also assume you are familiar with Windows Server 2012 and basic things like DNS, AD, etc. It is also worth noting that in Windows Server 2012 failover clustering comes with every edition, unlike Windows Server 2008 R2 and earlier where failover clustering was only included in Enterprise Edition and above.

Focus On Basic 2-Node Cluster

This particular series will focus on a basic 2-node cluster, where we have two servers (named PRIMARY and SECONDARY) running Windows Server 2012 in a Windows Server 2012 Domain (domain controller named DC). It also assumes that PRIMARY and SECONDARY can communicate with each other over two network connections I have labeled PUBLIC and PRIVATE. In production scenarios these network connections should run through entirely different network gear (switches, routers, etc) to eliminate any single point of failure.

Let’s Start! Clustering Windows Server 2012, here we go!

This series will be written in a very basic, step-by-step style that walks you through the process in an ordered list with basic instructions and plenty of screen shots to help illustrate the procedure where needed. So let’s begin at the beginning…

  1. Add the Failover Clustering Feature on all of the servers you want to add to the cluster
    1. Open the Server Manager Dashboard (this 1st step will need to be completed on both PRIMARY and SECONDARY)
    2. Click on Add roles and features
    3. Clustering Windows Server 2012 Step-By-StepChoose Role-based or feature-based installation
    4. Clustering Windows Server 2012 Step-By-StepChoose the server on which you wish to enable the failover cluster feature
      Clustering Windows Server 2012 Step-By-Step
    5. Skip over the Server Roles page
      Clustering Windows Server 2012 Step-By-Step
    6. On the Features page select Failover Clustering and click Next and then confirm the installation
      Clustering Windows Server 2012 Step-By-Step
  2. Before we start configuring the cluster, we need to consider what kind of storage the cluster will use. Traditionally clusters will use some sort of SAN, but with Windows 2012 not all clusters will use a SAN. For instance, if you are building a cluster to support SQL Server AlwaysOn Availability Groups your storage will be replicated by SQL Server, eliminating the need for a SAN. Also, with SMB 3.0 being support as cluster storage for Hyper-V and SQL Server you may not have a traditional SAN for storage. And let’s not forget clustered Storage Spaces with shared SAS drives is also a possibility in Windows Server 2012. In addition to the options mentioned above, you also can use local disks and 3rd party host based replication solutions like DataKeeper Cluster Edition which is an excellent alternative which I blog about pretty frequently.For the purposes of this post to share about Clustering Windows Server 2012 , I am going to assume you have no shared storage. However, if you do have shared storage at this point you should configure you storage such that you have LUN(s) carved out and shared with each of the cluster nodes with one LUN being used as a disk witness and the remaining LUNs can be used for the application which you want to cluster. In lieu of a disk witness for our quorum, I am going to use a node and file share witness quorum type which I will explain later.
  3. Now that Failover Clustering is enabled on each server, you can open the Failover Cluster Manager on your PRIMARY server. The first thing we will want to do is to run “Validate Configuration” so we can identify any potential issues before we begin. Click on Validate ClusterClustering Windows Server 2012 Step-By-Step
  4. Step through the Validate a Configuration Wizard as shown in the following steps.
    1. Select the servers you want to cluster
      Clustering Windows Server 2012 Step-By-Step
    2. Run all tests (depending on what roles you have installed on the servers you may get more or less tests. For instance, if Hyper-V is enabled there are new Hyper-V specific tests for clusters)
      Clustering Windows Server 2012 Step-By-Step
    3. Assuming your cluster “passed” validation you should have a report that looks similar to mine. You will notice that my report contains “warnings” but no errors. It is important for you to view the report and understand what warnings might be present, but you as long as you understand the warnings and they make sense for your particular environment you can move on. If you validation “failed”, you MUST fix the failures before moving on. Click View Report to view the report
      Clustering Windows Server 2012 Step-By-Step
    4. You will see all of my warnings are related to storage, so I am not concerned since I have not configured any shared storage, so I would expect some of these thests to produce warnings.
      Clustering Windows Server 2012 Step-By-Step

 

  1. Once Validation completes without any errors, you will automatically be thrown into the Create Cluster Wizard. Walk through this wizard as shown below to create your basic cluster.
    1. In this first screen you will choose a name for your cluster and pick an IP address that will be associated with this name in DNS. This name is just the name used to manage your cluster – this is NOT the name that your clients will use to connect to the clustered resource(s) you will eventually create. Once you create this access point a new computer object will be created in AD with this name and a DNS A record will be created with this name and IP address.
      Clustering Windows Server 2012 Step-By-Step
    2. On the confirmation screen you will see the name and IP address you selected. You will also see an option which is new with Windows Server 2012 failover clustering…”Add all eligible storage to the cluster”. Personally I’m not sure why this is selected by default, as this option can really confuse things. By default, this selection will add all shared storage (if you have it configured) to the cluster, but I have also seen it add just local, non-shared disks, to the cluster as well. I suppose they want to make it easy to support symmetric storage, but generally any host based or array based replication solutions are going to have some pretty specific instructions on how to add symmetric storage to the cluster and generally this option to add all disks to the cluster is more of a hindrance than a help when it comes to asymmetric storage. For our case, since I have no shared storage configured and I don’t want the cluster adding any local disks to the cluster for me automatically I have unchecked the Add all eligible storage to the cluster option.Clustering Windows Server 2012 Step-By-Step
    3. After you click next you will see that the cluster has finished the creation process, but there may be some warnings. In our case the warnings are probably related to the quorum configuration which we will take care of in the next step. Click View Report to check out any warnings.
      Clustering Windows Server 2012 Step-By-Step
      You see that the warning is telling use to change the quorum type.
      Clustering Windows Server 2012 Step-By-Step
  2. Because we have no shared storage, we will not be using a Node and Disk Majority quorum as suggested. Instead, we will use and Node and File Share Majority quorum. The following steps will help us configure the Node and File Majority Quorum
    1. A File Share Witness needs to be configured on a server that is not part of the cluster. A file share witness is a basic file share that the cluster computer name (MYCLUSTER in our case) has read/write access. The first step involves creating this file share. In our example, we are going to create a file share on our DC and give MYCLUSTER read/write access to it.
    2. The file share does not need to reside on a Windows 2012 server, but it does need to be on a Windows Server in the same domain as the cluster. The important thing to remember is that the cluster computer name that we created needs read/write access at both the share level and NTFS level. The following are some screen shots that walk you through this process on the DC server which is running Windows Server 2012 in my lab.
      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step
      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step
      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step
      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step

      Clustering Windows Server 2012 Step-By-Step

    3. Now that we have the file share created on DC, we will go back to PRIMARY and use the Failover Cluster Manager to change the quorum type as shown in the following steps.
      Clustering Windows Server 2012 Step-By-Step
      Clustering Windows Server 2012 Step-By-Step
      Clustering Windows Server 2012 Step-By-Step
      Clustering Windows Server 2012 Step-By-Step
      Clustering Windows Server 2012 Step-By-Step
      Clustering Windows Server 2012 Step-By-Step
      If by chance this wizard fails, it is most likely related to the permissions on the file share. Make sure you give the cluster computer name read/write permissions at BOTH the file share and security (NTFS) level and try again.
  3. You now have a basic 2-node cluster and are ready to move on to the next step of series Clustering Windows Server 2012 which is creating your cluster resources. I will be publishing a series of articles on how to cluster different resources, starting with SQL 2012 in my next post.

Reproduced with permission from https://clusteringformeremortals.com/2012/12/31/windows-server-2012-clustering-step-by-step/

Filed Under: Clustering Simplified, Datakeeper Tagged With: Clustering, clustering windows server, failover, Windows Server 2012

Datakeeper Cluster Edition 7.5 Now Support Windows Server 2012

February 7, 2018 by Jason Aw Leave a Comment

Benefits Of Using DataKeeper Cluster Edition

Great news for you Windows Server 2012 early adopters – you can now use DataKeeper Cluster Edition with Windows Server 2012. I’ll be posting some Windows Server 2012 Step-by-Step articles before the end of the year and will be sure to include some multisite cluster examples as well. In the meantime, if you want to build clusters based on Windows Server 2012 and want to eliminate shared storage as a single point of failure or you want to stretch your cluster across geographic locations you can do that with DataKeeper Cluster Edition v7.5.

Reproduced with permission from https://clusteringformeremortals.com/2012/12/19/datakeeper-cluster-edition-7-5-now-support-windows-server-2012/

Filed Under: Clustering Simplified, Datakeeper Tagged With: DataKeeper, DataKeeper Cluster Edition, Windows Server 2012

No More Free Google Apps

February 7, 2018 by Jason Aw Leave a Comment

Free Google Apps – A Great Intro Before Purchase

http://googleenterprise.blogspot.com/2012/12/changes-to-google-apps-for-businesses.html

I’m glad I got Boy Scout Troop 20 registered under the deadline. Free Google Apps was a great intro to the product for me and I looked at it as a gateway “drug” that gave me enough of a look to consider the premium version for any “serious” cloud based business operation, i.e., not a Boy Scout Troop.

Is The Subscription Worth It?

While $50/year per user is not expensive, it certainly can be a show stopper for many small non-profit organizations who may have otherwise been potential customers. So the question is will Microsoft take advantage of this opening to gain market share? If so, I know where I will be deploying my next cloud based small business site.

Reproduced with permission from https://clusteringformeremortals.com/2012/12/10/no-more-free-google-apps-googleapps-azure/

Filed Under: Clustering Simplified Tagged With: Google, google apps, Microsoft

Alwayson Availability Groups A Viable Alternative To Failover Clusters?

February 7, 2018 by Jason Aw Leave a Comment

Is Alwayson Availability Groups A Viable Alternative To Alwayson Failover Clusters In The Public Cloud?

I recently read an article entitled SQL Server 2012 AlwaysOn: High Availability database for cloud data centers where the author John Joyner makes a case for using AlwaysOn Availability Groups for SQL Server high availability in the cloud. I have been investigating AlwaysOn Availability Groups since it was available in pre-release versions of SQL Server 2012. While it certainly has some valid uses (mostly in disaster recovery configurations), saying that it is a “new way to achieve HA SQL” glosses over many of the issues that make deploying AlwaysOn Availability Groups as a replacement for failover clusters simply not a viable option in many cases.

My Response

In a response I wrote to the article I proposed that an AlwaysOn Multisite Clustering using the host based replication solution DataKeeper Cluster Edition is a much better alternative and I went ahead and explained why..

My original response to the article seems to have been deleted, so I decided to repost my response to the original article below:

There are a few things to consider with AlwaysOn Availability Groups. As you mention, “Microsoft announced support for some System Center 2012 SP1 applications to work with SQL AlwaysOn”, meaning that there are still applications that do not support AlwaysOn. In fact, there are a LOT of applications that do not support AlwaysOn Availability Groups, including any applications that use distributed transactions. And what about the other limitations, like not being able to keep MSDB, Master and other databases in sync? I blog about these limitations here.

https://clusteringformeremortals.com/2012/11/09/how-to-overcome-the-limitations-of-sql-server-alwayson-availability-groups-sqlpass/

I agree that SQL HA is important, however, the only way to get “High Availability” (meaning automatic recovery in the event of a failure) with AlwaysOn Availability Groups is by using synchronous mirroring. At PASS Summitt in Seattle earlier this month I sat in many different presentations on AlwaysOn and almost without fail the presenters talked about AlwaysOn in an asynchronous configuration. The reason being is that AlwaysOn synchronous replication has a SIGNIFICANT impact on the performance of your application. I have personally measured up to a 68% performance penalty with AlwaysOn Synchronous mirroring, and that was across a dedicated 10 Gbps LAN! I blog about this result here

Unfortunately, in an asynchronous configuration you give up automatic failover, so you really are not getting HA, you are getting data protection, but certainly not the same RTO as you can expect from a traditional SQL failover cluster.

And then finally there is the cost to consider. SQL Server 2012 Enterprise is nothing to sneeze at. If you want to build a 2-node cluster and take advantage of readable secondaries and you are using a 2-socket, 16-core servers you are looking at shelling out close to $220k for SQL Server 2012 Enterprise licenses. I broke down the associated cost in my blog article here.

Don’t get me wrong, SQL Server 2012 AlwaysOn Availability Groups can solve many problems, but I would not categorize the asynchronous configuration required in most cloud deployments as an HA alternative. Many people are overlooking the other “AlwaysOn”, AlwaysOn Failover Clusters. New features of SQL Server AlwaysOn Failover Clusters, including enhanced support for cross subnet multisite clusters, will give you a true HA solution and overcomes all of the limitations I describe above. Of course in a pure cloud solution you may not be able to integrate with array based replication to support multisite clusters, but you can always use host based replication solutions such as SteelEye DataKeeper Cluster Edition to build multisite clusters in public or private clouds and in your own physical data center and you can do this with SQL Server 2008 through 2012 AND it works on SQL Server Standard edition as well as Enterprise.

Have you done any testing with AlwaysOn Availability Groups in a HA configuration? If so I’d be curious to know if you measured the overhead associated with synchronous replication in your environment.

Reproduced with permission from https://clusteringformeremortals.com/2012/11/27/is-alwayson-availability-groups-a-viable-alternative-to-alwayson-failover-clusters-in-the-public-cloud/

Filed Under: Clustering Simplified, Datakeeper Tagged With: AlwaysOn Availability Groups, Alwayson Failover Clusters, High Availability, SIOS DataKeeper Cluster Edition, SQL Server 2012

  • « Previous Page
  • 1
  • …
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • Next Page »

Recent Posts

  • Streamlining External Communication for Emergency Procedures
  • Avoiding the Disaster You Don’t See Coming: Building a Resilient DR Plan
  • The Best Rolling Upgrade Strategy to Enhance Business Continuity
  • How to Patch Without the Pause: Near-Zero Downtime with HA
  • SIOS LifeKeeper Demo: How Rolling Updates and Failover Protect PostgreSQL in AWS

Most Popular Posts

Maximise replication performance for Linux Clustering with Fusion-io
Failover Clustering with VMware High Availability
create A 2-Node MySQL Cluster Without Shared Storage
create A 2-Node MySQL Cluster Without Shared Storage
SAP for High Availability Solutions For Linux
Bandwidth To Support Real-Time Replication
The Availability Equation – High Availability Solutions.jpg
Choosing Platforms To Replicate Data - Host-Based Or Storage-Based?
Guide To Connect To An iSCSI Target Using Open-iSCSI Initiator Software
Best Practices to Eliminate SPoF In Cluster Architecture
Step-By-Step How To Configure A Linux Failover Cluster In Microsoft Azure IaaS Without Shared Storage azure sanless
Take Action Before SQL Server 20082008 R2 Support Expires
How To Cluster MaxDB On Windows In The Cloud

Join Our Mailing List

Copyright © 2025 · Enterprise Pro Theme on Genesis Framework · WordPress · Log in