How is StoreGrid different from other backup software?

Introduction What is StoreGrid? How is StoreGrid different from other backup software? StoreGrid Features What is StoreGrid? Very simply, Vembu StoreGrid is an extremely versatile Backup Software that works with your Existing Hardware! StoreGrid literally creates a storage grid from free space on your network. For example, if you have a few PCs connected through a LAN but no backup server, StoreGrid can create a trusted intranet peer-to-peer backup solution to backup desktop and laptop data -it simply taps into surplus hard disk capacity on PCs in a network and uses this to back up user data. But say, you did have a backup server (or servers) - StoreGrid could then be deployed in a conventional client-server mode. StoreGrid also handles remote online backups easily ideal if you prefer backing up to a server outside your network. Like we said, StoreGrid works with your existing hardware! But there s more StoreGrid is more than plain vanilla backup. Features include robust data encryption, compression & versioning and all of these are user configurable. Backup schedules can be continuous, at fixed intervals, or at a particular time and day. When you do need to restore your data, you could drill down as deep as you d like. Restore everything, just a few folders, or just a few files its your call! With all this and a detailed reporting engine, you can control your backups the way you want. And yes, all of this at a great price! How is StoreGrid different from other backup software? The difference lies in its flexibility! StoreGrid allows the flexibility of multiple deployment modes use it in Intranet P2P Backup Mode, Client- Server backup mode, or for Remote/Online Backups (or any other configuration we don t know of). Since it can be deployed in multiple ways, StoreGrid can be used by a variety of users. It works across various operating systems: Windows XP, Windows 2000/2003 servers, Windows NT 4.0 server, Windows 98, Windows ME, Windows 2000 Professional, Linux RedHat 8.0 & above, Debian 3.0, Mandrake 10.0 & above, SuSE 9.x & above, Mac OS X 10.x and FreeBSD 5.2 & above. StoreGrid allows users the flexibility to configure their backups the way they want. Every network is different. You are different. Your data is different. You need different backups for different data/users/networks StoreGrid recognises this and except for the source code, allows you to configure almost everything else the way you want! StoreGrid is different because it offers all this flexibility without compromising on the basics your data is well encrypted and password protected, compressed, and best of all StoreGrid quietly works without eating into your CPU, thanks to the incremental backup feature.

StoreGrid Features 1. Data Backup Automatically detects changes in files and/or directories and backs up accordingly Mobile (laptop) users' data can be backed up immediately as they connect to the LAN Hot links provided for windows registry backup and windows system files backup, among others Versioning support for backing up multiple versions of the same file Incremental backups supported: backs up only changes in files and not the entire file every time. This saves bandwidth and time Supports MySQL Backup in Linux Quick restore capability: end users can easily restore their data up to the file level Optional compression of backed up data possible: saves disk space and network bandwidth Support for auditing User Operations Support for non-english PCs 2. Data Security Encryption support provided to protect users' personal data Robust encryption based on the blowfish algorithm 3. Deployment Flexibility Trusted intranet P2P backup deployment Typical client-server backup deployment Remote backup with StoreGrid server residing outside the intranet Permutations & combinations of 1,2,3 4. Supported Platforms - StoreGrid is platform independent and supports the following operating systems Windows XP, Windows 2000/2003 Server, Windows NT 4.0 Server, Windows 98, Windows ME Debian Linux 3.0 Mandrake Linux 10.0 and above RedHat Linux 8.x and above SuSE Linux 9.x and above Mac OS X 10.x FreeBSD 5.2 and above 5. Supported Browsers - StoreGrid requires one of the following browsers to be installed in the system Internet Explorer 5.5 and above Netscape 7.0 and above Opera 7.01 and above Mozilla 1.5 and above Safari 1.2.4 and above

StoreGrid Editions Editions: Highlights: Feature packed as in the 'Professional Edition'. Can only be used by up to 3 computers within a network Our feature packed flagship edition - with multiple schedules, encryption, compression, and much more. Ideal for client-server and remote backups Everything in the 'Professional Edition' and more: especially created for VARs, SIs, Online Backup Service Providers and MSPs Features Download Download Partners Only Create any number of backup schedules Incremental backups Hot links for commonly used files & folders Multiple versions of backed up files Deleted file support Robust Encryption Configurable CPU / bandwidth utilization Different compression options Various scheduling options (with configurable key length) Detailed reporting Number of installations Maximum of 3 Operating Systems supported Remote Backup to server outside the subnet Product/feature messages in User Interface Windows only Unlimited (5 in the trial version) Windows, Linux, Mac OS X, FreeBSD (includes enhanced reporting) Unlimited Windows, Linux, Mac OS X, FreeBSD Technical Support Forums only Forums & email support Premium support Client Authentication Email my reports feature Customer centric reporting Bandwidth economizer module (First backup taken locally, thereafter incremental backups done online) Consolidated disk usage reporting for multiple installations in a single location Option to co-brand StoreGrid (enhanced)

Terminology These are some terms we use quite liberally both in this document, and in our user interface. So here s a short description of what each of them mean. StoreGrid Server: A StoreGrid Server receives (and stores) backup data from StoreGrid Clients. The backed up data is stored in the machine which runs the StoreGrid Server a PC can run StoreGrid server if you plan to store data on that PC. If you wish, the same machine can run StoreGrid Server and StoreGrid Client. This would be the case in a true P2P deployment, or if you have a backup server that will in turn be backed up, as well. StoreGrid Client: A machine that has data it wants to back up has to run StoreGrid Client. The StoreGrid Client backs up its data on to a machine running StoreGrid Server. If you wish, the same machine can run StoreGrid Server and StoreGrid Client. This would be the case in a true P2P deployment, or if you have a backup server that will in turn be backed up, as well (Anyone who purchases a paid licence of Vembu StoreGrid is also a StoreGrid client ) StoreGrid Web Console: This is the browser based StoreGrid user interface from which the backup, restore and administration of StoreGrid servers and clients are done. Since the user interface is browser based, any StoreGrid Client or Server can be configured and administered from any location. Peer-to-Peer (P2P): In P2P, individual entities like Desktops (Peers) exchange information with each other without the help of a central server. In a true P2P architecture, all peers are equal and participate in some form of network activity. In the case of Vembu StoreGrid, which can be deployed in a P2P fashion, the Peers (Desktops) use each others free disk space to backup data between each other. In the case of a true P2P deployment both the StoreGrid Server and the StoreGrid Client will run in the same machine as a single process. Client-Server: A Client-Server architecture is a concept in which many clients are served by a single or multiple servers. In the context of Vembu StoreGrid, multiple clients (Desktops) can backup to a single Backup Server or multiple Backup Servers. The Backup Servers are generally dedicated to a particular purpose, in this case, to store the backed up data. Remote / Online Backups: The same as client-server (see above), except that the server is outside the clients network.

Deployment Scenarios One of the unique features of Vembu StoreGrid is the deployment flexibility it offers. This flexibility makes it suitable for a broad spectrum of users. Depending upon their existing/planned Backup & Storage infrastructure, users can choose a suitable type of deployment (or a hybrid of both) 1. Peer-to-Peer(P2P) or Grid deployment 2. Dedicated Backup Server deployment (Client-Server / Remote Online Backups) Peer-to-Peer or Grid Deployment (P2P Backup) In a true P2P deployment StoreGrid can be configured to run both the server and the client in all the desktops or laptops that need to be backed up, thus forming a StoreGrid P2P network. Each individual Peer can then be configured to backup to one (or more) other peers. This deployment is the most cost-effective solution as it does not require a dedicated backup storage server (and the associated expenses). This is perfect for Home, SoHo, & Small businesses where it is easy to set up a trusted peer-to-peer StoreGrid Backup network. In general, laptops are not suitable for storing other peers' backup since the laptop may not be on the network when needed! So, it is advisable not to configure a laptop as a StoreGrid Server, but run it only in Client mode. In such cases where all peers do not store backup data, the deployment is still a Peer-to-Peer deployment - but one where all peers are not equal. Dedicated Backup Server deployment (Client-Server / Remote Online Backups) This is a more traditional deployment - ideal for leveraging existing backup infrastructure by allowing them to include desktop and laptop data. All the desktops and laptops run the StoreGrid in Client mode only, and they all back up their data to a central backup storage server. The backup storage server alone runs the StoreGrid in Server mode. It is also possible to have more than one backup server for additional data protection. The backup storage server can also be deployed in a remote location to support remote/online backup and disaster recovery.

NAT/Firewall Configuration This page provides information about the ports used by StoreGrid, and details on what ports need to be opened to enable StoreGrid to work across different networks behind a NAT/Firewall. TCP Port 32004 StoreGrid Server opens this port. All Client-Server communication including backups, restore etc. (except TCP discovery) is done through this port. If a StoreGrid Server is behind a NAT/Firewall then this port needs to be opened to enable StoreGrid clients to backup to this server. Opening up this port is mandatory for the core functionality of backup and restore to work in StoreGrid. TCP Port 32005 Both StoreGrid Client and Server open this port. This port is used for two purposes: 1. For all communication between the PHP module (invoked by the StoreGrid browser based WebConsole) and the StoreGrid C++ modules. In StoreGrid, all UI requests from the browser are served by PHP pages, which in turn connect to this port to get the required data. 2. StoreGrid peers also use this port to do a more complete discovery of each other sharing details about other peers etc. This TCP discovery is always enabled in StoreGrid. This port need not be configured in the NAT/Firewall. If so, the only feature that would not work is: Switching to a StoreGrid peer behind the NAT/Firewall through the WebConsole of another StoreGrid peer outside the NAT/Firewall. TCP Port 6060 This port is used by the StoreGrid Web Server (Apache) to serve requests from StoreGrid WebConsole (User Interface). This port is configurable. When you first installed StoreGrid you would have been given an option to change this port. The NAT/Firewall should also 'allow' this port if you need the ability to connect/administer a StoreGrid peer behind the NAT/Firewall. Multicast Ports (UDP) 6363, 6364 These two multicast ports are used by StoreGrid Clients and Servers for discovering peers within a subnet. In most networks, multicasting will work only within a subnet. There is no need to open these ports in firewall or NAT devices as multicast packets may not be sent across networks, anyway. Multicast discovery is enabled by default in StoreGrid. UDP Port 32006 This UDP port is used in discovery of StoreGrid peers in a network. StoreGrid does a UDP scanning on port 32006 of all possible IP Addresses in a network to detect the presence of other StoreGrid peers. There is no need to open this port in the NAT/firewall as StoreGrid does the UDP scanning only within its subnet. By default, UDP network scanning is disabled in StoreGrid.

Troubleshooting Guide I use Windows XP (with Service Pack 2 installed); StoreGrid doesn t seem to work? A PC/server running StoreGrid Server is not listed in the "Backup Servers" list? I tried to shut down and restart StoreGrid (Windows version). I get an error message saying that StoreGrid has exited and asking if I want to restart it? I reinstalled / upgraded StoreGrid (Windows version); the installation process alerted me that apache.exe could not be replaced. I am using Mac OS X 10.4.1 (Tiger). StoreGrid WebConsole does not seem to work in Safari and Internet Explorer browsers. I am backing up to server in a remote location. I am getting an error- SG0147/SG0136 in the backup report. My problem is not listed here? I use Windows XP (with Service Pack 2 installed); StoreGrid doesn t seem to work? This is a common issue, but very easy to resolve In Windows XP SP2, the firewall is enabled by default! So StoreGrid can neither discover other StoreGrid peers nor it can backup data to other machines. To change this, you ll either have to disable the firewall settings or you need to enable the following ports for StoreGrid to work. TCP Ports: 32004, 32005, 6060 UDP Ports: 32006, 6363, 6364 How do I enable these ports? 1. Open START->CONTROL PANEL->WINDOWS FIREWALL 2. Select Exceptions tab 3. Under Programs and Services, click "Add Port" button 4. Add 3 TCP Ports with unique names, allowing TCP Port numbers 32004,32005 and 6060. 5. Add 3 UDP Ports with unique names, allowing UDP Port numbers 32006,6363 and 6364. 6. Select OK to save the configuration and exit. That s all! The ports used by StoreGrid are now enabled. Another way to accomplish the same thing is described below 1. Open START->CONTROL PANEL->WINDOWS FIREWALL 2. Select Exceptions tab 3. Under 'Programs and Services', click on "Add Programs" button 4. Browse and choose the StoreGrid.exe and Apache.exe (Storegrid.exe is located at "InstallDir"\Vembu\StoreGrid\bin directory) (Apache.exe is located at "InstallDir"\Vembu\StoreGrid\apache directory) "InstallDir " is the location where StoreGrid is installed (by default it is C:\Program Files). 5. Select OK to save the configuration and exit. StoreGrid can now use any TCP/UDP ports as the firewall settings have been disabled for the StoreGrid and Apache applications. A PC/server running StoreGrid Server is not listed in the "Backup Servers" list? StoreGrid automatically discovers other StoreGrid peers in a network using various means (multicast, UDP port scan, TCP port scan etc). If for some reason a StoreGrid server or client is not discovered automatically, then you can add/discover the StoreGrid peer using the menu item "Administration->Add Peer".

