Meta tags:

Headings (most frequently used words):

create, configure, availability, the, volumes, sql, server, for, on, group, storage, groups, and, cluster, netapp, block, to, always, domain, clustering, up, windows, failover, quorum, use, google, cloud, stay, organized, with, collections, save, categorize, content, based, your, preferences, objectives, costs, before, you, begin, accounts, compute, engine, vms, join, servers, prepare, mount, iscsi, each, vm, set, test, clean, host, provision, pool, firewall, file, share, enable, in, database, dnn, resource, delete, project, products, pricing, support, resources, engage,

Text of the page (most frequently used words):
the (244), and (184), #create (161), for (150), vms (111), server (94), with (85), sql (72), select (62), troubleshoot (62), about (59), instance (53), disk (52), configure (50), cloud (46), manage (46), using (46), windows (45), click (40), google (39), view (39), availability (38), cluster (38), use (36), compute (35), disks (35), name (34), from (34), mig (33), your (32), group (31), performance (31), overview (31), set (30), you (29), connect (29), engine (29), storage (27), reservation (27), project (26), network (26), volumes (26), new (24), configuration (24), access (24), machine (24), host (23), failover (22), sqlnode1 (22), groups (22), hyperdisk (22), resources (21), add (21), data (21), mssql (21), microsoft (21), images (21), that (20), sqlnode2 (20), monitor (20), service (19), management (19), tcp (19), database (18), type (18), instances (18), gpu (18), run (17), following (17), example (17), backup (17), iscsi (17), domain (17), image (17), linux (17), policies (16), manager (16), log (16), apply (16), account (16), install (16), snapshots (16), reservations (16), right (15), load (15), enable (15), file (15), virtual (15), ssh (15), recommendations (15), delete (14), mssqlserver (14), workload (14), creation (14), custom (14), resource (13), open (13), share (13), modify (13), logs (13), netapp (13), bulk (13), high (12), node (12), based (12), sole (12), persistent (12), best (12), regional (12), page (11), always (11), restore (11), zone (11), each (11), location (11), existing (11), boot (11), practices (11), workloads (11), stateful (11), application (10), dns (10), files (10), quorum (10), choose (10), protocol (10), allow (10), start (10), agent (10), list (10), pool (10), internal (10), managed (10), metadata (10), migs (10), machines (10), attached (10), migrate (10), zones (10), action (9), dnn (9), update (9), properties (9), back (9), recovery (9), steps (9), tempdb (9), login (9), change (9), target (9), addresses (9), networking (9), licenses (9), tenant (9), multiple (9), openshift (9), shutdown (9), time (9), hpc (9), all (8), this (8), license (8), ssms (8), alter (8), nodes (8), wizard (8), tab (8), section (8), netfirewallrule (8), displayname (8), direction (8), inbound (8), localport (8), powershell (8), administrator (8), these (8), clustering (8), manually (8), remove (8), startup (8), directory (8), multi (8), local (8), console (8), snapshot (8), region (8), deploy (8), import (8), cpu (8), optimize (8), disaster (8), guest (8), keys (8), h4d (8), flexibility (8), optimized (8), tpu (8), thumb (7), need (7), projects (7), after (7), both (7), default (7), mode (7), full (7), options (7), databases (7), perform (7), enter (7), then (7), next (7), path (7), witness (7), control (7), tools (7), move (7), locations (7), volume (7), capacity (7), block (7), pools (7), security (7), active (7), accounts (7), usage (7), commitments (7), balancing (7), benchmark (7), idle (7), request (7), scale (7), mysql (7), zonal (7), maintenance (7), templates (7), join (6), events (6), information (6), details (6), send (6), can (6), replica (6), ensure (6), mydb1 (6), object (6), model (6), services (6), permissions (6), clusters (6), master (6), stop (6), paths (6), filename (6), sqlsvc (6), advanced (6), command (6), vpc (6), flex (6), get (6), operating (6), between (6), migration (6), updates (6), instant (6), nested (6), gpus (6), across (6), applications (6), demand (6), extension (6), transfer (6), customized (6), spot (6), code (5), samples (5), system (5), support (5), understand (5), down (5), more (5), tutorial (5), check (5), sys (5), replicas (5), automatic (5), created (5), expand (5), role (5), roles (5), distributed (5), follow (5), creating (5), ldf (5), mdf (5), temp (5), size (5), shell (5), iqn (5), uses (5), monitoring (5), errors (5), future (5), drivers (5), virtualization (5), nvidia (5), operations (5), placement (5), highly (5), available (5), build (5), schedules (5), audit (5), symphony (5), email (5), scripts (5), systems (5), enhanced (5), capabilities (5), tenancy (5), regions (5), types (5), workstation (5), faq (5), other (4), primary (4), running (4), listener (4), manual (4), ars (4), group_id (4), where (4), query (4), connection (4), complete (4), balancer (4), transaction (4), tasks (4), copy (4), settings (4), shared (4), before (4), udp (4), msdb (4), backups (4), dialog (4), portal (4), initiator (4), mount (4), specific (4), project_id (4), windowsfeature (4), net (4), prepare (4), series (4), plan (4), how (4), guides (4), authentication (4), issues (4), ubuntu (4), bandwidth (4), pmu (4), number (4), ssd (4), upgrade (4), live (4), autoscaling (4), cross (4), requests (4), calendar (4), single (4), metrics (4), health (4), containers (4), container (4), postgresql (4), extensions (4), work (4), suspend (4), resize (4), graceful (4), plans (4), replication (4), review (4), bound (4), sign (3), terms (3), pricing (3), see (3), content (3), under (3), are (3), apache (3), selecting (3), verify (3), which (3), configured (3), synchronous (3), bring (3), client (3), traffic (3), only (3), synchronization (3), port (3), 5022 (3), specify (3), pane (3), restart (3), grant (3), folder (3), computer (3), static (3), address (3), 3343 (3), rpc (3), firewall (3), wsfc (3), errorlog (3), their (3), drives (3), exec (3), xp_instance_regwrite (3), hkey_local_machine (3), software (3), reg_sz (3), repeat (3), format (3), device (3), devices (3), mpio (3), targets (3), one (3), ips (3), replace (3), two (3), volume_name (3), gcloud (3), host_group_name (3), pool_name (3), throughput (3), provision (3), hosts (3), rsat (3), core (3), features (3), close (3), credentials (3), interface (3), subnet (3), interfaces (3), balanced (3), memory (3), general (3), api (3), user (3), rdp (3), costs (3), through (3), cloning (3), infrastructure (3), observability (3), analytics (3), troubleshooting (3), encryption (3), pro (3), serial (3), configurations (3), patterns (3), higher (3), discounts (3), cuds (3), scalable (3), resilient (3), autoscale (3), prevent (3), policy (3), testing (3), ibm (3), spectrum (3), deploying (3), during (3), deployment (3), rhel (3), environment (3), protect (3), certificates (3), state (3), disable (3), increase (3), schedule (3), lifecycle (3), design (3), non (3), workstations (3), tpus (3), product (3), 한국어 (2), 日本語 (2), עברית (2), português (2), brasil (2), italiano (2), indonesia (2), français (2), español (2), américa (2), latina (2), deutsch (2), english (2), third (2), site (2), youtube (2), center (2), started (2), status (2), products (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), its (2), feedback (2), used (2), also (2), clicking (2), secondary (2), replica_server_name (2), availability_groups (2), availability_replicas (2), replica_id (2), commit (2), test (2), include (2), have (2), don (2), must (2), checkbox (2), any (2), online (2), provide (2), point (2), instead (2), endpoints (2), explorer (2), specifying (2), norecovery (2), browser (2), finish (2), sqlcluster (2), customize (2), different (2), validation (2), validate (2), msc (2), endpoint (2), 135 (2), sharing (2), smb (2), 445 (2), 49152 (2), 65535 (2), 3260 (2), 1433 (2), commands (2), old (2), program (2), mssql16 (2), mastlog (2), parameters (2), drive (2), modellog (2), msdbdata (2), msdblog (2), templog (2), member (2), password (2), foreach (2), appears (2), discover (2), associated (2), iscsicpl (2), exe (2), 165 (2), 128 (2), note (2), range (2), private (2), psa_range_name (2), vpc_name (2), west1 (2), 1024 (2), total (2), iops (2), sqlnode2_iqn (2), sqlnode1_iqn (2), record (2), cvsdemo (2), framework (2), required (2), administrators (2), when (2), servers (2), premium (2), save (2), 2022 (2), enterprise (2), 2025 (2), public (2), purpose (2), activate (2), within (2), identity (2), enabled (2), selector (2), resourcemanager (2), require (2), iam (2), begin (2), generate (2), cost (2), documentation (2), sdk (2), languages (2), frameworks (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), development (2), quota (2), commitment (2), consumption (2), standard (2), registration (2), sles (2), export (2), collecting (2), report (2), arm (2), app (2), latency (2), analyze (2), visible (2), cores (2), automatically (2), committed (2), generation (2), underutilized (2), insights (2), utilization (2), globally (2), web (2), autohealing (2), iis (2), external (2), reserve (2), autoscaler (2), autoscalers (2), activity (2), kubernetes (2), provider (2), place (2), setting (2), redis (2), writer (2), alwayson (2), authenticate (2), method (2), global (2), switch (2), byol (2), payg (2), byos (2), changes (2), families (2), guide (2), securing (2), event (2), simulate (2), topology (2), together (2), repairs (2), repair (2), failures (2), template (2), suspended (2), stopped (2), distribution (2), physical (2), cancel (2), once (2), limit (2), ipv6 (2), decrease (2), basic (2), consistent (2), scoped (2), appliances (2), asynchronous (2), encrypt (2), names (2), extreme (2), organization (2), rdma (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), accelerator (2), apis (2), reference (2), technology (2), areas (2), subscribe, newsletter, our, decade, climate, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, getting, github, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, java, registered, trademark, oracle, affiliates, developers, creative, commons, attribution, avoid, incurring, charges, shutting, clean, show, dashboard, reconnecting, checking, servername, initiate, ag_name, primaryreplica, dm_hadr_availability_replica_states, role_desc, availability_mode_desc, failover_mode_desc, strings, multisubnetfailover, true, binds, exclude, them, possible, owners, clear, aren, route, initial, yes, readable, tree, confirm, option, actions, cno, browse, shares, folders, window, intend, recommend, preferably, serve, prompts, administering, tests, pass, proceeding, cluadmin, mapper, printer, allows, respectively, parameter, pointing, script, redirect, mounted, backupdirectory, defaultdata, defaultlog, modeldev, tempdev, logins, necessary, default_database, default_language, us_english, sysadmin, studio, previous, step, left, mounting, respective, item, itemtype, force, structure, newly, formatted, assign, letter, ntfs, 64k, allocation, unit, initialize, gpt, compmgmt, rebooting, reboot, prompted, panel, discovered, adapter, 216, 217, iscsitargetportal, targetportaladdress, replacing, assigned, configuring, listed, unique, eight, times, 200, protocols, hostgroups, false, separate, allocated, match, level, unified, psa, iscsi_initiator, description, containing, iqns, ensures, specified, 1991, com, initiatorport, nodeaddress, qualified, alternatively, cmdinterface, includeallsubfeature, includemanagementtools, multipath, msdsmautomaticclaim, bustype, prereqs, localgroupmember, restarts, welcome, message, now, link, workgroup, second, named, tier, gvnic, card, datacenter, version, highmem, 8vcpu, privileges, domainadmin, installation, rules, computers, established, administrative, billing, keep, procedure, removing, creator, contains, permission, learn, projectcreator, doesn, been, granted, billable, components, estimate, projected, calculator, objectives, explains, internet, small, provides, fully, such, categorize, preferences, stay, organized, collections, home, concurrent, operation, renewal, nvme, resizing, common, pay, viewing, output, diagnostic, sudoers, screenshots, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, kernel, panic, fstab, unresponsive, suspension, reboots, shutdowns, connectivity, tips, nics, dpdk, improve, resiliency, communication, reduce, compact, idpf, irdma, driver, nic, threads, per, sustained, merge, split, extend, renew, without, purchase, savings, dynamic, overcommit, cpus, floating, reliable, backends, routing, https, scaling, consuming, consume, combine, cud, decisions, signals, serving, predictions, organize, labels, states, observe, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, spark, forwarding, others, integrate, exchange, 2016, sharepoint, strategies, passive, inactive, setups, built, integrations, were, deployed, transition, hammerdb, bucket, aws, ec2, pacemaker, s2d, hot, standby, drbd, architectures, mailjet, mailgun, sendgrid, sending, blue, green, deployments, lamp, joomla, asp, interactive, mongodb, flask, terraform, over, mtls, random, generator, virtio, rng, accurate, ntp, append, els, restrictions, packages, deprecate, versions, family, trusted, red, hat, knowledgebase, functionality, risks, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, process, faulty, unmanaged, affect, preserved, turn, off, alternate, fails, repairing, maintain, upgrades, override, selectively, applying, accelerate, out, outage, rebalance, reenable, proactive, redistribution, shape, distribute, define, info, accidental, deletion, spread, edit, rename, reset, resume, referrers, source, uuid, recover, corrupted, duplicate, clones, alerts, vss, regionally, protection, considerations, consistency, failback, replicate, make, provisioned, limits, evaluate, help, kms, customer, supplied, symbolic, links, practice, ram, attach, additional, exapools, ptr, failure, rates, tags, restrict, automate, sac, securely, apps, root, vpn, bastion, iap, connections, networks, iso, imported, prerequisites, importing, exporting, own, detach, reattach, constraint, accounting, examples, slurm, reserved, team, slice, slices, adds, scenarios, deterministic, base, requirements, ready, aci, preempted, historical, alternative, similar, displays, ops, logging, has, gpudirect, ultra, minimum, platform, hostname, quickstarts, office, licensing, strategy, gemini, bare, metal, accelerators, platforms, scores, free, skip, main,

