Instant recovery as an enabler for uninhibited mobility between primary storage and secondary storage
In accordance with some aspects of the present disclosure, a non-transitory computer readable medium is disclosed. In some embodiments, the non-transitory computer readable medium includes instructions that, when executed by a processor, cause the processor to receive, from a workload hosted on a host of a cluster, first I/O traffic programmed according to a first I/O traffic protocol supported by a cluster-wide storage fabric exposed to the workload as being hosted on the same host. In some embodiments, the workload is recovered by a hypervisor hosted on the same host. In some embodiments, the non-transitory computer readable medium includes the instructions that, when executed by the processor, cause the processor to adapt the first I/O traffic to generate second I/O traffic programmed according to a second I/O traffic protocol supported by a repository external to the storage fabric and forward the second I/O traffic to the repository.
1. A non-transitory computer readable medium comprising instructions that, when executed by a processor, cause the processor to:
receive, from a workload hosted on a host of a cluster comprising a plurality of hosts, wherein the workload is recovered and launched by a hypervisor hosted on the same host, first I/O traffic of the recovered workload programmed according to a first I/O traffic protocol supported by a cluster-wide storage fabric shared across the plurality of hosts, the storage fabric exposed to the recovered workload as being hosted on the same host by a virtual disk controller which virtualizes storage resources of the storage fabric;
adapt the first I/O traffic to generate second I/O traffic of the recovered workload programmed according to a second I/O traffic protocol supported by a repository external to the storage fabric and the cluster of hosts, wherein the repository is not virtualized by the virtual disk controller; and
forward the second I/O traffic of the recovered workload to the repository.
2. The medium of claim 1 , comprising the instructions stored thereon that, when executed by the processor, further cause the processor to:
expose a data source of the repository as a virtual disk.
3. The medium of claim 2 , comprising the instructions stored thereon that, when executed by the processor, further cause the processor to:
map the virtual disk to a uniform resource locator (URL) of the data source.
4. The medium of claim 2 , comprising the instructions stored thereon that, when executed by the processor, further cause the processor to:
adapt the first I/O traffic in the virtual disk to generate the second I/O traffic.
5. The medium of claim 2 , comprising the instructions stored thereon that, when executed by the processor, further cause the processor to:
clone the first I/O traffic from the virtual disk to a second virtual disk; and
adapt the first I/O traffic in the second virtual disk to generate the second I/O traffic.
6. The medium of claim 1 , wherein the recovered workload is instantly recovered by immediately restoring the workload from a data source of the repository.
7. The medium of claim 1 , wherein the recovered workload is instantly recovered from one or more snapshots stored on a data source of the repository.
8. The medium of claim 1 , wherein the hypervisor, the virtual disk controller and the storage fabric are tightly coupled in a hyperconverged infrastructure.
9. An apparatus comprising a processor and a memory, wherein the memory includes programmed instructions that, when executed by the processor, cause the apparatus to:
receive, from a workload hosted on a host of a cluster comprising a plurality of hosts, wherein the workload is recovered and launched by a hypervisor hosted on the same host, first I/O traffic of the recovered workload programmed according to a first I/O traffic protocol supported by a cluster-wide storage fabric shared across the plurality of hosts, the storage fabric exposed to the recovered workload as being hosted on the same host by a virtual disk controller which virtualizes storage resources of the storage fabric;
adapt the first I/O traffic to generate second I/O traffic of the recovered workload programmed according to a second I/O traffic protocol supported by a repository external to the storage fabric and the cluster of hosts, wherein the repository is not virtualized by the virtual disk controller; and
forward the second I/O traffic of the recovered workload to the repository.
10. The apparatus of claim 9 , wherein the memory includes the programmed instructions that, when executed by the processor, further cause the apparatus to:
expose a data source of the repository as a virtual disk.
11. The apparatus of claim 10 , wherein the memory includes the programmed instructions that, when executed by the processor, further cause the apparatus to:
map the virtual disk to a uniform resource locator (URL) of the data source.
12. The apparatus of claim 10 , wherein the memory includes the programmed instructions that, when executed by the processor, further cause the apparatus to:
adapt the first I/O traffic in the virtual disk to generate the second I/O traffic.
13. The apparatus of claim 10 , wherein the memory includes the programmed instructions that, when executed by the processor, further cause the apparatus to:
clone the first I/O traffic from the virtual disk to a second virtual disk; and
adapt the first I/O traffic in the second virtual disk to generate the second I/O traffic.
14. The apparatus of claim 9 , wherein the recovered workload is instantly recovered by immediately restoring the workload from a data source of the repository.
15. The apparatus of claim 9 , wherein the recovered workload is instantly recovered from one or more snapshots stored on a data source of the repository.
16. The apparatus of claim 9 , wherein the hypervisor, the virtual disk controller and the storage fabric are tightly coupled in a hyperconverged infrastructure.
17. A computer-implemented method comprising:
receiving, from a workload hosted on a host of a cluster comprising a plurality of hosts, wherein the workload is recovered and launched by a hypervisor hosted on the same host, first I/O traffic of the recovered workload programmed according to a first I/O traffic protocol supported by a cluster-wide storage fabric shared across the plurality of hosts, the storage fabric exposed to the recovered workload as being hosted on the same host by a virtual disk controller which virtualizes storage resources of the storage fabric;
adapting the first I/O traffic to generate second I/O traffic of the recovered workload programmed according to a second I/O traffic protocol supported by a repository external to the storage fabric and the cluster of hosts, wherein the repository is not virtualized by the virtual disk controller; and
forwarding the second I/O traffic of the recovered workload to the repository.
18. The method of claim 17 , further comprising:
exposing a data source of the repository as a virtual disk.
19. The method of claim 18 , further comprising:
mapping the virtual disk to a uniform resource locator (URL) of the data source.
20. The method of claim 18 , further comprising:
adapting the first I/O traffic in the virtual disk to generate the second I/O traffic.
21. The method of claim 18 , further comprising:
cloning the first I/O traffic from the virtual disk to a second virtual disk; and
adapting the first I/O traffic in the second virtual disk to generate the second I/O traffic.
22. The method of claim 17 , wherein the recovered workload is instantly recovered by immediately restoring the workload from a data source of the repository.
23. The method of claim 17 , wherein the recovered workload is instantly recovered from one or more snapshots stored on a data source of the repository.
24. The method of claim 17 , wherein the hypervisor, the virtual disk controller and the storage fabric are tightly coupled in a hyperconverged infrastructure.