In the "Add Peer" page, you can enter multiple StoreGrid peers name / IP address and add them to the discovered StoreGrid peers. This is especially relevant if some peers are outside your network (as in the case of remote online backups) This problem happens when you click on multiple links before a page is returned. Since StoreGrid uses PHP and Apache, the PHP instances created by Apache are not getting automatically killed since multiple requests are sent from the browser before a request is processed. To solve the problem, do one of the following: 1. Right Click the StoreGrid Tray and choose the "Restart StoreGrid Web Server" option. This will restart the Apache Web Server thus killing all the php instances. After doing this, open the WebConsole and it should work. 2. Open the Task Manager and choose the Processes Tab. Manually kill all the php instances running. After doing this, open the WebConsole. It should work now! I tried to shut down and restart StoreGrid (Windows version). I get an error message saying that StoreGrid has exited and asking if I want to restart it? This is a rare one! When this happens please run the command netstat a from a command window (Start > All Programs > Accessories > Command Prompt) and check if the TCP ports 32004 or 32005 are in listening mode. If yes, you need to restart your system! This happens because even after the StoreGrid application is shutdown, sometimes, Windows does not clean up the TCP network connections! Sorry, there isn t much we can do about it. I reinstalled / upgraded StoreGrid (Windows version); the installation process alerted me that apache.exe could not be replaced. This happens because the StoreGrid web server service (which uses apache) did not exit properly when the previous installation of StoreGrid service was stopped. To fix the problem, open the windows task manager and kill any instances of php and apache that is running. If this does not help, open the "Control Panel- >Administrator Tool->Services" and stop the StoreGrid Web server service. I am using Mac OS X 10.4.1 (Tiger). StoreGrid WebConsole does not seem to work in Safari and Internet Explorer browsers. In Max OS X 10.4.1 (Tiger), StoreGrid WebConsole User Interface works only with FireFox browser. Both Safari and Internet Explorer are not supported. You can get the FireFox browser from http://www.mozilla.org/products/firefox/ I am backing up to server in a remote location. I am getting an error-sg0147/sg0136 in the backup report. SG0147/SG0136 error means the remote server is not reachable from your client. This can happen due to the following reasons: i. The DNS look up for the remote server failed. ii. StoreGrid is not running in your remote server. iii. There is a network failure. To troubleshoot the problem, do the following: i. Try "Ping <ServerName>" from a command window in your Client machine. If there is no respone, then either there is a network problem or the DNS for your server name failed. ii. Try "telnet <Servername> 32004" from a command window. If the telnet does not connect, then check if StoreGrid is running in your server machine. If the telnet works then StoreGrid backup should also work. iii. If step 1 and step 2 do not resolve your problem, please email us at mailto:storegridsupport@vembu.com

My problem is not listed here? Please check out our FAQs to see if your problem is listed there. If not, please fill in the Technical Support form at http://www.vembu.com/technical-support.html

Migrating from version 1.2.1 to 1.6 NOTE: StoreGrid 1.6 is a minor bug fix release over 1.5.1. So there is no special migration procedure if you are updating from 1.5.1 to 1.6 Vembu StoreGrid 1.6 has some significant improvements in terms of how a StoreGrid client internally maintains metadata information. In earlier versions, metadata information like the signature (used for incremental backups) and file statistics (modified time, created time etc.) were stored in flat files. This was relatively inefficient as the metadata occupied more space than necessary. StoreGrid 1.6 uses an embedded relational database (RDBMS) to store the metadata efficiently. Moving to an RDBMS also enhances StoreGrid's ability to provide more detailed reports. The first time it runs, StoreGrid 1.6 automatically migrates the metadata maintained in flat files to the embedded RDBMS. Depending upon the number of files you had backed up earlier, the migration may take some time. The time taken for the migration depends upon the total number of files that were earlier backed up with StoreGrid 1.2.1. Migrating 10,000 files will take about 2 minutes and 100,000 files will take about 30 minutes. StoreGrid will not be functional while the migration is in progress. While you update from Version 1.2.1 to 1.6, please note that: 1. StoreGrid will not be able to schedule any backups while the migration is in progress. 2. The StoreGrid Web Console, when accessed, will come up with a message that "Migration is in progress". StoreGrid Web Console features cannot be used while the migration is in progress. 3. StoreGrid Migration process may use high CPU cycles and may slow down other processes on the machine/pc. Hence it is advisable to update to StoreGrid 1.6 when you are not using the machine/pc for CPU intensive tasks. 4. The last backup information in the backup reports will be reset after the migration, i.e. the last backup information like Total Files, Total Files Protected etc. will be set to zero. These fields will be updated once StoreGrid 1.6 runs and completes a backup. For Advanced Users The following points should help you understand the internal migration process when you run StoreGrid 1.6 for the first time after updating from 1.2.1 1. StoreGrid 1.6 creates a relational database file "storegrid.db" in <INSTALLATION_HOME>/Vembu/StoreGrid/data directory. 2. The 1.2.1 version metadata information available in the <INSTALLATION_HOME>/Vembu/StoreGrid/data/<backup-schedule> directory will be copied to the relational database. At the end of migration of every backup schedule, StoreGrid will rename the existing backup schedule metadata directories to <backup-schedule>_sg_1_2_1. StoreGrid 1.6 will not delete the 1.2.1 version's meta data information. All the directories renamed with _SG_1_2_1 can be deleted by the user manually after making sure StoreGrid 1.6 works correctly after the migration process. 3. StoreGrid 1.6 will also migrate the reports available under <INSTALLATION_HOME>/Vembu/StoreGrid/report/backup to the relational database. 4. In case StoreGrid is terminated during migration, StoreGrid will migrate the remaining metadata the next time StoreGrid is restarted.

Vembu StoreGrid Windows Installation Guide The StoreGrid Windows version is available for download in the following URL: http://www.vembu.com/storegrid/storegrid-download-form.html Download the Windows installer, VembuStoreGrid_1_6.exe (Professional Edition) or VembuStoreGrid_1_6_Free_Edition.exe (Free Edition) To install StoreGrid on Windows machines, follow the steps given below: 1. Double click VembuStoreGrid_1_6.exe (Professional Edition) or VembuStoreGrid_1_6_Free_Edition.exe (Free Edition) and follow the instructions in the installation wizard 2. Click Next to begin the installation process. Go through the license agreement, select "I accept the agreement" and proceed to the Next step. If you are updating from an earlier version, you will be asked to confirm this. 3. Installation Configuration (Windows Application or Service): By default, StoreGrid is installed as an application in Windows 98 - please go directly to Step 5 if you use Windows 98 By default, StoreGrid is installed as a service in Windows NT Server 4.0 - please go directly to Step 4 if you use Windows NT Server 4.0 Other Windows users please read on: While updating to or installing StoreGrid 1.6, you can either install StoreGrid as a Windows Application or as a Windows Service. By default, StoreGrid will be installed as a Windows Application and it will run in the background. Note that if you choose this mode, StoreGrid will only start if the user who installed it logs in to the PC. If the user logs off, then StoreGrid will exit. Advanced users may choose to install StoreGrid as a Windows Service. Click on the link that says, "Click here to install StoreGrid as a Windows service" and proceed to the next step. 4. If you want to run StoreGrid Service from the Windows Local System Account, then select this option. If you run StoreGrid service from the Local System Account, then StoreGrid will not be able to automatically collect information on User specific backup configurations like Outlook/Outlook Express backup, and IE Settings. You will need to manually select the required files and folders. If you want to run StoreGrid service from a Windows User account, then select this option and provide the User Name and the Password for the user account in the appropriate fields and click Next. In this case, StoreGrid Service will always be run from this user account. Hence, StoreGrid can correctly collect information on User specific backup configurations like Outlook/Outlook Express backup, and IE Settings. If your Windows user login is dependent on a Domain Controller, then run StoreGrid Service from the Windows Local System Account. You can manually configure StoreGrid to run from a User account later by going to Control Panel -> Administrator Tools -> Services and changing the StoreGrid service options to run as a user. 5. Select how you d like StoreGrid to run on this machine. You have three options: Client & Server This computer can back up on to other computers and vice versa. This setting is especially relevant if you are running StoreGrid as a peer to peer backup solution. Client only This computer can back up on to other computers. However, other computers cannot back up on to this computer. Server only Other computers can back up on to this computer. However, this computer cannot back up on to other computers.

Select one of the three options and click Next 6. By default, StoreGrid will be installed under "Vembu\StoreGrid" in the "C:\Program Files" directory. Click Next to continue installation in the default directory. Click Browse to choose a different directory. Note that this will create the "Vembu\StoreGrid" directory under the directory you choose. Click Next to continue. 7. There are two parts to this step. Configure Web Server Port: StoreGrid's user interface is browser based. You have the option to configure the port used by StoreGrid web server here. Once configured you need to use this port to start the StoreGrid Web Console from your browser. By default StoreGrid Web server is configured to run on port 6060. Unless you are an advanced user, please leave this as is. Username & Password: Since StoreGrid's user interface is browser based you need to configure a username and password to login to StoreGrid Web Console. Note that you can add additional users, delete users, change password etc. from the Web Console UI after the installation. By default the username and password used by StoreGrid is "admin" and "admin". You have the option to change these default settings here. If you are updating StoreGrid from a previous version, the User Name and Password fields for the Web Console authentication will be disabled. The Usernames and Passwords originally used will be retained. 8. Click Next to select the Programs Folder to add the StoreGrid shortcuts (ideally, leave it as it is). Proceed to the next step to select required icons. For ease of use, allow the StoreGrid installer to create a desktop icon & a quick launch icon. 9. Click Next to review your settings. Thereafter, click Install, and proceed to install StoreGrid. If you are updating from an earlier version, you will be informed that StoreGrid will now stop and restart after the installation. StoreGrid will automatically migrate your old data to 1.6 more detail on this process is available in the help documentation. 10. If this is the first time you are using StoreGrid, have a look at the README file when prompted; it will help you get started real quick. Note A shortcut to start StoreGrid and StoreGrid Web Console will be created on the System Tray and in the Start > Programs > Vembu StoreGrid menu. After successful installation, you can open the StoreGrid Web Console by right-clicking the StoreGrid icon in your system tray and selecting the StoreGrid Web Console from the menu, or alternatively, doing the same through the Start > Programs > Vembu StoreGrid > StoreGrid Web Console menu. You will have to login to the Web Console using the username and password you provided in the "Vembu StoreGrid Configuration" screen during the installation.

Vembu StoreGrid Linux Installation Guide The Linux version of StoreGrid is available for download at the following URL: http://www.vembu.com/storegrid/storegrid-download-form.html Download the bin file: For RedHat Linux 8.0, 9.0 and Later: VembuStoreGrid_1_6_RH.zip For Mandrake Linux 10.0 and Later: VembuStoreGrid_1_6_MDK.zip For Debian Linux 3.0: VembuStoreGrid_1_6_DBN.zip For SuSE Linux 9.x: VembuStoreGrid_1_6_SuSE.zip To install StoreGrid on Linux machines, follow the steps given below: 1. Unzip the downloaded ZIP file. 2. Execute the bin file. For RedHat Linux 8.0, 9.0 and Later: VembuStoreGrid_1_6_RH.bin For Mandrake Linux 10.0 and Later: VembuStoreGrid_1_6_MDK.bin For Debian Linux 3.0: VembuStoreGrid_1_6_DBN.bin For SuSE Linux 9.x: VembuStoreGrid_1_6_SuSE.bin 3. The first step in the installation is to choose the type of installation. You will be given two options: You can install StoreGrid in a newly created storegrid user account, where the storegrid user account will be automatically created with root privileges You can install StoreGrid in the current user account without root privileges. Choose option 1, if you want StoreGrid to have root privileges so that it can be configured to backup user data, MySQL, System Files etc. Note that StoreGrid will be installed as a daemon process and will automatically start when the system boots up. You can START and STOP StoreGrid by running the command "/etc/init.d/storegrid start/stop". You can check the status of StoreGrid application by running the command "/etc/init.d/storegrid status". Choose option 2, if you want StoreGrid to only backup files in the current user directories. Note that StoreGrid will be installed in the current user directory and has to be manually started every time the machine is rebooted. You can START and STOP StoreGrid by running the script startstoregrid.sh and stopstoregrid.sh 4. If you chose option 1 in the above step, then you will either be asked to give the root password or the installation will quit and ask you to login as root and start the installation process again. Once you give the root password, you will be asked to provide a password for the storegrid user account which will be created. Note that StoreGrid will be installed as a daemon process and will automatically start when the system boots up. You can START and STOP StoreGrid by running the command "/etc/init.d/storegrid start/stop". You can check the status of StoreGrid application by running the command "/etc/init.d/storegrid status". If you chose option 2, then you will be taken to the next step directly. Note that StoreGrid will be installed in the current user directory and has to be manually started every time the machine is rebooted. You can START and STOP StoreGrid by running the script startstoregrid.sh and stopstoregrid.sh 5. Read through the License Agreement carefully. If you agree, enter Yes to continue with the installation. If you do not agree, enter No to abort the installation. 6. By default StoreGrid will be installed in the "Current Directory". Setup will install StoreGrid under "Vembu/StoreGrid" in the "Current Directory" directory. To install in a different directory, enter the

absolute path for Vembu StoreGrid installation. Note that setup will create the "Vembu/StoreGrid" directory under the directory you entered. 7. Updating from StoreGrid 1.5.1 to 1.6 If Vembu/StoreGrid directory is found in the installation path. You will be provided with three update options. 1 - UPDATE Vembu StoreGrid by retaining the previous backup data. Note that all backup data in StoreGrid 1.2.1 is compatible with StoreGrid 1.6. [Recommended] 2 - RENAME previous backup data folders and continue with updating Vembu StoreGrid. 3 - DELETE previous backup data and continue with updating Vembu StoreGrid. You will lose all your previous configuration and other backup metadata and also any backup data from other users backing up to this computer. [Not Recommended] 8. Updating from StoreGrid 1.2.1 to 1.6 If Vembu/StoreGrid directory is found in the installation path. You will be provided with three update options. 1 - UPDATE Vembu StoreGrid by retaining the previous backup data. Note that all backup data in StoreGrid 1.5.1 is compatible with StoreGrid 1.6 [ Recommended ] 2 - RENAME previous backup data folders and continue with updating Vembu StoreGrid. 3 - DELETE previous backup data and continue with updating Vembu StoreGrid. You will lose all your previous configuration and other backup metadata and also any backup data from other users backing up to this computer. [ Not Recommended ] 9. Configure StoreGrid as: You need to choose one of the options (Client-Server, Client, Server). The three modes are explained in detail below. Client-Server - This option will configure this StoreGrid installation to run in full peer mode, which means StoreGrid can function both as a client backing up local files/folders to other StoreGrid peers and also as a server which can be used for backing up data from other StoreGrid peers. Client - This option will configure this StoreGrid installation to run only as a client (half peer), which means StoreGrid can backup local files/folders to other StoreGrid peers but cannot accept backup data from other StoreGrid peers. Server - This option will configure this StoreGrid installation to run only as a server (half peer), which means StoreGrid can accept backup data from other StoreGrid peers but cannot backup local files/folders to other StoreGrid peers. 10. Vembu StoreGrid Web Console Authentication: Since StoreGrid's user interface is browser based you need to configure a username and password to login to StoreGrid Web Console. Note that you can add additional users, delete users, change password etc. from the Web Console UI after the installation. 11. Web Server Port StoreGrid's user interface is browser based. By default StoreGrid Web server is configured to run on port 6060. From your browser you will have to type http://<your Machine Name>:6060 to start the StoreGrid Web Console. 12. This installs the product and completes the installation process. After successful installation, you are provided with an option to start the StoreGrid. After the installation, you can start StoreGrid by executing the script "startstoregrid.sh" from the directory "<INSTALLATION_HOME>/Vembu/StoreGrid/".

