#VMWare with MS Failover Cluster | Explore Tumblr posts and blogs

davesinfo-techspot · 6 years ago

Text

Setting up Always On SQL Clustering Group, with Microsoft Server 2016 and VMWare

Setting up clusters in Windows Server 2016 has become so easy. However; When integrating it with other environments, like VMWare, and AO SQL Clustering. It can get quite Tricky. First we want to setup our environment in VSphere. Next we will setup Windows Server 2016 with Failover Clustering. Then we’ll make sure to make some adjustments to DNS. Finally, We will setup AlwaysOn SQL Clustering.

Please make sure you have .NET Framework 3.5.1 or greater on the servers. Then We will need to create 2 VMs with 3 drives each. Then we will need to make sure that the drives are online, and available from other locations. However one main aspect that I had overlooked was that the Virtual Disks have to be created Eager Zero Thick not Lazy Zero Thick. I made the heinous mistake of using Lazy Zero Thick, and then could not understand why I was having so many problems.

Note: When creating virtual disks with Eager Zero Thick, it does take longer than using the faster Lazy Zero Thick option. Eager Zero Thick Disks allocates the space for the virtual disk, then zeros it all out unlike the Lazy Zero Thick which only allocates the space.

You also generally wouldn’t use Eager Zero Thick except for Microsoft clustering and Oracle programs. Once the disks are created we are reading to install Windows Server 2016.

Install either Datacenter edition or Standard edition. For this example we’ll use the standard edition. Install all the Microsoft Windows feature updates and verify that you have already allocated all the resources needed. Check that the additional Virtual Disks are available, and make sure you install the Failover Cluster feature. You may want to reboot after the feature is installed, if you have not done so. Once you installed the feature go to the Failover Cluster Manager and prepare to create the cluster. If this is a two node cluster be sure to add a Witness Server or Desktop. Once this is created and validated, go to your computer manager and verify that the virtual disks are online and initialized. Next, you will want to configure the cluster quorum settings. I created a separate server for this quorum and configured a File share witness.

Now, make sure you can access these from another computer on the secured network. You will have to setup a Host A record round robin DNS situation, where you give a specified name the 2 failover cluster nodes IP adresses in the Host address. Example: if the nodes had up address of 192.168.1.43 and 192.168.1.44. Then the two Host records you would need to create are AOSqlServer -> 192.168.1.43 and AOSqlServer -> 192.169.1.44

Finally, We will enable AlwaysOn Availability Groups on SQL Server 2016.

After Installing SQL Server 2012 or 2014 Enterprise edition on all the replicas. Please install it on as a stand-alone instance, and then we will configure SQL Server. Once you expand SQL Server Network Configuration node, and click on Protocols for MSSQLServer, you will see the TCP/IP dialog box on the right panel. Right click on the TCP/IP entry and select Enable.

In SQL Server Configuration Manager, right click on SQL Server Services to open the Properties dialog box. Navigate to the AlwaysOn High Availability tab to select the “Enable AlwaysOn Availability Groups.

Now we must configure the login accounts and the replicas that will need read write privileges.

First verify that your SQL Service Account is there and is a domain account, not a local machine account. Now login through SQL Management Studio (SSMS). Add you SQL Service account to the Administrators group on each replica (via computer management). Then allow connect permissions to the SQL Service account through SSMS: Right click on the SQL Service login to open the Properties dialog box. On each replica navigate to the Securables page and make sure Connect SQL Grant box is checked and allow remote connections. You can do this by using SSMS in the instance properties or by using sp_configure.

EXEC sp_configure ‘remote access’, 1;

RECONFIGURE;

Now we will create the file share through the Server Manager that the SQL Service account, and the replicas can access. The File is for the initial backup/restore process that happens to the databases when you join the AlwaysOn group during setup.

