debian 12
7.30.8 Pro
24 core cpu
64 gig of ram
when i have virtualmin make a backup and use the make a single archive file it doesn’;t route it through pbzip it simply creates an uncompressed .file. Is this expected behavior?
What does it mean “it doesn’t route it through pbzip”?
it doesn’t use pbzip it simply tars the file install of tar.bzip2
it uses tar by default and seems to forget this setting choice. 
My guess is that the OP is backing up multiple domains to a single file and the outer file is a tar rather than some form of compressed format, that said compressing compressed files can make the resulting file larger than a standard tar file.
which is why I posted that example (there are 12 VS on that VM) I regularly backup to a zip (compressed file).
I hate tar 
balls
but fully agree 
double compression 
So the outer file is a tar and each domain inside of that tar will be zipped (or whatever), I still don’t quite understand the need to compress a compressed file, this could be down to the OS of the client not being able to understand tar files natively but who knows the OP has not been very forthcoming on what they are trying to achieve
Do you consider TAR a form of compression?
not exactly - more specifically i think that would be a .tar.gz file
tar files are as old as “Tape Archive” (some would say ‘as old as me’ 
but not quite, though I do remember tape machines - both reel-to-reel and cassette 
however, back on topic:
I am confused as to why there is a call for any change to the current working system?
I use .zip and it works
others presumably use .tar which also works
just seems like a 
Can you explain what you mean? What kind of change are you talking about?
Tarallows the keeping of file structureGZipperforms compression only. (It does not understand file systems)
That is exactly what I said, I thought everyone knew that a tar is just a container
the OP @hescominsoon seemed to be requesting a change to the current system or a claim that it is not working.
I think it is working. therefore requires no further change to the options already provided.
as I indicated this is just a
That’s because the OP was expecting a compressed tar which contains compressed tars hence my coment on double compression
tar is not compressed at all..it should be a tar.bzip2 which is what i get when doing my normal backups…
That is the whole point why would you compress compressed files ? or are you saying each domain is uncompressed within the parent (outer) tar file ?
tar.bzip2 and tar.gz are the same sort of construction.
As mentioned by a few members a tar file on its own is not compressed, its purposes is to store files and maintain file structure, It is incapable of compression.
Gzip is not capable of maintaining a file structure but can compress single files. I am guess bzip has similar limitations.
Or
are you trying to say that my notes above are correct but that the compression level of the gzip is set to “Store”?
If you go to “Backup and Restore ⇾ Backup Virtual Servers”, only do the following:
- Choose which server to backup (choose smallest)
- Change “Backup compression format” to “tar+bzip2”
- Click “Backup Now”
- When done, download the backup file
- Run
file downloaded-file-name.tar.bz2on it
What output do you get?
doing a single file per server it op3rates correctly..only when doing all of the accounts as a single file does it not obey the comrpession settings.
So, does it work if you follow my exact instructions from my previous comment?