Abstract
This is the second in a series of papers detailing results from on-going investigations of using Git - a distributed source control system - as a database backup and disaster recovery tool. The first paper, published early 2017 after 2,000 hours of data processing and simulations, warns that the default configuration of Git is unsuitable for database backups, but also shares configuration tweaks that make it safe and more space-efficient than zipped .sql archives - as low as only 1% of the storage space needed by .sql archives. This second paper focuses on optimization, looking specifically to identify which configuration tweaks and factors affect the reliability, scalability and efficiency of a Git-based database backup and disaster recovery system. Critical insights regarding the reliability and scalability of a Git-based database backup system were found after 6,000 hours of experimentation, centered around the problem of configuring Git to be able to handle .sql files measured in gigabytes.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: IOP Conference Series: Materials Science and Engineering
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
