Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
CIT233 Ch 6 - 8
CIT233 Chapters 6 - 8
| Term | Definition |
|---|---|
| active node | A cluster member that’s responding to client requests for a network application or service; also referred to as an “active server.” |
| client access point | A name and IP address by which clients can access a clustered service in a failover cluster. See also failover cluster. |
| client affinity value | An option specified in multiple host filtering modes that determines whether the same or a different host handles successive requests from the same client. |
| Cluster-Aware Updating (CAU) | A new failover cluster feature in Windows Server 2012 that automates software updates on cluster servers while maintaining cluster service availability. See also failover cluster. |
| cluster heartbeat | Communication between cluster nodes that provides the status of each cluster member to the cluster quorum. The cluster heartbeat, or lack of it, informs the cluster when a server is no longer communicating. |
| cluster operation mode | A cluster parameter that specifies the type of network addressing used to access the cluster: unicast, multicast, or IGMP multicast. |
| cluster shared volume | A storage option in a failover cluster in which all cluster nodes have access to the shared storage for read and write access. See also failover cluster. |
| cluster server | A Windows Server 2012/R2 server that participates in a failover cluster; also referred to as a “cluster node” or “cluster member.” See also failover cluster. |
| clustered application | An application or service installed on two or more servers participating in a failover cluster; Also called a “clustered service.” See also failover cluster. |
| failback options | Settings that specify a cluster should revert to the most preferred owner when the server is available again. The failback can occur immediately or between certain hours of the day. |
| failover cluster | Two or more servers appearing as a single server to clients. The active server handles all client requests for the clustered application, and the passive servers wait in standby mode until the active server fails. |
| failover options | Settings that specify how many times a service attempts to restart or fail over to another server in the specified period. |
| filtering mode | An option in a port rule that specifies whether multiple hosts or a single host respond to traffic identified by the port rule. Multiple host is the default mode and allows scalability. |
| handling priority | An NLB parameter used in single host mode that determines which host handles all traffic meeting the port rules’ criteria. See also filtering mode and network load balancing (NLB). |
| high availability | A network or computer configuration in which data and applications are almost always available, even after a system failure. |
| load weight | An NLB parameter that allows configuring how much network traffic, as a percentage, each node should handle. See also network load balancing (NLB). |
| network load balancing (NLB) | A Windows Server feature that uses server clusters to provide scalability and fault tolerance. See also server cluster. |
| Partitioned | A cluster status that can occur if communication fails between cluster servers, resulting in two or more subclusters, each with the objective of handling the clustered service. See also cluster server. |
| passive node | A cluster member that’s not currently responding to client requests for a clustered application but is in standby in case the active node fails; also called a “passive server.” |
| port rule | A setting that specifies which type of TCP or UDP traffic an NLB cluster should respond to and how the traffic is distributed among cluster members. See also network load balancing (NLB). |
| preferred owner | The server selected as the active server for a service or an application. |
| Quorum | A database containing cluster config info about the status of each node (active or passive) for clustered apps. Also used to determine, in a failure, whether the cluster is to remain online and which servers should continue to participate in the cluster. |
| rolling upgrade | An NLB cluster upgrade method that involves taking each cluster node offline, upgrading the host, and then bringing it back online. See also network load balancing (NLB). |
| server cluster | A group of two or more servers configured to respond to a single virtual IP address. |
| standby mode | A cluster node that isn’t active. |
| virtual IP address | The IP address by which networking services provided by an NLB cluster are accessed by network clients. A DNS host record should exist for the cluster name mapped to this address. See also network load balancing (NLB). |
| witness disk | Shared storage used to store cluster configuration data and help determine the cluster quorum. |
| Active Directory–detached cluster | A new cluster configuration option that allows deploying a failover cluster without needing Active Directory for network name management. |
| core cluster resources | Resources in a failover cluster that include the quorum resource, which is usually the witness disk or witness share; the IP address resource that provides the cluster IP address; and the network name resource that provides the cluster name. |
| drain on shutdown | A new feature in Windows Server 2012 R2 that drains roles automatically and live-migrates VMs to another cluster node before the Hyper-V server shuts down. |
| dynamic quorum | A feature that assigns a cluster node vote dynamically depending on whether the node is an active member of the cluster. If a node is no longer active in the cluster, its vote is removed. |
| dynamic witness | A quorum feature in Windows Server 2012 R2 in which the cluster determines whether to give the witness a quorum vote, based on whether there’s an odd or even number of cluster nodes. |
| guest clustering | A clustering feature that requires two or more VMs with a guest OS installed and configured for failover clustering; the failover clustering occurs in the VM’s guest OS. |
| highly available virtual machine | A failover cluster configuration in which two or more servers with the Hyper-V role are configured in a failover cluster, and the VMs are stored on shared storage. Also called a “clustered virtual machine.” |
| live migration | An application or service installed on two or more servers participating in a failover cluster; also called a “clustered service.” |
| physical to virtual (P2V) | migration A migration that converts a physical computer to a virtual machine. |
| quick migration | A migration option available only between Hyper-V servers in a failover cluster; usually results in a minute or more of downtime, depending on how much memory the VM uses. |
| scale-out file server | A highly available share option that provides the reliability of failover clusters and the load distribution of an NLB because client connections are distributed among all nodes in the cluster. |
| shared virtual hard disk | A virtual hard disk configured on a VM in a guest cluster that’s used for shared storage among VMs in the guest cluster instead of traditional SAN storage. |
| shared-nothing live migration | A live migration done between Hyper-V servers that have no common storage. |
| split vote | A quorum situation in which no quorum can be reached. |
| storage migration | A VM migration process used to move a VM’s storage from one volume to another without moving the VM to another Hyper-V server. |
| tie breaker for 50% node split | A situation in which a cluster is partitioned into equal numbers of nodes, and the dynamic quorum feature is used to change node votes to break the tie. See also dynamic quorum. |
| virtual machine monitoring | A new feature in Windows Server 2012 that allows monitoring resources, applications, and services running on highly available VMs. See also highly available virtual machine. |
| virtual machine network health detection | A failover cluster feature that automatically live migrates a virtual machine to another node if its network connection fails. |
| virtual to virtual (V2V) migration | A migration that converts a virtual machine from one vendor’s format to another vendor’s format. |
| authoritative restore | A type of Active Directory restore operation in which the restored DC replicates to all other DCs in the domain, and any changes made to Active Directory objects since the backup occurred are lost. |
| bare metal recovery | A backup option that includes the system state, the system reserved volume, and the volume where Windows is stored. |
| boot configuration data (BCD) | store A binary file containing settings that determine how a Windows system boots. |
| differential backup | A backup method in which only the blocks that have changed are transferred to the destination if there is an existing backup. |
| Heartbeat | A signal sent between cluster nodes informing them that a node is up and running. |
| hot backup site | A location that duplicates much of the main site’s IT infrastructure and can be switched to if a disaster occurs at the main site. |
| Hyper-V Replica | A new feature in Windows Server 2012 that periodically replicates changes in a VM to a mirror VM hosted on another Hyper-V server. |
| Microsoft Azure Backup | An online backup solution that stores backups in the cloud; they can be accessed from anywhere you have an Internet connection. |
| nonauthoritative restore | A type of Active Directory restore operation in which changes made to Active Directory objects on other DCs since the backup are kept and replicated to the server being restored. |
| one-time backup | A backup type that creates a backup to a local volume or a share; the backup begins immediately. |
| recovery point | A checkpoint that can be generated automatically so that you can revert to an earlier server state in case there’s an unplanned failover and a VM is in an unworkable state. |
| replica server | In the Hyper-V Replica feature, the Hyper-V server where replication is enabled. |
| retention range | A setting in Microsoft Azure Backup that specifies how long a backup should be kept. |
| scheduled backup | A backup type that allows specifying how often a backup occurs and dedicating a disk to backups. |
| Secure Boot | A feature that prevents a computer from booting from untrusted software. |
| site-level disaster recovery | A process with procedures and technologies an organization uses to get its network and servers running quickly after a disaster. |
| system state backup | A backup option that backs up boot files, Windows system files, and the Registry. On a DC, the system state includes the Active Directory database and the SYSVOL folder. |
Created by:
Leisac
Popular Computers sets