Abstract: Provided are techniques for providing a global unique identifier for a storage volume. Under control of a storage initiator, a Global Universally Unique Identifier (GUUID) is identified for a storage volume of a storage device in a cloud system storing a plurality of storage devices, wherein the GUUID is generated for use with an ATA over Ethernet (AoE) protocol. The GUUID is stored in bytes of a packet header structure. Metadata is stored in remaining portions of the packet header structure. A request with the packet header structure is sent to a storage target.

Abstract: A request for changing data of a file system data structure stored on a shingled magnetic recording (SMR) drive is received. The data change is logged in a log entry of a log structure stored in a non-volatile random access memory (NVRAM). The log entry is added as a new entry at an end of the log structure. The log entry is marked within the NVRAM as modified and a predetermined criterion is determined to be satisfied. Responsive to determining that the predetermined criterion is satisfied, the NVRAM is searched for log entries marked as modified. The modified log entries are stored to the SMR drive.

Abstract: Provided are techniques for providing a global unique identifier for a storage volume. Under control of a storage initiator, a Global Universally Unique Identifier (GUUID) is identified for a storage volume of a storage device in a cloud system storing a plurality of storage devices, wherein the GUUID is generated for use with an ATA over Ethernet (AoE) protocol. The GUUID is stored in bytes of a packet header structure. Metadata is stored in remaining portions of the packet header structure. A request with the packet header structure is sent to a storage target.

Abstract: A current minimum memory requirement for each memory consumer of one or more memory consumers of a primary database system is received. A current memory allocation for a standby database system is received. A set of benefit-to-cost metrics is received. A benefit-to-cost metric is a measure of whether each memory consumer would benefit or would not benefit from additional memory. The set of benefit-to-cost metrics is applied to the standby database system to define an upper bound memory allocation of the standby database system to function in the event of a failover from the primary database system. A scaling factor is determined. In response to receiving an indication of a failover of the primary database system to the standby database system, a ramp up of the standby database system is monitored. The ramp up of the standby database system uses the set of benefit-to-cost metrics and the determined scaling factor.

Abstract: Provided are techniques for providing a global unique identifier for a storage volume. Under control of a storage initiator, a Global Universally Unique Identifier (GUUID) is identified for a storage volume of a storage device in a cloud system storing a plurality of storage devices, wherein the GUUID is generated for use with an ATA over Ethernet (AoE) protocol. The GUUID is stored in bytes of a packet header structure. Metadata is stored in remaining portions of the packet header structure. A request with the packet header structure is sent to a storage target.

Abstract: Provided are techniques for providing a global unique identifier for a storage volume. Under control of a storage initiator, a Global Universally Unique Identifier (GUUID) is identified for a storage volume of a storage device in a cloud system storing a plurality of storage devices, wherein the GUUID is generated for use with an ATA over Ethernet (AoE) protocol. The GUUID is stored in bytes of a packet header structure. Metadata is stored in remaining portions of the packet header structure. A request with the packet header structure is sent to a storage target.

Abstract: A request for changing data of a file system data structure stored on a shingled magnetic recording (SMR) drive is received. The data change is logged in a log entry of a log structure stored in a non-volatile random access memory (NVRAM). The log entry is added as a new entry at an end of the log structure. The log entry is marked within the NVRAM as modified and a predetermined criterion is determined to be satisfied. Responsive to determining that the predetermined criterion is satisfied, the NVRAM is searched for log entries marked as modified. The modified log entries are stored to the SMR drive.

Abstract: A request for changing data of a file system data structure stored on a shingled magnetic recording (SMR) drive is received. The data change is logged in a log entry of a log structure stored in a non-volatile random access memory (NVRAM). The log entry is added as a new entry at an end of the log structure. The log entry is marked within the NVRAM as modified and a predetermined criterion is determined to be satisfied. Responsive to determining that the predetermined criterion is satisfied, the NVRAM is searched for log entries marked as modified. The modified log entries are stored to the SMR drive.

Abstract: A request for changing data of a file system data structure stored on a shingled magnetic recording (SMR) drive is received. The data change is logged in a log entry of a log structure stored in a non-volatile random access memory (NVRAM). The log entry is added as a new entry at an end of the log structure. The log entry is marked within the NVRAM as modified and a predetermined criterion is determined to be satisfied. Responsive to determining that the predetermined criterion is satisfied, the NVRAM is searched for log entries marked as modified. The modified log entries are stored to the SMR drive.

