Backup Mitel Standard Linux

[AH64Armament]

We've been running a backup server using ProFTPd for several years and it's been working well until 5 December.
Nearly ALL of our systems that we manage stopped backing up to this. We have one site that is still on MiVB 8 and has to use FTP backups, that too has been failing.
Not all of our MSL's are failing, but the ones that are are showing error message “curl- (2) Failure establishing ssh session”.

Our tech that set this up is trying to get this running again using an older version of curl and it's still failing.
When you set the MSL to use this system to back up, it gives a green setup complete, but then when you back up, it simply shows "backup failed" with the above curl- (2) error in the event logs.

I have about 90 systems that we maintain that are backing up to this system - many of them are systems that have voicemail, so we back them up every day.

Thanks -
Mark

 

[Billz66]

i had a similar issue with an ubuntu sftp server - i had applied updates to it and that changed the supported cyphers, only some of the MSL servers that were sending to it were affected.
i reverted the server to a previous version of ubuntu and they started all working again , - was older MSL versions that were affected

 

[Lundah]

If the SSH is failing, I'm wondering if there's a certificate somewhere that expired.

 

[Billz66]

have you tried a manual sftp transfer from console
sftp username@ServerAddress:/foldername

you might see some more information provided as to the cause of the failure

 

[AH64Armament]

If the SSH is failing, I'm wondering if there's a certificate somewhere that expired.

both SSH and standard FTP... but NOT ALL are failing. Well, they weren't all failing until we tried to rebuild it. Now it's completely offline until we can get something to work.

 

[AH64Armament]

have you tried a manual sftp transfer from console
sftp username@ServerAddress:/foldername

you might see some more information provided as to the cause of the failure

SFTP with filezilla on a PC works fine for all accounts. It's specifically MSL's that are failing when they attempt to put the file to the server.

At this point, I'm about to spin up a MSL server at my office and port forward SSH to it and do the backups that way.

 

[Billz66]

what i meant is have you jumped on an affected MSL server, logged in as root and tried to connect to your sftp server
that will do the certificate exchange between the MSL and the remote SFTP server

testing from something else isnt going to help locate the issue

 

[AH64Armament]

what i meant is have you jumped on an affected MSL server, logged in as root and tried to connect to your sftp server
that will do the certificate exchange between the MSL and the remote SFTP server

testing from something else isnt going to help locate the issue

Yes, and that works. Since the SFTP server had already been in the known_hosts file, there wasn't any issues. I even deleted the known_hosts file on one of the affected systems and it rebuilt it, but still failed backups.

 

[Billz66]

there was a kms article mentioning the curl error although that was for physical not virtual controllers

S07077 MiVB - Backup fails when using Server Manager backup with SFTP option enabled on MXEIII & CXII
Symptoms When performing a backup from MiVB Server-Manager Backup with SFTP option enabled, backup may fail due to SSH handshake failure.
Journal logs show an error on backup - (Example shown below)
May 18 10:43:45 tlcss network_backup[18791]: curl: (2) Failure establishing ssh session
May 18 10:43:45 tlcss network_backup[18791]: Error creating backup file: curl: (2) Failure establishing ssh session
MiVB system controllers such as MXE III or CXII. (does not apply to virtual MiVB)
MiVB 9.x up to 9.4.0.25 versions of software
Server Manager backup setting using SFTP
The MiVB Server Manager backup with SFTP option, SSH Key algorithm only supports SSH -sha1 Key Algorithm.
Some servers require at least -sha256 Key Algorithm and no longer support SSH Sha1 for SFTP.
Resolution Upgrade system to MIVB 9.4 SP1 or higher.

 

[AH64Armament]

there was a kms article mentioning the curl error although that was for physical not virtual controllers

S07077 MiVB - Backup fails when using Server Manager backup with SFTP option enabled on MXEIII & CXII
Symptoms When performing a backup from MiVB Server-Manager Backup with SFTP option enabled, backup may fail due to SSH handshake failure.
Journal logs show an error on backup - (Example shown below)
May 18 10:43:45 tlcss network_backup[18791]: curl: (2) Failure establishing ssh session
May 18 10:43:45 tlcss network_backup[18791]: Error creating backup file: curl: (2) Failure establishing ssh session
MiVB system controllers such as MXE III or CXII. (does not apply to virtual MiVB)
MiVB 9.x up to 9.4.0.25 versions of software
Server Manager backup setting using SFTP
The MiVB Server Manager backup with SFTP option, SSH Key algorithm only supports SSH -sha1 Key Algorithm.
Some servers require at least -sha256 Key Algorithm and no longer support SSH Sha1 for SFTP.
Resolution Upgrade system to MIVB 9.4 SP1 or higher.

I experienced that too when we had 9.x systems running. When trying to back them up to our hosted backup server, they would fail for that same reason. I had to continue backing them up to our in-office MSL server.
Our bean counters and security guru were having cows over the fact that we were backing up to our local systems. They thought it was too much of a risk.
Now this issue and our guru tried to fix it by restoring a backup - this failed and now we have nothing.

I'm now working on rebuilding a MSL in our office and sending backups to this system.

This issue is pushing me closer to walking away from here to find another project somewhere else.

 

[kokolino23]

Would not be easier to configure a network backup folder for your MSL?

 

[AH64Armament]

Would not be easier to configure a network backup folder for your MSL?

We maintain about 90 systems that are using MSL - PBX's that are all above release 10, MiCollabs and MBG's. I had each of these backing up to a central server that something got updated and broke SOME of these systems from backing up. Since then, we've "fixed it till it completely broke" and now I'm rebuilding our in-house MBG server (MSL) and having each of these systems back up to it.

 

[AH64Armament]

I got most of the systems backing up to our new server. There's one MSL that's still missing, but the site has to redo the restriction on what IP address it backs up to on their firewall.

MiVB's that are still using FTP backups, I need to get into them and attempt to get them backing up using port 22... I have never had success with it, but here's hope.