Problems with 3300 Backup / Restore 1

[rtmolder]

Hi all, I'm on v8.0.8.8 and I'm am having difficulty backing up my 3300mxe. The box will appear as if it's going through the backup process but finishes in within 5 minutes and the file is not in the location selected. I've tried this with 4 different machines. I'm wondering if Java is the problem. Maybe someone knows how to backup the system another way?

Log file:

BR_BackupCustomAppServer - Backup starting (excluding Voicemail messages). (including call history records).
Using FTP, the client will transfer the archive file to directory 'C:/Backups'. Main Maintenance;0

BR_Manager - DB Backup - completed successfully. Client will initiate FTP transfer. Main Maintenance;0

 

[kwbMitel]

I suspect that the devices that you are backing up from have firewalls enabled.

The backup in completing but the file transfer is not.

Look for issues on the network/PC that would prevent FTP downloads. Especially remotely initiated FTP downloads

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[tomcotton]

Trying using Filezilla FTP instead of IIS. I've had trouble with restoring/backing up when it gets to the vmail1.tar file in the past. Although with Filezilla that's not a problem.

Cheers

 

[rtmolder]

I did verify that the firewall on the machines was turned off. I also talked with our network guys about any changes that might have taken place that would prevent FTP downloads - but we seem to be fine there.

I only know about backing up the system through the ESM under Maint. and Diagnostics. As for trying Filezilla, I'm not sure how I can specify the system to use that instead of IIS. If I knew where the actual backup file is stored after being created, I think that would solve my problem.

 

[rtmolder]

Thanks for the reply guys, I did verify that the firewall on the machines was turned off. I also talked with our network guys about any changes that might have taken place that would prevent FTP downloads - but we seem to be fine there.

I only know about backing up the system through the ESM under Maint. and Diagnostics. As for trying Filezilla, I'm not sure how I can specify the system to use that instead of IIS. If I knew where the actual backup file is stored after being created, I think that would solve my problem.

 

[Lundah]

FileZilla is just a different FTP server you can use instead of Microsoft's built in platform (IIS). However, that's irrelevant here, since the PC uses a CLIENT FTP connection during the backup, not server.

Verify that you can open an FTP session from a command prompt on the PC to the 3300ICP in question. The FTP server would be the 3300ICP RTC address, and use the ESM login credentials for the username/password. Once you're sure this works, you should not have any issues performing an ESM backup.

 

[Lundah]

One other thing, the target folder of the backup file might be the problem. Make sure the target folder exists, the folder name starts with a letter, and there are no spaces in the folder name.

 

[rtmolder]

We tried to connect with filezilla but were unable to. I disabled the WAN firewall through the ESM and tried again. The port scan shows that port 21 is open but still can't connect. The ID and PW entered is the same as what I use to access the ESM and the RTC address is correct.

 

[Lundah]

There must be something in the network configuration preventing the FTP connection. If you can't connect from the command prompt FTP client to the 3300, but you can open an ESM session, the problem is with the network, not the 3300.

 

[kwbMitel]

What Lundah says is true up to a point. If you can't initiate an FTP client session with the controller your issue is in the network but if you can initiate an ftp client session it does not necessarily eliminate the network. This is because PC initiated ftp sessions are typically allowed on the network but Remotely initiated ftp sessions are typically disabled.

In this case the 3300 is a remote device trying to initiate a FTP session with the PC. Firewalls and Virus checkers are the first place to look.

Make sure your IT support are aware that it is a remotely initiated ftp session and I think they will find the issue.


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.