Vanakkam 🙏,

I am happy to announce that we officially support snapshot sizes up to 1 TB (976 Gib), overcoming our prior support of 5 GB databases. To manage large databases effectively, we are introducing a new Windows application - Snapshot Downloader (SD).

SD is an essential tool for downloading large backups directly on-premise infrastructure. It supports features like parallel downloading, intelligent resuming, fast decryption, and more. All download speeds get amplified by downloading via multiple socket streams.

More on SD will be uncovered in the coming weeks. For now, you can download the latest version from the downloads page.

Other notable changes include:

• Downloaded snapshots name now represent backup type & timestamp for better identification.
  • Old Naming: Db_x.bak
  • New Naming: Db_Full_2023-12-06_12-00-00.123__x.bak
• Petti Client: Migrate to a job-based backup mechanism for superior robustness. The client will now keep the necessary data on the drive until each step of the job is executed successfully. It also eliminates issues caused by disk crashes & poor bandwidth.
• Improve snapshot download speeds on the browser.

Vanakkam 🙏,

I am excited to announce that Petti 2.0.0 is up! We have implemented the previously requested features in this release because we love to serve our kings A.K.A customers.

• Support multiple database backups under a single integration: You no longer have to create separate integrations for each database. Now, all of them sit under one roof (integration) making it very easy to manage all db backups.
• Set backup frequency (Daily, 15 minutes, 30 minutes, Hourly, 2 hours, 4 hours, 6 hours, 8 hours, 12 hours). Frequency change will reflect in less than 2 minutes on the backup agent.
• Added email alerts for critical updates such as
  • when snapshot fails
  • when the backup agent goes offline
  • when the backup agent comes online
• Dashboard UI/UX Updates
  • Filter snapshots by database name
  • Allow backup name editing
  • More info on backup
    • Display SQL Server Backup Strategy [ex: Full backup (Copy Only)]
    • Display no. of snapshots
  • More info on snapshot
    • Display database name
    • Display time of snapshot
• Petti's Windows Client now displays a "Server Not Reachable" warning when the agent is connected but cannot communicate with the backend. Notifying this to our support will speed up in troubleshooting errors.

Happy Tuesday.

Best, Shiv.

Vanakkam 🙏,

We added a lot of new changes to better serve our kings.

• Added support for snapshots up to 5 GB in size.
• Improved backup download & upload speeds (Now it's 5X faster)
• Added new 'Timeout' error for backup job. It is useful for identifying unknown snapshot errors in the future.
• Improved dashboard UI & responsiveness at respective places.
• Added installation tutorial for MS SQL Windows Server Client.
• Added integration support for SQL Server 2019 on Windows Server 2016.
• Added cloud event logging for improved technical support. It can help our engineers view detailed information about failures on your server to better assist in troubleshooting.
• Postgres integration support (Linux) added to the roadmap.

Have a great day!

Best, Shiv.

Vanakkam 🙏,

We added 4 new sections to our website - Documentation, Roadmaps, Downloads, & Changelog.

We value our customers as kings. So, we added these to provide transparency over our previous, active, and future development.

Best, Shiv.

After leading an IT agency for over a decade, I have frequently encountered a persistent challenge that demands a solution. It's the backups. Every time I bring up the topic of backups. The clients resort to a janky solution.

Below are the top 2 solutions adopted by the companies.

Solution 1: Manual Backups by IT Administrator​

Pros:​

• Gets the job done

Cons:​

• Opportunity Cost
• Human Errors
• Slow

Solution 2: Using cron jobs.​

Pros:​

• Quick
• One-time engineering cost

Cons:​

• The backup script can fail in some scenarios
• No backup verification in most cases

Some script failure scenarios​

• Cron jobs have been reset
• Ransomware mutating the script
• Python 3.6-based backup script fails as the admin installs Python 3.7 for another project.

In both these solutions, there exist other problems​

1. Reliability​

No way to ensure the backup was successful.

2. Protection​

Vulnerable to ransomware, virus, hardware failure, platform suspension, and human error.

3. Security​

No encryption. Susceptible to data leaks & misuses.

4. Replication​

No redundancy. All data is in one local drive. Failure of the hard drive is an easy gateway to disaster. Backups errors cost a fortune and can severely damage a company's reputation. What is even worse? It is the end users. Imagine if Notion lost their weeks of backups. All their customers lose their previous weeks of work along with it.

At Petti, we address these issues by delivering a high-quality one-stop backup solution for any use case. It involves building an all-in-one dashboard that enables users to reliably manage & restore backups for any platform with just a few clicks.