Client object replication between a first backup server and a second backup server
First Claim
1. A computer program product for backing up objects from a client to a first backup server and a second backup server, wherein the computer program product comprises a computer readable storage medium having computer readable program code embodied therein that executes to perform operations, the operations comprising:
- backing-up objects from a client to the first backup server;
generating, by the first backup server, metadata on the objects from the client;
transmitting as part of a metadata-only replication command, by the first backup server, the metadata to the second backup server, wherein the objects represented by the transmitted metadata backed-up at the first backup server are not copied to the second backup server as part of the metadata-only replication command, and wherein while the objects are backed up to the first backup server, the second backup server maintains only client object metadata of the objects backed-up to the first backup server from the client;
determining that the first backup server is unavailable after transmitting the metadata as part of the metadata-only replication operation;
using the metadata at the second backup server to determine modifications to the objects at the client since the metadata was last generated in response to determining that the first backup server is unavailable; and
backing-up, by the client, the determined modifications to the objects to the second backup server to backup.
1 Assignment
0 Petitions
Accused Products
Abstract
Provided are a computer program product, system, and method for client object replication between a first backup server and a second backup server. Objects are backed-up from a client to a first backup server. The first backup server generates metadata on the objects from the client and transmits the metadata to a second backup server, wherein the objects backed-up at the first backup server are not copied to the second backup server. A determination is made that the first backup server is unavailable after transmitting the metadata. The metadata at the second backup server is used to determine modifications to the objects at the client since the metadata was last generated in response to determining that the first backup server is unavailable. The client backs-up the determined modifications to the objects to the second backup server to backup.
40 Citations
20 Claims
-
1. A computer program product for backing up objects from a client to a first backup server and a second backup server, wherein the computer program product comprises a computer readable storage medium having computer readable program code embodied therein that executes to perform operations, the operations comprising:
-
backing-up objects from a client to the first backup server; generating, by the first backup server, metadata on the objects from the client; transmitting as part of a metadata-only replication command, by the first backup server, the metadata to the second backup server, wherein the objects represented by the transmitted metadata backed-up at the first backup server are not copied to the second backup server as part of the metadata-only replication command, and wherein while the objects are backed up to the first backup server, the second backup server maintains only client object metadata of the objects backed-up to the first backup server from the client; determining that the first backup server is unavailable after transmitting the metadata as part of the metadata-only replication operation; using the metadata at the second backup server to determine modifications to the objects at the client since the metadata was last generated in response to determining that the first backup server is unavailable; and backing-up, by the client, the determined modifications to the objects to the second backup server to backup. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A system for backing up objects from a client implemented in at least one computing device, comprising:
-
a first backup server; a second backup server; a client; wherein the first backup server performs operations, the operations comprising; backing-up objects from the client; generating metadata on the objects from the client; transmitting as part of a metadata-only replication command the metadata to the second backup server, wherein the objects represented by the transmitted metadata backed-up at the first backup server are not copied to the second backup server as part of the metadata-only replication command, and wherein while the objects are backed up to the first backup server, the second backup server maintains only client object metadata of the objects backed-up to the first backup server from the client; wherein the client performs operations, the operations comprising; determining that the first backup server is unavailable after transmitting the metadata as part of the metadata-only replication operation; using the metadata at the second backup server to determine modifications to the objects at the client since the metadata was last generated in response to determining that the first backup server is unavailable; and backing-up the determined modifications to the objects to the second backup server to backup. - View Dependent Claims (11, 12, 13, 14, 15)
-
-
16. A method for backing up objects, comprising:
-
backing-up objects from a client to a first backup server; generating, by the first backup server, metadata on the objects from the client; transmitting, as part of a metadata-only replication command, by the first backup server, the metadata to a second backup server, wherein the objects represented by the transmitted metadata backed-up at the first backup server are not copied to the second backup server as part of the metadata-only replication command, and wherein while the objects are backed up to the first backup server, the second backup server maintains only client object metadata of the objects backed-up to the first backup server from the client; determining that the first backup server is unavailable after transmitting the metadata as part of the metadata-only replication operation; using the metadata at the second backup server to determine modifications to the objects at the client since the metadata was last generated in response to determining that the first backup server is unavailable; and backing-up, by the client, the determined modifications to the objects to the second backup server to backup. - View Dependent Claims (17, 18, 19, 20)
-
Specification