Ok, I think I have it sussed. There are two methods of getting around this.
First and simplest I found was to use the URL
http://serverIP:980 eg
http://192.168.2.1:980 instead of the URL
http://your_server/server-manager. This worked a treat and allowed me verify my 1GB backup file which took around an hour.
Second and more difficult is to modify httpd.conf. There is a template called 45Timeout which has the timeout set for 300 sec or 5 min which is how long I got before timeout.
To modify this, log in as root
# pico /etc/e-smith/templates/etc/httpd/conf/httpd.conf/45Timeout
you will see
UW PICO(tm) 4.0 File: /etc/e-smith/templates/etc/httpd/conf/httpd.conf/45Timeout
#Timeout:The number of seconds before receives and sends time out
Timeout 300
I changed the timeout value to 5400 sec or 1.5 hours.
Expand the template and restart httpd
# /sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf
# /etc/rc.d/init.d/httpd restart
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
Of course the proper way of doing this is to create a custom template fragment.
I can now use the URL httpd://servername/server-manager to restore or verify without the browser timing out.
When I started out the first thing I decided to do was to remove all the MP3's out of one of the Ibays (this was close to 1GB in itself) to make the backup file smaller. I re-ran backup but the size of it didn't change and when I unpacked it on my desktop, the MP3's were still in the backup.
Is there a copy of the backup file stored on the server that it has been using.??
Hope this helps
Cheers,
Jon