Note: After successful installation, you can open the StoreGrid Web Console from your browser by typing http://<your Machine Name>:6060. You will have to login to the Web Console using the username and password you provided in the "Vembu StoreGrid Web Console Authentication" step during the installation.

Vembu StoreGrid Mac OS X Installation Guide The StoreGrid Mac OS X version is available for download in the following URL: http://www.vembu.com/storegrid/storegrid-download-form.html Download the Mac OS X installer, VembuStoreGrid_1_6_Mac.zip Note: In Mac OS X, you will not be able to open a new terminal window when StoreGrid installation process is in progress. Browser Support: In Max OS X 10.4.1 (Tiger), StoreGrid WebConsole User Interface works only with FireFox browser. Both Safari and Internet Explorer are not supported. You can get the FireFox browser from http://www.mozilla.org/products/firefox/ To install StoreGrid on Mac OS X machines, follow the steps given below: 1. Unzip the file VembuStoreGrid_1_6_Mac.zip. The contents of the zip file will be extracted under the directory VembuStoreGrid_1_6_Mac. 2. Go to the VembuStoreGrid_1_6 directory and double click the file "InstallStoreGrid" and follow the instructions in the installation wizard. 3. Click Next to begin the installation process. Go through the license agreement, select "I accept the agreement" and proceed to the Next step. 4. By default, StoreGrid will be installed under "Vembu/StoreGrid" in the current directory. Click Next to continue installation in this directory. Click Browse to choose a different directory. Note that this will create the "Vembu/StoreGrid" directory under the directory you choose. Click Next to continue. 5. Updating from StoreGrid 1.5.1 to 1.6 If Vembu/StoreGrid directory is found in the installation path. You will be provided with three update options. 1 - UPDATE Vembu StoreGrid by retaining the previous backup data. Note that all backup data in StoreGrid 1.5.1 is compatible with StoreGrid 1.6 [ Recommended ] 2 - RENAME previous backup data folders and continue with updating Vembu StoreGrid. 3 - DELETE previous backup data and continue with updating Vembu StoreGrid. You will lose all your previous configuration and other backup metadata and also any backup data from other users backing up to this computer. [ Not Recommended ] 6. Select how you d like StoreGrid to run on this machine. You have three options: Client & Server This computer can back up on to other computers and vice versa. This setting is especially relevant if you are running StoreGrid as a peer to peer backup solution. Client only This computer can back up on to other computers. However, other computers cannot back up on to this computer. Server only Other computers can back up on to this computer. However, this computer cannot back up on to other computers. Select one of the three options and click Next 7. There are two parts to this step.

Configure Web Server Port: StoreGrid's user interface is browser based. You have the option to configure the port used by StoreGrid web server here. Once configured you need to use this port to start the StoreGrid Web Console from your browser. By default StoreGrid Web server is configured to run on port 6060. Unless you are an advanced user, please leave this as is. Username & Password: Since StoreGrid's user interface is browser based you need to configure a username and password to login to StoreGrid Web Console. Note that you can add additional users, delete users, change password etc. from the Web Console UI after the installation. By default the username and password used by StoreGrid is "admin" and "admin". You have the option to change these default settings here. 8. This installs the product and complete the installation process. After successful installation, you are provided with two options to start StoreGrid. Either you can start StoreGrid as a daemon process or as an application. To start StoreGrid as daemon process, select "Daemon Process" and click "OK" and enter the password of the current user. Make sure that the current user has admin rights. To stop StoreGrid, open a terminal and execute the command "/sbin/systemstarter stop StoreGrid" To start StoreGrid, execute "/sbin/systemstarter start StoreGrid". To remove StoreGrid running as daemon process, remove the directory "/System/Library/StartupItems/StoreGrid". To start StoreGrid as application, select "Application Process" and click "OK". To stop StoreGrid, execute the script "stopstoregrid.sh" from the directory "<INSTALLATION_HOME>/Vembu/StoreGrid/". To start StoreGrid, execute the script "startstoregrid.sh" from the directory "<INSTALLATION_HOME>/Vembu/StoreGrid/". Note: After successful installation, you can open the StoreGrid WebConsole from your browser by typing http://<your Machine Name>:6060. You will have to login to the WebConsole using the username and password you provided during installation.

Vembu StoreGrid FreeBSD (for FreeBSD 5.2 and above) Installation Guide The FreeBSD version (for FreeBSD 5.2 and above) of StoreGrid is available for download at the following URL: http://www.vembu.com/storegrid/storegrid-download-form.html Download the bin file: For FreeBSD 5.2 : VembuStoreGrid_1_5_1_FreeBSD.zip For FreeBSD 5.4 : VembuStoreGrid_1_5_1_FreeBSD_5_4.zip To install StoreGrid on FreeBSD machines, follow the steps given below: 1. Unzip the downloaded ZIP file. 2. Execute the bin file VembuStoreGrid_1_5_1_FreeBSD.bin. 3. The first step in the installation is to choose the type of installation. You will be given two options: You can install StoreGrid in a newly created storegrid user account, where the storegrid user account will be automatically created with root privileges You can install StoreGrid in the current user account without root privileges. Choose option 1, if you want StoreGrid to have root privileges so that it can be configured to backup user data, MySQL, System Files etc. Note that StoreGrid will be installed as a daemon process and will automatically start when the system boots up. You can START and STOP StoreGrid by running the command "/etc/init.d/storegrid start/stop". You can check the status of StoreGrid application by running the command "/etc/init.d/storegrid status". Choose option 2, if you want StoreGrid to only backup files in the current user directories. Note that StoreGrid will be installed in the current user directory and has to be manually started every time the machine is rebooted. You can START and STOP StoreGrid by running the script startstoregrid.sh and stopstoregrid.sh 4. If you chose option 1 in the above step, then you will either be asked to give the root password or the installation will quit and ask you to login as root and start the installation process again. Once you give the root password, you will be asked to provide a password for the storegrid user account which will be created. Note that StoreGrid will be installed as a daemon process and will automatically start when the system boots up. You can START and STOP StoreGrid by running the command "/etc/init.d/storegrid start/stop". You can check the status of StoreGrid application by running the command "/etc/init.d/storegrid status". If you chose option 2, then you will be taken to the next step directly. Note that StoreGrid will be installed in the current user directory and has to be manually started every time the machine is rebooted. You can START and STOP StoreGrid by running the script startstoregrid.sh and stopstoregrid.sh 5. Read through the License Agreement carefully. If you agree, enter Yes to continue with the installation. If you do not agree, enter No to abort the installation. 6. By default StoreGrid will be installed in the "Current Directory". Setup will install StoreGrid under "Vembu/StoreGrid" in the "Current Directory" directory. To install in a different directory, enter the absolute path for Vembu StoreGrid installation. Note that setup will create the "Vembu/StoreGrid" directory under the directory you entered. 7. Updating from StoreGrid 1.5.1 to 1.6 If Vembu/StoreGrid directory is found in the installation path. You will be provided with three update options. 1 - UPDATE Vembu StoreGrid by retaining the previous backup data. Note that all backup data in StoreGrid 1.2.1 is compatible with StoreGrid 1.6. [Recommended]

2 - RENAME previous backup data folders and continue with updating Vembu StoreGrid. 3 - DELETE previous backup data and continue with updating Vembu StoreGrid. You will lose all your previous configuration and other backup metadata and also any backup data from other users backing up to this computer. [Not Recommended] 8. Configure StoreGrid as: You need to choose one of the options (Client-Server, Client, Server). The three modes are explained in detail below. Client-Server - This option will configure this StoreGrid installation to run in full peer mode, which means StoreGrid can function both as a client backing up local files/folders to other StoreGrid peers and also as a server which can be used for backing up data from other StoreGrid peers. Client - This option will configure this StoreGrid installation to run only as a client (half peer), which means StoreGrid can backup local files/folders to other StoreGrid peers but cannot accept backup data from other StoreGrid peers. Server - This option will configure this StoreGrid installation to run only as a server (half peer), which means StoreGrid can accept backup data from other StoreGrid peers but cannot backup local files/folders to other StoreGrid peers. 9. Vembu StoreGrid Web Console Authentication: Since StoreGrid's user interface is browser based you need to configure a username and password to login to StoreGrid Web Console. Note that you can add additional users, delete users, change password etc. from the Web Console UI after the installation. 10. Web Server Port StoreGrid's user interface is browser based. By default StoreGrid Web server is configured to run on port 6060. From your browser you will have to type http://<your Machine Name>:6060 to start the StoreGrid Web Console. 11. This installs the product and completes the installation process. After successful installation, you are provided with an option to start the StoreGrid. After the installation, you can start StoreGrid by executing the script "startstoregrid.sh" from the directory "<INSTALLATION_HOME>/Vembu/StoreGrid/". Note: After successful installation, you can open the StoreGrid Web Console from your browser by typing http://<your Machine Name>:6060. You will have to login to the Web Console using the username and password you provided in the "Vembu StoreGrid Web Console Authentication" step during the installation.

User Guide Once StoreGrid is installed in your PC, you can control, configure and administer it from the StoreGrid System Tray, StoreGrid Program Menu and the StoreGrid Web Console. StoreGrid System Tray/StoreGrid Program Menu (In Windows) From the System Tray and StoreGrid Program Menu (Start->Programs->Vembu StoreGrid) you can do the following: Start StoreGrid: This will start the StoreGrid service if it is not already started. Stop StoreGrid: This will stop the StoreGrid service if it is running. Any backup or restore in progress will be stopped abruptly and hence they will be incomplete. Open StoreGrid Web Console: This will open the Web Console in your default browser. You can also open the Web Console by typing the URL http://[machine-name]:6060. StoreGrid Web Console is the browser based user interface from which you can configure backups, restore backed up data, manage and administer StoreGrid peers etc. Open StoreGrid Help Documentation: This will open this help documentation in your default browser. Help documentation can also be opened from the StoreGrid Web Console. Change StoreGrid Mode: This option is available only from the System Tray. A computer can be a StoreGrid "Client" or a StoreGrid "Server" or "Both". You would have selected one of these options: Client/Server/Both when you installed StoreGrid. Please see Terminology for a more detailed explanation of StoreGrid Clients & Servers. You can change the mode in which StoreGrid is running from the menu in the System Tray. Note that StoreGrid will restart automatically before the mode is changed. Uninstall StoreGrid: This option is available from the program menu. This will stop the StoreGrid service and uninstall StoreGrid from your PC. Note that not all files will be deleted. You need to go to the StoreGrid installation directory and delete some of the directories and files manually. StoreGrid Web Console You can open the Web Console by right-clicking the StoreGrid icon in your system tray and selecting the Storegrid Web Console from the menu, or alternatively, doing the same through the Start Menu: Start->Programs->Vembu StoreGrid->StoreGrid Web Console. In other operating systems like Linux, you need to open the browser and type the URL http://[machine-name]:6060 to open the StoreGrid Web Console. 1. StoreGrid Web Console is a browser based intuitive User Interface that is all you need to ensure your data is backed up as required. Before starting up, it will require you to enter a username & password (the same as entered while installing StoreGrid). Your machine name will be your unique identifier on the StoreGrid network, and your computer will be referred to as a client / server / both (depending on set up) using your machine name. 2. If you look at the top left corner of the StoreGrid Web Console, your current mode of operation is indicated there. "Joe [Client]" would indicate that the machine with a machine name 'Joe' is currently active in 'Client mode'. You can change the mode in which StoreGrid is running from the StoreGrid Tray. But the change of mode is supposed to be done rarely. Changing from Client to a Server etc. will affect any backup that has been done. So when a change of mode is done it is better to delete the backups etc. in the peer and configure everything afresh. You can switch to other StoreGrid peers of your choice by 'Switching' to it in the pop down menus provided (of course you'll need the appropriate Username/Password) in the top right corner. This feature allows StoreGrid to be configured and managed from/to any machine on the network. The next sections in this help documentation describe in detail how to use the features in the StoreGrid product from the Web Console.

