Backing up your Frog Server

From Frog Knowledge Base
Jump to: navigation, search

Setting up the Backup

When the Frog server has been installed into your school, it is important that regular backups are scheduled by the system administrator.

It is also important that the backups are retrieved from the Frog server and stored externally for safety in case of a hardware failure.

The Frog server has its own backup routine which can be configured in a variety of ways to include or exclude certain parts of the server data.

This video covers the set up of a regular backup on Windows Server 2008.

Configuring the Toolkit

In order to take a backup of your Frogserver you will need to do the following:

Login to your Toolkit as an Administrator and navigate to Admin -> Server Configuration -> Server Backup. Ensure that under "Schedule backup preperation" that at least one day is ticked.

If you don't know the password to the Frog backup share on your server you can change this now by pressing the "Frogbackup" button in the "Reset System passwords" section of this page.

The option "Include Frogoffice/Frogweb files in backup" means that if this check box is selected the data from the Frogoffice and Frogweb will be included in the backup.

The "Prepare Backup" button at the bottom of this tab will force the Frog server to immediately prepare a backup.

File on centre

Accessing the Backup Share

From another machine in your network, for example your backup server, navigate to \\frogserver\frogbackup

You will be presented with an authentication box. The username is frogbackup and the password is whatever you have set while Configuring the Toolkit.

When you have access to this share you need to copy the entire contents to another location on your network. This will then need to be included in your normal backup routine. From now on the files must be retrieved from the Frog Backup share on the Frog server as part of your backup routine, using the username and password shown in the Server Backup section to connect with.

It is possible to automate this process by use of a script. Frog Technical Support cannot support the content of this script as it will change depending on each individual school network set up. Different schools use different methods for taking a backup. These range from a simple robocopy script to copy the contents to another location, to using a their own backup software to map the drive and take a copy. Whatever method you use, for Frog to be able to restore data you will need to provide Frog with a complete backup of the system.

Important Notes

It is important to note the following:

  • Your Backup is not valid until it has been copied from the Frog server to another network location, this is because:
    • The backup prepared on the Frog server uses simlinks which point back to the orginal files, and are not copies of the files.
    • If the Hard Drives on the server were to fail, or the server was damaged or destroyed by an accident it may not be possible to recover the data from the damaged system.
  • This backups is for disaster recovery purposes only, as it is used to do a full restore of your system. It cannot be used to restore single files / emails. To restore deleted files in Frog please check the recycle bin in the Toolkit. If emails or users are deleted then they cannot be recovered without running a full restore of the Frog server. Frog Technical Support will assess each request for a system restore individually.

Using ADSSO?

Please be aware, if you are using AD SSO, you must create the frogweb (and frogbackup) users on your domain, via AD Users and Computers - these are the details you should then pass to your backup software to authenticate against the share.

Push Backups

Following customer feedback, it has been highlighted that customers would prefer to use a push backup process, rather than the pull process currently used by Frog.

We are pleased to announce that we are now able to implement this new backup process. The process must be enabled by Frog Technical Support and to do this we require the following information:

  • A UNC path to a share for Frog to put the backup on.
  • A username and password of an account that has full read and write access to the share (not the domain admin).
  • An email address for the backup results to be sent to.

Frog Technical Support will then enable the new backup process in the Toolkit and enter the details. You will then be able to see and edit the backup details under Toolkit > Admin > Server Configuration > Server Backup as normal.

What are the advantages?

The new backup process has several major advantages over the current backup process, which is slowly being deprecated.

Firstly, the old backup process does not generate as accurate emails and reports for any faults. This may mean that issues with the backup are undetected by the end user, resulting in inaccurate backups.

The new backup process provides full and detailed reports into the process it is running meaning any errors will be highlighted to the end user complete with detail. These can then be passed to Frog Technical Support to allow us to resolve the issue quickly.

There are some conditions in which the old backup process will fail. These are normally related to process space and inodes on the Frog server itself. The new backup process does not fail in these conditions. The only way to resolve the issues caused by these conditions is to switch to the new process.

From customer feedback we have identified that the majority of customers would like to see a backup process that works as a "push" rather than a "pull". This is another reason why we have introduced the new process.

Please note that this backup will run every day. If you would like to keep a specific copy or historic changes in a backup then we recommend copying the contents of the backup share to another separate network location so it will not be overwritten by the nightly backup.


There are sometimes issues encountered when copying files from a Linux machine, to a Windows box. If you find that your backup doesn't complete, it may be worth trying these changes on the Windows PC that is being accessed:

SYMPTOM: After a while windows will not allow to copy any more data and rsync cannot allocate enough memory. This can be allowed via a few registry entries:

FIX 1: 1.Set “HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache” to “1″

FIX 2: 2.Set “HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size” to “3″

FIX 3: Restart the “server” service.