Abstract: Example implementations relate to application-specific policies for failing over from an edge site to a cloud. When an application becomes operational within an edge site, a discovery phase is performed by a local disaster recovery (DR) agent. I/O associated with a workload of the application is monitored. An I/O rate for data replication that satisfies latency characteristics of the application is predicted based on the incoming I/O. Based on results of tests against multiple clouds indicative of their respective RTO/RPO values, information regarding a selected cloud to serve as a secondary system is stored in an application-specific policy. The application-specific policy is transferred to a remote DR agent running in the selected cloud. Responsive to a failover event, infrastructure within a virtualized environment of the selected cloud is enabled to support a failover workload for the application based on the application-specific policy.

Abstract: Example implementations relate to application-specific policies for failing over from an edge site to a cloud. When an application becomes operational within an edge site, a discovery phase is performed by a local disaster recovery (DR) agent. I/O associated with a workload of the application is monitored. An I/O rate for data replication that satisfies latency characteristics of the application is predicted based on the incoming I/O. Based on results of tests against multiple clouds indicative of their respective RTO/RPO values, information regarding a selected cloud to serve as a secondary system is stored in an application-specific policy. The application-specific policy is transferred to a remote DR agent running in the selected cloud. Responsive to a failover event, infrastructure within a virtualized environment of the selected cloud is enabled to support a failover workload for the application based on the application-specific policy.

Abstract: Examples described herein relate to method and system for managing write modes of a filesystem, wherein the filesystem is mapped to a thinly-provisioned virtual volume (TPVV) defined using a common-provisioning group (CPG) of a set of physical storage devices. The filesystem may be operated in a read-write mode. A used storage capacity of the CPG may be monitored when the filesystem is operational in the read-write mode. Further, a check may be performed to determine whether the used storage capacity of the CPG has reached a storage fullness threshold value. Accordingly, if it is determined that the used storage capacity of the CPG has reached the storage fullness threshold value, the filesystem may be transitioned to a partial read-only mode from the read-write mode.

Abstract: Example implementations relate to multi-protocol access control lists. In an example, a multi-protocol access control list (ACL) is maintained in an extended attribute of an object stored in a file store. The multi-protocol ACL holds a primary ACL in a format associated with a primary protocol of a file store and a secondary ACL in a format associated with a secondary protocol.

Abstract: Some examples relate to updating of metadata of objects in a file system. In an example, in response to an invocation by an application to update metadata related to a plurality of objects of a file system, an API may initialize a new metadata deduplication database based on an active metadata deduplication database that includes the metadata related to the plurality of objects and a deduplication key linked with the metadata. API may add new metadata to the new metadata deduplication database. API may associate a new deduplication key with the new metadata in the new metadata deduplication database. API may initialize a new translation database. API may add the new deduplication key to the new translation database. API may associate the respective object IDs of the plurality of objects with the new deduplication key in the new translation database.

Abstract: Example implementations relate to multi-protocol access control lists. In an example, a multi-protocol access control list (ACL) is maintained in an extended attribute of an object stored in a file store. The multi-protocol ACL holds a primary ACL in a format associated with a primary protocol of a file store and a secondary ACL in a format associated with a secondary protocol.