Last thing is to install the AlwaysOn Availability group. Once you’s ensured that full backups have been created, and all databases are in Full recovery mode, you will have to remove these databases from the tlog backup maintenece during the installation of Always on (you can always add them back). It could cause errors with both tlogs backing up while AlwaysOn is being created.

On you primary, open SSMS and expand the AlwaysOn High Availablity folder. Right click on the Availability Groups and select New Availability Group Wizard.

Select only the databases you want to include in the AlwaysOn group.

Next to the databases you will see the status with a blue link. If you see "Meets Prerequisites” it will signify that these databases are included in your group. If it does not say "Meets Prerequisites”, then click on the link to see more details on what needs to be corrected.

Now, you will specify and Add the Replicas. You will need to specify if you want Automatic or Manual Failover, Synchronous or Asynchronous Data Replication, and the type of Connections you are allowing to the end users.

Be sure to view the troubleshooting page if you have any issues:

http://blogs.msdn.com/b/alwaysonpro/archive/2013/12/09/trouble-shoot-error.aspx

The backup preferences tab will assist in choosing the type of backup and to prioritize the replica backups.

In the Listener tab, you will create an availability group listener button, Enter the string DNS name, enter port 1433 and enter the IP address for your listener, which should be an unused IP address on the network.

Next, you will Select Initial Data Synchronization page, join the databases to the Always on group, then verify the Full option is selected for using File Shares. For large databases select Join or Skip to restore the databases to the secondary replica. We will use Full for now. Last thing to do here is remember the SQL Service accounts and set that all replicas have read/write permissions to the file Share or it will not work.

Run the Validation checks, and make sure it the results are successful.

That is it, once you get that done you should have High availability and AlwaysOn SQL Server. I hope you’ve enjoyed this instructional blog. Please come back and visit us to see other projects.

#Always On SQL Server #High Availability SQL #Failover Cluster #SQL Failover Cluster #VMWare Failover Cluster #VMWare with MS Failover Cluster #VMWare with MSFC #AlwaysOn SQL

1 note · View note

tayfundeger · 5 years ago

Text

New Post has been published on

New Post has been published on https://www.tayfundeger.com/clustered-vmdk.html

Clustered VMDK

Merhaba,

Clustered VMDK isimli bu yazımda sizlere vSphere 7 ile birlikte gelen yeni bir özellikten bahsedeceğim. VMware, yeni vSphere sürümleri ile birlikte özellikle Windows Server Failover Cluster sistemlerde yenilikler yapmaya devam ediyor.

vSphere 7 ile birlikte storage tarafında önemli değişliklikler yapıldı. Bunları aralıklar ile yazmaya devam edeceğim. vSphere 7 ile birlikte VMware, virtual disk yani VMDK düzeyinde bazı değişiklikler yaptı. SCSI-3 Persistent Reservation yani SCSI-3 PR desteği geldi. Bu yeni bir terim bundan dolayı açıklamam gerekiyor.

SCSI-3 PR Nedir?

Aslında bunu ilk olarak VSAN 6.7 Update 3 ‘de duymuştuk. Daha önceki makalelerimi inceleyenler bunu görecektir. Windows Server Failover Cluster yani WSFC, cluster bir disk kaynağına erişimi koordine etmek için SCSI-3 PR komutlarını kullanır. Bu komutlar (SCSI Persistent Reserve Out ve Persistent Reserve IN), datastore’da bu özelliğin support edildiğini varsayılarak VSCSI katmanında işlenmeye başlar. Cluster VMDK’ları barındırmak için yapılandırılan bir datastore’lara bir clusteredVMDK datastore adı verilir.

Clustered VMDK