Abstract: A request for changing data of a file system data structure stored on a shingled magnetic recording (SMR) drive is received. The data change is logged in a log entry of a log structure stored in a non-volatile random access memory (NVRAM). The log entry is added as a new entry at an end of the log structure. The log entry is marked within the NVRAM as modified and a predetermined criterion is determined to be satisfied. Responsive to determining that the predetermined criterion is satisfied, the NVRAM is searched for log entries marked as modified. The modified log entries are stored to the SMR drive.

Abstract: A request for changing data of a file system data structure stored on a shingled magnetic recording (SMR) drive is received. The data change is logged in a log entry of a log structure stored in a non-volatile random access memory (NVRAM). The log entry is added as a new entry at an end of the log structure. The log entry is marked within the NVRAM as modified and a predetermined criterion is determined to be satisfied. Responsive to determining that the predetermined criterion is satisfied, the NVRAM is searched for log entries marked as modified. The modified log entries are stored to the SMR drive.

Abstract: A current minimum memory requirement for each memory consumer of one or more memory consumers of a primary database system is received. A current memory allocation for a standby database system is received. A set of benefit-to-cost metrics is received. A benefit-to-cost metric is a measure of whether each memory consumer would benefit or would not benefit from additional memory. The set of benefit-to-cost metrics is applied to the standby database system to define an upper bound memory allocation of the standby database system to function in the event of a failover from the primary database system. A scaling factor is determined. In response to receiving an indication of a failover of the primary database system to the standby database system, a ramp up of the standby database system is monitored. The ramp up of the standby database system uses the set of benefit-to-cost metrics and the determined scaling factor.

Abstract: A current minimum memory requirement for each memory consumer of one or more memory consumers of a primary database system is received. A current memory allocation for a standby database system is received. A set of benefit-to-cost metrics is received. A benefit-to-cost metric is a measure of whether each memory consumer would benefit or would not benefit from additional memory. The set of benefit-to-cost metrics is applied to the standby database system to define an upper bound memory allocation of the standby database system to function in the event of a failover from the primary database system. A scaling factor is determined. In response to receiving an indication of a failover of the primary database system to the standby database system, a ramp up of the standby database system is monitored. The ramp up of the standby database system uses the set of benefit-to-cost metrics and the determined scaling factor.

Abstract: A current minimum memory requirement for each memory consumer of one or more memory consumers of a primary database system is received. A current memory allocation for a standby database system is received. A set of benefit-to-cost metrics is received. A benefit-to-cost metric is a measure of whether each memory consumer would benefit or would not benefit from additional memory. The set of benefit-to-cost metrics is applied to the standby database system to define an upper bound memory allocation of the standby database system to function in the event of a failover from the primary database system. A scaling factor is determined. In response to receiving an indication of a failover of the primary database system to the standby database system, a ramp up of the standby database system is monitored. The ramp up of the standby database system uses the set of benefit-to-cost metrics and the determined scaling factor.

Abstract: A current minimum memory requirement for each memory consumer of one or more memory consumers of a primary database system is received. A current memory allocation for a standby database system is received. A set of benefit-to-cost metrics is received. A benefit-to-cost metric is a measure of whether each memory consumer would benefit or would not benefit from additional memory. The set of benefit-to-cost metrics is applied to the standby database system to define an upper bound memory allocation of the standby database system to function in the event of a failover from the primary database system. A scaling factor is determined. In response to receiving an indication of a failover of the primary database system to the standby database system, a ramp up of the standby database system is monitored. The ramp up of the standby database system uses the set of benefit-to-cost metrics and the determined scaling factor.

Abstract: A current minimum memory requirement for each memory consumer of one or more memory consumers of a primary database system is received. A current memory allocation for a standby database system is received. A set of benefit-to-cost metrics is received. A benefit-to-cost metric is a measure of whether each memory consumer would benefit or would not benefit from additional memory. The set of benefit-to-cost metrics is applied to the standby database system to define an upper bound memory allocation of the standby database system to function in the event of a failover from the primary database system. A scaling factor is determined. In response to receiving an indication of a failover of the primary database system to the standby database system, a ramp up of the standby database system is monitored. The ramp up of the standby database system uses the set of benefit-to-cost metrics and the determined scaling factor.