Configure Backup Schedule How to get here in the StoreGrid Web Console? In the top menu, select: "Backup->Add Backup Schedule" Backup Files/Folders Configuration On the left side of the "Configure Backup Schedule" Page, is the tree with a list of drives and directories in the client machine. Select the directories and (or) files that need to be backed up as part of this schedule. Don't worry if some strange files/directories appear in this tree - StoreGrid allows you to backup hidden/system files as well, and while these may not be visible in your file explorer, they are nonetheless there! You will also see shortcuts and icons of stuff you may routinely wish to backup, eg. IE/Firefox settings, windows registry, etc. Backup Parameters Configuration Adjacent to the directory tree on the right side of the page, the configuration options of this backup schedule should be provided. For convenience, the configuration options are split into four windows: 1. Backup Details 2. Schedule Details 3. Security Details 4. Advanced Settings Each of these is described below: Backup Details Backup Name - This is a unique name for this backup schedule. Write anything you please. Backup Server(s) - This is the list of peers/backup servers in which the backup data can be stored. The more the number of backup machines chosen, the better will be the reliability (just in case a bunch of machines on your network decide to crash at the same time). The backed up data is mirrored across all the selected backup server machines. CPU Utilization - For each backup schedule, you can also specify the CPU utilization level as Low, Medium or High. When you set the CPU Utilization to high, the backup will be really fast - but the backup process may affect the speed of other active applications. If CPU utilization is set to Low, the backup will take longer but will be done in a non-intrusive manner allowing you to comfortably work on the computer as the backup continues in the background. In general for a continuous backup, it is best to set the CPU utilization to Medium or Low. And for backups which are done everyday or every week in off-hours, the CPU utilization can be set to High. Actual performance is obviously a function of your individual machine and your network. We encourage you to experiment with different settings to figure what works best for you. Compression - Should the data be compressed? Setting it to "No compression" will not compress the data and hence the backup may happen faster. The other options are : Best Compression - Slow but best level of compression Default Compression - Optimal trade-off between compression ratio & speed Fast Compression - Sacrifices compression ratio for speed No Compression - Fastest but occupies more space on destination machine as no compression is being done

Schedule Details This field has the following options from which any one can be chosen. Immediate - Choosing this option will do the backup only once immediately. And the backup will then be put into suspended mode. If you wish to run this backup again, you ll have to manually select it from the List Backup Schedules page. Continuous - Choosing this option will execute an immediate backup; thereafter, StoreGrid continuously monitors any changes to the files or directories configured for backup. When changes occur, a backup is scheduled. Run Every - Choose the hours/minutes between each time StoreGrid must run. Run Daily at - Execute the backup everyday at a particular time. Run Weekly on - Execute the backup every week on a particular day, at a particular time. Security Details Encryption - This option is to enable or disable encryption of the data that is being backed up. StoreGrid uses a well known encryption algorithm, Blowfish. If enabled, a password has to be specified which will be used as the KEY for the encryption. The password has to be exactly 8 characters. If the password is forgotten the data can never be recovered as the data cannot be decrypted without this password. So, please ensure that you keep your password in a safe place. Encrypting data ensures that it cannot be read in the destination machine (backup server) where your backup is stored, and is especially relevant for sensitive information. Advanced Settings (Optional) Incremental Backup - When a backup schedule is executed, StoreGrid checks if the file has changed since the last backup. If yes, then StoreGrid can either backup the full file all over again or it can backup only the modified content (incremental). If "Incremental Backup" is set to ENABLE, only modified content in a file is backed up. If set to DISABLE, the full file will be backed up every time the schedule runs. Needless to say, an incremental backup is faster. Versioning - StoreGrid can maintain multiple versions of the same file when it is backed up. Here, you can specify the maximum number of versions that StoreGrid should maintain for each file in this backup schedule. The number of versions can be between 1 and 10. Do note that if you have disabled Incremental backup, then the versioning settings are not considered. Advanced Backup Schedule Settings There are three options here on how the backup should be scheduled. Run this backup each time StoreGrid restarts - If you enable this option by checking the checkbox, then this backup schedule will be run every time StoreGrid is restarted or the machine is rebooted irrespective of the actual schedule time of this backup schedule. This is to ensure that any modified or new files created when StoreGrid was down are backed up as soon as possible. Run this backup immediately after saving this configuration (thereafter, Backups will be scheduled as per the schedule stipulated) - If you enable this option, then this backup schedule will be executed once immediately after you save this backup schedule even if its not yet time as per the schedule. For example if you configure a daily backup at 10.00 AM but you configured the backup at 8.00 AM, then the backup schedule will be run once immediately (8.00 AM) and then as per schedule (eg. daily at 10.00 AM).

Attempt to run this backup every 5 minutes in case of non completion because of a problem (Network error etc.) - If enabled, then this backup schedule, irrespective of the schedule time/interval, will be scheduled every 5 minutes whenever a backup is incomplete because of a network error, server crash etc. This is to ensure that an incomplete backup is completed as soon as possible without waiting for the actual schedule time. Files/Folders Filter Settings Include Files of Type - Using this field you can specify one or more file types that should be backed up. For example, setting it to *.doc will backup only the files with extension doc (in the folders selected). However, any files specifically selected for backup in the tree will be backed up even if they are not.doc files StoreGrid assumes that you selected these files with a reason! You can specify multiple file types by separating them with commas (eg *.doc, *.xls). Please note that these filter criteria will not be applied for shortcut backup schedules like IE Favorites, Outlook & Registry backups. Exclude Files of Type - Using this field you can specify one or more specific type of files that should not be backed up. For example, setting it to *.gif will not backup any file with extension gif for all the folders configured in the tree. However, any files specifically selected for backup in the tree will be backed up even if they are.gif files StoreGrid assumes that you selected these particular files with a reason! You can specify multiple file types by separating them with comma (eg *.gif, *.jpg). Please note that these filter criteria will not be applied for shortcut backup schedules like IE Favorites, Outlook & Registry backups. Exclude Subdirectories - Check this option if you want to exclude all the subdirectories under your selected folders for backup. Saving the configured backup Once all the directories/files to be backed up are chosen and the configuration options are set, you simply need to click on the "Configure Backup button to activate the backup as per the schedule- on to the configured backup servers. Limitations - The Files/Folders tree in this page is based on Java Script. Every time a folder is opened a fresh request is sent to the StoreGrid client and the full page is re-loaded. This process may take a little time. Also, when a folder has 1000s of files, then the java script takes time to load the tree. Please be patient

Open File Backup During a backup, StoreGrid needs the requisite permission to access the file(s) that are to be backed up. Some (open) files may be in use at the time by other applications. While StoreGrid makes all possible efforts to backup these files, it may not always be possible. For example, Microsoft Outlook cannot be backed up if it is open as StoreGrid cannot access the requisite files as Outlook does not permit the file to be shared! While StoreGrid can still manage Outlook Backups (click for details), the best way to handle open file backups is to use StoreGrid s Open File Plug-in. The plug-in is pre-configured to allow StoreGrid access to open files, and with it you needn t worry about files not being backed up because they happened to be in use at the time of backup. For more details, please visit us at http://www.vembu.com/storegrid/open-file-backup.html

Outlook Backup If you ve created a StoreGrid schedule to backup your Outlook data (emails, calendar, notes, etc) there are a couple of points you need to be aware of. If Outlook is open at the time StoreGrid attempts a backup, StoreGrid, by itself, will not be able to access all files required for backup. The best way to solve this is to install StoreGrid s Open File Plug-In. Please see http://www.vembu.com/storegrid/open-file-backup.html for more details on this. Besides Outlook, this plug in will also facilitate backups of other open files. If you do not have the open file plug-in, and have Outlook open at the time of backup, StoreGrid can still complete the backup! StoreGrid, recognizing that Outlook is open, will prompt you with an alert mentioning that you have an Outlook backup scheduled and that it needs to close Outlook to complete the backup. If you agree, StoreGrid will close Outlook, complete the backup and thereafter reopen Outlook. Outlook will prompt you to save any open work before it is closed. If StoreGrid is unable to close Outlook, the Outlook backup will not be fully completed and StoreGrid alerts you about this as well.

Check Backup Progress As soon as you configure a backup from the Configure Backup Schedule page, you will be taken to a new page, which will show the backup schedule just configured. It will also pop up a window, which will show the progress of this backup if it is currently in progress. If the pop up window does not open automatically (could also happen if you have popup blockers installed), you can click on the "Backup Progress" button in the "View Backup Configuration" page. Alternatively, you can go to the List Backup Schedules page from the backup menu and then click on the backup name. This will also open the backup progress window if the backup is active! What does the Check Backup Progress window tell you? The total number of files to be backed up. The number of files backed up so far. The name of the file that is currently being backed up (might change too fact for you to take notice). The Backup server on to which the backup is being taken. Total time elapsed since the backup started. The Backup Report button will open the detailed report of the backup schedule. Limitations - The backup progress window polls the StoreGrid Client every single second to get the progress of backup. This process can slow down the actual backup operation by between 50 to 75%! So, for large backup schedules it is better to keep the backup progress window closed and open it only occasionally to check the backup progress.

Suspend Backup Schedule To suspend (and later resume) a backup schedule, you need to do the following: Go to the List of Backup Schedule page. In the column titled "Backup Status", you will see a link named suspend or resume for each backup schedule listed. Clicking on the suspend link will suspend the backup (and the status will change to suspended ). Clicking on the resume link will resume the backup and schedule it as per its schedule. However, a resumed backup will also run once immediately and thereafter as scheduled. Limitations - Suspending a backup schedule may not take immediate effect if the backup is in progress; the schedule will be suspended only after the file currently being backed up - is backed up. Obviously, if the current file is a large file, then the suspension can take a few seconds and even up to a few minutes.

Edit Backup Schedule How to get here in the StoreGrid Web Console? In the top menu, select: "Backup->List Backup Schedules". From the list of backup schedules, select the required backup schedule and click the Edit button at the bottom. This page is used to edit a configured backup schedule. Note that only some of the configuration options are editable. Please note that the following options are not editable: 1. File and Folders Configured for backup. 2. Compression type. 3. Encryption (and password). 4. Incremental Backup settings. Limitations - Some of the backup schedule parameters cannot be edited. Editing settings like compression, encryption and incremental backup will make the new backup data and the old backup data (already backed up) incompatible. Editing files/folders configured for backup while feasible is not possible in this version.

View Backup Schedule How to get here in the StoreGrid Web Console? In the top menu, select: "Backup-> List Backup Schedules. From the list of backup schedules, select the backup schedule and click the View button at the bottom. Very simply, this page displays details on schedules you ve previously configured!

Delete Backup Data/Schedule How to get here in the StoreGrid Web Console? In the top menu, select: "Backup-> List Backup Schedules. From the list of backup schedules, select the backup to be deleted and click on the "Proceed to Delete" button at the bottom. This will delete backed up data from a backup server. It will also delete all the meta data information about the backup (stored in the client). The following options are configurable before proceeding with the delete operation: 1. What to delete: Schedule & Data OR Data only. 2. Backup server(s) from which to delete. Once all the options are set as described above, click on the Delete button to activate the delete operation. The status of the delete can be viewed from the Deleted Backup Reports page. Please note the the following: 1. If a backup is in progress when the delete operation was invoked, then the backup will be suspended automatically and the backup data (and schedule) will be deleted. 2. If there are problems with the delete operation, the status report will indicate that and the delete operation will be scheduled every 5 minutes. 3. If a restore of the backup data is in progress when the delete operation is invoked, then the delete operation will be aborted. The delete operation has to be manually invoked again. Limitations - If a backup could not be deleted because of some reason (the backup server being down permanently etc.) then the delete operation will be scheduled every 5 minutes. There is no way to cancel the delete operation. It will be scheduled again even when StoreGrid is stopped and restarted.

Client Deleted Backup Report How to get here in the StoreGrid Web Console? In the top menu, select: "Reports -> Deleted Backup Report" This page gives a status report of the delete backup operations initiated in this StoreGrid Client. The following information is provided in the report for each delete operation scheduled. Backup Schedule - This is the backup schedule name in the client for which the delete operation was scheduled. Click on the backup schedule name for a detailed report on each delete operation, including relevant messages concerning the delete operation. Backup Server - The backup server on which this schedule's backup data is to be deleted. Status - This gives the status of the delete operation. It can be either a Success or a Failure. Configured Time - The time at which the delete operation was scheduled. Total Time Taken - Time taken to execute the delete operation. Total Time Attempted - The number of times StoreGrid attempted to execute the delete operation (if this is more than 1, you know there was a problem first time around).

List of Backup Schedules How to get here in the StoreGrid Web Console? In the top menu, select: "Reports-> List Backup Schedule This page gives the list of backup schedules configured in this client with a summary of each schedule s backup status. List of Backup Schedules This tabular summary of each schedule s backup status includes the following: Backup Schedule - The name of the backup schedule detailed in this row. Backup Servers - Backup server on to which this backup schedule backs up. If a backup schedule backs up to more than one server, then it will be represented as a separate row in the table. That is, each row in this table represents a backup report for a backup operation to a single server. Total Files - The total number of files to be backed up as part of this backup schedule. Total Files Protected - The number of files that were successfully backed up to the server specified in the column "Backup Server". Total Files Skipped - The number of files that could not be backed up. Some of the reasons a file could not be backed up are: 1. The file is being modified. 2. The file did not have appropriate permissions and hence could not be read. The detailed backup report contains the actual reason a file could not be backed up. Note that StoreGrid tries to backup all skipped files continuously until it succeeds. Last Backup - The time at which the Last backup was done on to the backup server for this backup schedule. Success Rate - This gives the percentage of total files that were successfully backed up. View Report Button Each row in this report has a radio-button on the left corner of the row. You can choose a backup schedule and click on the View Report button to view a more Detailed Report for this schedule.

