zBackup | A lightweight ZFS backup tool | Continuous Backup library
kandi X-RAY | zBackup Summary
kandi X-RAY | zBackup Summary
zBackup is a bash script that helps you backup your ZFS datasets. With the help of zBackup, it becomes easier to automate your backup process. Disclaimer: zBackup is a personal project developed by an amateur college student. It is not guaranteed to work correctly. Use at your own risk. Currently, zBackup can create snapshots, export snapshots, upload exported files and clean old snapshots. During a single run, these tasks (if enabled) will be performed in the listed order.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of zBackup
zBackup Key Features
zBackup Examples and Code Snippets
Community Discussions
Trending Discussions on Continuous Backup
QUESTION
ANSWER
Answered 2022-Feb-22 at 10:59I am not sure if you have seen this message in the portal when you created the account/also mentioned in the doc
"You will not be able to switch between the backup policies after the account has been created"
since you need to select either "Periodic" or "Continuous" at the creation of Cosmos Account, it becomes mandatory.
Update:
You will not see the above in portal anymore, you can Switch from "Periodic" to "Continous" on an existing account and that cannot be reverted. You can read more here.
QUESTION
What would be the consistency of the continuous backup of the write region if the database is using bounded staleness consistency? Will it be equivalent to strong consistent data assuming no failovers happened?
Thanks Guru
...ANSWER
Answered 2021-Nov-25 at 17:15Backups made from any secondary region will have data consistency defined by the guarantees provided by the consistency level chosen. In the case of strong consistency, all secondary region backups will have completely consistent data.
Bounded staleness will have data that may have stale or inconsistent data inside the defined staleness window (minimum 300 seconds or 100k writes). Outside of that staleness window the data will be consistent.
Data for the weaker consistency levels will have no guarantees for consistency from backups in secondary regions.
QUESTION
MongoDB has deprecated the continuous back up of data. It has recommended using CPS (Cloud provider snapshots). As far as I understood, snapshots isn't really going to be effective compared to continuous backup coz, if system breaks, then we can only be able to restore the data till the previous snapshot which isn't gonna make the database up-to-date or close to it atleast.
Am I missing something here in my understanding?
...ANSWER
Answered 2020-May-19 at 10:12Cloud provider snapshots can be combined with point in time restore to give the recovery point objective you require. With oplog based restores you can get granularity of one second.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install zBackup
Use the flag -e to tell zBackup to export specified snapshots as files. You need to specify where these files should be stored using the -t flag. zBackup uses gzip to compress the exported contents and uses split to split the backup into 10GB files. Example: zbackup.sh --date 20201231 -f pool/fs -t ~/backups -e will export the snapshot pool/fs@20201231 to ~/backups/pool/fs/20201231/. Supposing that the snapshot is 25GB large, these files will be created: backup.zfs.gz_part00(10GB), backup.zfs.gz_part01(10GB),backup.zfs.gz_part02(5GB). Currently, zBackup cannot restore the backup for you. You may manually concatenate these files, decompress them and use zfs receive to restore it. zBackup calls zfs send with the -w flag so that encrypted datasets will be exported encrypted. There should be no need to disable this feature. Warning: Please make sure that you do not store other files in the target directory. Otherwise your files may get overwritten.
Use the -u flag to tell zBackup to upload the files created using -e to your cloud storage. zBackup calls rclone for this functionality. -u should be followed by a rclone-style address, e.g. clouddisk:some/dir. -t should be used to tell zBackup where to look for the files to upload. The value should be exactly the same as when you used -e to export the snapshot. -e and -u can be used together.
zBackup can help you clean the snapshots following your policy. Use the -c flag followed by a policy to use this feature. Note that the exported files will NOT be deleted. Only the snapshots themselves will be destroyed. Currently two types of policies are supported.
keep: Destroys all snapshots except the most recent ones. For example, keep5 keeps the latest 5 snapshots only.
before: Destroys all snapshots before the specified date. For example, before20201231 destroys pool/fs@20201230 and pool/fs@20201125, but not pool/fs@20201231 and pool/fs@20210102.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page