Pre-seeding Backup Data Across Multiple Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data backup methods are inefficient and risk losing data due to server malfunctions or destructive events, as they rely heavily on a single server for backup and increase bandwidth on the client device.
Innovation Solution
A system and method for pre-seeding data to multiple backup servers, where initial backup data is stored on a primary server and then seeded to secondary servers, allowing additional metadata or data to be sent directly to available servers, reducing reliance on a single server and minimizing client device bandwidth usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If backup data is sent to a single primary server, then the backup process is simple to manage, but the system reliability decreases and bandwidth usage on client device increases
Solution Approach 1:
The backup system segments the backup destination into multiple servers (primary server and secondary servers). The backup data is divided and distributed across these servers, with the primary server receiving initial backups and secondary servers receiving additional backups. This segmentation improves reliability by preventing single-point failure while distributing the backup load.
Solution Approach 2:
The system performs preliminary actions by pre-configuring multiple backup servers and establishing backup relationships before actual backup operations. The primary server is pre-configured with instructions to forward backups to secondary servers, so that when backup operations occur, the multi-server architecture is already in place to handle the data flow efficiently.
2Reliability
If backup data is sent to multiple servers directly from client device, then data safety improves, but bandwidth usage on client device increases
Solution Approach 1:
The primary server acts as an intermediary between the client device and secondary backup servers. The client device sends backup data only to the primary server, which then automatically forwards copies to secondary servers. This intermediary approach ensures data safety through multiple backups while minimizing bandwidth consumption on the client device, as it only needs to transmit data once.
3Device complexity
If all backup data is transmitted through primary server to multiple secondary servers, then data distribution is simplified, but backup time increases
Solution Approach 1:
The system performs preliminary actions by pre-configuring multiple backup servers and establishing backup relationships before actual backup operations. The primary server is pre-configured with instructions to forward backups to secondary servers, so that when backup operations occur, the multi-server architecture is already in place to handle the data flow efficiently.
Solution Approach 2:
The backup process maintains continuity by enabling parallel operations. While the primary server receives backups from the client device, it simultaneously forwards data to secondary servers without waiting for confirmation from each transfer. This continuous action reduces overall backup time while maintaining the simplified architecture of client-to-primary-server communication.
Data Source
AI summary
A system and a method are disclosed for pre-seeding data to backup servers and determining servers for additional backups. Backup data is received from a client device through a first backup request and sent to a primary server for storage. Additional backup data from a second backup request is received. After the initial backup data is stored on the primary server and pre-seeded by the primary server on a secondary server, a status of backup servers associated with the client device is received. The backup servers include the primary server and can include the secondary server. Responsive to the status indicating availability of a server in the backup servers, a recipient server is identified from the backup servers and the additional backup data is sent to the identified recipient server.