Mick, you don't need to change anything inside the .cgi file.  This is how you can run it:

Login to your ftp server for your web site.  Create a folder called "test" in your root directory and drop this .cgi file into that folder.  Say your site URL is http://www.micksplace.com, the URL to that file would be: http://www.micksplace.com/test/advanced-test.cgi

Hopefully you understand by that example.  Again, there's no need to edit anything inside the .cgi file.  Just place it anywhere you can access via a web browser, and point your browser to that file.

You are likely using a Windows server with very few Perl modules, or a *nix server with few Perl modules and weird paths.

In Beta 2, I plan to do the following to help with this:
- Include all the pure-Perl modules (Archive::Tar is the only one at the moment) so you can use these.
- Check the path ENV variable and look for the binary compression methods.
- Provide support for Windows compression methods. (Hopefully Windows comes with a command line compression tool that I could use)

(untested) As for now, you'll want to grab Archive::Tar from CPAN. Make a Modules/Archive directory and add the file there. Then you'll need to put something like

push(@INC, './Modules/Archive'); 

in the Backup pl file.

Of course, if this is your own server, you could add whatever module/program you want to do the compression. Just check what's supported in my first post if this is the case.

Yep. From my experience, Netfirms has nearly no modules. It also seems they removed tar. Oh well, at least there's Archive::Tar which is pure-Perl code.

When the page stops loading, the backup is done. Sometimes the new page won't load at all, but if you check via FTP you'll find the file there.

I'm glad it worked well the second time. I'll add a more specific notice that it's finished in Beta 2.

Yes, I can add any module that's wanted . I wrote it in a way that allows more methods to be added.

However, I would advise people to avoid compression for the time being. The reason being is that some servers kill scripts that run too long, and compression takes more time then the tar.

Quote:


Sure That was easy enough for me.
But it didn't run. I got the message:
Quote:


In the cgi is written, that I have to chmod it to 755
and rename it to "servercheck.cgi". I do this also, but
got the same message. 

(path to perl is ok, server use cgi-extension)

AK108 wrote on Dec 19^th, 2005 at 8:30pm:

Than I got this message:
Quote:


Quote:


I want to run the tool, because the mod runs only with ZIP-Compression. But: Forget it and Thx

Best regards
Mick


Edit:
Now I forgot to change chmod
It runs, after copy to cgi-bin and chmod to 755!

That means that your server won't let you use tar or zip, but they are out there.