Backup failed

11 posts / 0 new
Topic locked
Last post
#1 Sat, 03/10/2012 - 01:22
erussolillo

Backup failed

Hi Everyone,

I have a problem with my scheduled backup to my home pc with filezilla server.

First, the ftp from ssh work, i am able to connect to create directory, put and get files.

Wher I try to make the automatic backup from Virtualmin i see the open connection on filezilla (the icon on tha tray is green) but the file is not transfered and i see this message in the virtualmin :

Uploading archive to FTP server ip-address .. .. upload failed! Failed to connect to ip-addrees : Connection timed out

Backup failed! See the progress output above for the reason why.

How i can solve the problem ? Best Regards Ernesto

Tue, 03/13/2012 - 04:34
Hans

Hiya Ernesto,

I don't have an answer for you, but a similar problem:

virtualmin is scheduled to make a backup via ssh every night. The initial backup apparently did "something" (we see the files, however most have only some k of size which is far too small and vm didnt send a positive confirmation). 24 hrs, later, w. the 1st and all following backups, wm sends an email:

Subject: Failed backup of Virtualmin on xxx.xxx

There are currently 0 backups running, and the system-wide limit is
Backup gescheitert! Im folgenden nun die Angabe des Grundes/von Gründen.
Total backup time was 00 minutes, 00 seconds.

Virtual servers that failed :
   {list of domains}
Sent by Virtualmin at: https://xxx.xxx:10000

We chose incremental backup, but the files do not grow and neither their timestamp increases.

here the settings we use:

Virtual servers
Servers to save
  All virtual servers
Include sub-servers of those selected?
  yes
Limit to servers on plan
  <Any plan>
Features and settings
everything
Destination and format
Backup destination
  SSH server
Do strftime-style time substitutions on file or directory name
  no
Transfer each virtual server after it is backed up
  yes
Backup format
  One file per server
Create destination directory?
  no
Action on error
  Continue with other features and servers
Backup level
  Incremental (only files changed since last full backup)
Schedule and reporting
Scheduled backup time
  Simple schedule
Delete old backups Never
Command to run before backup None set 
Command to run after backup None set 

Why are the backups failing? What do you recommend?

Thanks for your support,

Hans

Tue, 03/13/2012 - 09:29
andreychek

There are currently 0 backups running, and the system-wide limit is Backup gescheitert!

Hmm, that's an unusual message, though that's different from the original posters issue (as you noted).

If you go into System Settings -> Virtualmin Config -> Backup and Restore, what is "Maximum concurrent backups" set to?

-Eric

Tue, 03/13/2012 - 10:02 (Reply to #3)
Hans

Hallo Eric,

thank you for your quick reply.

Where can I find System Settings?

Cheers, Hans

Tue, 03/13/2012 - 10:45 (Reply to #4)
andreychek

System Settings is in Virtualmin, on the navigation bar on the left -- above the "Email Messages" option.

-Eric

Tue, 03/13/2012 - 12:23 (Reply to #5)
Hans

thanks for the pointer Eric.

We found 'System Settings', but there is no 'Virtualmin Config' there sorry. We have the follwing options:

Features and Plugins
Server Templates
Account Plans
Bandwidth Monitoring
Upgrade to Virtualmin Pro
Module Config

No Virtualmin Config, no Backup and Restore.

Forgot to mention: we are on ol' 3.77GPL - maybe this has something to do w. it? Cheers, Hans

Tue, 03/13/2012 - 13:08 (Reply to #6)
andreychek

Aha, you're using an older Virtualmin version. In older versions, it's called "Module Config".

Tue, 03/13/2012 - 15:29 (Reply to #7)
Hans

cool, found that, thank you for your patience, Eric, we are getting there...

Backup and restore
Backup compression format gzip
Extra command-line parameters for compression command None   
Maximum concurrent backups Unlimited  
Time to wait if maximum is exceeded Halt immediately 
Apply limit to Backups by anyone
Backup types to limit   Scheduled only
Tue, 03/13/2012 - 16:04 (Reply to #8)
andreychek

Okay, something may be awry with "Maximum concurrent backups".

Can you try setting that to, say, "3" rather than unlimited?

I'm wondering if that will resolve your issue.

If it does, that sounds like a bug of some sort that we'll need to look into.

-Eric

Tue, 03/13/2012 - 10:15
Hans

a short update:

we additionally scheduled a backup via FTP and get exactly the same error. I guess it is safe to presume the problem is on the source vm-server from where the backup is made, not on the target ftp/ssh server.

Thanks,

Hans

Thu, 03/15/2012 - 11:25
Hans

Eric, you ROCK! :)

Backup is working perfectly now, thanks to your support! Keep it up, Eric I really appreciate your help! <3

Topic locked