atcomsystems.ca/forum Forums TDM Business Telephone Systems Mitel Telephones & Systems ftp backup on 200 ICP

Have an odd one.

When doing an FTP backup on the 200 ICP the process is, after testing the ftp connection, the system archives the files then sends it across to the ftp server (either local or remote) as a .gz (gzip) file. It is not necessary to put that (or any) file extension on the name of the backup file when naming it in the PBX.

I have two sites - both fairly large with 5-6 peripheral nodes - where this used to work properly. Now when I do the backup (to either a remote or local computer with ftp server set up on it) it doesn't seem to be compressing the file into a gzip. I am just getting a file about 10 times larger than it should be and it is just a binary file. Both systems have been rebooted and had a restore done on the software.

Any ideas?

Interesting enough Dane, When I do the process and it asks me to enter the name of the file I want it to extract as, i always put in the site name followed with a .ftp -- i do my kermits with a .bkp. I just looked at all my ftp backups and they all are binary as well....the ftp back ups are. I would be willing to bet if you reloaded the/A system with what your backup copy came out as, it would probably load just fine, of course entering in the name exactly as we always would do....I have never pulled down a .gz from an ftp back up?

Using Windows Vista
Winrar as my archiving program
Guild FTP for my ftp server
Putty for my telnet client

EZ you wouldn't know it was gzip unless you right click on it and look at the properties

they are tarballs and/or gzip probably. nice thing about gzip is that it actually looks at the header and not the extension. *nix doesn't even require extensions.

as far as vxworks not compressing would be strictly in the scripts. you can telnet to the vxworks shell on port 2002

however this makes no sense to me. afik this is a static setting and there is no reason this would change..

I would humor the idea of putting the .gz extension after your filename and see if you can get it to uncompress using winrar or gnuzip.
i.e. rename baseload.ftp to baseload.tar.gz

I already tried that a long time ago. It shows up with the gz extension, but it is the same overblown binary file

It has to be a tar.gz because there are multiple files being compressed. gzip can only compress one file, that is why they are tarballed up first, because tar will archive multiple files and ball them up into one. Gzip is then applied to the tarball to compress it down further. If you try to open the filename.gz with winrar you will find another file inside named with your filename (just without the extension). If you rename it filename.tar.gz you can then open it up. If this doesn't work, then you got me. It can't possibly be making it as a straight binary, because it's not just one file - its a whole tree of files. From the looks of it you got a big system, therefore lots of voicemail boxes and other goodies would roll up to make a large file.

Actually no - the system(s) are only marginally bigger than many others I have out there. The odd thing here is that they used to back up perfectly. And as far as the gzip files go they are only one file on the 200 ICP. However that has given me an idea so I will check into it and let everyone know.

right. the file it sends is only one file, but that file includes multiple files and directories

Have you tried uploading that binary file to a system?