This article explains the differences between FTP storage, a snapshot, an image, and a backup package.
In contrast, the purpose of a backup is to store data in the short and medium term, providing a regular snapshot of the data in question. This concept allows copies of whole data sets to be made so that they can be swapped out to external storage or a cloud environment and restored at a later date. One of the common abuse of language in Virtualisation is the use of the term snapshot to designate a backup.Let me explain the fundamental difference between a virtual machine snapshot and backup. Virtual machine snapshot. Both VMware and Hyper-V snapshots capture the state (eg. Powered-on, powered-off, suspended), data. If you are running SQL Server Enterprise, the granular backup system can optionally use SQL Server database snapshots to make sure that data remains consistent while the backup or export is in progress. After you create a snapshot, SharePoint Server uses it to create the backup or export package, and then deletes the snapshot. A snapshot backup can also be scheduled to occur at a certain frequency. A snapshot backup is an important data-protection tool for VMs, but it should not be the only backup technique. The VM snapshot backup process treats virtual machine disk files as a single file, so the entire instance must be restored to recover a lost text or deleted note.
With FTP Storage, you can store your data in a secure location that is physically separate from your servers. Only your servers have access to your data via a secure FTP connection. For access, you only need an FTP program. This storage method can be used with almost any operating system and backup tool.
A Snapshot is a copy of the current state of your server's data. Once you have taken a snapshot, you can restore the recorded state of your server's data whenever you need to do so. This can be useful, for example, if you are testing a new application, new software, or a change to the settings in your operating system. You can take one snapshot per server. This will be deleted automatically after 3 days.
An image is a complete backup copy of your server that can be stored in the IONOS Cloud Panel for a long time.
You can use an image to restore a server. Alternatively, you can use an image to install another server. This clones the original server.
Images can be created manually or automatically at regular intervals. The data to be backed up is not compressed during image creation.
Database Snapshot Vs Backup
A backup package is particularly useful for planned, medium and long-term backups. With a backup package, you can back up and restore the servers you host in an IONOS data center. Your back ups are managed from the backup console. To perform backups, you must install the Backup Agent on the server to be backed up and register the server in the Backup Console.
The backup console offers you a variety of configuration options for your backups. When configuring a backup plan, you can specify, for example, whether the entire server, individual drives, or individual files are to be backed up. You can also use the Backup Console to set a schedule, set the desired retention period and compression level, and enable encryption of your backups. You can also map complex backup routines by configuring multiple backup plans. The monthly price for the backups you create is calculated based on the size of the disk space used.
What does a snapshot do?
In short snapshots are versioning, or the ability to undo a change. If you take a snapshot every hour, for example, then all your files or folders can be reverted back to the state they were at the time of any of your snapshots. So, if you get a virus, then you can just revert your files, folders, or whole volume to the state it was before you got the virus
How is this different than a backup?
A backup is a complete copy of your data. So, if you have 5TB of data each copy will take up an additional 5TB of space. If you make a backup every 1 hour, then after just 10 hours, your backups would take 50TB of space. For this reason, it is not common to save many versions of your backups and backups are not good for versioning.
Snapshots are great for versioning because they are not backups and they can have many versions without taking up much space. A snapshot only needs to save enough information to undo a change and that makes it take less space than a backup.
How do QNAP’s block-level snapshots work?
When you take a snapshot, the metadata recording where each block of data is stored is copied to the snapshot. This takes very little space and the snapshot is created very quickly. From then on, any time you change a block of data, that block is written to a designated snapshot space. The current metadata is updated to reflect the change as well. This procedure is called “Redirect on write”.
Because your snapshot has the metadata, it can recognize what blocks of data have been added or changed since the creation of the snapshot. If you revert to one of your snapshots, every block of data that was added or changed since the snapshot was taken is removed from where it is saved in the snapshot. Then every block of data is as it was at the time the snapshot was taken. And since your files are made up of blocks of data, every file is now as it was when the snapshot was taken.
This allows you to undo changes to your files, folders, and even volume, or to bring back files you have deleted accidentally.
What is good about the way QNAP does snapshots?
Easy to navigate interface:
Just click on what snapshot you want to load, and then you can revert the whole volume or select a specific file or folder to restore.
You can also easily schedule snapshots or take one manually at any time on the same interface.
Because QNAP does block level snapshots, they are more space efficient than file level snapshots. With file level snapshots, if you make even a small change to a file, you need to save the whole file to the snapshot. But with block level snapshots, you only need to save the blocks within the file that have been changed.
Much better for iSCSI LUNs:
Data Backup And Data Snapshot Difference Definition
Block level snapshots let you take snapshots of any volumes or LUNs on your NAS including a block level iSCSI LUN. Other snapshots that rely on BTRFS cannot do this because they can only take a snapshot of a volume & a thin LUN managed by the BTRFS file system. Steel construction manual free download.
Control snapshot space allocation to keep your NAS functional:
QNAP built their snapshots from the ground up and gave you more control of how space for the snapshots is allocated. You control how much storage to reserve for the snapshots. And other files and applications will have priority over the space that you did not allocate to snapshots.
For other NAS providers that rely on BTRFS, you have less control, and sometimes the snapshots can take up so much space that the NAS is no longer functional as a file server.
When are snapshots small?
When you only add files to the NAS, you don’t need to save blocks of data to the snapshot. The Snapshot just needs to have the metadata recording what blocks have been added to the NAS since the creation of the snapshot.
What makes a snapshot big?
When you delete files, the snapshot needs to be able to restore the files you deleted. To do that, any block of data you delete and overwrite will be saved to the snapshot. Saving blocks of data to the snapshot takes much more space than just saving metadata. So, deleting files makes your snapshot size grow much more than adding file
Most people delete some files and make some changes to their files, but not enough to make the snapshots get too big. The default for QNAP is to allocate 20% of your storage space for snapshots and this is usually more than enough to have 256 snapshots. You could never get close to this many complete backups without taking up huge amounts of space. That is why snapshots are much better than backups for versioning. But snapshots don’t protect you from drive failure so it is still good to have RAID redundancy and at least one backup of your data to another device.
Difference Between Backup And Snapshot
(Originally posted on April 24, 2018; contents updated by Michael Wang)