Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Eraiyanbupeterfrancis/AutoBackupTool/llms.txt

Use this file to discover all available pages before exploring further.

Every time a backup completes successfully, AutoBackupTool appends a record to backup_log.json in the project directory. This file gives you a persistent, human-readable history of every backup you have run — including when it happened and where to find it on Google Drive.

​
Log file format

Each entry in backup_log.json is a JSON object with three fields. The file contains an array of these objects, one per backup: 
[
  {
    "file": "backup_20240115_220000.enc",
    "timestamp": "2024-01-15T22:00:03.412187",
    "cloud_link": "https://drive.google.com/file/d/..."
  }
]

​
Fields

FieldDescription
fileThe encrypted filename uploaded to Drive. Format: backup_YYYYMMDD_HHMMSS.enc
timestampISO 8601 datetime when the backup completed, generated by datetime.now().isoformat()
cloud_linkThe Google Drive alternateLink — a direct shareable link to the file on Drive

​
How the log is written

After each successful upload, log_backup() in backup_utils.py reads the existing log, appends the new entry, and writes the full array back to disk: 
def log_backup(filename, link):
    log_file = 'backup_log.json'
    log = []
    if os.path.exists(log_file):
        try:
            with open(log_file, 'r') as f:
                content = f.read().strip()
                if content:
                    log = json.loads(content)
        except json.JSONDecodeError:
            log = []
    log.append({
        'file': filename,
        'timestamp': datetime.now().isoformat(),
        'cloud_link': link
    })
    with open(log_file, 'w') as f:
        json.dump(log, f, indent=2)
If backup_log.json does not exist yet, the function creates it. If the file exists but contains invalid JSON, it resets gracefully and starts a fresh log rather than crashing.
backup_log.json grows with every backup and is never automatically pruned. The 5-backup limit enforced by AutoBackupTool applies only to files stored on Google Drive — it has no effect on local log entries. You can manually edit or archive backup_log.json at any time without affecting backup or restore functionality.
Use the cloud_link value in any log entry to jump directly to that backup file in your Google Drive browser. This is handy when you want to verify an upload or share a specific backup with someone else.

Build docs developers (and LLMs) love

Get started for freeTalk to us