[Feature request] Use backup_tmpdir for "local" backups too (locally mounted NFS)
Currently `backup_tmpdir` is used only for remote FTP destinations.
But when we're using a locally mounted remote NFS share for a backup destination,
the temporary dirs/files are created on that locally mounted remote NFS share,
which is crazy with huge accounts, because:
1. DA copies temporary all user data to that locally mounted remote NFS share
(data goes over network once, uncompressed, slow, because NFS is slow with
huge amounts of files)
2. Then all these copied data is being tar-gzipped locally and stored on this share,
so the data goes back (uncompressed) and forth (compressed) over the network again.
It would be great to have one of these features:
1. Allow to force the usage of `backup_tmpdir`defined in directadmin.conf via backup config.
2. Or detect NFS destinations as remote locations and use `backup_tmpdir`
as usual for remote backup destinations.
Or simply add an option when defining backups, like "Use local `backup_tmpdir`".
Currently `backup_tmpdir` is used only for remote FTP destinations.
But when we're using a locally mounted remote NFS share for a backup destination,
the temporary dirs/files are created on that locally mounted remote NFS share,
which is crazy with huge accounts, because:
1. DA copies temporary all user data to that locally mounted remote NFS share
(data goes over network once, uncompressed, slow, because NFS is slow with
huge amounts of files)
2. Then all these copied data is being tar-gzipped locally and stored on this share,
so the data goes back (uncompressed) and forth (compressed) over the network again.
It would be great to have one of these features:
1. Allow to force the usage of `backup_tmpdir`defined in directadmin.conf via backup config.
2. Or detect NFS destinations as remote locations and use `backup_tmpdir`
as usual for remote backup destinations.
Or simply add an option when defining backups, like "Use local `backup_tmpdir`".