Bunun amacı aslında RDM disk’in gereksinimi azaltmaktır. VMFS datastore üzerinde bulunan virutal machine’lerde eğer shared disk kullanırsanız Windows Failover Cluster kullanabilirsiniz. Support edilen hardware ‘lerde spesifik bir datastore içerisinde bulunan vmdk’larda clustered vmdk desteğini etkinleştirebilir siniz. Böylece RDM’lerinizi VMFS datastore’a geçirebilir ve RDM kullandığınız için kaybetmiş olduğunuz yetenekleri tekrar kazanmanıza olanak sağlar. Yani Clustered VMDK desteği bize RDM disklerin yapmış olduğu yetenekleri bize sunuyor ve bunları sunarken RDM’de yaşamış olduğumuz kısıtlamaların büyük bir çoğunluğunu ortadan kaldırıyor.

Clustered VMDK

Bunu kullanabilmeniz için belirli gereksinimleri karşılamanız gerekiyor.

Gereksinimler:

Bu özelliği kullanabilmeniz için vSphere 7 ve üzeri versiyon kullanmanız gerekiyor. vSphere 7 ve önceki sümlerde support bulunmuyor.

ESXi host mutlaka ve mutlaka bir vCenter Server’a bağlı olmalıdır.

Cross vCenter Server support bulunmamaktadır. Windows Failover Cluster’ın bulunduğu ESXi host’ların aynı vCenter Server tarafından yönetilmesi gerekiyor.

VMFS6 datastore kullanılması gerekiyor.

Cluster için kullanılan VMDK’ların Eager Zeroed Thick yani EZT olmalıdır.

Cluster VMDK’ların mutlaka bir virtual SCSI Controller’a bağlı olması ve bus sharing’in physical olarak ayarlanması gerekir. Virtual machine’in boot disk’i ve cluster’da kullanılmayan disklerin ayrı bir virtual SCSI Controller üzerinde bulunmalı ve bus sharing none olarak işaretlenmelidir.

Multi-Writer support edilmemektedir.

Multi Writer ile ilgili daha önce bir makale yazmıştım. Buna aşağıdaki diskten ulaşabilirsiniz.

Multi Writer Disk Kullanımı

Virtual machine’lerin farklı ESXi host’lar üzerine dağıtmak için mutlaka DRS Rule’u kullanmalısınız.

Clustered VMDK desteği, datastore oluşturulduktan sonra mutlaka enable duruma getirilmelidir. Bunu eğer disable duruma getirmek isterseniz datastore içerisinde bulunan virtual machine’lerde cluster VMDK bulunmaması gerekir. Eğer buna rağmen bu özelliği disable duruma getirirseniz virtual machine power on olmaz.

Yanlızca FC yani Fibre Channel Stroage protocol’unde kullanılır.

VMDK’ların barındığı fiziksel disk’in ATS support’u bulunmalıdır.

512/512e sektör size’lı diskler gerektirir.

VMware, bunu test ederken Windows Server 2012 R2 / 2016 ve 2019 üzerinde test etmiştir. Yapılandırmanın doğru çalıştığını görmek için ise SQL Server 2016 kullanılmıştır. Ayrıca Cluster across Box support edilirken, Cluster in Box support edilmemektedir. Snapshot, Clone, Hot-add CPU/Memory değiştirme ve fault tolerance support edilmemektedir.

Bir Datastore oluştururken Clustered VMDK support’unun olup olmadığını datastore oluştururken görebilrisiniz. Datastore’u oluşturduktan sonra Clustered VMDK özelliğini aktif etmeniz gerekiyor. Bunu aktif ettiğinizde eğer istereniz daha sonra disable duruma getirebilirsiniz ancak disable duruma getirirken içerisinde virtual machine olmamasına dikkat etmeniz gerekiyor. Zaten içerisinde virtual machine var ise disable duruma getirmiyor. Böyle bir durumda bu datastore içerisindeki tüm virtual machine’lerin farklı bir datastore’a taşınması gerekiyor.

Clustered VMDK özelliğini aktif etmek istediğinizde karşınıza bir uyarı gelecektir. Özelliği aktif ettikten sonra, Windows Failover Cluster dökümanlarına göre virtual machine oluşturabilir ve böylece Clustered VMDK özelliğini kullanmaya başlayabilirsiniz.

