Method for coordinating peer-to-peer replicated backup and versioning based on usage metrics acquired from peer client
View Patent ↗Techniques are presented for peer-to-peer (P2P) replicated backup and versioning. Peer clients register and share storage with one another for purposes of P2P data replication, data versioning, and/or data restoration via a P2P server. The P2P server also provides security and management between the peer clients. Moreover, the P2P sever can audit behaviors of the peer clients and take punitive actions against any of the peer clients that violate policy.
1. A machine-implemented method to process on a processor-enabled device, comprising:
receiving, by the processor-enabled device, a registration request from a first peer client;
interactively acquiring, by the processor-enabled device, usage metrics from the first peer client, the usage metrics including a time zone for the first peer client, times during a day that the first peer client is online, and an estimated amount of time that the first peer client is online during the data;
dividing, by the processor-enabled device, first-peer-client storage on the first peer client into a configurable number of slots in response to some of the usage metrics;
allocating, by the processor-enabled device, a first number of the slots on the first peer client for exclusive use of the first peer client;
determining, by the processor-enabled device, a maximum number of second peer clients that the first peer client can use for data replication or data versioning of the first number of the slots, the data replication and data versioning occur via a peer-to-peer (P2P) communication between the first peer client and each of the second peer clients; and
registering, by the processor-enabled device, the first peer client, the slots, and the maximum number of second peer clients for P2P data sharing and data management, the second peer clients selected based on the usage metrics acquired from the first peer client.
2. The method of claim 1 , wherein interactively acquiring further includes determining from the first peer client the usage metrics representing a total size of the first-peer-client storage to use for the P2P data sharing and data management, and a requested number of the second peer clients that the first peer client wants to use for the P2P data sharing and data management.
3. The method of claim 2 , wherein determining further includes calculating the total size as a product for a first peer client provided data size to share with the second peer clients multiplied by a sum associated with adding one to the requested number of the second peer clients that the first peer client wants to use.
4. The method of claim 3 , wherein dividing further includes determining the configurable number of the slots by dividing the total size by the sum, and wherein each slot is of an equal size with remaining ones of the slots.
5. The method of claim 2 , wherein determining further includes calculating the total size as a product for a first peer client provided data size to share with the second peer clients multiplied by the requested number of the second peer clients that the first peer client wants to use.
6. The method of claim 5 , wherein allocating further includes resolving the first number of slots by dividing the configurable number of slots by the requested number of the second peer clients.
7. The method of claim 1 further comprising:
monitoring, by the processor-enabled device, actions of the first peer client in relation to the second peer clients once the first peer client begins participating in the P2P data sharing and management with the second peer clients; and
deregistering, by the processor-enabled device, the first peer client when the actions violate a policy or violate a threshold.
8. A machine-implemented method to execute on a processor-enabled device, comprising:
receiving, by the processor-enabled device, a request from a first peer client to connect to another peer client for data replication, data versioning, or data restoration;
supplying, by the processor-enabled device, a list of second peer clients having one or more second peer clients, the list is supplied to the first peer client;
acquiring, by the processor-enabled device, a selected second peer client received from the first peer client and selected from the list;
incrementing, by the processor-enabled device, a serial number representing a total number of other peer clients currently connected to the selected peer client, and the serial number is incremented to reflect a connection to the selected peer client by the first peer client, the serial number evaluated to determine when requesting ones of the second peer clients are attempting to connect with the first peer client to decide whether to permit such attempted connections; and
signing, by the processor-enabled device, the serial number and supplying the signed serial number to the first peer client.
9. The method of claim 8 , wherein receiving further includes receiving the request from an automated service running on the first peer client that processes when it detects that a file has been modified on the first peer client and then automatically makes the request to version the file.
10. The method of claim 8 , wherein supplying further includes determining for inclusion within the list those available second peer clients that can currently receive at least one more connection from the first peer client.
11. The method of claim 8 , wherein acquiring further includes determining that when the selected second peer client is acquired that the selected second peer client cannot accept a current connection and in response thereto asking the first peer client to wait or hold until a particular connection is terminated with the selected second peer client.
12. The method of claim 8 , wherein incrementing further includes producing a packet that includes the serial number and that is supplied to the first peer client, and wherein the packet includes a time period for which the first peer client can connect to the selected second peer client and unique identifiers identifying the first peer client and the selected second peer client.
13. The method of claim 12 , wherein producing further includes determining the time period by considering a variety of factors that include: how much time the selected second peer client has been burdened with shared data requests within a last configurable period of time, how many connection requests were made of the selected second peer client in the last configurable period of time, and how many times the first peer client connected to the selected second peer client in the last configurable period of time.
14. The method of claim 13 , wherein determining further includes ensuring that a minimum time period is assigned to the packet when the time period falls below a threshold.