Dear all,
allowing vzdump to use ram-backed directory for temporary backup files
speeds up backups and thus results in shorter container/VM downtimes.
Currently, VZDump.pm will decline tmpfs-backed directories as they are
are missing from its hardcoded POSIX compliant filesystem list.
This small
Signed-off-by: Martin Lablans
---
PVE/VZDump.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/VZDump.pm b/PVE/VZDump.pm
index 004672d..d1b8cc2 100644
--- a/PVE/VZDump.pm
+++ b/PVE/VZDump.pm
@@ -19,7 +19,7 @@ use PVE::JSONSchema qw(get_standard_option);
use PVE::HA::Env:
For simple container/systems is is probably OK, but I cannot backup a
multiple TB system on tmpfs.
Also, the backup is normally limited by CPU power or network
throughput, not storage speed (at least for my machines).
On Sun, Jul 23, 2017 at 7:40 PM, Martin Lablans wrote:
> Dear all,
>
> allowin