Abstract: Techniques are provided for timestamp consistency. An operation targeting a first storage object having a synchronous replication relationship with a second storage object is intercepted. A timestamp is assigned to the operation. A replication operation is created as a replication of the operation. The same timestamp is assigned to the replication operation. The operation is implemented upon the first storage object and the replication operation is implemented upon the second storage object.

Abstract: Techniques are provided for inofile management and access control list file handle parity. For example, operations targeting a first storage object of a first node are replicated to a second storage object of a second node. A size of an inofile maintained by the second node is increased if an inode number to be allocated by the replication operation is greater than a current size of the inofile. Access control list file handle parity is achieved by maintaining parity between inode number and generation number pairings of the first node and the second node.

Abstract: Techniques are provided for inofile management and access control list file handle parity. For example, operations targeting a first storage object of a first node are replicated to a second storage object of a second node. A size of an inofile maintained by the second node is increased if an inode number to be allocated by the replication operation is greater than a current size of the inofile. Access control list file handle parity is achieved by maintaining parity between inode number and generation number pairings of the first node and the second node.

Abstract: Techniques are provided for timestamp consistency. An operation targeting a first storage object having a synchronous replication relationship with a second storage object is intercepted. A timestamp is assigned to the operation. A replication operation is created as a replication of the operation. The same timestamp is assigned to the replication operation. The operation is implemented upon the first storage object and the replication operation is implemented upon the second storage object.

Abstract: Techniques are provided for inofile management and access control list file handle parity. For example, operations targeting a first storage object of a first node are replicated to a second storage object of a second node. A size of an inofile maintained by the second node is increased if an inode number to be allocated by the replication operation is greater than a current size of the inofile. Access control list file handle parity is achieved by maintaining parity between inode number and generation number pairings of the first node and the second node.

Abstract: Techniques are provided for timestamp consistency. An operation targeting a first storage object having a synchronous replication relationship with a second storage object is intercepted. A timestamp is assigned to the operation. A replication operation is created as a replication of the operation. The same timestamp is assigned to the replication operation. The operation is implemented upon the first storage object and the replication operation is implemented upon the second storage object.

Abstract: Techniques are provided for timestamp consistency. An operation targeting a first storage object having a synchronous replication relationship with a second storage object is intercepted. A timestamp is assigned to the operation. A replication operation is created as a replication of the operation. The same timestamp is assigned to the replication operation. The operation is implemented upon the first storage object and the replication operation is implemented upon the second storage object.

Abstract: Techniques are provided for inofile management and access control list file handle parity. For example, operations targeting a first storage object of a first node are replicated to a second storage object of a second node. A size of an inofile maintained by the second node is increased if an inode number to be allocated by the replication operation is greater than a current size of the inofile. Access control list file handle parity is achieved by maintaining parity between inode number and generation number pairings of the first node and the second node.

Abstract: A method includes receiving a change in a primary configuration of a primary storage node while the primary storage node is operational, wherein primary data stored in the primary storage node is to be backed up as backup data in a backup storage node. The method includes locating at least one identifier in the change that identifies the primary storage node. The method includes replacing the at least one identifier in the change that identifies the primary storage node with an identification of the backup storage node to create an updated configuration change. The method includes updating a backup configuration of the backup storage node based on the updated configuration change.

Abstract: A method includes receiving a change in a primary configuration of a primary storage node while the primary storage node is operational, wherein primary data stored in the primary storage node is to be backed up as backup data in a backup storage node. The method includes locating at least one identifier in the change that identifies the primary storage node. The method includes replacing the at least one identifier in the change that identifies the primary storage node with an identification of the backup storage node to create an updated configuration change. The method includes updating a backup configuration of the backup storage node based on the updated configuration change.