If you are simply backing up the files on a system that Shut down containers before backing up their storage volumes.įor some systems Borg might work well enough without these.Shut down virtual machines before backing up their images.Dump databases or stop the database servers.Snapshot files, filesystems, container storage volumes, or logical volumes.Avoid running any programs that might change the files.In a specific or consistent state, you must take steps to preventĬhanges to those files during the backup process. If you have a set of files and want to ensure that they are backed up A file could change while Borg is backing it up, making the file internally inconsistent.By the time Borg backs up a file, it might have changed since the backup process was initiated.It just reads and backs up each file in whatever state Same method by using ssh to borg note about files changing during the backup process ¶īorg does not do anything about the internal consistency of the data If you need to access a local repository from different users, you can use the borg You can use thisįrom different local users, the remote user accessing the repo will always be The easy way to avoid this is to always access the repo as the same user:įor a local repository just always invoke borg as same user.įor a remote repository: always use e.g. Of course, a non-root user will have no permission to work with the filesĬreated by root (or another user) and borg operations will just fail with Non-privileged user and root) while accessing the same repo. This can easily happen if you run borg using different user accounts (e.g. If you only back up your own files, you neither needĪvoid to create a mixup of users and permissions in your repository (or cache). Using root likely will be required if you want to backup files of other users Hard quotas (which may not be reflected in statvfs(2)).Other tasks fill the disk simultaneously.The underlying file system doesn’t support statvfs(2), or returns incorrectĭata, or the repository doesn’t reside on a single file system.This failsafe can fail in these circumstances: Some unallocated PEs you can add to the LV. if you use LVM: use a LV + a filesystem that you can resize later and have.
Backup exec master compatibility list free#
create a big file as a “space reserve”, that you can delete to free space.In your backup log files (you check them regularly anyway, right?). You can use some monitoring process or just include the free space information If you really run out of disk space, it can be hard or impossible to free space,īecause Borg needs free space to operate - even to delete backup This mechanism is not bullet-proof in some If Borg runs out of disk space, it tries to free as much space as itĬan while aborting the current operation safely, which allows to free more spaceīy deleting/pruning archives. Borg config /path/to/repo additional_free_space 2G