Backup Summary Report How to get here in the StoreGrid Web Console? In the top menu, select: "Reports->Dash Board " This page gives a summary report of all backups configured for this client along with the disk utilization information. This report has three tables: Backup Summary This table gives the summary of all the backup schedules configured on this client. The table has the following details Backup Schedule - The name of the backup schedule detailed in this row. Backup Servers - Backup server on to which this backup schedule backs up. If a backup schedule backs up to more than one server, then it will be represented as a separate row in the table. That is, each row in this table represents a backup report for a backup operation to a single server. Total Files - The total number of files to be backed up as part of this backup schedule. Total Files Protected - The number of files that were successfully backed up to the server specified in the column "Backup Server". Total Files Skipped - The number of files that could not be backed up. Some of the reasons a file could not be backed up are: 1. The file is being modified. 2. The file did not have appropriate permissions and hence could not be read. The Detailed Backup Report contains the actual reason a file could not be backed up. Note that StoreGrid tries to backup all skipped files continuously until it succeeds. Last Backup - The time at which the Last backup was done on to the backup server for this backup schedule. Success Rate - This gives the percentage of total files that were successfully backed up. Disk Space Used By This Client This table gives the disk space utilized by this Storegrid client on all the backup servers it backs up on to. Note that if this StoreGrid installation is not configured as a StoreGrid client, this table will be empty. The following are the columns in the table: Backup Server - The backup server on to which this client backs up. Allotted Space - The maximum disk space allotted for this client on the backup server. Used Space - The disk space this client's data is occupying in the backup server. Note if this disk space used becomes equal to the allotted space, the server will reject this client's backup. Disk Space Used On This Server This table gives the disk space utilization of other StoreGrid clients backing up to this Storegrid server. Note that if this StoreGrid installation is not configured as a StoreGrid server, this table will be empty. The following are the columns of this table: Client Name - This is the StoreGrid client name, which is backing up to this storegrid server.

Allotted Space - The maximum disk space allotted for the client in this storegrid server. Used Space - The disk space the client's data is occupying on this StoreGrid server. Note if this disk space used becomes equal to the allotted space, this server will reject the client's backup. The final row in the table gives the Total disk space configured on this server for all clients along with the total disk space used by all the clients.

Detailed Backup Report How to get here in the StoreGrid Web Console? In the top menu, select: "Reports-> List Backup Schedule". Choose a backup schedule from the list and click on View Report button. This page gives a detailed report for a backup schedule: Backup Schedule Name - The name of the backup schedule for which this backup report is generated. Backup Server(s) - The list of backup servers on to which the backup schedule is backing up. Backup Report Table - This table gives specific details on the consolidated and last backups: Total Files - The total number of files to be backed up as part of this backup schedule. Total Files Protected - The number of files that were successfully backed up to the server specified in the column "Backup Server". Skipped Files - The number of files that could not be backed up. Some of the reasons a file may not be backed up are: 1. The file is being modified. 2. The file did not have appropriate permissions and hence could not be read. If there are skipped files, then you will have a View link, which when clicked will list the skipped files and also the details on the reasons why the file is skipped. Note that, StoreGrid tries to backup all skipped files continuously until it is successful. Transferred Size - The total number of bytes transferred to the server as part of this backup. Success Rate - This gives the percentage of total files that were successfully backed up. Files and Directories List - Click Show for a list of all the directories and files included in this backup schedule. Table detailing last backup & schedule information - Provides the start time, the end time and the total time taken to complete the last backup. It also provides details on the last schedule - it simply reassures you that StoreGrid is running as scheduled (for example, if nothing changed after the last backup, the next time StoreGrid is scheduled to execute the backup, it will simply run the schedule but not a backup - since there is no change after the last backup. In this case, the last schedule time will be more recent than the last backup time) Other Information The other information that are shown are the backup configuration information for this backup schedule. They are Schedule Interval, Incremental Backup, Encryption, Compression, CPU Utilization, Backup File Filter etc.

Restore Backup Data How to get here in the StoreGrid Web Console? In the top menu, select: "Restore". It will display the "List Of Backup For Restore" page. Select the backup schedule to restore and click on the "Proceed to Restore" button. In StoreGrid, restoring files and directories is quite simple and can easily be done by end users themselves without the help of System Administrators. You need to choose the files/folders that need to be restored from the tree on the left side. You can restore all the files/folders backed up by choosing the root node (of your backed up files/folders path) in the tree. Files with multiple versions backed up have a blue (v) adjacent to them, expanding (clicking the + next to the file name) the file lists all available backed up versions of the file. If you simply check the box adjacent to the file name itself, or a higher-level folder, by default, the latest version is restored! Deleted files are crossed out with a red X indicating that while a version of this file has been previously backed up, the file no longer exists in the original location. You can restore these files if you wish! The following additional items need to be configured before restoring your data: Backup Server Name - This is a drop down menu with a list of servers on to which the backup schedule has backed up data to. Choose one of the servers. You may wish to simply select the default server listed - as that server is available for restore for sure. Password - If you had password protected the backup schedule, you will need to provide the 8- character password here. Restore Machine - This is the StoreGrid client to which the backup data has to be restored to. By default it will show the current client (from which the backup was done). Restore Deleted Files - This is a checkbox. When checked, StoreGrid will restore any deleted files in the chosen directories. If not checked, StoreGrid will leave out the deleted files and only restore other files. Restore Location - You have two options: 1. Original: Setting this option will restore the backup data to its original location. Note that if the original file is already present in that location, the restored file will be saved with an extension SG (eg. a.doc will be saved as a.doc.sg) unless you specify otherwise in the Advanced Settings below. 2. Alternate: By setting this option, you can specify the alternate location to which the backup data has to be restored. The restored files will be saved in this location, but with their full original path that way you know exactly where these files were in the first place! Advanced Settings - When backup data is restored, it is possible that the original files are already present in the restore location. In this case StoreGrid by default will retain the original file and rename the restored file with an extension *.SG. Advanced settings allows you to change this. The following options are available: 1. Rename the restored file with a.sg extension and keep the existing file as it is. This is the default behaviour, and is recommended. 2. Rename the existing file with a.sg extension and restore the backed up file as it is. 3. Overwrite the existing file with the restored file. If the existing file is different from the backed up file being restored, the contents of the existing file will be. Choose this option only if you are absolutely sure that the current file can be overwritten. Restore and Cancel Button - Once all the options are set and the files and folders to be restored are selected, click on the Restore button to restore the files and folders. The status of the restore operation will be displayed on a pop-up browser window. The Cancel button will cancel the restore operation and take you back to List of Backup For Restore page.

Restoring IE, Outlook Express & Registry IE Settings, Outlook Express & Registry data are stored in multiple locations. In order to completely restore your backed up configuration, you need to follow a few extra steps 1. Follow the steps for a regular restore operation ensuring that when prompted for Restore Location, you select the Original location. you click on Advanced Settings and select the third option, viz. Overwrite the existing file with the restored file. Note that any old data will be overwritten! 2. Restore! (if restoring Outlook, please ensure that Outlook is closed at the time of restore) 3. The required files are now in their designated locations. You only need to update the registry now an easy task with StoreGrid! For Win2000 Pro, Server, Win XP Pro, Home Edition, Win 2003 Server Simply double click the registry file from the appropriate location (locations of the registry files are mentioned at the bottom of this page) Say Yes/OK when prompted For Win 98, Win NT Server, WorkStation, Win ME (Not Tested) Use a text editor (like notepad) to open the registry file from the appropriate location (locations of the registry files are mentioned at the bottom of this page) Manually replace the first line of this file with the following text: REGEDIT4 Save the file and then double click it Say Yes/OK when prompted Registry file locations: Internet Explorer Settings: <Vembu_StoreGrid_Installed_Path>\data\IESettings\<Login_User_Name>\IEBackupFile.reg Outlook Express: <Vembu_StoreGrid_Installed_Path>\data\OutlookExpress\<Login_User_Name>\OutlookExpressBackupFile.reg Registry: <Vembu_StoreGrid_Installed_Path>\registry\regbackup.reg (note that Windows will say that all files could not be updated for a registry restore this is normal)

