SnipeIT – P9 Full SnipeIT on Ubuntu Manual Backup, Cron Schedule & Restore Tutorial

Backing up your Snipe-IT system is not optional — it is critical.

In production environments, Snipe-IT stores valuable asset data, user information, license tracking, and file uploads. A server crash, disk failure, or misconfiguration can result in permanent data loss if you do not have a proper backup strategy.

In this tutorial, you will learn how to:

• ✅ Perform a full Snipe-IT backup (files + database)

• ✅ Run manual backups via CLI

• ✅ Automate backups using cron jobs

• ✅ Restore Snipe-IT from backup

• ✅ Apply best practices for permissions and security

This guide works for:

• Ubuntu Server 20.04

• Ubuntu Server 22.04

• Newer Ubuntu versions

By the end of this tutorial, you will confidently manage Snipe-IT backup and disaster recovery.

#1. SnipeIT Manual Backup (Guide)

Snipe-IT provides a built-in backup feature from the web interface.

Steps:

Gui => Admin Setting => Backup => General Backup => Click Link Download

This method downloads a full backup archive including:

• Database dump

• Uploaded files

• Private uploads

• OAuth keys

• .env configuration file

⚠ Recommended for quick manual backup before system upgrades.

#2. Backup CLI (Manual + Schedule)

For production environments, CLI backup is highly recommended.

🔹 Manual Backup Command

Run:

The backup file will be stored at:

This command generates a ZIP file containing:

• Full MySQL dump

• public/uploads

• storage/private_uploads

• OAuth keys

• .env file

🔹 Scheduled Backup (Cron Job)

To automate backups:

Backup every day at 2AM:

Quick demo – backup every 2 minutes:

📌 Best Practice:

• Store backups on external storage

• Sync to NAS or offsite location

• Monitor log file: /var/log/snipeit-backup.log

Automation ensures your data is protected without manual effort.

#3. Restore

If your server crashes or you migrate to a new server, follow these steps.

Step 1: Identify the Backup File

List available backups:

Example:

Create temporary restore directory:

Unzip backup:

Locate SQL dump:

Example:

Step 2: Delete Old Database (Optional)

⚠ Only do this if performing a full restore (not migration).

Drop database:

Enter mysql root password (Previous video : Abc@1234)

Create new database:

Enter mysql root password (Previous video : Abc@1234)

Import database:

Step 3: Restore Files

#1 Restore File Uploads

#2 Restore Private Uploads

#3 Restore OAuth Keys

Set proper ownership and permissions:

#4 Restore the .env File

Step 4: Fix Permissions + Clear Cache

Navigate to Snipe-IT directory:

Fix ownership:

Set permissions:

Clear Laravel cache:

Step 5: Restart Service

🚀 Final Thoughts

A proper backup strategy is the backbone of any production Snipe-IT deployment.

With:

• Manual GUI backup

• CLI backup

• Cron automation

• Full restore procedure

You now have a complete disaster recovery workflow ( SnipeIT Manual Backup).

Whether running Snipe-IT in a lab, SMB environment, or enterprise infrastructure — mastering backup and restore ensures business continuity and data integrity.