Replicating a file system
An illustrative data storage system is configured to replicate, from a source storage system to a target storage system, a pod that includes a file system constructed of block objects. The pod may be a storage system construct that groups storage entities within a namespace and supports operations on the storage entities as a group. The block objects may store metadata for individual files and directories of the file system and may support random read-write access to blocks of data associated with the files and directories of the file system.
1. A data storage system comprising:
a memory storing instructions; and
a processor communicatively coupled to the memory and configured to execute the instructions to:
replicate, from a source storage system to a target storage system, a pod that includes a file system constructed of block objects;
the pod being a storage system construct that groups storage entities within a namespace and supports operations on the storage entities as a group;
the block objects presented to the file system and mapping contents of files and directories of the file system to blocks of data associated with the files and directories of the file system, the block objects supporting random read-write access to ranges of bytes at a block level of the block objects.
2. The data storage system of claim 1 , wherein the processor is configured to execute the instructions to:
apply the replication of the pod to an additional file system that is added into the pod during the replication of the pod.
3. The data storage system of claim 1 , wherein the processor is configured to execute the instructions to:
synchronize an additional file system, which is to be added into the pod during the replication of the pod, between the source storage system and the target storage system before completing the addition of the additional file system into the pod.
4. The data storage system of claim 1 , wherein the processor is configured to execute the instructions to:
check for new block objects included in the pod that have not been replicated; and
replicate any identified new block objects from the source storage system to the target storage system.
5. The data storage system of claim 1 , wherein a replica of the file system on the target storage system becomes read-write accessible when transitioned from a demoted state to a promoted state.
6. The data storage system of claim 1 , wherein the file system on the source storage system and a replica of the file system on the target storage system are symmetrically accessible by a host.
7. The data storage system of claim 1 , wherein the processor is configured to execute the instructions to:
stretch the pod as a unit from the source storage system to a mirrored copy on the target storage system.
8. The data storage system of claim 1 , wherein the processor is configured to execute the instructions to:
asymmetrically replicate the pod on the source storage system to a separate pod on the target storage system, wherein a live version of the file system is only accessible and writable from either the source storage system or the target storage system at any one time.
9. The data storage system of claim 1 , wherein the processor is configured to execute the instructions to:
synchronously replicate the pod on the source storage system to the target storage system.
10. The data storage system of claim 1 , wherein the processor is configured to execute the instructions to:
use a snapshot-based replication model to replicate the pod on the source storage system to the target storage system.
11. The data storage system of claim 1 , wherein the processor is configured to execute the instructions to:
replicate the pod on the source storage system to a target pod on the target storage system;
wherein a modification to the pod on the source storage system is sent to the target pod on the target storage system and signaling completion of the modification to the pod on the source storage system does not require waiting for an indication that the modification completed on the target pod.
12. A method comprising:
replicating, from a source storage system to a target storage system, a pod that includes a file system constructed of block objects;
the pod being a storage system construct that groups storage entities within a namespace and supports operations on the storage entities as a group;
the block objects presented to the file system and mapping contents of files and directories of the file system to blocks of data associated with the files and directories of the file system, the block objects supporting random read-write access to ranges of bytes at a block level of the block objects.
13. The method of claim 12 , further comprising:
applying the replication of the pod to an additional file system that is added into the pod during the replication of the pod.
14. The method of claim 12 , further comprising:
synchronizing an additional file system, which is to be added into the pod during the
replication of the pod, between the source storage system and the target storage system before completing the addition of the additional file system into the pod.
15. The method of claim 12 , further comprising:
checking for new block objects included in the pod that have not been replicated; and
replicating any identified new block objects from the source storage system to the target storage system.
16. The method of claim 12 , further comprising:
transitioning a replica of the file system on the target storage system from a demoted state to a promoted state such that the replica become read-write accessible.
17. The method of claim 12 , wherein the file system on the source storage system and a replica of the file system on the target storage system are symmetrically accessible by a host.
18. The method of claim 12 , further comprising:
stretching the pod as a unit from the source storage system to a mirrored copy on the target storage system.
19. The method of claim 12 , further comprising:
asymmetrically replicating the pod on the source storage system to a separate pod on the target storage system, wherein a live version of the file system is only accessible and writable from either the source storage system or the target storage system at any one time.
20. A non-transitory computer-readable medium storing instructions executable by a processor to cause the processor to:
replicate, from a source storage system to a target storage system, a pod that includes a file system constructed of block objects;
the pod being a storage system construct that groups storage entities within a namespace and supports operations on the storage entities as a group;
the block objects presented to the file system and mapping contents of files and directories of the file system to blocks of data associated with the files and directories of the file system, the block objects supporting random read-write access to ranges of bytes at a block level of the block objects.