ERROR - Cannot backup the database on the remote host
Created: 25 Jun 2012 | Updated: 25 Jun 2012 | 5 comments
HI all,
I have implemented a client SMG 9.5.4-4, which is configured a FULL backup and backup reports / logs / etc intended to FTP on the LAN to run automatically.
The problem is detected when you run the backup schedule, and goes to an FTP folder, where there are previous backups. This task fails and sends it to the administrators of SMG the following notice:
Subject: Symantec Messaging Gateway Alert - Scheduled tasks Failures
Symantec Messaging Gateway Alert Notification for xxxxxx@xxxxxx.com
========================= ALERT NOTIFICATION ======================= =======
The Following Have Failed Scheduled Tasks:
Task: Backup (Backup FULL Monthly)
Host: xxxxxx.xxxxxx.xxx (10.xxx.2.xx)
Last Run Time: Thursday, May 31, 2012 1:00:00 AM BST
Task: Backup (Backup Logs, reports, weekly config)
Host: xxxxx.xxxxx.xxxxx (10.xxx.2.xx)
Last Run Time: Saturday, June 23, 2012 1:00:00 AM BST
Details about this failure to Have Been logged BrightmailLog.log. Access this Control Center console log on the Logs page of the Symantec Messaging Gateway Control Center.
===========================================================================
In reviewing the file BrightmailLog.log, detected the following error:
June 23, 2012 1:00:00 [BrightmailScheduler_Worker-13] ERROR - Can not backup the database on the remote host.
June 23, 2012 1:00:00 [BrightmailScheduler_Worker-13] ERROR - FTP: Can not transmit the file: Can not open data connection.ERROR: Unable to send to the Specified URL.
June 23, 2012 1:00:00 [BrightmailScheduler_Worker-13] ERROR - Error occurred while Attempting to execute scheduled backup.
By eliminating all previous backups on the FTP destination folder, the backup is performed correctly.
We reviewed user permissions for connecting to the FTP server, and this is OK.
The files, as we all know, are renamed with the date and time running.
Some of you did this happen?
Thank you all from now!
Discussion Filed Under:
Comments 5 Comments • Jump to latest comment
.
It sounds like the FTP space was full or over quota. You should check the logs on the sever to find out why it wouldn't allow the Messaging Gateway to upload the file. You might run a packet capture on the FTP server of this happens again so you can see the server's response when the Messaging Gateway issues the upload command.
I agree either the ftp server is run out of space or the sapce alloted to the user doing the ftp must have got exhausted.
Today I received recently commented that the FTP server logs. From what I could see only an 425 error ..
We need iis logs.
Nothing would be better than sniffing the packets though.
Would you like to reply?
Login or Register to post your comment.