Clustered VMDK özelliğini aktif ettiğinizde virtual machine üzerinde Paravirtual SCSI controller ekleyeceksiniz ve bunun sharing seçeneğini physical olarak ayarlayacaksınız. Bir EZT disk oluşturuyoruz. İkinci virtual machine üzerinde yine aynı şekilde Paravirtual SCSI Controller ekliyor ve sharing seçeneğini physical olarak değiştiriyoruz. Daha sonra use add in existing disk seçeneği ile 1. virtual machine üzerinde oluşturduğumuz diski ekliyoruz. Herşey bukadar aslında 🙂

vSphere 7 ile birlikte çok güzel özellikler geliyor ve özellik ile ilgili en kısa zamanda bir uygulama makaleside yazacağım.

Umarım faydalı olmuştur.

İyi çalışmalar.

#failover cluster desteği #ms cluster vmware #sanal windows cluster #windows cluster vmware

0 notes

adsindubai · 7 years ago

Text

Citrix & Windows Administrator for Qatar

VAM Systems is a Business Consulting, IT Technology Solutions and Services company with operations in UAE, Qatar, Bahrain, USA, Australia, Singapore & India. VAM Systems is currently looking for Citrix & Windows Administrator for our Qatar operations with the following skill set and terms and conditions: MAIN DUTIES AND RESPONSIBILITIES: Configuring and administering Citrix Xenapp 6.5 infrastructure Configuring and administering Xendesktop 7.6 infrastructure spanning across multiple sites Configuring and administering Provisioning services 7.6 Experience in XEN desktop provisioning services in VMWARE environment, Desktop OS image capturing, managing Desktop OS for Citrix VDI environment. Configuring and administering Storefront 3.12 and above/Web interface Servers Configuring and administering Netscaler, Access Gateway, Load Balance, Routes, Services, Virtual servers and GSLB Configuring and administering Xenmobile and Sharefile. Solid knowledge of networking protocols (HTTP/S, S/FTP, TCP/IP, DNS, DHCP, etc.) Certificate Integration within the server environment. Diagnosing and resolving performance issues Maintaining consistent system documentation. Plan and failover Citrix component during disaster Recovery Coordinating, managing, and validating software and environment changes Perform installations and upgrades during weekend maintenance window Configuring and administering applications in a Citrix / Windows Server Environment Comply with bank’s Change Management processes and best practices Provide technical leadership for upcoming projects Lead design updates and architecture revisions Address high severity issues and service outages Review periodic reports of server health, resource usage, user experience, and overall environment performance to determine next steps and upgrade paths Review change control requests which impact the Citrix and Windows environment Raise support tickets with the appropriate vendor to resolve critical issues. Experience working with Windows 2008 R2, 2012 R2 & 2016 OS. Experience with Active Directory, Group policies. Experience with Microsoft Windows clustering, load balancing and experience in troubleshooting technical problems involving software and operating systems & includes desktop OS. Develop & Executes PowerShell or Command Shell commands and experience in scripting Experience with Exchange 2010, Office 365, System Center and assisting other Administrators as required on a daily or timely basis. Familiarity with Physical server hardware and VM environment. Assists in the monthly patching of server systems which is part of the maintenance activity. Experience using patience, sensitivity and effective communication with a wide range of people, including the technically proficient and those with minimal computing experience or technical skill. Coordinating with Application teams for service planning and deployment across the organization. Experience writing technical documentation. Experience participating in diverse work groups. Works remotely to provide 24x7 support on critical systems Works efficiently with minimal guidance from Senior or Lead administrators. CORE COMPETENCIES Citrix XENAPP 6.6, XENDESKTOP, XENMOBILE, Share file, NetScaler, Load Balancer Active Directory, Group Policies, IIS , Certificates, PowerShell, Scripting Windows 2008 R2, Windows 2012 R2 & Windows 2016, Clustering, Load Balancing Exchange 2010, Office 365, System Center, Education: University Degree (IT) Professional Certifications Citrix Certified Associate (CCA for Citrix XenApp & XenDesktop) Microsoft Certified Systems Engineer (MCSE ) – Server Infrastructure Microsoft Certified Systems Engineer ( MCSE ) - Messaging Experience Required: 7 years of Systems Administration experience. Terms and conditions: Joining time frame: 30 days. The selected candidates shall join VAM Systems – Qatar and shall be deputed to one of the leading Banks in Qatar. Should you be interested in this opportunity, please send your latest resume in MS Word format at the earliest at [email protected] or call us +91 476 2684924.