Restoring MySQL databases in Linux Restoring MySQL databases in Linux require a couple of extra steps. Please follow the instructions detailed below in sequential order. 1. Follow the steps for a regular restore operation ensuring that 2. Restore! when prompted for Restore Location, you select the Original location. you click on Advanced Settings and select the third option, viz. Overwrite the existing file with the restored file. Note that any old data will be overwritten! 3. The required files are now in their designated locations: <Vembu_StoreGrid_Installed_Path>\mysqlbackup\<Backup_Name>\<Database_Name>\<Restore_Fil e_name> The restored MySQL database files end with an extension ".gz". In order to use the restored database, you need to manually extract the restored ".gz" file to the original database location (which is /var/lib/mysql/" in most cases) as detailed below: gunzip <Restore_File_Name> - this will result in a tar file <Tar_File>. tar -xvf <Tar_File> - this will extract the tar and you will get the database directory <DB_NAME> which is the actual database. Apply the command chown mysqlusername:mysqlgroupname <DB_NAME> to the database directory to change the user and group of restored directory to the original user and group Copy the <DB_NAME> directory to the original database location.

Detailed Restore Report How to get here in the StoreGrid Web Console? In the top menu, select: "Restore". Select a backup schedule and click on the "Last Restore Report" button below. This page gives a detailed report of last restore operation done with this backup. This report will be empty if a restore was never done for a backup schedule. The following are the details given by the restore report: Backup Schedule Name - The name of the backup schedule this restore report is generated for. Backup Server - The backup server from which the restore was done. Destination Directory - The directory (in the client machine) where the backup data is restored to. Note that the data will be restored with the full original path under this destination directory just so you know where the data was in the first place! Also note that if a file with the same name is present already, then the restored file will be renamed with an extension *.sg If the last restore was done to the original location, then it simply says so! Start Time - The time at which the restore operation was started. End Time - The time at which the restore operation was completed. Time Taken For Restore - The time taken for the full restore operation to complete. Total Files - Total number of files present in the backup server that needs to be restored. Total Files Restored - The number of files successfully restored. Skipped Files - The number of files that could not be restored. Remaining Files - Number of files that could not be restored. Success Rate - The percentage of files that were successfully restored. Other settings configured during backup/restore Compression Settings Password protection (True/False) Incremental Backup (True/False) Restored Deleted Files (Yes/No)

List Of Events How to get here in the StoreGrid Web Console? Choose the menu item "Events". Thereafter, select the category of events you d like to view: critical/major/minor/warning/information Events are messages which give details about any problem that needs to be looked into by an administrator. There are number of problem scenarios under which events can be generated. Some of them are listed below: 1. When a backup is not taken because of a connection problem with the backup server. 2. When a file is skipped for backup because of inadequate permissions. 3. When a backup server refuses a backup request from a client because of exceeding allotted backup space. And so on... Events are also classified based on severity in typical Sys Admin lingo: Critical Events are relatively serious in nature and an administrator has to take some corrective action. Major, Minor and Warning events are less severe and may be transient. Information events are simply for information purposes.

Client Backup Disk Utilization How to get here in the StoreGrid Web Console? In the top menu, select: "Administration-> Disk Utilization" This page gives details of the disk space utilization of this StoreGrid client on all the backup servers it backs up on to. The following information is provided. Backup Server - The destination backup server on which the disk utilization of this client is being shown. Backup Location - The backup directory where this client's backup is being stored in the destination backup server. Allotted Space - The total disk space allotted for this client on the destination backup server. Used Space - The disk space currently used by this client on the destination backup server. Free Space - The disk space that is available for backup for this client on the destination backup server.

Add / Discover StoreGrid Peer(s) How to get here in the StoreGrid Web Console? In the top menu, select: "Administration-> Add/Delete Peer" and select the "Add Peer(s)" Tab. This page is used to discover & add StoreGrid peers, which are not automatically discovered. The console has the following fields: Machine Name - This is the name of the peer (if known) which needs to be added / discovered. You can also give the IP address of the peer and the DNS name will be automatically obtained. Machine Type - If you know the type of the peer (server/client), specify it here. If you don t, choose "Unknown". StoreGrid will try to automatically discover the type. Add Button - Once the machine name and the machine type are specified as described above, you can add it to the Machine List below by clicking on the Add Button. Once a StoreGrid peer is added to the list, you can go back and add more peers by following these steps again. Discover Button - Once you have added all the peers to be discovered, click the Discover button to start the discovery process. The StoreGrid peers will get added to the list of peers discovered, irrespective of whether they are currently available or not. Reset Button - Click on this button to reset the machine list and start afresh.

Remove / Delete StoreGrid Peer(s) How to get here in the StoreGrid Web Console? In the top menu, select: "Administration-> Add/Delete Peer" and select the "Delete Peer" Tab. This page is used to delete/remove StoreGrid peers which are no-longer running StoreGrid. Note that the deleted peer will get removed only from the current StoreGrid peer. Machine List - This lists all the currently discovered peers. Machines Selected to Delete - Peers to be deleted should be moved from the Machine List to this List. Delete Button - Click on the delete button to initiate the delete operation. Reset Button - Resets the list to the original values.

Allowing and Denying Backups StoreGrid 1.6 has a new feature, which allows you to configure a StoreGrid server to allow or deny backups from certain Clients. This configuration has to be done manually by editing the file conf/sgpremissions.conf. Once edited, StoreGrid has to be restarted for the configuration to take effect. Configuration of this feature is illustrated below with examples. Note: In the SGPermissions.conf XML file, the Allow tag will take precedence over the Deny tag. If you do not have the Allow tag, then it means Allow all except the ones specified under the Deny tag. If you do not have Deny tag, then it means Deny all except the ones specified under the Allow tag. If both the Allow and Deny tags are not present, then it means Allow all clients. Example 1: Allow only StoreGrid Client with name "debian30" and ipaddress "172.16.0.140" to backup to this server. Deny all other clients from SubNet 172.16.0.0 and netmask 255.255.0.0. Also deny all clients from all other subnets. <StoreGrid> <Permission> <Allow> <Peer id="1" IPAddress="172.16.0.140" Name="debian30"/> </Allow> <Deny> <Peer id="1" NetworkAddress="172.16.0.0" SubNetMask="255.255.0.0"/> </Deny> </Permission> </StoreGrid> Example 2: Allow only StoreGrid client with name "debian30" and ipaddress "172.16.0.140" to backup to this server. Deny all other clients from any subnet. Basically if you do not have the Deny tag, it means deny everything except the ones specified under the Allow tag. <StoreGrid> <Permission> <Allow> <Peer id="1" IPAddress="172.16.0.140" Name="debian30"/> </Allow> </Permission> </StoreGrid> Example 3: Allow all clients and Deny only StoreGrid Client with name "debian30" and ipaddress "172.16.0.140" <StoreGrid> <Permission> <Deny> <Peer id="1" IPAddress="172.16.0.140" Name="debian30"/> </Deny> </Permission> </StoreGrid> Example 4: Allow all Clients from subnet 172.16.0.0 with subnet mask 255.255.0.0. In this case the Deny StoreGrid Client with name "debian30" and ipaddress "172.16.0.140" will not be enforced as the ipaddress falls within the subnet rage allowed in the Allow tag. That is the Allow tag takes precedence over the deny tag. <StoreGrid> <Permission> <Allow> <Peer id="1" NetworkAddress="172.16.0.0" SubNetMask="255.255.0.0"/> </Allow> <Deny> <Peer id="1" IPAddress="172.16.0.140" Name="debian30"/> </Deny> </Permission> </StoreGrid>

User Administration How to get here in the StoreGrid Web Console? In the top menu, select: "Administration-> User Administration" The following tabs are available Create User - Enter the user name, password (must be confirmed) in the respective fields and click on the Create button. This will create a new user for accessing the current StoreGrid peer. Delete User - You can delete a user after entering the user name and the password for the user and clicking the Delete button. Change Password - You can change the current user's password by entering the current password, the new password (with reconfirmation) in the respective fields and clicking on the Update button.

Restore Client Configuration How to get here in the StoreGrid Web Console? In the top menu, select: "Administration-> Restore Client Configurations" Why is this feature necessary? In StoreGrid, without the backup schedule configurations, backed up data cannot be restored. So this page helps you in restoring the backup schedule configurations first. The backed up data can be restored from the List of Backup For Restore page. When is this feature relevant? Typically, if StoreGrid needs to be installed afresh in a machine because of a computer crash or other reasons (old computer stolen, etc). Once the backup schedules are restored, the List Backup Schedules page will show the backup schedules in a suspended mode. Using the reinstalled configuration, any lost data can first be restored (from the List of Backup for Restore page). Thereafter, the backup schedules can be resumed manually, if required. The following describes the user input for this page: Client Name - This is a non-editable field displaying the current StoreGrid client for which the configurations have to be restored. Choose Server Name - Choose the backup server name from which configurations have to be restored and press the Add button to be added to the "Added Server List". Enter Server Name - This is an optional field. If the backup server from which the configurations have to be restored is not present in the "Choose Server Name" above, you can manually enter the backup server name here and then press the Add button to be added to the "Added Server List". Restore Button - Once the server names chosen are added to the list, click the "Restore" Button. This will initiate the process of getting the client backup configurations from all the servers chosen. Reset Button - It will reset all the fields to their original values. Cancel Button - It will take you to the List of Backup Schedule page. Limitations - To restore the client configurations, you will necessarily need to know the servers on to which the backups were originally done. StoreGrid does not discover this information automatically.

Discovery Configuration How to get here in the StoreGrid Web Console? In the top menu, select: "Administration-> Discovery Configuration" This page is meant for configuring the automatic discovery feature in StoreGrid. Discovery is done to discover other StoreGrid peers in the subnet and also to check the status of other StoreGrid peers. The following are the types of discovery done and you can enable/disable them and also change the time interval for each type of discovery. Note that StoreGrid will discover other StoreGrid peers only within a subnet. You will have to manually add StoreGrid peers in other subnets from the menu item "Administration- >Add Peer". UDP Network Scanning - This scans for the UDP port 32006 inside the subnet to detect the presence of any StoreGrid peer. This is done every minute by default. You can enable/disable this discovery or change the time interval as required. By default, UDP Network Scanning is disabled in StoreGrid. TCP Network Scanning - This scans for the TCP port 32005 inside the subnet to detect the presence of any StoreGrid peer inside the subnet. This is done every 5 minutes, by default. Note that before a TCP port scan is done, StoreGrid actually does an ICMP ping to collect valid IP addresses. You can enable/disable this discovery or change the time interval from this user interface. By default TCP Network Scanning is disabled in StoreGrid. Multicast Discovery - StoreGrid uses the multicast ports 6363 and 6364 to send and receive multicast requests to discover other StoreGrid peers within the subnet. This is one of the fastest ways of discovering other StoreGrid peers provided multicasting works inside the subnet. This discovery is done every minute, by default. You can disable/enable this discovery or change the time interval as required. TCP Discovery - This is a more comprehensive discovery mechanism where StoreGrid shares peer information between each other. This sharing is done only within already discovered StoreGrid peers. Hence, no scanning of invalid IP addresses is done. This discovery cannot be disabled and by default it is run every 5 minutes. You can change the time interval of this discovery to a maximum time interval of 60 minutes. Note: 1. If a StoreGrid peer is not discovered automatically, you can add it manually from the Add Peer page. StoreGrid will discover peers only within a subnet. StoreGrid Peers outside the subnet have to be added manually. The manually added StoreGrid peer will show up only in the web console of the StoreGrid peer, which added it. 2. You can delete any StoreGrid peer from the Delete Peer page. The delete will take effect only in the web console of the StoreGrid peer that deleted the peer.

Server Name Migration This feature is extremely useful if you were originally backing up to a server and later wish to seamlessly transfer your backups to another server. A useful application of this feature is in the context of online backup services where the first backup is typically the most time consuming and is often completed overnight or in batches. With StoreGrid s Server Name Migration facility, you can now do a local backup first (perhaps on to an external hard disk) and thereafter transfer this data on to your remote server. From this point on, clients can send incremental backups alone to the remote server saving bandwidth and time. This feature is available from version 1.6. Here s how you can get it working: 1. Log in as the client (or type http://<storegrid client>:<webconsole port> in your browser - <webconsole port> Is typically 6060) 2. Once you ve logged in, type http://<storegrid client>:<webconsole port>/servernamemigration.sgp in your browser (later versions will have a shortcut from the main menu to this feature) 3. From the dropdown list select the server on which the backed up data you wish to migrate currently resides. If you re not sure, simply list your backup schedules in StoreGrid & check which servers you re backing up to. 4. In the New Server Name give a name for the server to which you wish to migrate your client s data. You can also enter a URL or an IP address here. 5. StoreGrid automatically displays a list of all backup schedules that currently use the server you selected in step 3. Select the Backup Schedules whose data you wish to move. Please ensure that none of the backup schedules selected are currently active (ie backing up data at the time of migration) 6. Click Migrate. The Backup Configuration, Backup Report, and the Client metadata information will all be updated in the StoreGrid Client to reflect the new server name. Note: 1. The backup schedules selected for migration will be temporarily suspended. 2. The backed up data in the old server has to be migrated manualy to the new server.

Server Settings How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Server Settings" This page is used to configure StoreGrid server settings. The table on the right (titled: Server Disk Space Utilization) gives details about this server's disk space utilization in terms of backup space configured and used and also the total disk space along with partition information. The table on the left (titled: StoreGrid Server Settings) gives the various options for server settings, some of which are configurable: Server Name - Non-editable field displaying the StoreGrid peer name. Backup Directory - This is the directory into which all the client backups are stored. Note that the new directory will take effect only for the new clients backing up to this server. Backup data of all existing clients who are already backing up on to this server will still be stored in the same location. Total Disk Space - This is non-editable field displaying the total disk space available in the StoreGrid peer machine. Backup Space Allotted - By default, the total backup space allotted in the server will be 30% of the free disk space available. You can change this value to set the total backup space in this server allotted for all the StoreGrid clients (ensure you ve selected MB/GB correctly). Used Backup Space - A non-editable field displaying the backup space used by all the backup clients backing up to this server. Free Backup Space - A non-editable field displaying the free backup space available for backup. CPU Utilization - This is used to specify how this server s CPU should be utilized by the StoreGrid process when clients are backing up on to this server. This is especially useful if this server is a desktop with a user actively using it. Setting it to Low will make the StoreGrid process do the backup slowly without taking much CPU so that it is least intrusive. If this is a dedicated Backup Server, then the CPU Utilization should be set to high so that backups can happen fast. Save Button - Once all the above options are set, click the "Save" button to save the server settings. Note that the backup location, backup space etc. can be individually configured for each of the StoreGrid clients from the Client Backup Configuration page.

Client Backup Configuration How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Client Backup Configuration" This page is used to configure backup space and backup locations for StoreGrid clients backing up on to this server. The table on the right (titled: Server Disk Space Utilization) gives details about this server's disk space utilization in terms of backup space configured and used and also the total disk space along with partition information. The table on the left (titled: Backup Space Configuration for Clients) gives the various options for client backup settings, some of which are configurable: Server Name - A non-editable field displaying the name of this StoreGrid server. Choose the Client - This field lists all the StoreGrid clients discovered. Select the client for which backup space configuration is to be done. Backup Location - This field is used to set the backup location where the selected client's backup data needs to be stored. Note that if the client is already backing up on to this server, then this field will be non-editable as the backup location cannot be changed if a client has already backed up some data to a location. For a new client, you can edit this directory. Space Allotted - This field can be edited to modify the backup space allotted for this client. The space allotted can be given either in GB or MB by clicking the appropriate button. By default, the total backup space configured in the Server Settings page will be used on a first come, first served basis with any new client backing up to this server getting 50% of the existing free backup space. Used Space - A non-editable field displaying the used backup space for the selected client. Free Space - A non-editable field displaying the free space available for the selected client. Save Button - After configuring the options specified above, click on the Save button to save the configuration for the selected client. Note: when a client uses up all the backup space configured for it in the server, the server will not allow the client to backup thereafter. The client will be forced to abort future backups and StoreGrid will generate an event about this problem. Backup can proceed only after the client is allotted more space by the server.

List Backup Clients How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->List Backup Clients" This page lists the StoreGrid clients that are backing up on to this server and provides information on the backup location & space allotted and used by each client. Delete - Clicking on this button after selecting a client will schedule a delete job on this server for the selected client. The delete operation will be done asynchronously. The server will also notify the backup client about the delete operation so that the client can take appropriate action. The status of the delete operation can be obtained by invoking the menu item Server Admin->Deleted Backup Status. Note that if the delete operation did not succeed for any reason, then the delete operation has to be manually scheduled again by the user. List Backups - Clicking on this button after selecting a client will list all backups on this server for the selected client. Individual backups can be deleted from this list, if required.

List Backup Schedules For Client How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->List Backup Clients". From the list of clients displayed in the table, select a client and then click on the "List Backups" button. This will open a page which lists the backup schedules backing up to this server (from the selected client). Delete Backup Button - Clicking on this button will schedule a delete job in this server for the selected backup schedule(s). The delete operation will be done asynchronously. The server will also notify the backup client about the delete operation so that the client can take appropriate action. The status of the delete operation can be obtained by invoking the menu item "Server Admin->Deleted Backup Status". Note that if the delete operation did not succeed for any reason, then the delete operation has to be manually scheduled again by the user.

Deleted Backup Status (initiated by Server) How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Deleted Backup Status" This page gives a report of deleted client/backup operations initiated by this StoreGrid server: Client Name - This is the client name for which the delete operation was scheduled on this server. Backup Schedule - This is the backup schedule (of the client) for which the delete operation was scheduled on this server. Delete Status - This gives the status of the delete operation (Success / Failure). Message - This is useful to identify problems if/when the delete operation fails. Note that if the delete operation failed for some reason, it has to be manually scheduled again. Time - The time at which the delete operation was scheduled. Client Acknowledgment - This field indicates whether the StoreGrid client whose backup is being deleted has acknowledged the notification sent by this server. If the client has acknowledged the notification, then the client would have initiated its own delete of the Meta data about the backup. If there is no acknowledgment from the client, the user has to manually delete the meta data from the client.

Apply License Key How to get here in the StoreGrid Web Console? In the top menu, select: "Administration->Apply License Key" Every StoreGrid installation in a subnet (and outside) will require a license if it is used beyond the 30 day evaluation period. To purchase your license key (if you haven t done so already), please visit http://www.vembu.com/storegrid/storegrid-pricing.html The license key is based on: 1. Organization/User Name. 2. Number of Computers in the subnet that will run StoreGrid. 3. The period for which StoreGrid is licensed. StoreGrid can be obtained in a subscription based licensing wherein the license is valid for 1 year. Perpetual licenses are also available wherein the license expiry date is set to 31st December 2035. The license applied to any StoreGrid peer in a subnet will be propagated to all the other StoreGrid peers in the subnet. The peers will update themselves if the new license allows more StoreGrid peers than the current license does. If a StoreGrid peer in a subnet adds a peer which is in another subnet manually, then that peer will be counted in the license for this peer alone. License information will not be shared across subnets. Limitations - If you wish to increase the number of StoreGrid installations in a subnet, you will need to send an email explaining your requirement to mailto:storegrid-sales@vembu.com to enable this. By default, new license keys are issued for new subnets.

Frequently Asked Questions How is StoreGrid different from other desktop backup and laptop backup products? Can StoreGrid be used to backup desktops and laptops to a dedicated backup server inside the intranet? Can StoreGrid be used for Remote Backups? I have given a daily backup schedule to run at 5.00 PM. But at times, StoreGrid seems to be running this backup schedule at other times as well. Why? Why does my StoreGrid peer not discover other StoreGrid peers in my network automatically? How does StoreGrid do Open File Backups? Can the StoreGrid Client be installed on a NAS file server to back it up to user desktop machines or other dedicated backup servers? What type of encryption does StoreGrid use to secure the data being backed up? How secure is my data? What happens if I forget my backup encryption password? Why does StoreGrid restart automatically even after I shut it down? Does StoreGrid support backing up to peers over the internet? How does StoreGrid do incremental backups? When I click on StoreGrid Web Console, I am redirected to a search/directory page. Why does this happen and how do I get around it? If I shut down and restart StoreGrid after a period of time, will StoreGrid automatically detect modified files and newly created files and back them up? How is StoreGrid different from other desktop backup and laptop backup products? StoreGrid is a flexible backup solution that works with your existing hardware. This flexibility allows it to be deployed in traditional client-server and remote online backup modes. Additionally, StoreGrid provides an easy and intuitive mechanism to use the free space in user desktops in a network for backup purposes. StoreGrid P2P deployment capability is based on the concept of trusted peers in an intranet whose desktop space can be utilized in a peer-to-peer fashion. Another important feature of StoreGrid is the ease with which end users can configure backups and restore them, when required, without the help of system administrators. StoreGrid also allows centralized administration from a Web Console (Browser based), to make it easy for system administrators to manage and monitor StoreGrid deployments. Can StoreGrid be used to backup desktops and laptops to a dedicated backup server inside the intranet? Yes, StoreGrid can be used to backup desktops and laptops to a dedicated backup server inside the intranet. In this deployment, the dedicated backup server(s) should run StoreGrid in server mode and desktops and laptops should run StoreGrid in client mode. Can StoreGrid be used for Remote Backups? Yes, StoreGrid can be used to backup a computer to a Remote location provided the computer has direct connectivity to the Remote Backup server running StoreGrid. This facility is however not available in the Free Edition!

I have given a daily backup schedule to run at 5.00 PM. But at times, StoreGrid seems to be running this backup schedule at other times as well. Why? There are two reasons why StoreGrid will run a backup schedule at a time different from the configured schedule time. When StoreGrid is shutdown and restarted, it will run all backup schedules once before scheduling them at the configured time. This is to ensure that any files created/modified when StoreGrid was shutdown are backed up as soon as possible. If you selected "Attempt to run this backup every five minutes..." in Advanced options, and a backup schedule is incomplete because of various reasons (like network connection problem etc.), StoreGrid will schedule the backup every 5 minutes to ensure the backup schedule is completed as soon as possible. In this case, only after the backup schedule is completed will StoreGrid schedule it at the configured time. Why does my StoreGrid peer not discover other StoreGrid peers in my network automatically? StoreGrid relies on multi-casting, UDP and TCP port scan to discover at least one StoreGrid Client/Server(peer)in the network. But if multi-casting is disabled in the network, then discovery may be delayed because UDP or TCP port scans can be time consuming. Also, StoreGrid is configured to discover StoreGrid peers only in a subnet. You can manually discover a StoreGrid peer (both within and outside the subnet) using the "Add Peer" feature from the StoreGrid Web Console. If you are using Windows XP with Service Pack 2 installed, please click here. How does StoreGrid do Open File Backups? When StoreGrid backs up a file, it can detect automatically if the file has been changed. And hence StoreGrid can ensure that no file is backed up incorrectly. For files that change during a backup, StoreGrid does a best effort attempt continuously (in the background) until the backup for the file succeeds. In a desktop/laptop environment this strategy almost never fails. However, it is important that StoreGrid be allowed the requisite permission to access the file(s) that are to be backed up. For example, Microsoft Outlook cannot be backed up if it is open as StoreGrid cannot access the requisite files (Please click here to understand how StoreGrid works around this problem) The best way to handle open file backups is to use StoreGrid s Open File Plugin. See this page for more details on this. Can the StoreGrid Client be installed on a NAS file server to back it up to user desktop machines or other dedicated backup servers? StoreGrid can be installed on Linux or Windows based NAS servers. It is possible to backup a NAS file server over the network to other user desktops or a dedicated backup server. If StoreGrid cannot be installed on a NAS filer, it will be possible to install StoreGrid on a PC, mount the NAS server and then back it up. In the case of NAS file servers, open file backup may not happen if a file is being continuously modified by an application. In Windows Storage Server, it is possible to use the Volume Shadow Copy feature to support Open File backups. In NAS filers where files are not modified continuously StoreGrid's open file backup should suffice. What type of encryption does StoreGrid use to secure the data being backed up? How secure is my data? StoreGrid uses the Blowfish encryption algorithm. You can get more information about blowfish algorithm at http://www.schneier.com/blowfish.html Excerpts from the blowfish website: "Blowfish was designed in 1993 by Bruce Schneier as a fast, free alternative to existing encryption algorithms. Since then it has been analyzed considerably, and it is slowly gaining acceptance as a strong encryption algorithm". StoreGrid will support other encryption algorithms as options in the future. As such your data is very secure as blowfish based encryption has never been broken before. What happens if I forget my backup encryption password?

Whoops! If you forget the backup encryption password, then there is no known way to decrypt your backed up data. So it is recommended that you write down the backup encryption password in a safe and secure place. Why does StoreGrid restart automatically even after I shut it down? During installation, StoreGrid also installs a separate application called StoreGrid Tray. This application appears as an icon in your Windows Tray. If you want to stop the StoreGrid application, you need to stop it through the menu that pops up while right clicking the StoreGrid Tray. If you stop the StoreGrid application in any other way, StoreGrid Tray will automatically restart the StoreGrid application. This feature is to ensure that StoreGrid application is always running to protect your data even if it exits unexpectedly because of any bugs or other reasons. Does StoreGrid support backing up to peers over the internet? StoreGrid (Professional Edition) peers can communicate with each other and backup data over the internet if there is direct connectivity between the peers. StoreGrid does not work across networks which are behind NAT (Network Address Translation). The feature to support NAT traversal will be done in a future release. How does StoreGrid do incremental backup? StoreGrid uses the librsync library which provides a streaming API implementation of the RSYNC algorithm to find differences in a file using a signature for a file. You can get more information about RSYNC algorithm at http://samba.anu.edu.au/rsync/ When I click on StoreGrid Web Console, I am redirected to a search/directory page. Why does this happen and how do I get around it? Some toolbars and related software can take over your browser window even if you don't want them to! Uninstalling them usually solves the problem. Alternatively, you could manually type in the URL in your browser's address bar: http://machine-name:6060 where "machine-name" is the name of your machine, eg. http://joe:6060 If I shut down and restart StoreGrid after a period of time, will StoreGrid automatically detect modified files and newly created files and back them up? It depends on the settings you ve selected when creating the backup schedule. StoreGrid will automatically detect all the modified and newly created files and back them up after a restart if: i. You selected the continuous backup option ii. You selected the run every hours minutes option. In this case, StoreGrid will run this schedule whenever it restarts, and thereafter schedule the next backup after the period you ve selected. iii. You ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options

Limitations Limitations in StoreGrid 1. Discovery of StoreGrid clients/servers may not work properly if multicasting is disabled in the network. 2. If the user forgets her encryption key/password, then there is no way to restore the data. The data cannot be decrypted and hence the backup is as good as lost. 3. StoreGrid accepts encryption key/password as exactly 8 characters. This will be fixed in the StoreGrid 2.0 release. 4. StoreGrid cannot do a complete backup of Outlook and Outlook Express if they are open as StoreGrid cannot get the required permission to open the mailbox files. Hence Outlook and Outlook Express backups should be configured to run when these applications are closed. 5. If a backup was suspended before completing a full backup then the reports will show only the count of number of files not backed up and does not show the list of files skipped. 6. Backing up of Empty directories is not supported. 7. StoreGrid does a backup of its internal meta-data database as part of each backup schedule. The total time taken for backup includes the time taken for backing up this meta-data database. Depending upon the size of the meta-data database, the total time taken can appear large for even small backups. 8. Encryption key for a backup cannot and should not be changed across backup schedules. 9. A StoreGrid peer group should not have more than about 100 clients/servers. 10. Only one backup operation can run in a StoreGrid client at a time. Other scheduled/continuous backups will become active only after the current backup operation completes. 11. When the user configures multiple destination servers for backup, then during restore, the server which has the latest backup is not automatically detected. 12. All the user configured to log-in to StoreGrid have the same permissions. Fine grained access control is not supported. 13. If StoreGrid configuration is changed from server mode to client mode or client-server mode, then all backups should be deleted and StoreGrid restarted afresh. Existing configuration and backups can become inconsistent. 14. If a backup schedule is configured which includes the StoreGrid installation directory itself, then StoreGrid will ignore the StoreGrid installation directory and backup only rest of the data. The reason is that StoreGrid creates meta-data information for every file it backs up and store it in the installation directory. If StoreGrid were to backup the StoreGrid installation directory, then for every meta-data file, there will be another meta-data file created and so on. So the backup will never finish. 15. If the user forgets the username or password, then there is no mechanism to recover them. The user will not be able to login to StoreGrid. 16. StoreGrid does not support automatic directory and file monitoring in Windows 98 and Mac OS X machines. So, when a continuous backup is configured, the backup will check for modified files continuously by listing all the files and checking with StoreGrid backup meta data. This process will affect the performance of other applications. Hence configuring a continuous backup is not recommended in Windows 98 and Mac OS X machines. This is also applicable to LINUX machines in which Vembu StoreGrid File Monitor Driver is not installed. 17. In Max OS X 10.4.1 (Tiger), StoreGrid WebConsole User Interface works only with FireFox browser. Both Safari and Internet Explorer are not supported. You can get the FireFox browser from http://www.mozilla.org/products/firefox/

Issues Known Issues in StoreGrid 1.6 1. In Windows and Linux machines backup for a file fails when the full path of the file exceeds about 250 characters. 2. The client backup location configured in the StoreGrid Server cannot not be changed across backup schedules. 3. When StoreGrid is killed abruptly, Windows does not clean up the all the StoreGrid ports (TCP- 32004,32005 and UDP-32006,6363,6364) occasionally. This will prevent StoreGrid from being restarted as the ports are already occupied. The only solution is to then reboot the machine. 4. The tree display in the StoreGrid Web Console will take a long time to load if a directory contains 1000s of files/directories under it. 5. The Web Console some times hangs the browser. When it happens, the browser has to be restarted. 6. Events mechanism may not report all the important error conditions. And there may be repetition of the same event for the same problem. 7. StoreGrid discovery takes between 2 to 5 minutes to detect when other StoreGrid peers become available or unavailable. 8. If a backup schedule is configured to two backup servers (StoreGrid peers), then the backup data in both the servers need not be the same. As the backup is done to the servers one by one, the data, files etc. can differ between the backups. 9. If an active backup schedule is suspended, then it will get suspended only after the current file that is being backed up is completed. So there may be a delay while suspending an active backup. 10. All StoreGrid peers and their backup data, disk utilization data etc. are identified by the StoreGrid peer machine's DNS name. If DNS fails then the StoreGrid WebConsole may not be able to show the correct information. 11. If a StoreGrid server machine's DNS name is changed and an existing backup schedule is reconfigured to backup to this new server machine, then there are some manual steps to be done in the StoreGrid client if it has to backup based on the old backup information. If not, all backups will be done as a fresh backup to this server. 12. In Windows 98 machines, a backup configured with a medium or low CPU utilization settings will take an unusually long time to finish. Hence for good backup performance it is recommended that the CPU settings for a backup is set to HIGH in Windows 98.

Support Vembu's support plan includes: Support Email Id 1. Free email support during the 30 days evaluation period. 2. For paid users, standard support is email based and most questions will be responded to in one business day. 3. Partners enjoy different support levels depending on partner tier. This is detailed at http://www.vembu.com/storegrid/partner.html Please send all your support questions to storegrid-support@vembu.com

Vembu Technologies Software License Agreement (Professional Edition) This License Agreement details the policy for license of Vembu StoreGrid 1.6 ("Licensed Software") on the following topics: Evaluation License Commercial License Technical Support Please read the following license carefully, before either (i) completing the electronic order or download of the Licensed Software from an authorised website, or (ii) installing the Licensed Software from media that was delivered after being ordered by alternative order process, as applicable. You acknowledge that you have read this License Agreement, have understood it, and agree to be bound by its terms. If you do not agree to the terms and conditions of this Agreement, either (i) exit the web site page without continuing the ordering process, or (ii) return the provided unused media and documentation within thirty (30) days from the date of shipment of the Licensed Software for a full refund of your payment, as applicable. Evaluation License: Vembu Technologies grants to you a non-exclusive, non-transferable, Evaluation License for trial and evaluation of the Licensed software, in binary object code form, for a period of thirty (30) days from the date of download or installation. This License begins upon downloading or installing the Licensed Software and ends thirty (30) days thereafter ("Evaluation Period"). If you are not willing to use the Licensed Software after the Evaluation Period, delete all the copies installed in your computer with immediate effect. You are forbidden from using the Licensed Software for any other use or otherwise offering it for resale under the terms of this Section 1. Vembu Technologies retains all rights not specifically granted to you herein. Commercial License: As part of purchasing a fee-bearing commercial license, Vembu Technologies grants you a non-exclusive, nontransferable, world-wide license to Use the Licensed Software, including user documentation that you have downloaded from or received on media provided by Vembu Technologies, including all updates provided through the Vembu Technologies subscribed support services, where applicable, provided that such access and Use of the Licensed Software is in accordance with the Time Limited Network License granted by Vembu Technologies. "Use" means storing, loading, installing, executing or displaying the Licensed Software as part of your application. Time Limited Network License means that the number of machines in a network the Licensed Software can be installed and the time period the Licensed Software can be used. Third Party Products: The Licensed Software may contain software which originated with third party vendors and without limiting the general applicability of the other provisions of this Agreement, you agree that (a) the title to any third party software incorporated in the Licensed Software shall remain with the third party which supplied the same; and (b) you will not distribute any such third party software available with the Licensed Software, in any manner, unless the license of the third party software states otherwise. Restrictions on Use: In addition to all other terms and conditions of this Agreement, you shall not: 8. Install the Licensed Software in more computers than the number of computers the license is granted for; 9. Use the licensed software beyond the time period the license is granted for; 10. Remove any copyright, trademark or other proprietary notices from the Licensed Software or its copies; 11. Rent, lease, license, sublicense or distribute the Licensed Software or any portions of it on a standalone basis or as part of your application;

12. Modify or enhance the Licensed Software; 13. Use the Licensed Software in a computer-based services business or publicly display visual output of the Licensed Software or use the Licensed Software for the benefit of any other person or entity; 14. Reverse engineer, decompile or disassemble the Licensed Software. 15. Allow any third parties to access, use or support the Licensed Software. Technical Support: Vembu Technologies provides support that includes email support for problem reporting, product updates, for a period of one year. Vembu Technologies specifically excludes upgrades from the support program. Upgrade to the Licensed Software will be provided upon payment of an Upgrade License Fee in accordance with Vembu Technologies' then current pricing policy. Ownership and Intellectual Property: Vembu Technologies owns all right, title and interest in and to the Licensed Software. Vembu Technologies expressly reserves all rights not granted to you herein, notwithstanding the right to discontinue or not to release any Licensed Software and to alter prices, features, specifications, capabilities, functions, licensing terms, release dates, general availability or characteristics of the Licensed Software. The Licensed Software is only licensed and not sold to you by Vembu Technologies. Audit: Vembu Technologies has the right to audit your Use of the Licensed Software by providing at least seven (7) days prior written notice of its intention to conduct such an audit at your facilities during normal business hours. Confidentiality: The Licensed Software contains proprietary information of Vembu Technologies that are protected by the laws of the United States and you hereby agree to take all reasonable efforts to maintain the confidentiality of the Licensed Software. You agree to reasonably communicate the terms and conditions of this Agreement to those persons employed by you who come into contact with or access the Licensed Software, and to use reasonable efforts to ensure their compliance with such terms and conditions, including but not limited to, not knowingly permitting such persons to use any portion of the Licensed Software for a purpose that is not allowed under this Agreement. Warranty Disclaimer: Vembu Technologies does not warrant that the Licensed Software will be error-free. Except as provided herein, the Licensed Software is furnished "as is" without warranty of any kind, including the warranties of merchantability and fitness for a particular purpose and without warranty as to the performance or results you may obtain by using the Licensed Software. You are solely responsible for determining the appropriateness of using the Licensed Software and assume all risks associated with the use of it, including but not limited to the risks of program errors, damage to or loss of data, programs or equipment, and unavailability or interruption of operations. Because some jurisdictions do not allow for the exclusion or limitation of implied warranties, the above exclusions or limitations may not apply to you. Limitation of Liability: In no event will Vembu Technologies be liable to you or any third party for any special, incidental, indirect, punitive or exemplary or consequential damages, or damages for loss of business, loss of profits, business interruption, or loss of business information arising out of the use or inability to use the program or for any claim by any other party even if Vembu Technologies has been advised of the possibility of such damages. Vembu Technologies' entire liability with respect to its obligations under this agreement or otherwise with respect to the Licensed Software shall not exceed the amount of the Time Limited Network License fee paid by you for the Licensed Software. Because some jurisdictions do not allow the exclusion or limitation of liability for incidental or consequential damages, the above exclusions or limitations may not apply to you. Indemnification:

Vembu Technologies agrees to indemnify and defend you from and against any and all claims, actions or proceedings, arising out of any claim that the Licensed Software infringes or violates any valid U.S. patent, copyright or trade secret right of any third party; so long as you provide; (i) prompt written notice to Vembu Technologies of such claim; (ii) cooperate with Vembu Technologies in the defense and/or settlement thereof, at Vembu Technologies' expense; and, (iii) allow Vembu Technologies to control the defense and all related settlement negotiations. The above is Vembu Technologies' sole obligation to you and shall be your sole and exclusive remedy pursuant to this Agreement for intellectual property infringement. Vembu Technologies shall have no indemnity obligation for claims of infringement to the extent resulting or alleged to result from (i) any combination, operation, or use of the Licensed software with any programs or equipment not supplied by Vembu Technologies; (ii) any modification of the Licensed Software by a party other than Vembu Technologies; and (iii) your failure, within a reasonable time frame, to implement any replacement or modification of Licensed Software provided by Vembu Technologies. Termination: This Agreement is effective until terminated by either party. You may terminate this Agreement at any time by destroying or returning to Vembu Technologies all copies of the Licensed Software in your possession. Vembu Technologies may terminate this Agreement for any reason, including but not limited to your breach of any of the terms of this Agreement. Upon termination, you shall destroy or return to Vembu Technologies all copies of the Licensed Software and certify in writing that all know copies have been destroyed. All provisions relating to confidentiality, proprietary rights, non-disclosure, and limitation of liability shall survive the termination of this Agreement. General: This Agreement shall be construed, interpreted and governed by the laws of the State of California exclusive of its conflicts of law provisions. This Agreement constitutes the entire agreement between the parties, and supersedes all prior communications, understandings or agreements between the parties. Any waiver or modification of this Agreement shall only be effective if it is in writing and signed by both parties hereto. If any part of this Agreement is found invalid or unenforceable, the remainder shall be interpreted so as to reasonable effect the intention of the parties. You shall not export the Licensed Software or your application containing the Licensed Software except in compliance with United States export regulations and applicable laws and regulations. This software is a collective work consisting of the following Open Source components: Apache software, PHP and librsync each licensed under a separate Open Source License. vembu.com is not affiliated with nor endorsed by any of the above providers. 1. Apache Version 1.3 or 2.0 developed by The Apache Software Foundation (http://www.apache.org/) For license details please see the file at <STOREGRID_HOME_DIR>/apache/LICENSE.txt 2. PHP Version 4.3.9 developed by The PHP Group (http://www.php.net). For license details please see the file at <STOREGRID_HOME_DIR>/php/LICENSE.txt 3. librsync version 0.9.6. For license details please see the file at <STOREGRID_HOME_DIR>lib/librsync/COPYING.txt

Vembu Technologies Software License Agreement (Free Edition) This License Agreement details the policy for license of Vembu StoreGrid 1.6 ("Licensed Software") on the following topics: Free Edition License Technical Support Sponsored Advertisement Please read the following license carefully, before either (i)completing the electronic order or download of the Licensed Software from an authorised website, or (ii)installing the Licensed Software from media that was delivered after being ordered by alternative order process, as applicable. You acknowledge that you have read this License Agreement, have understood it, and agree to be bound by its terms. If you do not agree to the terms and conditions of this Agreement, either (i)exit the web site page without continuing the ordering process, or (ii)return the provided unused media and documentation within thirty (30) days from the date of shipment of the Licensed Software for a full refund of your payment, as applicable. Free Edition License: Vembu Technologies grants you a non-exclusive, non-transferable, world-wide license to use the Free Edition of the Licensed Software, in binary object form, for no cost in perpetuity. The Free Edition License allows you to install and use the Licensed software on up to 3 computers within the same subnet. A fee-bearing upgrade to Professional Edition of the Licensed Software is required if you want to use it in more than 3 computers within the same subnet or if you want to install and use the Licensed software across different subnets. If you are not willing to use the Free Edition of the Licensed Software, delete all the copies installed in your computer with immediate effect. You are forbidden from using the Licensed Software for any other use or otherwise offering it for resale under the terms of this Section 1. Vembu Technologies retains all rights not specifically granted to you herein. Third Party Products: The Licensed Software may contain software which originated with third party vendors and without limiting the general applicability of the other provisions of this Agreement, you agree that (a) the title to any third party software incorporated in the Licensed Software shall remain with the third party which supplied the same; and (b) you will not distribute any such third party software available with the Licensed Software, in any manner, unless the license of the third party software states otherwise. Restrictions on Use: In addition to all other terms and conditions of this Agreement, you shall not: 1. Install the Licensed Software in more computers than the number of computers the license is granted for; 2. Use the licensed software beyond the time period the license is granted for; 3. Remove any copyright, trademark or other proprietary notices from the Licensed Software or its copies; 4. Rent, lease, license, sublicense or distribute the Licensed Software or any portions of it on a standalone basis or as part of your application; 5. Modify or enhance the Licensed Software; 6. Use the Licensed Software in a computer-based services business or publicly display visual output of the Licensed Software or use the Licensed Software for the benefit of any other person or entity; 7. Reverse engineer, decompile or disassemble the Licensed Software. 8. Allow any third parties to access, use or support the Licensed Software. Technical Support: Vembu Technologies provides support that includes email support for problem reporting, product updates, for a period of one year. Vembu Technologies specifically excludes upgrades from the support program. Upgrade

to the Licensed Software will be provided upon payment of an Upgrade License Fee in accordance with Vembu Technologies' then current pricing policy. Sponsored Advertisement Vembu Technologies reserves the right to display any advertisement/advertisements in the user interface of the Free Edition of the Licensed Software. Ownership and Intellectual Property: Vembu Technologies owns all right, title and interest in and to the Licensed Software. Vembu Technologies expressly reserves all rights not granted to you herein, notwithstanding the right to discontinue or not to release any Licensed Software and to alter prices, features, specifications, capabilities, functions, licensing terms, release dates, general availability or characteristics of the Licensed Software. The Licensed Software is only licensed and not sold to you by Vembu Technologies. Audit: Vembu Technologies has the right to audit your Use of the Licensed Software by providing at least seven (7) days prior written notice of its intention to conduct such an audit at your facilities during normal business hours. Confidentiality: The Licensed Software contains proprietary information of Vembu Technologies that are protected by the laws of the United States and you hereby agree to take all reasonable efforts to maintain the confidentiality of the Licensed Software. You agree to reasonably communicate the terms and conditions of this Agreement to those persons employed by you who come into contact with or access the Licensed Software, and to use reasonable efforts to ensure their compliance with such terms and conditions, including but not limited to, not knowingly permitting such persons to use any portion of the Licensed Software for a purpose that is not allowed under this Agreement. Warranty Disclaimer: Vembu Technologies does not warrant that the Licensed Software will be error-free. Except as provided herein, the Licensed Software is furnished "as is" without warranty of any kind, including the warranties of merchantability and fitness for a particular purpose and without warranty as to the performance or results you may obtain by using the Licensed Software. You are solely responsible for determining the appropriateness of using the Licensed Software and assume all risks associated with the use of it, including but not limited to the risks of program errors, damage to or loss of data, programs or equipment, and unavailability or interruption of operations. Because some jurisdictions do not allow for the exclusion or limitation of implied warranties, the above exclusions or limitations may not apply to you. Limitation of Liability: In no event will Vembu Technologies be liable to you or any third party for any special, incidental, indirect, punitive or exemplary or consequential damages, or damages for loss of business, loss of profits, business interruption, or loss of business information arising out of the use or inability to use the program or for any claim by any other party even if Vembu Technologies has been advised of the possibility of such damages. Vembu Technologies' entire liability with respect to its obligations under this agreement or otherwise with respect to the Licensed Software shall not exceed the amount of the Time Limited Network License fee paid by you for the Licensed Software. Because some jurisdictions do not allow the exclusion or limitation of liability for incidental or consequential damages, the above exclusions or limitations may not apply to you. Indemnification: Vembu Technologies agrees to indemnify and defend you from and against any and all claims, actions or proceedings, arising out of any claim that the Licensed Software infringes or violates any valid U.S. patent, copyright or trade secret right of any third party; so long as you provide; (i) prompt written notice to Vembu Technologies of such claim; (ii) cooperate with Vembu Technologies in the defense and/or settlement thereof, at Vembu Technologies' expense; and, (iii) allow Vembu Technologies to control the defense and all related settlement negotiations. The above is Vembu Technologies' sole obligation to you and shall be your sole and exclusive remedy pursuant to this Agreement for intellectual property infringement.

Vembu Technologies shall have no indemnity obligation for claims of infringement to the extent resulting or alleged to result from (i) any combination, operation, or use of the Licensed software with any programs or equipment not supplied by Vembu Technologies; (ii) any modification of the Licensed Software by a party other than Vembu Technologies; and (iii) your failure, within a reasonable time frame, to implement any replacement or modification of Licensed Software provided by Vembu Technologies. Termination: This Agreement is effective until terminated by either party. You may terminate this Agreement at any time by destroying or returning to Vembu Technologies all copies of the Licensed Software in your possession. Vembu Technologies may terminate this Agreement for any reason, including but not limited to your breach of any of the terms of this Agreement. Upon termination, you shall destroy or return to Vembu Technologies all copies of the Licensed Software and certify in writing that all know copies have been destroyed. All provisions relating to confidentiality, proprietary rights, non-disclosure, and limitation of liability shall survive the termination of this Agreement. General: This Agreement shall be construed, interpreted and governed by the laws of the State of California exclusive of its conflicts of law provisions. This Agreement constitutes the entire agreement between the parties, and supersedes all prior communications, understandings or agreements between the parties. Any waiver or modification of this Agreement shall only be effective if it is in writing and signed by both parties hereto. If any part of this Agreement is found invalid or unenforceable, the remainder shall be interpreted so as to reasonable effect the intention of the parties. You shall not export the Licensed Software or your application containing the Licensed Software except in compliance with United States export regulations and applicable laws and regulations. This software is a collective work consisting of the following Open Source components: Apache software, PHP and librsync each licensed under a separate Open Source License. vembu.com is not affiliated with nor endorsed by any of the above providers. 4. Apache Version 1.3 or 2.0 developed by The Apache Software Foundation (http://www.apache.org/) For license details please see the file at <STOREGRID_HOME_DIR>/apache/LICENSE.txt 5. PHP Version 4.3.9 developed by The PHP Group (http://www.php.net). For license details please see the file at <STOREGRID_HOME_DIR>/php/LICENSE.txt librsync version 0.9.6. For license details please see the file at <STOREGRID_HOME_DIR>lib/librsync/COPYING.txt 2002-2005, Vembu Technologies Pvt. Ltd. Technical support - storegrid-support@vembu.com