Backupin to S3 - "All" doesn't work.

When running a Virtualmin scheduled backup to S3 a "full" backup doesn't seem to work.

Boxes checked: Full (all files)

and: One file per server

The tar.gz files uploaded to S3 when downloaded and unpacked consist of dozens of what look like incremental backup folders.

If I change the backup destination to: "Local file or directory" then it works correctly and the unpacked tar.gz file has the complete (Full) account archived.

Using Virtualmin Version 4.01.gpl and Webmin version 1.801



Howdy -- ah, it looks like you're using a fairly old version of Virtualmin there... that was released about 3 years ago.

There's been quite a few bugfixes since then.

Could you try updating to the most recent Virtualmin version, and then attempt the backup again?

Yeah if you aren't using the latest Webmin or Virtualmin I'd definitely recommend updating. The latest version of both of those is available in the repository now.

When will this update be available via the Virtualmin Package Updates module?

The Package Updates module installs packages from the Virtualmin repository.

So if it's in the repository, it should be available for install via that module.

Hmmm... it's not coming up for me: webmin A web-based administration interface for Unix systems. No update exists from version 1.800-1 That's on Virtualmin Pro 5.03 with everything updated.

What output do you receive if you run the command "yum update webmin" on the command line?

Loaded plugins: fastestmirror, security
Setting up Update Process
Loading mirror speeds from cached hostfile
* base:
* extras:
* updates: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
To address this issue please refer to the below knowledge base article

If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.

Error: Cannot retrieve repository metadata (repomd.xml) for repository: scl. Please verify its path and try again

It looks like there is a repository enabled that's no longer functioning.

That is preventing your other repositories from working.

What you'd need to do is look in /etc/yum.repos.d for a repository that's looking in "", and then disable that repository.

Sweet! Worked a charm :) Also freed up about a dozen updates that must have not been loaded due to the same problem. Thanks for your help!

No problem, glad you were able to get that working!

Feel free to let us know if you have any additional questions.