Abstract: Techniques are provided for a high availability solution (e.g., a network attached storage (NAS) solution) with address preservation during switchover. A first virtual machine is deployed into a first domain and a second virtual machine is deployed into a second domain of a computing environment. The first and second virtual machines are configured as a node pair for providing clients with access to data stored within an aggregate comprising one or more storage structures within shared storage of the computing environment. A load balancer is utilized to manage logical interfaces used by clients to access the virtual machines. During switchover, the load balancer preserves an IP address used to mount and access a data share of the aggregate used by a client.

Abstract: Techniques are provided for a high availability solution (e.g., a network attached storage (NAS) solution) with address preservation during switchover. A first virtual machine is deployed into a first domain and a second virtual machine is deployed into a second domain of a computing environment. The first and second virtual machines are configured as a node pair for providing clients with access to data stored within an aggregate comprising one or more storage structures within shared storage of the computing environment. A load balancer is utilized to manage logical interfaces used by clients to access the virtual machines. During switchover, the load balancer preserves an IP address used to mount and access a data share of the aggregate used by a client.

Abstract: Techniques are provided for lock reservations for shared storage. A reserve command to reserve a storage structure is received by a driver from a node. The reserve command is formatted according to a storage protocol. The driver translates the reserve command into a lease acquire command formatted according to an object store protocol and targeting an object stored within an object store and corresponding to the storage structure. A lease identifier derived from a node identifier of the node is inserted into the lease acquire command. The lease acquire command is routed to the object store for obtaining a lease on the object for granting the node exclusive write access to the object.

Abstract: Techniques are provided for a high availability solution (e.g., a network attached storage (NAS) solution) with address preservation during switchover. A first virtual machine is deployed into a first domain and a second virtual machine is deployed into a second domain of a computing environment. The first and second virtual machines are configured as a node pair for providing clients with access to data stored within an aggregate comprising one or more storage structures within shared storage of the computing environment. A load balancer is utilized to manage logical interfaces used by clients to access the virtual machines. During switchover, the load balancer preserves an IP address used to mount and access a data share of the aggregate used by a client.

Abstract: Techniques are provided for a high availability solution (e.g., a network attached storage (NAS) solution) with address preservation during switchover. A first virtual machine is deployed into a first domain and a second virtual machine is deployed into a second domain of a computing environment. The first and second virtual machines are configured as a node pair for providing clients with access to data stored within an aggregate comprising one or more storage structures within shared storage of the computing environment. A load balancer is utilized to manage logical interfaces used by clients to access the virtual machines. During switchover, the load balancer preserves an IP address used to mount and access a data share of the aggregate used by a client.

Abstract: Techniques are provided for load balancing for IP failover. A backend address of a first node is identified as a routing destination to which a request is to be routed by a load balancer based upon a load balancer rule mapping a frontend address, specified by the request as a request destination, to the backend address of the first node. The request is routed to a primary network interface of the first node using the backend address. The first node has a loopback interface with an address matching the frontend address for routing the request to a destination data structure based upon the request maintaining the frontend address as the request destination. Health probes are used by the load balancer for detecting a failure of the first node in order to failover to routing requests to a second backend address of a second node.

Abstract: Techniques are provided for load balancing for IP failover. A backend address of a first node is identified as a routing destination to which a request is to be routed by a load balancer based upon a load balancer rule mapping a frontend address, specified by the request as a request destination, to the backend address of the first node. The request is routed to a primary network interface of the first node using the backend address. The first node has a loopback interface with an address matching the frontend address for routing the request to a destination data structure based upon the request maintaining the frontend address as the request destination. Health probes are used by the load balancer for detecting a failure of the first node in order to failover to routing requests to a second backend address of a second node.

Abstract: Techniques are provided for lock reservations for shared storage. A reserve command to reserve a storage structure is received by a driver from a node. The reserve command is formatted according to a storage protocol. The driver translates the reserve command into a lease acquire command formatted according to an object store protocol and targeting an object stored within an object store and corresponding to the storage structure. A lease identifier derived from a node identifier of the node is inserted into the lease acquire command. The lease acquire command is routed to the object store for obtaining a lease on the object for granting the node exclusive write access to the object.

Abstract: Techniques are provided for load balancing for IP failover. A backend address of a first node is identified as a routing destination to which a request is to be routed by a load balancer based upon a load balancer rule mapping a frontend address, specified by the request as a request destination, to the backend address of the first node. The request is routed to a primary network interface of the first node using the backend address. The first node has a loopback interface with an address matching the frontend address for routing the request to a destination data structure based upon the request maintaining the frontend address as the request destination. Health probes are used by the load balancer for detecting a failure of the first node in order to failover to routing requests to a second backend address of a second node.

Abstract: Techniques are provided for a high availability solution (e.g., a network attached storage (NAS) solution) with address preservation during switchover. A first virtual machine is deployed into a first domain and a second virtual machine is deployed into a second domain of a computing environment. The first and second virtual machines are configured as a node pair for providing clients with access to data stored within an aggregate comprising one or more storage structures within shared storage of the computing environment. A load balancer is utilized to manage logical interfaces used by clients to access the virtual machines. During switchover, the load balancer preserves an IP address used to mount and access a data share of the aggregate used by a client.