How it works: Brief introduction

This is a brief introduction of how TTO Backup works

📘

TTO Backup functionality

TTO Backup is still under heavy development. The current functionality of this tool works on a basic level, but there are features that still aren't available yet, such as Gmail backup and restore. These are on the development roadmap, but not functional at this time (v 0.89)

For an overall view of the project and where it's going, visit https://waffle.io/mtucker6784/tto-googlebackup!

You will configure TTO Backup to use a domain wide delegation account (information provided under "Configuring Google Apps") which will let the program gain access to all your users' data for backup and restore purposes.

TTO Backup manipulates what Google calls "tokens". TTO Backup writes to 5 separate files inside each user directory which contain:

Current google token, Filename Token Ids, actual file name, mimetype format, foldername Id, foldername name, parent folder id (if applicable).

TTO Backup records the current token of the user (as Google Apps sees it), then as the program goes through the downloads for the user, it records the token it's currently on. This allows TTO Backup to resume from the last file recorded the next time the backup process is ran (so in short, it can automatically resume from last stop point)

TTO Backup does not support files revisions at this time. It's a thought, but not sure if it's something I will commit to as my production backup tool provides me this functionality. If it's something that may be desired by others, we can look into the concept.

This is an FOSS program hosted on Github at https://github.com/mtucker6784/tto-googlebackup/. Please feel free to view the source, perform edits/improvements/enhancements and open pull requests so that I may view and merge the code into the program. When doing a PR, please merge against the develop branch.

At this time, TTO Backup can:
Backup all your user's drives
Restore single file by right click and choosing "Restore"
The file is then restored in the user's root directory as its original filename with a random generation of characters as to not overwrite any existing file.

Example, If I restored a file named "MikeTucker" under my own drive, it'll show up under my Google Drive's root directory as "MikeTucker_"