SYSTEM INFORMATION | |
---|---|
OS type and version | CentOS Stream Linux 9 |
Webmin version | 2.105 |
Virtualmin version | 7.9.0 Pro |
Related packages | SUGGESTED |
Switched to Google Drive from Dropbox for my off site domain backups, which works great from a speed standpoint, it’s about 1/3 of the time it takes to get the job done with Dropbox. However, I noticed a quirk.
When I upload to Google Drive, it doesn’t put the resultant files in the same structure as Dropbox (and a local copy) despite using the same command. These are the commands that I’m telling Virtualmin to use:
Local: /serverbu/backup_%m_%d_%Y_%H_%M
Dropbox: virtualmin/backup_%m_%d_%Y_%H_%M
Google Drive: virtualmin/backup_%m_%d_%Y_%H_%M
Using an example of one of my domains here: (black-sabbath.com), what I get for each is this:
Local put today’s backup files in a directory called backup_12_18_2023_00_01 and I get three files. They are black-sabbath.com.tar.gz, black-sabbath.com.tar.gz.dom, & black-sabbath.com.tar.gz.info.
Dropbox does the same thing. This is what I want. However, Google Drive using the same “folder & path” string results in this:
I get them in the virtualmin directory, but the files look like this:
backup_12_18_2023_00_01 black-sabbath.com.tar.gz
It’s not creating the additional directory with the date and time, it’s appending the date and time to the filename. Local doesn’t do that, Dropbox doesn’t do that, but Google Drive does. It’s not the end of the world, the files are getting there, I can massage them myself afterwards to be in the right spot, but I wonder why it’s not putting them there the same way that local and Dropbox are.
I did check, the “create destination directory” is checked.
Suggestions?