Text of the page (random words):
g billable components of google cloud compute engine netapp volumes to generate a cost estimate based on your projected usage use the pricing calculator before you begin before you begin ensure you have the following in the google cloud console on the project selector page select or create a google cloud project roles required to select or create a project select a project selecting a project doesn t require a specific iam role you can select any project that you ve been granted a role on create a project to create a project you need the project creator role roles resourcemanager projectcreator which contains the resourcemanager projects create permission learn how to grant roles note if you don t plan to keep the resources that you create in this procedure create a project instead of selecting an existing project after you finish these steps you can delete the project removing all resources associated with the project go to project selector verify that billing is enabled for your google cloud project a google cloud project with administrative permissions for compute engine networking identity and access management and cloud storage a vpc network with a subnet in your target region active directory and dns services established within the region an active directory user with permissions to join computers to the domain and access vms using rdp ensure that vpc firewall rules allow traffic between nodes for iscsi tcp 3260 wsfc udp tcp 3343 sql server tcp 1433 sql server ag endpoints tcp 5022 smb tcp 445 and rpc tcp 135 tcp 49152 65535 enable the netapp volumes api in the google cloud console activate cloud shell activate cloud shell configure domain accounts configure two active directory accounts for sql server installation account an account with domain administrator privileges for example domain domainadmin to sign in to vms and configure the cluster and availability group service account an account for example domain sqlsvc for the sql server service and sql agent service on both sql server vms create compute engine vms for sql server create two compute engine instances sqlnode1 and sqlnode2 running sql server 2022 enterprise on windows server 2025 in the google cloud console go to the create an instance page go to create an instance for name enter sqlnode1 in the machine configuration section select general purpose and then do the following in the series list select n4 in the machine type list select n4 highmem 8 8vcpu 64 gb memory select the region and zone where you configured your vpc in the boot disk section click change and then do the following on the public images tab select sql server on windows server from the operating system list from the version list select sql server 2022 enterprise on windows server 2025 datacenter in the boot disk type list select hyperdisk balanced set the size gb to 50 to save the boot disk configuration click select expand the advanced options section then expand networking for network interfaces select the vpc and subnet for your project in the network interface card type list select gvnic for network service tier select premium click create repeat these steps to create a second instance named sqlnode2 join servers to the domain and prepare for clustering perform these steps on both sqlnode1 and sqlnode2 connect to the vm using a local administrator account in the server manager select local server select the workgroup link in the computer name section select change select the domain checkbox enter your domain name for example cvsdemo internal and click ok in the windows security dialog enter the credentials for your domain administrator account and click ok when the welcome message appears for the domain complete the following steps a click ok b click close and then select restart now after the vm restarts connect to it using your domain administrator account add the domain sqlsvc account to the local administrators group on the vm you can use the following powershell command add localgroupmember group administrators member domain sqlsvc open powershell as an administrator and run the following commands to install required windows features install failover clustering and tools install windowsfeature failover clustering rsat clustering powershell rsat clustering cmdinterface includeallsubfeature includemanagementtools install and enable mpio for iscsi install windowsfeature name multipath io enable msdsmautomaticclaim bustype iscsi install net and other sql prereqs install windowsfeature net framework 45 core net framework 45 features install windowsfeature rsat ad powershell to get the iscsi qualified name iqn for the vm run iscsicpl exe go to the configuration tab and copy the initiator name alternatively run the following powershell command get initiatorport select object nodeaddress record the iqn for both sqlnode1 and sqlnode2 you need these in the next section example iqn 1991 05 com microsoft sqlnode1 cvsdemo internal create netapp volumes block storage volumes follow these steps to create a host group storage pool and iscsi volumes create a host group a host group ensures that only the specified hosts your sql server vms can access the volumes you create in cloud shell create a host group containing the iqns of sqlnode1 and sqlnode2 gcloud netapp host groups create host_group_name location location type iscsi_initiator hosts sqlnode1_iqn sqlnode2_iqn os type windows description sql server ag nodes replace the following information host_group_name the name for the host group for example sql ag hosts location the region for your host group for example us west1 sqlnode1_iqn the iqn of sqlnode1 sqlnode2_iqn the iqn of sqlnode2 provision a storage pool in cloud shell create a storage pool for your volumes gcloud netapp storage pools create pool_name project project_id location zone service level flex type unified capacity 1024 total throughput 64 total iops 1024 network name vpc_name psa range psa_range_name replace the following information pool_name the name for the storage pool for example sql pool project_id your google cloud project id zone the zone for your storage pool which must match the zone of your vms for example us west1 b vpc_name the name of your vpc network psa_range_name the name of the allocated range of your private services access connection create volumes create separate volumes for sql server data logs tempdb and backups for each node in cloud shell run the following command for each volume you need to create gcloud netapp volumes create volume_name project project_id location zone storage pool pool_name capacity 200 protocols iscsi block devices name volume_name host groups projects project_id locations location hostgroups host_group_name os type windows snapshot directory false replace volume_name with a unique name for each volume for this two node tutorial you need to run the command eight times to create volumes for data logs tempdb and backups for each node for example sqlnode1 data sqlnode1 log sqlnode1 temp sqlnode1 backup sqlnode2 data sqlnode2 log sqlnode2 temp and sqlnode2 backup mount iscsi volumes on each sql vm for each vm sqlnode1 and sqlnode2 mount the volumes you created for that specific node in the google cloud console go to the volumes page for netapp volumes go to volumes select a volume assigned to the node you are configuring note the target portal ip addresses listed in the iscsi target details section you need these addresses to connect to the volume on the vm open powershell as an administrator and run the following command replacing the example ips with the target portal ips for your volume 10 165 128 216 10 165 128 217 foreach object new iscsitargetportal targetportaladdress _ run iscsicpl exe to open iscsi initiator properties go to the targets tab select one of your volume targets from the list and click connect in the connect to target dialog select enable multi path and click advanced in the advanced settings dialog local adapter select microsoft iscsi initiator initiator ip select an ip address on the vm target portal ip select one of the portal ips you discovered click ok in the connect to target dialog click ok repeat the connection steps for all targets associated with the vm to configure mpio for iscsi devices open mpio properties from control panel or server manager click the discover multi paths tab select add support for iscsi devices and click add reboot the vm if prompted after rebooting open device manager and expand disk drives your iscsi disk appears as a multi path device open disk management compmgmt msc for each new disk bring the disk online initialize the disk gpt create a new volume assign a drive letter for example d for data e for logs f for backups g for tempdb and format it using ntfs with an allocation unit size of 64k create the directory structure for sql server on the newly formatted drives for example paths d mssql data e mssql log f mssql backup g mssql temp paths foreach object new item itemtype directory path _ force configure sql server perform these steps on both sqlnode1 and sqlnode2 after mounting their respective volumes open sql server configuration manager in the left pane select sql server services in the right pane right click sql server mssqlserver select properties go to the log on tab and change the account name to your service account domain sqlsvc enter the password and click ok repeat the previous step for sql server agent mssqlserver connect to the sql server instance using sql server management studio ssms with your domain administrator account create logins for the service account and grant it necessary permissions use master go create login domain sqlsvc from windows with default_database master default_language us_english go alter server role sysadmin add member domain sqlsvc go run the following script in ssms to redirect the default database log backup and tempdb paths to the iscsi volumes you mounted use master go exec xp_instance_regwrite n hkey_local_machine n software microsoft mssqlserver mssqlserver n backupdirectory reg_sz n f mssql backup go exec xp_instance_regwrite n hkey_local_machine n software microsoft mssqlserver mssqlserver n defaultdata reg_sz n d mssql data go exec xp_instance_regwrite n hkey_local_machine n software microsoft mssqlserver mssqlserver n defaultlog reg_sz n e mssql log go modify model and msdb paths alter database model modify file name modeldev filename d mssql data model mdf alter database model modify file name modellog filename e mssql log modellog ldf alter database msdb modify file name msdbdata filename d mssql data msdbdata mdf alter database msdb modify file name msdblog filename e mssql log msdblog ldf go modify tempdb paths alter database tempdb modify file name tempdev filename g mssql temp tempdb mdf alter database tempdb modify file name templog filename g mssql temp templog ldf go stop the sql server mssqlserver service move the existing model msdb and tempdb files from their old locations for example c program files microsoft sql server mssql16 mssqlserver mssql data to their new locations on drives d e and g to move the master database and errorlog open sql server configuration manager right click sql server mssqlserver select properties and go to the startup parameters tab for each existing parameter d e and l pointing to the c drive select it and click remove add the following parameters clicking add for each dd mssql data master mdf le mssql log mastlog ldf ee mssql log errorlog click ok manually move master mdf and mastlog ldf from c program files microsoft sql server mssql16 mssqlserver mssql data to d mssql data and e mssql log respectively move the errorlog file from its old location to e mssql log start the sql server mssqlserver service set up windows server failover clustering follow these steps to create the cluster and configure a quorum witness configure windows firewall before creating the cluster ensure windows firewall on each node allows traffic for wsfc sql server and iscsi on sqlnode1 and sqlnode2 open powershell as an administrator and run the following commands new netfirewallrule displayname failover clusters udp in direction inbound protocol udp localport 3343 action allow new netfirewallrule displayname failover clusters tcp in direction inbound protocol tcp localport 3343 action allow new netfirewallrule displayname rpc endpoint mapper direction inbound protocol tcp localport 135 action allow new netfirewallrule displayname file and printer sharing smb in direction inbound protocol tcp localport 445 action allow new netfirewallrule displayname failover cluster manager rpc direction inbound protocol tcp localport 49152 65535 action allow new netfirewallrule displayname iscsi direction inbound protocol tcp localport 3260 action allow new netfirewallrule displayname sql server direction inbound protocol tcp localport 1433 action allow new netfirewallrule displayname sql server ag endpoint direction inbound protocol tcp localport 5022 action allow create the cluster on sqlnode1 open failover cluster manager cluadmin msc in the management section select validate configuration follow the wizard to validate sqlnode1 and sqlnode2 ensure all tests pass before proceeding after validation select create cluster in the create cluster wizard add sqlnode1 and sqlnode2 as cluster nodes for access point for administering the cluster enter a cluster name for example sqlcluster and provide a static ip address for the cluster follow the prompts to create the cluster create a file share for cluster quorum we recommend creating a file share on a third vm preferably in a different zone to serve as the cluster quorum witness connect to the vm you intend to use as the file share witness in the server manager window select tools computer management expand system tools shared folders right click shares and select new share follow the create a shared folder wizard on the folder path page browse to or create a folder for the share on the permissions page select customize permissions click add and grant full control to the cluster name object cno account for example sqlcluster complete the wizard to create the share configure cluster quorum on sqlnode1 open failover cluster manager right click the cluster name and select more actions configure cluster quorum settings in the configure cluster quorum wizard select next on the select quorum configuration option page choose select the quorum witness and click next on the select quorum witness page choose configure a file share witness and click next for file share path enter the path to the share you created for example witness server quorum and click next confirm your settings and click next then click finish configure always on availability groups apply the steps in this section to both sql server vms to enable and configure the availability group enable availability groups in sql server open sql server configuration manager in the browser tree select sql server services rig...