0 notes

marlik-job-blog · 8 years ago

Text

New Post has been published on مارلیک | اخبار و تازه های استخدامی

New Post has been published on http://job.marlik.ir/news/%d8%a7%d8%b3%d8%aa%d8%ae%d8%af%d8%a7%d9%85-%db%b1%db%b1-%d8%b1%d8%af%db%8c%d9%81-%d8%b4%d8%ba%d9%84%db%8c-%d8%af%d8%b1-%d8%b4%d8%b1%da%a9%d8%aa-%d9%be%d8%b1%d8%af%d8%a7%d8%b2%d8%b4%da%af%d8%b1%d8%a7/

استخدام ۱۱ ردیف شغلی در شرکت پردازشگران سامان

شرکت پردازشگران سامان در راستای تکمیل کادر پرسنلی خود از واجدین شرایط در ردیفهای شغلی زیر در تهران دعوت به همکاری می‌نماید.

ردیف عنوان شغل مهارت تخصصی مهارت فنی ۱ برنامه نویس جاوا

-At least 3 years of experience in solution, design and development of web-based applications using Java/J2EE, Java Servlets, JSP, EJB3, Primefaces/JSF, XML, and Struts

-Very strong understanding of the OOAD concepts and able to use it in the low level design

-Experience in developing SOAP (JAX-WS) and RESTful (JAX-RS) Web Services using Spring Web Serviceو , Apache CXF, Jersey and Axis

-Important Spring Modules like Core, Context, DAO, ORM, AO, WEB-MVC, Security …

-Strong Back End experience to develop Data Layer using at least one of the ORM frameworks like Hibernate, JPA etc

-Experience in web based application Servers, WebLogic, Websphere and Apache Tomcat

-Continuous integration (Jenkins, Maven, Gradle, Ant, Bamboo/Hudson, SVN, Git)

-Strive to constantly improve the application development processes and tools

-Expert in tuning all tiers of applications on JEE platform and experience in implementing J2EE Design Patterns for module designs

-Experience in using JMS Queue and Topic’s

-Experience with IDEs like Eclipse, JDeveloper, IntelliJ, Spring Suite etc

-Bachelor’s degree in Computer Science or Engineering or equivalent working experience

-Application of software development principles, theories, concepts, and techniques

-Provides resolutions to an assortment of technical problems

-Innovative in providing solutions, likes to take on challenges with calculated risks

-Understand Business Requirements; participates in System Requirement Analysis; design Applications based on System Requirements and Architecture, prototype if necessary, develop, unit test and deploy application. Will use MS Visio, UML, RUP, and Agile Methodology

-Hands-on experience with build and deployment tools and languages

-Good knowledge of database concepts with working knowledge on SQL, SQL Server, Oracle, DB2 or Sybase database, and Stored Procedures

-Improve and expand Test Driven Development (TDD & ATDD / BDD) Approach to development

-Strong understanding of Service Oriented Architecture (SOA) and service design concepts

۲ برنامه نویس دات نت

-C# .Net

-OOP

-MVC

-Angular

-Wcf & WebServices

-WF

-Entity Framework & LINQ