livebackup
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| livebackup [2022/07/06 07:47] – nexrom | livebackup [2023/09/24 09:38] (current) – nexrom | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== LiveBackup ====== | ====== LiveBackup ====== | ||
| - | LiveBackup | + | LiveBackup |
| - | An genau dieser Problematik setzt LiveBackup | + | LiveBackup |
| - | ===== Vorteile | + | ===== Advantages |
| - | Vorteile von LiveBackup | + | Advantages of LiveBackup |
| - | * Datenverlust im Desaster-Fall lässt sich minimieren | + | * Data loss in the event of a disaster can be minimized |
| - | * " | + | * " |
| + | * In the event of a disaster, the time until recommissioning can be significantly shortened (" | ||
| + | |||
| + | ===== Disadvantages ===== | ||
| + | |||
| + | Disadvantages of LiveBackup compared to classic backups: | ||
| + | |||
| + | * Depending on the number of I/O writes within the virtual machine, the backup created by nxmBackup can be very large because every write is recorded | ||
| + | * Depending on where the backups are stored within your own infrastructure, | ||
| + | |||
| + | ===== Recommendations ===== | ||
| + | |||
| + | Basically, the following recommendations should be considered when using nxmBackup: | ||
| + | |||
| + | * LiveBackup should not be used on virtual machines where high I/O write rates are expected | ||
| + | * The backup target should be accessible at least with the same write and read rates as the memory of the virtual hard drives of the virtual machine being backed up | ||
| + | * It should be noted that the storage required for a LiveBackup can increase significantly. Therefore, a size limit must be set when creating a job. This storage size should be at least available on the backup target. | ||
| + | * When restoring from a LiveBackup to a certain point in time, it should be noted that, for example, a file that was written to the virtual hard drive shortly before that point in time may not yet be visible or not completely visible in the restored machine. A slightly later point in time should be chosen for the restoration. | ||
livebackup.1657093649.txt.gz · Last modified: 2022/07/06 07:47 by nexrom