If I extract the homedir file jew.com_dir.tar.gz with 7z I get the following errors and the files and folders are all in folders with different numbers rather than all under public_html (this is obviously caused by 7zip not liking the Gzip format and thus extracting as a straight TAR)
It seems that the issues you described aren’t related to Virtualmin backup file. Most probably it happens because limited symlink support in Windows—if I remember correctly, it’s disabled by default, and non-administrator users cannot create symlinks unless developer mode is enabled.
Also, I think you could try using the native tar command in PowerShell instead.
Todo : stop using windows applications to play with files that are produced via a linux OS it could be said there are issues with, perhaps, windows applications, that are not 100% compatible with a linux based archive, cut your losses ditch windows as your daily driver and use a linux desktop and associated utilities:) - joke
@shoulders The domain.tld.tar.gz created inside the main backup file is actually just a tar archive, not gzipped. It seems Windows applications might rely on file extensions rather than the actual file type.
On Linux or macOS, file extensions don’t matter, you could even name it domain.tld.tar.gz.exe and extract it using tar -xf domain.tld.tar.gz.exe, and it would work just fine.
@Jamie, perhaps we should reconsider naming the file domain.tld_dir.tar.gz inside the main archive, as it’s technically inaccurate. file domain.tld.tar.gz clearly shows it’s not a gzipped archive—compressing it twice doesn’t make much sense either (which we don’t).
I renamed the home directory archive and then opened it with winrar and it looks normal. So the file extension for us windows users is important. @Ilia a good find, thanks.
these images are a simple comparison, most of the archive appears missing if you have the wrong file extension.
