Presenting cloud based storage as a virtual synthetic
In one example, a method is provided for presenting cloud based storage as a virtual synthetic. The method begins when file system information is requested from a datacenter server. The requested file system information is then received at the requesting client from the datacenter server. Next, the received file system information is presented at the client in the form of a virtual file system interface that makes the file system information appear as a local file system to a user at the client, notwithstanding that the file system is not actually present at the client. Finally, user access at the client is enabled, by way of the file system interface, to data residing in the file system at the datacenter server, where the data is in the form of a virtual synthetic that includes respective portions of data from each of a plurality of backups residing at the datacenter.
1. A method, comprising:
at a client, requesting file system information from a datacenter server of a datacenter, and the file system information is associated with a file system located at the datacenter server;
receiving, at the client, the requested file system information from the datacenter server;
presenting, at the client, the received file system information in the form of a virtual file system interface that makes the file system information appear as a local file system to a user at the client, notwithstanding that the file system is not actually present at the client;
enabling user access at the client, by way of the virtual file system interface, to data residing in the file system at the datacenter server;
translating, at the client, a file system request made by an application of the client, into a dataset request for data in a byte range that defines a subset of a dataset that resides at the datacenter and is used by the application, and the dataset request specifies the byte range;
transmitting to the datacenter, by the application at the client, the dataset request, the dataset request causing creation, at the datacenter, of a virtual synthetic that comprises an assemblage of respective portions of data from each of a plurality of different backups of the dataset residing at the datacenter server, wherein all the portions of data that make up the virtual synthetic are within the byte range, and one of the portions of data in the virtual synthetic is less than an entire file, and wherein the virtual synthetic did not exist separately at the datacenter server prior to the client request, and the virtual synthetic is less than a full backup of the dataset; and
accessing at the client, by way of the virtual file system interface, the virtual synthetic.
2. The method as recited in claim 1 , wherein the file system information includes an identification of the contents of a manifest that resides at the datacenter server.
3. The method as recited in claim 1 , further comprising performing, at the client, a file system operation with respect to data of the virtual synthetic.
4. The method as recited in claim 1 , wherein enabling user access at the client, by way of the virtual file system interface, to data residing in the file system at the datacenter server comprises:
selecting, at the client by way of the virtual file system interface, a particular dataset stored at the datacenter; and
mounting the particular dataset at the client.
5. The method as recited in claim 4 , further comprising accessing, by the client, a manifest having a list of datasets that lists the particular dataset.
6. The method as recited in claim 3 , further comprising uploading, from the client to the datacenter server, one or more changes associated with the filesystem operation.
7. The method as recited in claim 1 , wherein the plurality of different backups of the dataset comprises one or both of an incremental backup and a full backup.
8. The method as recited in claim 1 , wherein data communicated between the datacenter and the client is in an encrypted form.
9. The method as recited in claim 1 , wherein the byte range of the virtual synthetic is defined ad hoc at the client.
10. A non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, perform the operations comprising:
at a client, requesting file system information from a datacenter server, and the file system information is associated with a file system located at the datacenter server;
receiving, at the client, the requested file system information from the datacenter server;
presenting, at the client, the received file system information in the form of a virtual file system interface that makes the file system information appear as a local file system to a user at the client, notwithstanding that the file system is not actually present at the client;
enabling user access at the client, by way of the virtual file system interface, to data residing in the file system at the datacenter server;
translating, at the client, a file system request made by an application of the client, into a dataset request for data in a byte range that defines a subset of a dataset that resides at the datacenter and is used by the application, and the dataset request specifies the byte range;
transmitting to the datacenter, by the application at the client, the dataset request, the dataset request causing creation, at the datacenter, of a virtual synthetic that comprises an assemblage of respective portions of data from each of a plurality of different backups of the dataset residing at the datacenter server, wherein all the portions of data that make up the virtual synthetic are within the byte range, and one of the portions of data in the virtual synthetic is less than an entire file, and wherein the virtual synthetic did not exist separately at the datacenter server prior to the client request, and the virtual synthetic is less than a full backup of the dataset; and
accessing at the client, by way of the virtual file system interface, the virtual synthetic.
11. The non-transitory storage medium as recited in claim 10 , wherein the file system information includes an identification of the contents of a manifest that resides at the datacenter server.
12. The non-transitory storage medium as recited in claim 10 , wherein the operations further comprise performing, at the client, a file system operation with respect to data of the virtual synthetic.
13. The non-transitory storage medium as recited in claim 10 , wherein enabling user access at the client, by way of the virtual file system interface, to data residing in the file system at the datacenter server comprises:
selecting, at the client by way of the virtual file system interface, a particular dataset stored at the datacenter; and
mounting the particular dataset at the client.
14. The non-transitory storage medium as recited in claim 10 , further comprising accessing, by the client, a manifest having a list of datasets that lists the particular dataset.
15. The non-transitory storage medium as recited in claim 12 , wherein the operations further comprise uploading, from the client to the datacenter server, one or more changes associated with the filesystem operation.
16. The non-transitory storage medium as recited in claim 10 , wherein the plurality of different backups of the dataset comprises one or both of an incremental backup and a full backup.
17. The non-transitory storage medium as recited in claim 10 , wherein data communicated between the datacenter and the client is in an encrypted form.
18. The non-transitory storage medium as recited in claim 10 , wherein the byte range of the virtual synthetic is defined ad hoc at the client.
19. A physical device, wherein the physical device comprises:
one or more hardware processors; and
the non-transitory storage medium as recited in claim 10 .