Backup and Archive

backup use cases For desktop users

Desktop user file management cases

Every time when end-users work on desktops, files are created. Those desktops are primarily responsible for storing these files but with modern cloud solutions there is a possibility for remote file storage and file synchronization across multiple devices. Beyond file synchronization file backup is key as well to decrease the risk of data loss.

Circumstances that can result in data loss:
- human factors, mistakes
- hardware failures
- software errors
- security incidents exploiting vulnerabilities
- data theft

To lessen risks of data loss, desktop systems need regular backups. S3 storage service is an ideal backup use case because it supports the classic file system backup, the widespread hierarchical folder structures (hierarchical naming convention).
Although the S3 Object Storage does not store data based on the classic hierarchical folder structures, the S3 client softwares and S3 server services are compatible with the hierarchical folder structures.

How to backup data? How to restore and recover lost data?

We recommend you to do backup pre-planned. When creating the backup plan keep in mind the frequency of backups and versioning depending on the type of work done and the amount of data generated in a given period of time. If you have the backup plan and backups run successfully you may never need to do a restore.

If one file is lost all you need to do is a simple file restoration. If the whole file system is corrupt - including even hardware failures - then you have a full data loss and you need to do a full recovery. This is called disaster recovery.

To be able to do a disaster recovery it is important to have backup of the complete system image wherewith complete configuration setups of applications are available byte to byte in a state matching the time of backup besides user created documents. Since the problem involves the whole system and the workstation or server is down therefore it is essential to do a restore as soon as possible to avoid reduce of business hours and growth of costs ensuing from downtime.

That is why we do not recommend storing your full backup on cold storage, rather use hot storage. Cold storage is perfect for archiving.

Application backup

You need application backup if one of the functions of an application wants to save data created within the app. It is crucial not to store them only on your desktop, though local storage prevents data loss arising from software failures but it is still a half solution since desktop software or hardware errors or other activities can result in data loss too.

App developers usually provide remote backup solutions and an S3 compatible object storage is an excellent service worth considering. Data backup occurs within the app seamless without user intervention.

Backup Cases for businesses and Organizations

File Server Backup Cases

Every data is key in business. Enterprises and organizations need a well-planned backup now more than ever to eliminate the serious financial risks deriving from data loss. Wether it is emailing of a work station, documents and excel files or the backup of a complete system with softwares and their configurations, backup frequently and on several isolated locations so that data is available easily and quickly if you have data loss.

Generally, small or large businesses have in-house servers and businesses have to provide backup for these servers too, preferably on more locations. S3 compatible object storage service is capable of storing file systems, databases and complete system images.

Database Backup Cases

Databases are used in business critical environments, in sectors like finance, sales, production, operation, distribution, etc. and by governmental and educational institutions. Data security and minimizing the threat of data loss are high priorities for these institutions. S3 compatible object storage is eligible for database backup as well.

backup vs. archive

Virtually, archive is a type of backup but their use cases differ from each other.

Regular backup is a must if you want to have the latest backup of your softwares and your data and in case of data loss or system failure you can restore them as soon as possible.

While the most important aspect of archiving is to store the utmost versions of a data and to reach back farthest in time to find a version. Basically, it is necessary to reserve each and every little change done to the data since it was created but they may never be needed or actively used.

The conclusion:
Backup may be used more actively than archive. Backup restores or recovers the latest version of a data when data loss happens. Archive is for retention purposes, keeping the most versions of data for certain purposes (research, regulatory, etc.).

Formerly, archiving differed from backup technically because the archived data was saved to a low-cost, high-capacity tape drive. Usually these data were never or seldom needed which explains the budget offline storage method, hence the name cold-storage. On the other hand backup was stored on a hot storage because if needed you had to retrieve and restore data as fast as possible.

Nowadays the lines between backup and archive are somewhat blurred due to the clever versioning and high-efficiency economic storages. Backup can easily become archive and archive is available way faster (if not as fast as) the latest backup.