What is StoreGrid? Very simply, Vembu StoreGrid is an extremely versatile Backup Software that works with your Existing Hardware!

Transcription

1 Introduction 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, Windows ME, Windows 2000/2003 Server, Linux RedHat 8.0 & above, Debian 3.0, Mandrake 10.0 & above, SuSE 9.x & above, Mac OS X 10.x and FreeBSD 5.4 & 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 recognizes 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

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

3 StoreGrid Editions Editions: Usage: Ideal for SoHos, Home Networks and single computers Perfect for SMBs and Remote & Branch Offices of larger companies Especially created for XSPs, VARs, SIs offering Online Backup Services to SMBs Features Download Download Partners Only Operating Systems supported Windows Desktop OS only Windows Desktop & Server OS, Linux, Mac OS X, FreeBSD Windows Desktop & Server OS, Linux, Mac OS X, FreeBSD Number of installations Maximum of 3 Create any number of backup schedules Intelli-Delta technology for Incremental backups Hot links for commonly used files & folders Multiple versions of backed up files Deleted file support Robust Encryption with configurable (up to 448 bit) key length Configurable CPU / bandwidth utilization Backup Data Compression Various scheduling options including continuous backup Multi-threaded backup schedules Large File Backup support (including 'continue where you left off' feature) As purchased (free trial supports 5 installations) As purchased (free trial as required)

4 my reports feature Detailed reporting Backup only during certain hours of the day Support for Volume Shadow Copy Service (VSS) in Windows Secure (HTTPS) WebConsole option MySQL Server backup (Windows) SSL Connectivity NTFS File Permissions Backup Multiple simultaneous restores Map Drive Support Mailbox/Folder Level Exchange Backup MySQL Server backup (Linux) Client Authentication (includes enhanced group management) (includes enhanced customer management) MS SQL Server Backups MS Exchange Server Backups Remote Backup to server outside the subnet Backup Server Replication Local to Remote Server Data Migration (First backup taken locally, thereafter incremental backups done online) Customer/Group centric reporting Automatic Software Update Customer Invoice Generation Module Option to co-brand StoreGrid

5 Technical Support Forums only Forums & support Forums & support Product/feature messages in User Interface

6 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 means. StoreGrid General Terminology: 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 StoreGrid ID: This is the unique ID each installation of StoreGrid is identified with. StoreGrid will prompt you to give an ID during the installation. It will automatically take the machine name as the StoreGrid ID by default. (anyone who purchases a paid license of Vembu StoreGrid is also a StoreGrid client ) 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. Replication: Term used for the process where a backup server sends its backup data to a replication server to create a redundant copy of the backup data. StoreGrid Replication Server: A machine that receives replication data from a backup server. In case the backup server crashes, it can be restored from the replicated data in the replication server. A backup server can replicate to only one replication server. A replication server can accept replication from more than one backup servers. 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.

7 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. Remote / Online Backups : The same as client-server (see above), except that the server is outside the clients network.

8 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 do a mix and match type of deployment) 1. Service Provider Hosted Remote Online Backup Deployment 2. Peer-to-Peer(P2P) or Grid deployment 3. Dedicated Backup Server deployment (Client-Server) Service Provider Hosted Remote Online Backup Deployment Online Backup service provider including MSPs, VARs, SIs etc. can use this deployment to offer an online backup service to their customers. This deployment mode is supported in the StoreGrid Service Provider Edition. Typically, the service provider will install StoreGrid in server mode in the data center and install StoreGrid from a custom Client Only installation (provided by Vembu) in the customer PCs. The Service Provider Edition supports comprehensive customer based management of backup clients, storage, reports etc. 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)

9 This is a more traditional deployment - ideal for leveraging existing backup infrastructure by allowing customers 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.

10 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 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. By default the port used by StoreGrid is 32004, if you have modified the 'Backup Server Port' during installation, then you have to open the corresponding port in your NAT/Firewall. TCP SSL Port From StoreGrid v2.3, StoreGrid clients can send the backup data to the backup server on secure SSL port This port is disabled in the backup server and the client by default. SSL port can be enabled by changing the Enabled attribute to 1 in the SSL tag in the SGConfiguration.conf file. When enabled in the backup server, the StoreGrid backup server can accept backup requests on both port and the SSL port When enabled in the client, the client will start sending the backup data on the SSL port. If SSL port is enabled in the backup server and in the client, all Client-Server communication including backups, restore etc. (except TCP discovery) from that client will be done through the SSL port and therefore if a StoreGrid Server is behind a NAT/Firewall then this port needs to be opened to enable the StoreGrid client to backup to this server. By default the port used by StoreGrid for SSL is But it can be modified by changing the 'SSLServer' attribute in the 'Ports' tag in the SGConfiguration.conf file. This port number should be set the same in both the server and the client. TCP Port 32008(Windows 64-bit OS) From StoreGrid v2.4 Exchange Mailbox backup and restore is supported for Exchange Server StoreGrid 64-bit client exe can send the backup request to the 32-bit client exe on port running in the same machine. If a StoreGrid Client is behind a NAT/Firewall then this port needs to be opened to enable Exchange 2007 Mailbox backup and restore to be performed. Opening up this port is mandatory for the core Exchange 2007 Mailbox functionality of backup and restore to work in StoreGrid. By default the port used by StoreGrid for Exchange 2007 Mailbox backup is But it can be modified by changing the "MAPI32Bit" attribute in the &quote;ports&quote; tag in the SGConfiguration.conf file located in <SG_Home>/conf folder. TCP Port 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. By default the port used by StoreGrid is 32005, if you have modified the 'UI Communication Port' during installation, then you have to open the corresponding port in your NAT/Firewall. 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, 6061

11 These ports are used by the StoreGrid Web Server (Apache) to serve requests from StoreGrid WebConsole (User Interface). These ports are configurable. When you first install StoreGrid you would have been given an option to change these ports. The NAT/Firewall should also 'allow' these ports 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 This UDP port is used in discovery of StoreGrid peers in a network. StoreGrid does a UDP scanning on port 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.

12 Vembu StoreGrid Troubleshooting Guide 1. Description of the Error Codes Common StoreGrid Error Codes and their corresponding description are listed below. If you require further clarification on these or if you encounter a different error code from those listed below, contact us at storegridsupport@vembu.com Error Codes What does this error code mean? SG0083 This error occurs when : i. The socket connection between the Client and the Server gets disconnected due to any external force such as an Internet Link error, Intrusion Detection software, Antivirus software or NAT/Firewall Idle socket configuration. Click here for the resolution ii. Exceeding allotted backup space in the server. Click here for the resolution SG0198 SG0145/SG0134 SG0147/SG0136 SG0200 SG0191 SG0178 SG0180 SG0601 SG0094 SG0290 This error occurs when the socket connection between the Client and the Server gets disconnected due to any external force such as a. Internet Link error, b. Intrusion Detection software, c. Antivirus software, d. NAT/Firewall Idle socket configuration. Click here for the resolution Problem in resolving Backup Server Name and IP Address, DNS Lookup for Backup Server Name or IP Address failed. Click here for the resolution Problem in connecting to Backup Server, Backup Port (32004) not opened up in NAT/Firewall or StoreGrid not running. Click here for the resolution No drive space available in the Backup Server to continue the backups Active backup is suspended in the client or the Backup Server Exceeding allotted backup space in Backup Server Backup space not configured for the client in the Backup Server Failed to initialize the compression module to compress file contents for backup Unable to read the file during time of backup Backup schedule is active during delete schedule configuration, suspend

13 the backup and schedule delete SG0291 SG0292 SG0170 SG0132 SGRP0001 Error Code 21 Backup schedule Restore is active during delete schedule configuration, suspend the backup and schedule delete Backup schedule Delete is in progress, Delete schedule updated Unable to send out delete request to Backup Server for deletion of backup data from client Invalid remote socket. Click here for the resolution No Server available for Replication. Click here for the resolution Cannot Start Storegrid or Error in Starting StoreGrid. Click here for the resolution 2. StoreGrid reports an error "Unable to list the Exchange mailbox users. Make sure sufficient permissions are available for the user account under which StoreGrid service is running. Exchange Mail Level Backup requires the user account to have 'Full Control' access to the Exchange Server to list the mailbox users." while trying to configure mailbox level backup. Resolution : If you encounter an error while accessing "Create Exchange Mailbox Backup" page in the StoreGrid webconsole, then follow the steps given below to resolve the issue: 1. Create a new user with sufficient rights through Active Directory Users and Computers. 2. Assign "Full Mailbox Access" permission to that new user. 3. Add that new user in the 'PluginConfiguration.conf' file located in "<SG_Home>/plugins" folder. 4. Add the 'MSPST MS' service by modifying the MAPISVC.INF file. (NOTE: above 3 steps should resolve the issue in listing the Mailbox users in the "Create Exchange Mailbox Backup" page. However 'MSPST MS' service should be added in the MAPISVC.INF file to successfully backup the Exchange users mailbox). Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access the mailboxes. 3. StoreGrid doesn t start after upgrading an old version of StoreGrid to the latest version. Cause : StoreGrid databases not upgraded properly. Resolution : Please refer this online detailed help document on upgrading StoreGrid and on how to recover from a bad upgrade 4. StoreGrid reports an error "Unable to list the Exchange mailbox users..." when trying to configure Exchange Mailbox level backup in 2007 Exchange server (64 bit) machines. Resolution :

14 StoreGrid uses Microsoft's MAPI client component installed in the Exchange Server to backup the Exchange Mailboxes. For 64-bit environment the MAPI client component is yet to be released by Microsoft. Currently, StoreGrid uses its 32-bit exe to list, backup and restore the Exchange Mailboxes in 64-bit machines. To accomplish this, StoreGrid 32-bit exe requires Microsoft's 32-bit MAPI client component. Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access the Exchange 2007 mailboxes. 5. SG0147/SG0136: Unable to connect to the Backup Server Cause: This error occurs when a. Client is not able to connect to the Backup Server's Backup Port (default 32004). b. StoreGrid is not started in the server machine, therefore Backup Port (default 32004) is not occupied by StoreGrid. Resolution: Confirm if the client is able to connect the Backup Server's Backup Port (default 32004) by executing telnet <Server Name/IP Address> <Backup Port> command in the StoreGrid Client system through the command prompt. If the telnet command doesn't work, then check the firewall configuration of the StoreGrid Server and make sure the Backup Port (default 32004) is open for the incoming traffic. Check that the StoreGrid server is running in your StoreGrid Server machine and the Backup Port is in LISTEN state by executing netstat -an find <Backup Port> [in Windows OS] or netstat -an grep <Backup Port> [in Linux OS] in StoreGrid Backup Server system. If Backup Port is not in LISTEN state, start the StoreGrid in the Backup Server. Also make sure StoreGrid is running in either Server Only or in Client-Server mode in the StoreGrid Server. If the Backup Port is in LISTEN state and telnet command fails, make sure the Backup Port is open in the Backup Server network's NAT/Firewall settings. Also confirm that both the backup server and the client are configured with the same Backup Port (by default, the port should be 32004). Verify this by checking the <StoreGrid Home>/conf/SGConfiguration.conf file. Refer the following URL to know more about NAT/Firewall configurations SG0198: Connection failure error / SG0083: Unable to send backup details to server Cause: These errors occur when the connection between a client and the Backup Server is closed prematurely by an external force, while the StoreGrid is actively processing the backup data to the Backup Server. The external forces may be:. NAT/Firewall configurations. a. Low end routers/switches.

15 b. Intrusion detection software. c. Internet-link error. Resolution: Most routers, NATs and firewalls keep a track of all connections made through them. They will assume a connection to be dead if no data is transferred in either direction for a certain time interval and they may then close the network connection. Hence, check the Idle Socket Timeout configuration in the NAT/Firewall settings. The premature closure of the connection can be prevented by configuring either the Keep Alive Time in the Windows Registry or by configuring the Application Level Keep Alive Time (available since StoreGrid 2.2 Release) For details, refer to the FAQ section at #Network-Backup-Faq SG0132: Invalid remote socket Cause: This error message occurs when StoreGrid client exits or its connection is closed when the backup is in progress. Check the Client side historical backup report from the Backup -> List Backup Schedules -> Backup Summary Report(action) -> Click to view historical backup report (link). The historical backup report page will show one of the following errors: 'StoreGrid stopped during backup' This error indicates that either the StoreGrid process was stopped during backup or the StoreGrid Client machine was shutdown/restarted while the backup was in progress. 'Unable to send backup details...' - This error indicates that the socket connection was closed prematurely. Check the timeout settings in the server side NAT/Firewall settings. Sometimes an existing socket connection is closed when the socket remains idle for a specified time period. Resolution: Check the StoreGrid FAQ on the same error at #Network-Backup-Faq34 8. SG0145/SG0134: Unable to get target machine Cause: This error occurs when there is a problem in resolving the Backup Server's name at the client side. This can be verified by running the following commands in the client machine's command prompt:. ping <Backup Server Name> command. a. nslookup <Backup Server Name> command. If the above commands work, then the StoreGrid should be able to resolve the Backup Server's hostname. If the above commands fail, then check the DNS configurations on the client side and make sure that the client is able to lookup Backup Server's hostname. Also, try running the telnet <Backup Server Name> <Backup Port> (by default the Backup Port is 32004) command in the client machine. If the telnet command works (shows a blank console screen), then backup should work. Resolution:

16 If the client is not able to resolve the Backup Server's hostname, try configuring the backup with the Backup Server's IP address as the server name by following the steps given below: Go to the Administration -> Add/Delete peer page in the StoreGrid Client web console. Delete the Backup Server name from the list of StoreGrid running machines. Add the IP address of the Backup Server in the Add Peer. Now the IP address of the Backup Server will be listed in the list of backup servers in the Backup -> Add Backup schedule page. Configure a backup using the Backup Server's IP from menu Backup -> Add Backup Schedules page. 9. SGRP0001: No Server available for Replication Cause: This error will occur if the Backup Server is unable to connect to the Replication Server during the replication process due to one of the following reasons:. Replication Server is not running in the system. a. Backup Server is not able to resolve the Replication Server's hostname due to DNS lookup issue. b. Replication Port (default: 32004) is not open in the Replication Server side NAT/Firewall/Router settings. Resolution: Use the following commands to check the connectivity from Backup Server to Replication Server: iii. ping <Replication Server Name> iv. nslookup <Replication Server Name> v. telnet <Replication Server Name> <Replication port> If the above commands work, then replication should also work. If the ping and nslookup commands fail, then it is a DNS lookup issue for the Replication Server hostname from the Backup Server. If the telnet command fails, then check if the Replication Port is open in the firewall at the Replication Server and make sure StoreGrid Replication Server is running in that port. 10. SG0083: Exceeding allotted backup space in the server Cause: This error occurs if the client is trying to use more backup space than the allotted space. Resolution: Check the allotted space for the particular client in the Backup Server. To increase the space for the client in Backup Server, go to Server Admin -> Group Management -> [Group_Name] ->Edit Configuration (Action for the particular Client) page and enter the required space in Space Allotted field. Refer to the URL for more details. 11. Server incorrectly shows that a backup is still in progress when the client has suspended the backup Cause:

17 This error occurs when the TCP connection between the client and the server is closed prematurely, due to which though the backup was suspended in the client, the server thinks that the backup is still in progress. In the next incremental backup schedule from the client, StoreGrid will reset the status of the backup schedule in the Backup Server. If the reset of active status completes successfully, then the StoreGrid client will continue the backup. However, if for some reason the reset of active status fails, then backup will fail with the 'Backup in progress' error message in the client's backup report. Resolution: This error should be cleared during the next backup schedule. If it doesn't, then try restarting the Backup Server once to see if this error goes off in the subsequent schedule. This issue is fixed in v2.3 by updating the status based on the Keep Alive messages (for each backup schedule) received from the clients. 12. Problem in accessing the snapshot device while opening file Cause: This error appears when the StoreGrid is unable to open the configured files for backup from the snapshot device, when the 'Volume Shadow Copy' option is enabled for the backup schedule. This happens if the file to be backed up doesn't exist when the snapshot is performed, but exists while StoreGrid is listing the files for backup. Resolution: StoreGrid will backup these skipped file(s) in the subsequent backup schedules Check the skipped files count in the next schedule. If the problem persists, try disabling the 'Volume Shadow Copy' option for that backup schedule through the Backup -> List Backup Schedules -> Edit(Action for the particular backup) -> Advanced Options page. 13. Error Code 21 Cannot Start Storegrid message from the tray / Error in Starting StoreGrid" message from StoreGrid Tray Cause: These errors occur when the StoreGrid tray is unable to start the StoreGrid Application or the Service. The reason could be one of the following: The StoreGrid Tray application doesn't have permissions to start the StoreGrid Service. The StoreGrid Application file is not available at the StoreGrid Tray Applications path, i.e <StoreGrid Home>\bin location. Another instance of StoreGrid is already running in the machine. Resolution: Check if the StoreGrid Tray Application is running in an user account who has privileges to start the StoreGrid Service. Check if the StoreGrid service's logon user has enough privileges to start Windows services. Check if any other StoreGrid instance is already running in the system. You can verify this by checking for

18 "StoreGrid.exe" process in the 'Task Manager' tool. If there is already another instance running, try stopping that process and then starting it again. 14. Your StoreGrid license has expired. Number of StoreGrid Installations exceeded 1. Backups disabled. Cause 1: System name/ip addresses are duplicated in the Administration -> Add/Delete Peer page Resolution:. Stop StoreGrid application. i. Rename the "<DB Storage Location>/data/sgdisc.db" to "sgdisc.db.org" file. ii. Start the StoreGrid application. Cause 2: More than one StoreGrid instance is trying to use the same license key. The applied StoreGrid license is shared by other StoreGrid instances running in the same network. If there is a StoreGrid instance running in trial-user mode or with expired license period, then the license key from a Server running on a valid license will be propagated to that StoreGrid instance. Resolution: Apply valid server licenses on the servers through Administration -> Apple License Key to Server page. Applying a valid license on the server will fix this issue. Cause 3: This error could occur if the Backup Server has multiple network cards and the localhost entry is duplicated in the Administration -> Add/Delete Peer page. Resolution: If this is the case, bind the StoreGrid application to a particular IP address/subnet only by following the steps below. iii. Stop the StoreGrid. iv. Open <StoreGrid Home>\conf\SGConfiguration.conf file in a text editor. v. Provide the private IP address value in the IPAddress attribute of the <StoreGrid> tag and save the file. vi. Restart the StoreGrid application. The StoreGrid application will be bound to the specified IP Address now. If peer system name/ip addresses are duplicated in the Administration -> Add/Delete Peer page, then the peer should be deleted from the Add/Delete Peer page. The following steps will rediscover the StoreGrid peers again and update itself correctly after restart. vii. viii. ix. Stop StoreGrid application. Rename the "<DB Storage Location>/data/sgdisc.db" to "sgdisc.db.org" file. Start the StoreGrid application. 15. Your StoreGrid license has expired. License period elapsed, Backups disabled Cause: This error might occur in a StoreGrid client if StoreGrid is installed in Client-Server mode in the client machine.

19 Resolution: If the StoreGrid is running as a Client-Server, then a valid server license is needed in that machine. Therefore, it is recommended that all the clients are installed in Client Only mode. If the client is a Windows OS machine, then right click the StoreGrid Tray icon, go to Change StoreGrid Mode menu and select the Client option mode. If the client is running in a non-windows machine, then the StoreGrid mode can be changed manually by following the steps given below: Stop StoreGrid. Edit the <STOREGRID_HOME>/conf/SGConfiguration.conf file and change the value of StartModule in Module tag. The possible values of StartModule attribute and the corresponding modes of StoreGrid installation are listed below Server only Client only Client-Server Replication Server Change the StartModule attribute value to 602 for Client and save the file. Start StoreGrid. 16. Failed to authenticate this client with the Backup Server Cause 1: If Deny Auto Authorization is enabled in the Backup Server. Resolution: Enable Allow Auto Authorization option for the particular group and check. Cause 2: If there is a password mismatch between the Backup Server and the Client. Resolution: If this is the case, Reset the client's password in the StoreGrid Backup Server. Go to Server Admin -> Group Management - > [Group Name] -> Reset Password (Action for the particular client) page in the backup server's web console. Reset the server password for the client through Administration -> Advanced option -> Reset Password (Action for the Backup Server) page in StoreGrid client's web console. Authorize a new password (for both client and server) by editing the password in the Backup Server in Server Admin -> Group Management -> [Group Name] -> Edit Client Configuration page in the server

20 web console and then authorizing the client with the same password from the Administration -> Advanced Options -> Authorize Client page in the client web console. Resume the backup schedule and check if it works. 17. Backup request failed for backup [Backup Name] To Server [Server Name] with Error : Unable to take backup to Replication Server Cause: This error will occur if the Backup is configured directly from the StoreGrid client to the StoreGrid Replication Server. The StoreGrid Replication Server will not accept the backup request from StoreGrid Clients. StoreGrid Replication Server is designed only for receiving replication requests and replication data from the Backup Server and to handle restore requests from the client. Similarly, the StoreGrid Backup Server is designed for receiving Backup/Restore Requests from the client. Hence, Replication Server will not process the backup request from the StoreGrid client. Resolution: Configure backup from StoreGrid client to StoreGrid Backup Server. Enable replication in the StoreGrid Backup Server for the corresponding group. The client will backup to their server and the backup data on the server will be replicated to Replication Server. 18. On backup completion, a message "there were no modified files" is shown though several files were actually modified Cause: This error might occur if files to be backed up are from a mapped drive and Automatic Directory Monitoring is enabled for the backup. StoreGrid client running on Windows OS can use the Windows Directory Monitoring to get a notification when a file configured for backup is added/deleted/modified. These notifications are saved in the database to create the list of files that need to be backed up during the next backup schedule. However, notifications are not sent by the Directory Monitoring when the files modified/deleted/updated are in a mapped drive. Therefore, StoreGrid will not be able to identify the changed files when Automatic Directory Monitoring is enabled for backup of files from a mapped drive. Resolution:

21 Disabling Automatic Directory Monitoring should resolve this issue. Uncheck Automatic Directory Monitoring in the Backup -> List Backup Schedules -> Edit Backup Configuration (Action for particular backup) -> Advanced Options page. If the backup is already in progress, then suspending and resuming it manually will make the StoreGrid list all files/folders for backup again and therefore the files will get picked up. 19. SG: Unable to allot backup space Cause: This error will occur if the sum of the allotted space for all the clients is larger than the total allotted space for the Backup Server. Resolution: Before increasing the space for a client, confirm if the server has enough allotted space. Then increase the allotted space for the client. If the server does not have the necessary space, increase the allotted space for the Backup Server by going to Server Admin -> Server Settings page and then increase the allotted space for the client. After increasing the allotted space for the client in the Backup Server, schedule the backup from the client and check if the backup is successful. 20. StoreGrid not able to backup over the internet Cause: StoreGrid is not able to connect to the server on the Backup Port (default 32004). Resolution: Check the Backup Server side NAT/firewall settings. Make sure the incoming traffic on the Backup Port (default 32004) to the Backup Server is not blocked. Run a quick check for the connectivity from the client with the command telnet <server name/server IP Address> <Backup port>. If this command works, then the client should be able to backup to the server over the internet. If it fails, then make sure that Backup Port (32004) is open in the Firewall/NAT configuration in the network where the server is installed. 21. StoreGrid doesn't seem to work in XP SP2/SP3 Cause: In Windows XP SP2/SP3, the firewall is enabled by default. StoreGrid can neither discover other StoreGrid peers nor it can backup data to other machines. Resolution: Either disable the firewall settings or enable the ports for StoreGrid to work.

22 To disable the firewall, follow the steps below: o o o o o Open START->CONTROL PANEL->WINDOWS FIREWALL Select Exceptions tab Under 'Programs and Services', click on Add Programs button 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). 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. Enable to the following ports: TCP Ports: 32004, 32005, 32007, 32008, 6060, 6061 UDP Ports: 32006, 6363, 6364 o Open START->CONTROL PANEL->WINDOWS FIREWALL o Select Exceptions tab o Under Programs and Services, click Add Port button o Add 4 TCP Ports with unique names, allowing TCP Port numbers 32004,32005, 32007, 32008, 6060 and o Add 3 UDP Ports with unique names, allowing UDP Port numbers 32006,6363 and o Select OK to save the configuration and exit. 22. StoreGrid Server is not listed in the "Backup Servers" list Cause: 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, it will not be listed in the 'Backup Servers' list. Resolution: Manually add the StoreGrid peer to the list from the menu item Administration->Add Peer. In the "Add Peer" page, enter the StoreGrid peer s name or IP address. This is especially relevant if some peers are outside the network (as in the case of remote online backups). 23. StoreGrid has exited, do you want to restart it Cause: This error appears when StoreGrid application is shutdown and Windows does not clean up the TCP network connections. Resolution: Run the command netstat -a from a command window (Start > All Programs > Accessories > Command Prompt) and check if the TCP ports or are in listening mode. If the ports are in listening mode, then the system has to be restarted.

23 24. "Apache.exe could not be replaced" message during installation Cause: This happens when the StoreGrid web server service (which uses Apache) did not exit properly when the previous installation of StoreGrid service was deleted. Resolution: 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 and then proceed with the install. 25. Linux installation fails while installing GD/PHP (applicable only to versions older than 2.3) Cause: StoreGrid uses Apache, GD and PHP for its browser based user interface. StoreGrid is bundled with Apache, GD and PHP source files and these files get compiled during installation. StoreGrid installs Apache, GD and PHP in "/Vembu/StoreGrid" directory. And it is packaged with the modules that are required for StoreGrid user interface. If the required packages or third party libraries are not present, then the compilation will fail. Resolution: Before installing StoreGrid in linux machines, please check that the following packages are installed. make, available from gcc, available from g++, available from libstdc++5, available from The following third-party libraries will be used by GD if found by configure. While GD will compile and install even without these, it is recommended that at least zlib, libpng, freetype and jpeg are installed as well: Data compression library: zlib, available from Portable Network Graphics library; requires libpng, available from Free, high-quality, and portable font engine: FreeType 2.x, available from Portable JPEG compression/decompression library: JPEG library, available from To install PHP following 3rd-party libraries are required : Flex, available from Flex is a tool for generating programs that perform pattern-matching on text. Bison, available from Bison is a general-purpose parser generator that converts a grammar description for an LALR context-free grammar into a C program to parse that grammar. libxml2, available from Unable to log you in. Make sure StoreGrid is running / No connection could be made because the target machine actively refused it Cause 1:

24 StoreGrid application is not running in the system. Resolution: In Windows OS. Confirm that the StoreGrid application [StoreGrid.exe] is running in the system by using "Task Manager". If the application is not running, start StoreGrid through the StoreGrid system tray application. In Linux OS Verify if the StoreGrid application is running in the system by executing the command 'ps -e grep StoreGrid'. If the application is not running, start it with the command "sh startstoregrid.sh" in <STOREGRID_HOME> directory. If you see the following error message: "error while loading shared libraries: libstdc++.so.5..." while trying to start StoreGrid, check whether the libstdc++.so.5 and other compatible libraries are installed in that system. You can check this by listing the libraries by "ls -l /usr/lib/libstdc++.so.5*" command. If it is a 64 bit system, make sure 32 bit compatible libraries are present in your 64 bit Linux OS as StoreGrid runs as a 32 bit application in a 64 bit Linux machine. If the libraries are missing, please install 32 bit compatible libraries in your system and then try to start StoreGrid. For example, if your Linux flavor is Debian or Ubuntu or Gentoo, then install the 32 bit libraries with the following command: $ apt-get install ia32-libs For RedHat machine, you can search the dependency packages and install it by the following commands:- $yum search <Package Name> - To check the package is in the machine or not. $yum install <Package Name> - To install the package. Note: The above command should be executed with the root user privileges. Cause 2: The StoreGrid web console is unable to connect the StoreGrid applications UI communication port [by default, 32005]. Resolution: Confirm if the StoreGrid is in the listening mode at the UI communication port. Verify this by running the command 'netstat -an find "32005"' in the command prompt to check if the port is in LISTEN state. Run the "telnet <machine name> 32005" command in command prompt to confirm if the web console can access the StoreGrid application UI communication port. If any personnel firewall/intrusion detection tools are installed in the system, try adding the StoreGrid.exe, SGTray.exe applications and default port in the NAT/Firewall configuration's exception list and then try logging into the StoreGrid s web console.

25 27. Cannot export.\registry\regbackup.reg:error opening the file. There may be a disk or file system error." error in Vista. Cause: This error message shows up in Windows Vista when the user does not have full administrator privileges. In Vista, an application can be run as a service only by the Administrator account. A user account cannot run it as a service even if it has all the administrative privileges. Resolution:. Select StoreGrid build exe. i. Right click the exe and "run as an administrator". 28. StoreGrid doesn't seem to run properly after upgrading Windows to Vista. Cause 1: If StoreGrid was installed in an older version of Windows and then if the OS was upgraded to Vista, StoreGrid may fail to run. Resolution 1: Install (upgrade) the same version of StoreGrid again on top of the existing install. Cause 2: StoreGrid is installed under C:/Program Files in Vista. Resolution 2: Make sure you run StoreGrid with the option "Run as Administrator". The reason been, Vista allows an application to access the 'Program Files' folder only when run as an administrator user. You can enable the 'Run as Administrator' option for the <StoreGrid Home>\bin\StoreGrid.exe application from it's file properties dialog through 'Compatibility' tab -> 'Privilege Level' -> 'Run this application as administrator' option. If you don't have administrator access or if you don't want to run StoreGrid under the administrator account, make sure you install StoreGrid under your user account folder or install it in a folder which is not under 'Program Files'. 29. Error while dumping the Exchange Mail Boxes. Unable to create the PST file [or] "No new/modified files for backup" Cause : 'MSPST MS' is not configured in the Exchange Server. Solution : Add the 'MSPST MS' service by modifying the MAPISVC.INF file. The MAPISVC.INF file should have the information of the Microsoft Personal Folder store service. If this file does not have this information, then the Exchange Mailbox dump will fail with an error indicating that it was "Unable to

26 create the PST file" [or] "No new/modified files for backup". The MAPISVC.INF file is usually located in the Windows system directory (e.g.c:\winnt\system32\ or C:\Windows\System32\). Verify the file has an entry for the Microsoft Personal Folder store service. You can determine this by looking for the following information. If this information is not in the file then you need to add it in the proper sections: [Services] MSPST MS=Personal Folders File (.pst) [MSPST MS] Providers=MSPST MSP PR_SERVICE_DLL_NAME=mspst.dll PR_SERVICE_INSTALL_ID={6485D262-C2AC-11D1-AD3E-10A0C911C9C0} PR_SERVICE_SUPPORT_FILES=mspst.dll PR_SERVICE_ENTRY_NAME=PSTServiceEntry PR_RESOURCE_FLAGS=SERVICE_NO_PRIMARY_IDENTITY [MSPST MSP] =4e495441f9bfb80100aa0037d96e0000 PR_PROVIDER_DLL_NAME=mspst.dll PR_SERVICE_INSTALL_ID={6485D262-C2AC-11D1-AD3E-10A0C911C9C0} PR_RESOURCE_TYPE=MAPI_STORE_PROVIDER PR_RESOURCE_FLAGS=STATUS_DEFAULT_STORE PR_DISPLAY_NAME=Personal Folders PR_PROVIDER_DISPLAY=Personal Folders File (.pst) For more information about the format of the MAPISVC.INF file see the following Microsoft article: Dump location does not have enough space to export the PST file Cause : The dump location configured for this backup schedule doesn't have enough free space to store the *.PST files. Resolution : Increase the free space or cleanup the used space for the drive which is configured as dump location for this backup schedule. Location configured for dump process can be viewed from the view backup configuration of that backup schedule. 31. Error while creating the dump location <Dump_Location> Cause : The configured dump location for that particular backup schedule is not accessible or StoreGrid does not have enough permission to access the directory. Resolution :

27 Make sure that the dump location drive exist in your StoreGrid client. If that drive exist, provide enough write permission to the user under which StoreGrid is installed. 32. Users Mailbox/folder are not listed in the "Create Exchange Mailbox Backup" page. Cause : StoreGrid would fail to list the Exchange Users Mailbox folders for the following reasons. Mailbox which was accessed does not exist in the Exchange Server or invalid logon information being used to list the users Mailbox. Insufficient rights on the Exchange user mailbox. Resolution : Exchange Mail Level Backup requires "Full Control" access on the Exchange Server for the user account under which StoreGrid service is running. Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access the mailboxes. 33. StoreGrid fails to list some files/folders during a backup schedule. StoreGrid fails to list the files/folders due to the following reasons: Cause 1: In Windows, StoreGrid logon user is not in the Backup Operators group. Resolution 1: Check if the StoreGrid logon user is added in the Backup Operators group. If the StoreGrid logon user is a member of Backup Operators group, StoreGrid should able to list and read the files & folders for backup irrespective of the security settings configured for the files/folders. Cause 2: If the file/folder doesn't have enough permission for the StoreGrid user. Resolution 2: Check if StoreGrid logon user has Read and 'List Folder Contents' access permissions for the skipped folder by going to 'Folder Properties -> Security' dialog. If StoreGrid logon user doesn't have permission, enable the required permissions. Reschedule the backup and check. Cause 3: File/folder name contains Unicode characters. Resolution 3: Rename the file/folder without the Unicode characters.

28 34. I had changed the dump location and now I am not able to restore the previous backups.[applicable for Advanced Exchange Server, Exchange Mailbox and Advanced SQL Server backups.] Resolution : Please follow the steps below to restore the files from backup server to client and then to the Exchange Server/SQL Server. Restore the files in the backup server side which were backed up before changing the dump location (i.e. backup files pertaining to the old dump location). Transfer the restored files from the backup server to the client machine, say by using an external USB drive. Edit the 'restore.conf' available in "<Restored_location>/plugin/" folder in client machine. Change the 'DumpLocation' attribute value to old dump location in <StoreGrid><Restore><Plugin> tag. Save the 'restore.conf' configuration file. In the client machine, choose the second option - "I have previously restored data from my backup server to a local folder. I now want to use this data to restore the Exchange Mailbox." in 'Step 0' in the Restore Backup Data page and restore the files restored in step 2 by specifying the location of the files in 'Restore Location' field.

29 Migrating from version to 2.4 You can install StoreGrid v2.4 on top of the existing version and StoreGrid will automatically migrate to v2.4 release. Before migrating to v2.4, please make a note of the following instructions: To upgrade to v2.4 SP edition, you should be currently running the v2.3.5 SP edition. To upgrade to v2.4, just install v2.4 on top of the v2.3.5 installation. DO NOT UNINSTALL v If you are currently running a previous version, make sure you first upgrade to v2.3.5 and start StoreGrid to complete the migration process before installing v2.4. Also ensure that your backup server is running the same (or higher) version than the clients backing up to it. For example: before upgrading clients to v2.4, you must ensure that your backup server has been upgraded to v2.4; we typically ensure backward compatibility for clients, for example, a v2.3.5 client can still backup to a v2.4 server (this way, you can upgrade your clients in a phased manner). In short, ALWAYS UPGRADE THE BACKUP (& REPLICATION) SERVERS FIRST. Versions previous to v2.3.5 cannot be migrated directly to v2.4. You will have to first migrate them to v2.3.5 and install v2.4 on top of it. For versions previous to v2.2.1, first migrate them to v2.2.1 and to v2.3 and then to v You can download the v2.2.1 from version v2.3 from and version v2.3.5 from Migrating from version lower than If you are currently running a version previous to 2.3.5, then you need to first upgrade to v2.3.5 before installing v2.4. It is very important that after every version upgrade, you need to start the StoreGrid application and login into the web console and confirm the upgrade has happened successfully before upgrading it to the next version.!!!! As an example, if you are currently running StoreGrid v2.2, then you need to follow the steps given below to upgrade to v2.4 Install StoreGrid v2.2.1 build on top of the existing v2.2 installation. Choose 'Start StoreGrid' option after completing the installation and wait for some time to let the StoreGrid application to complete the migration. If you log into the web console while the migration is in progress, you will be redirected to page that indicates the migration is in progress. Once the migration process is completed, login to the web console and verify all the configurations and backups are intact - VERY IMPORTANT Install StoreGrid v2.2.5 build on top of the existing v2.2.1 installation. Choose 'Start StoreGrid' option after completing the installation and wait for some time to let the StoreGrid application to complete the migration. Once the migration process completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT Install StoreGrid v2.3 build on top of the existing v2.2.5 installation. Choose 'Start StoreGrid' option after completing the installation and wait for some time to let the StoreGrid

30 application to complete the migration. Once the migration process completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT Install StoreGrid v2.3.5 build on top of the existing v2.3 installation. Choose start StoreGrid option after completing the installation and wait for some time to let the StoreGrid application to complete the migration. Once the migration process is completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT Install StoreGrid v2.4 build on top of the existing v2.3.5 installation. Choose start StoreGrid option after completing the installation and wait for some time to let the StoreGrid application to complete the migration. Once the migration process is completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT Migrating from version 2.3 to You can install StoreGrid v2.3.5 on top of the existing version 2.3 and StoreGrid will automatically migrate to release. Versions older than v2.3 cannot be migrated directly to v You will have to first migrate them to v2.3 and install v2.3.5 on top of it. For versions older than v2.2.1, first migrate them to v2.2.1 and then to v2.3. You can download the v2.2.1 from and version v2.3 from If you login into the web console when the migration process is in progress, you will be directed to a page which indicates that migration is in process. The migration might take up to 20 minutes depending upon the amount of data to be migrated. Wait for some time and then try re-logging in. Please don't shutdown and restart StoreGrid as this will only further delay the migration. Migrating from version to 2.3 You can upgrade StoreGrid v2.2.1 to v2.3 by just installing v2.3 on top of the current installation. Versions older than v2.2.1 cannot be migrated directly to v2.3. You will have to first migrate them to v2.2.1 and then migrate v2.2.1 to v2.3. You can download the v2.2.1 from Migration might take some time depending upon the amount of data to be migrated. Please don't restart StoreGrid as this will only further delay the migration. If you log into the StoreGrid web console during migration, you will be directed to a page indicating that the migration process is in progress. Wait for sometime and then try logging back in. In the backup server. migration could take about 5 minutes for every 100,000 files backed up. Migration in the client should not take much time. Migrating from version 2.0/2.0.1/2.1/2.1.1 to Migrating to StoreGrid is completely automatic. All you have to do is to install StoreGrid on top of your existing (2.0/2.0.1/2.1/2.1.1) StoreGrid installation. Please migrate your Backup Server & Replication Server first. Thereafter, you can migrate your clients in a phased manner.

31 Clients running version 2.0/2.0.1/2.1/2.1.1 will continue to backup to your backup server running v2.2.1! Section 1 below covers Server Side Migration, and Section 2 covers Client Side migration. 1. StoreGrid Server-side Migration While updating a StoreGrid server installation to version 2.2.1, most of the migration procedures are internal and automatic. The migration on the StoreGrid Backup Server and the StoreGrid Replication Server may take some time based on the number of files backed up on the StoreGrid Server. For example, migrating 100,000 files will take about 10 minutes and 200,000 files will take about 20 minutes. While updating a StoreGrid server installation to version 2.2.1, most of the migration procedures are internal and automatic. But the following changes to StoreGrid needs to be understood by the service provider before deploying and using StoreGrid StoreGrid Groups From StoreGrid 2.2.1, all clients are organized under Groups. In StoreGrid Professional Edition, the clients were listed directly in the 'Server Admin -> Client Management'. Now in StoreGrid 2.2.1, the clients will be by default organized under the 'Default Group'. Users can create multiple Groups (up to one level) and organize their clients based on their Groups, such as Departments, Office Branches, etc., NOTE: The Filtering configurations are not migrated from to Hence, please reconfigure the filtering options after upgrading to StoreGrid Release. Migrating from version 2.0/2.0.1/2.1 to There is no special migration procedure if you are updating from 2.0/2.0.1/2.1 to You can just install StoreGrid on top of the existing 2.0/2.0.1/2.1 version and StoreGrid will automatically migrate to the release. StoreGrid will not be functional while the migration is in progress. But the migration itself will take only a few seconds. While you update from Version 2.0.1/2.1 to 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. Migrating from version 1.6 to 2.0 Vembu StoreGrid 2.0 is a major upgrade release over the StoreGrid 1.6 release. StoreGrid's architecture and infrastructure have been revamped and improved significantly keeping in mind scalability, performance and flexibility in terms of evolution of future versions of StoreGrid. Towards that end, StoreGrid 2.0 completely leverages an embedded RDBMS both in the client and the server side. Except for the backup files, which uses the native file system itself, every other information StoreGrid generates or uses like configurations, file meta-data, file signatures, events, version information, backup reports, restore reports etc. are all driven from the RDBMS. Leveraging an RDBMS gives StoreGrid the capability to evolve rapidly in terms of new features and user-interface improvements etc. without compromising on scalability and performance. With this major re-design of StoreGrid with the 2.0 version, we expect to deliver customer focused features at a more rapid pace than before. Whether StoreGrid installation is a Client, Server, Or Client-Server Installation, the first time it runs, StoreGrid 2.0 automatically migrates all the file meta-data and configurations maintained in flat files or the 1.6 database to the newly created 2.0 database. The StoreGrid Client side migration is quite fast. Even for 1000s of files, the client side migration will take only a few minutes. On the StoreGrid server side, where the backup data is present, depending upon the number of

32 files you have backed up earlier, the migration may take some time. The time taken for the migration on the server side depends upon the total number of files that were earlier backed up with StoreGrid 1.6. Migrating 10,000 files will take about 4 minutes and 100,000 files will take about 40 minutes. StoreGrid will not be functional while the migration is in progress. While you upgrade from Version 1.6 to 2.0, please note the following points: 1. StoreGrid 2.0 will automatically migrate your 1.6 data to 2.0 formats when it runs first time after the upgrade. 2. StoreGrid 2.0 is not interoperable with StoreGrid 1.6. Hence make sure you upgrade and migrate both your client and server installations before you resume your backups. The recommended procedure is to update and migrate your StoreGrid servers first. StoreGrid 2.0 will put all the backup schedules in the client in suspended mode after the migration process.you need to resume them manually after making sure the backup servers also have been upgraded and migrated to StoreGrid will not be able to schedule any backups while the migration is in progress. 4. 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. 5. StoreGrid Migration process may use high CPU cycles and may slow down other processes on the machine/pc. Hence it is advisable to upgrade to StoreGrid 2.0 when you are not using the machine/pc for CPU intensive tasks. Advanced Users The following points should help you understand the internal migration process when you run StoreGrid 2.0 for the first time after upgrading from StoreGrid 1.6 to 2.0 Client Side Migration The operations performed in client side migration are as follows: a. User Account Migration: Read the user lists from userfiles.lst and write to Client DB. b. Backup Configuration Migration: List the *.sbf, *.imm & *.scc files from <STOREGRID_HOME>/conf & add backup configuration to DB. After migration, the backups will be in suspended status. User has to resume the backup schedule manually only after making sure the backup servers the client was backing up to are also upgraded to the StoreGrid 2.0 version and the migration has taken place in those servers. c. Discovered Peer List Migration: Read the discovery.log (if not present, discovery.tmp) file from <STOREGRID_HOME> and add them to Discovery DB. d. Discovery Configuration Migration: Read the discovery.conf file from <STOREGRID_HOME>/conf and write to Discovery DB. e. Delete Configuration & Reports Migration: List the *.sdf files from <STOREGRID_HOME>/conf & write them to Client DB. f. File Meta Data Migration: Attach the 1.6 DB to 2.0 DB and copy the file meta-data information and signature data. g. Backup Reports Migration: Attach the 1.6 DB to 2.0 DB and copy the backup reports information. h. Restore Reports Migration: List the *.rpt files from <STOREGRID_HOME>/report/restore and add them to DB.

33 2. StoreGrid 1.6 to 2.0 Server Side Migration The operations performed in server side migration are as follows: a. For each backup client backing up to the server, find the backup location from <SG_HOME>/conf/diskspaceconfiguration/and migrate the backed up files to a new 2.0 directory structure which is based on directory Ids. Note that StoreGrid 2.0 will move the backed up files from the original location to the new location. b. By default all the client's backup will be done under a directory called "1" under the backup location. c. Move Disk Space Configuration information of all clients to Server DB. Migrating from version to 2.0 If you are still using the release and want to migrate from to 2.0, then the migration is a two step process. Firstly you need to migrate from to 1.6 by installing StoreGrid 1.6. You can check whether the migration has completed by logging into the UI. The steps for migrating from to 1.6 is given below. After migrating to 1.6, then you can migrate StoreGrid to 2.0 by installing 2.0 on top of the 1.6 version. The steps for migrating from 1.6 to 2.0 is given above. Migrating from version to 1.6 NOTE: StoreGrid 1.6 is a minor bug fix release over So there is no special migration procedure if you are updating from 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 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 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.

34 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 StoreGrid 1.6 creates a relational database file "storegrid.db" in <INSTALLATION_HOME>/Vembu/StoreGrid/data directory. 2. The 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 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.

35 Vembu StoreGrid Windows Installation Guide The StoreGrid Windows version is available for download in the following URL: Download the Windows installer, VembuStoreGrid_2_4_Pro.exe To install StoreGrid on Windows machines, follow the steps given below: 1. Double click VembuStoreGrid_2_4_Pro.exe 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): While updating to or installing StoreGrid 2.4, 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. This step is applicable only if you have installed StoreGrid as a service. If you have installed StoreGrid as an application, please skip this Step and proceed to Step 5. 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 four options: o 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. o Client only This computer can back up on to other computers. However, other computers cannot back up on to this computer. o Server only Other computers can back up on to this computer. However, this computer cannot back

36 up on to other computers. o Replication Server Other StoreGrid backup servers can replicate their data to this server for redundancy. Select one of the four options and click Next. 6. (StoreGrid will skip this step and retain existing settings if it detects an earlier version installed) Enter a StoreGrid Identity. This will be used to identify this installation of StoreGrid on your network / your online backup service provider s network. By default, StoreGrid takes the machine name. Ideally, enter the ID of the client using this particular machine. Using an ID ensures that your StoreGrid ID is truly unique. Note: The StoreGrid ID value is case insensitive. Hence, the 'StoreGrid ID' you have entered will be automatically converted to lower case. Enter a valid StoreGrid Group Name. The StoreGrid Group name is the 'name' under which your client is categorized (on the backup server). By default, this is set to "Default Group". Please leave this as the default "Default Group". You need not to provide this value if you are installing StoreGrid in Server Only or Replication Server mode. 7. (StoreGrid will skip this step and retain existing settings if it detects an earlier version installed) 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. 8. If StoreGrid detects existing data left behind from a previous installation of StoreGrid (wherein you uninstalled the previous version but left some data behind) it will prompt you for a desired action. If no old data was found in the installation directory or if you are simply upgrading from an existing installed version, StoreGrid will skip this step. 9. (StoreGrid will skip this step and retain existing settings if it detects an earlier version installed) By default, StoreGrid Server will store the backup data from the clients to the "<INSTALLATION_DIR>/Vembu/StoreGrid" directory. If you want to change the server's default backup location, please choose a different directory from the tree. Click Next to continue. 10. (StoreGrid will skip this step and retain existing settings if it detects an earlier version installed) There are three parts to this step. o 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 Unless you are an advanced user, please leave this as is. o 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. 11. Advanced Port Configuration (Including HTTPS): Click on the Advanced Port Configurations (Including HTTPS) link to configure StoreGrid backup server port, UI communication port and HTTPS port. Provide valid TCP port numbers for Backup Server Port, UI Communication Port and HTTPS port. You will be able to configure 'Advanced Port Configuration' while upgrading StoreGrid too. Backup Server Port is the port through which StoreGrid clients will backup the data to the backup server. The default value is UI Communication Port is the port through which StoreGrid Apache/PHP modules communicate with

37 StoreGrid to serve UI requests from the StoreGrid WebConsole. The default value is HTTPS Port: HTTPS Port is the port used to access the StoreGrid Webconsole in a secured manner through HTTPS protocol. Default value is Enable HTTPS: HTTPS Port is the secure webconsole port through which you can access the StoreGrid webconsole in secure manner. You should enable "Enable HTTPS" option to edit this value. If you enabled HTTPS option, then you can access the StoreGrid webconsole through name>:<https port> URL. And also, if you try to access the StoreGrid webconsole through name>:<webconsole port>, then you will be automatically redirected to name>:<https port> url. 12. (StoreGrid will skip this step and retain existing settings if it detects an earlier version installed) 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. 13. 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. 14. After copying the StoreGrid files, a page will show the progress of StoreGrid installation. If StoreGrid installation completes successfully, you will be automatically redirected to the finished installation page. Otherwise, the installation progress page will show the error details. 15. 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. StoreGrid will automatically migrate your old data to 2.4 after you start StoreGrid for the first time. 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. Problem Starting StoreGrid in Vista If StoreGrid is installed under C:/Program Files in Vista, then make sure you run StoreGrid with the option "Run as Administrator". The reason been, Vista allows an application to access the 'Program Files' folder only when run as an administrator user. You can enable the 'Run as Administrator' option for the <StoreGrid Home>\bin\StoreGrid.exe application through it's file properties dialog through 'Compatibility' tab -> 'Privelege Level' -> 'Run this application as administrator' option. If you don't have administrator access or if you don't want to run StoreGrid under the administrator account, make sure you install StoreGrid under your user account folder or other than the 'Program Files' folder. StoreGrid Silent Installation 1. What is a silent installation?

38 Some service providers prefer not to have their groups go through the step by step installation screens typical of most installations from within the windows operating system, and instead would like to install StoreGrid directly and 'silently' from the command line prompt. The StoreGrid 'customized client build' you have been provided is capable of being installed from the command line exactly as described above. The same build will also work from within Windows(as a UI based installation) wherein you just double click the build file and follow the steps on the screen. 2. How do I do a 'silent install' from the command line? For command line/silent installation, just follow the simple steps below: o o o There are two options available: SILENT & VERYSILENT. In a SILENT installation, during installation, the Installation Progress page is displayed once installation has started and till it is complete. In a VERYSILENT installation, no Installation Progress page will be shown. Syntax to be followed: <Build File Name> [/SILENT or /VERYSILENT] /AGREE_LICENSE="yes/no" /SG_ID="<Client identity>" /SG_GroupName="<Group Name>" /DIR="<StoreGrid Home Path>" /SG_Mode="StoreGrid mode" /SG_Type="service/application" /SG_User="StoreGrid webconsole user name" /SG_Pass="StoreGrid webconsole Password" /SG_Port="StoreGrid webconsole port" /SG_PrevDataOption="delete/rename" /SG_BackupPort="The Backup server port." /SG_UIPort="The UI communication port." /SG_HTTPS="0/1" /SG_HTTPSPort="The HTTPS port." [/SG_WUser="Windows logon user name for StoreGrid service" /SG_WPass="Windows logon password for StoreGrid service"] /LOG="Installation log file name". Note: o o o o o /SILENT or /VERYSILENT must be the first argument immediately after the <build file name> Thereafter, there is no fixed order for providing the command line arguments. There should be a space between <build file name> and each command line arguments. Except user names and passwords, all other values are case insensitive We recommend that you provide the /LOG option the first couple of times that you use the silent installation so you can identify issues during the silent installation, if any. Description of Arguments, etc (Arguments with * are mandatory): Argument Description Values Default Value Note */SILENT */VERYSILENT You must specify either one of these options Hence this argument is necessarily required to be set to "Yes" to run the installation. Please install StoreGrid from *AGREE_LICENSE Do you agree with the License Agreement? Yes / No No within the Windows UI if you would like to see the license agreement. You may want to copy & paste this agreement on an html page on your website for your

39 groups to read, if required. More on valid client IDs: *SG_ID StoreGrid client id. Must not be null or invalid id. Ideally, this should be an ID as this is unique and easily remembered. In fact, if you can, insist that all your groups use IDs as StoreGrid IDs. As your business grows, you'll be glad you did! - - Allowed characters: [A-Z][a-z][0-9][ _.] Value must not contain more than two "@" characters Must not start or end with special characters Length must be 1-50 characters. More on valid Group Name SG_GroupName StoreGrid Group Name. Must not be null or invalid value. - Default Group # Allowed characters: [A-Z][a-z][0-9][ _.] Length must be 1-50 characters. DIR Installation location Any valid location C:\Program Files\ # This location is the StoreGrid Home Server Only SG_Mode Mode of StoreGrid installation 601/602/603/ # Client only Both Client and Server Replication Server SG_Type StoreGrid installation type Service / Application Application # If selected service option, please provide SG_WUser & SG_WPass also. SG_WUser & SG_WPass If StoreGrid installation type (see above) is Service, pls. provide the logon account details. Valid Windows User name and Password - No additional details are required for installing for Local System Account. Authentication details User name: SG_User & SG_Pass for StoreGrid webconsole [username - admin Password: - & password] admin SG_Port StoreGrid Webconsole port number. Any valid TCP port number 6060 # - SG_PrevDataOption During installation, if there is existing data from a previous installation of StoreGrid, what is to be done? Delete / Rename Rename -

40 SG_BackupPort The port through which StoreGrid clients will backup the data to the backup server. Any valid TCP port number between 1 to # - The port through which SG_UIPort StoreGrid Apache/PHP modules communicate with StoreGrid to serve UI requests from the StoreGrid WebConsole. Any valid TCP port number between 1 to # - SG_HTTPS You can enable the secure HTTPS web access by checking the "Enable HTTPS" check box. 0 / 1 0 # 0 - Disable 1 - Enable HTTPS Port is the secure SG_HTTPSPort webconsole port through which you can access the StoreGrid webconsole in secure manner. Any valid TCP port number between 1 to Must not be same as the 6061 # SG_Port / SG_UIPort / SG_BackupPort Some machines do not validate Windows login details correctly may reject even when the login details are right. In such cases, turning SG_WValidate Option to enable or disable validation of Windows login details. Enable - 1 Disable - 0 Enable this option off may be advisable. If this option is turned off and if the login details entered are wrong, then the user may not be aware that the login details are wrong till the backup is scheduled and fails to run. This status tells if the client needs to connect to the SG_SSL_SERVERPORT_STATUS HTTPS Port is the secure webconsole port through which you can access the StoreGrid webconsole in secure manner. Enable - 1 Disable backup server through the SSL enabled backup port or not. If this option is enabled, valid SSL Backup port should be specified during silent installation. If this option is not provided during upgrade, then the previous installation value is taken. The backup port value with SSL security option. It should SG_SSL_SERVERPORT Backup port with SSL security. Valid port value be the same at backup server and client system. If this option is not provided then the previous installation value is taken. # - While upgrading StoreGrid, if these arguments not provided, the values will be taken from the previous installation. If it is a new installation, the default values as mentioned in the table will be used.

41 VERY IMPORTANT: SG_ID and AGREE_LICENSE are mandatory arguments (besides /SILENT or /VERYSILENT); all other arguments are optional. Examples of valid Commands: a. Silent Install for a user whose SG installation will be referred by the client ID: billg@vembu.com ; install in both client-server mode; install as an application, the user will use the username: bill and password: abc123 to access the StoreGrid webconsole which must run on port Connects backup servers 3344 port for backup; The webconsole will communicate the StoreGrid application through 3355 port. The user would like to see the progress of the installation as it happens Required command line is: VembuStoreGrid_2_4_Pro.exe /SILENT /AGREE_LICENSE="yes" /SG_ID="billg@vembu.com" /SG_Mode="602" /SG_Type="Application" /SG_User="bill" /SG_Pass="abc123" /SG_Port="6087" /SG_BackupPort="3344" /SG_UIPort="3355" /SG_HTTPS="1" /SG_HTTPSPort="6088" [Note: All the command line options should come in single line.] b. Silent Install for a user whose SG installation will be referred by the client ID: billg@vembu.com ; install in both client-server mode; install as an application (default), the user will use the default username: admin and default password: admin to access the StoreGrid webconsole which must run on the default port The user is not bothered about seeing the progress of the installation as it happens. Just install it! Required command line is: VembuStoreGrid_2_4_Pro.exe /SILENT /AGREE_LICENSE="yes" /SG_ID="billg@vembu.com" [Note: All the command line options should come in single line.] Contact us at storegrid-support@vembu.com for any additional help you may require with silent installations.

42 Vembu StoreGrid Linux Installation Guide The Linux version of StoreGrid is available for download at the following URL: The Linux builds are pre-compiled and all the required dependencies are included in the build itself. You don't have to install the dependencies separately. The libstdc++.so.5 is a run time compilation library required for StoreGrid Application to run in the machine. This library can be downloaded and installed from Note: Linux installation should be run with the root user privileges. Once you have ensured that the above packages are all available in your linux machine, follow the steps given below to install StoreGrid: 1. Unzip the downloaded ZIP file. 2. Execute the bin file o o o For RedHat Linux 8.0, 9.0 and Later, RedHat EL 4 and Later, CentOS 4 and Later, Fedora Core 3 and Later, SuSE Linux 9.x and Later:./VembuStoreGrid_2_4_RH.bin For Mandrake Linux 10.0 and Later:./VembuStoreGrid_2_4_MDK.bin For Debian Linux 3.0 and Later:./VembuStoreGrid_2_4_DBN.bin StoreGrid needs root user privileges. Hence if StoreGrid is installed as an user which does not have root privileges, the installation will abort with the message 'You need root user privileges'. This is applicable for upgrades as well. 3. The first step in the installation is to choose the type of installation. You can select from one of the two options : o o 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. Choose option 1, if you want StoreGrid 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 be installed as an application to backup only the system files and folders. 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 StoreGrid is installed fresh and you chose option 1 in the above step, then you will be asked to provide a password for the StoreGrid user account which is 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

43 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. If you had chosen option 2 for the type of installation, StoreGrid will ask for a location to install StoreGrid. By default StoreGrid will be installed in the "Current Directory". StoreGrid setup will be installed under "Vembu/StoreGrid" in the "Current Directory" directory. To install in a different directory, enter the absolute path (full path) for Vembu StoreGrid installation. Note that the setup will create the "Vembu/StoreGrid" directory under the directory you entered. 7. If StoreGrid is already in the installed location, StoreGrid will try to upgrade. The installation will ask the user whether the previous setup can be migrated or not. Enter 'yes' to continue up gradation and 'no' to abort the installation. StoreGrid can be upgraded to 2.4 from StoreGrid version Configure StoreGrid as : You need to choose one of the options (Client-Server, Client, Server or Replication Server). The four modes are explained in detail below. o o o o 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 installations. 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 a StoreGrid backup server but cannot accept backup data from other StoreGrid installations. 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 installations but cannot backup local files/folders to other StoreGrid peers. Replication Server - Other StoreGrid backup servers can replicate their data to this server for redundancy but cannot accept backup data from other StoreGrid peers. 9. Assign A StoreGrid ID: StoreGrid ID is the unique name with which your StoreGrid installation is identified. By default, it takes your machine name as the StoreGrid ID. But we recommend giving a globally unique ID. Here you will be provided with these options: o o o o "Do you want to identify your machine name by other than hostname" If you enter "y/y" then following text will displayed in terminal to enter StoreGrid ID. "Enter StoreGrid ID" Enter the StoreGrid ID for your installation. We recommend using your id for this. Note:The StoreGrid ID value is case insensitive. Hence, the 'StoreGrid ID' you have entered will be automatically converted to lower case. Group Name: Enter valid StoreGrid Group Name. The StoreGrid Group name is the 'name' under which your client is categorized (on the backup server). By default, this is set to "Default Group ". Please leave this as the default "Default Group". 10. Configure StoreGrid Server backup location:

44 By default, StoreGrid Server will store the backup data from the clients to the "<INSTALLATION_DIR>/Vembu/StoreGrid" directory. If you want to change the server's default backup location, here you will be provided with these options. o o o o "Do you want to change the server's default backup location" If you enter "y/y" then following text will displayed in terminal to enter StoreGrid Server backup location. "Enter the absolute path for StoreGrid Server's backup location" Enter the backup location for this server here. 11. Enable HTTPS based StoreGrid WebConsole access: StoreGrid uses the TCP port '6060' for its web console and uses the TCP port '6061' for its https based web console access. StoreGrid supports 'https protocol' to access the StoreGrid webconsole in a secured manner. Hence, if you try to access the StoreGrid webconsole through name>:<webconsole port>, then you will be automatically redirected to name>:<https port> url. Note: StoreGrid Web Console access through HTTPS is enabled by default. 12. Vembu StoreGrid Web Console Authentication: StoreGrid's Web Console 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. 13. Configure Backup Server Port and UI Communication Port By default StoreGrid uses the ' Backup Server Port' 32004, for all the client-server communications and the 'UI Communication Port' for communication between the StoreGrid Web Console and the StoreGrid Application. If you wish StoreGrid to use ports other than the default, you are provided with the following options here : o o o o o o "Do you want to change these ports from default value?" If you enter "y/y" then following text will displayed in terminal to enter StoreGrid's Backup Server Port and the UI Communication Port. "Please enter a valid port value [numerical whole number] for Backup Server Port". Enter the Backup Server Port value here. "Please enter a valid port value [Numerical whole number] for UI Communication Port". Enter the UI Communication Port value here. 14. 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 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.

45 Vembu StoreGrid Mac OS X Installation Guide 1. Login as an admin user. To confirm, go to 'System Preference -> Accounts -> Security'. The option 'Allow user to administer this computer' should be enabled. If the option is not enabled, please enable the option and reboot the system. 2. Download the build from the URL: 3. Move the downloaded zip to the directory from where you want to run the StoreGrid installation. Note: The steps given below should be done in the Finder window - Mac OSX file explorer window. 4. Unzip the downloaded installation zip by double clicking the zip file. 5. Go to the unzipped folder ('VembuStoreGrid_2_4_PRO_Mac' or 'VembuStoreGrid_2_4_PRO_IMac'). 6. You will find two files namely: 1. InstallStoreGrid - Installer file 2. VembuStoreGrid.bin. - Installation binary file Double click the 'InstallStoreGrid' file in the Finder window. 7. Provide the login password. Enter the currently logged in user's password and proceed with installation. This should complete the installation. Note: If you get a prompt saying the entered password is incorrect or you don t have the admin rights, please verify whether the password you have entered is the password of the user you are currently logged in as. StoreGrid has two types of installation Typical Installation: StoreGrid will be installed with its default configurations except StoreGrid ID and the Group Name. Custom Installation: User will be prompted to select with different inputs like web console username and password, web console ports, etc during the installation. If 'Run Later' option has been selected at the end of custom installation, then follow the steps give below to run StoreGrid: 1. Open the terminal console and switch to root user by executing the command 'sudo s. If it prompts for a password, enter the currently logged in user password [the password given at the start of StoreGrid installation]. 2. Go to the '<StoreGrid_Installed_Dir>/Vembu/StoreGrid' directory and execute the following command to start StoreGrid: - sh startstoregrid.sh. The <StoreGrid_Installed_Dir> will be /Applications directory by default. This step is not required if the option 'Run now' has been selected during 'Custom' installation or if you have opted for 'Typical' installation. Note: To access StoreGrid setup after installation, you should be a root user. To do this, open the terminal console and switch to root user by executing the command 'sudo s. If it prompts for a password, enter the currently logged in user password [the password given at the start of StoreGrid installation].

46 Vembu StoreGrid FreeBSD (for FreeBSD 5.4 and above) Installation Guide The FreeBSD version (for FreeBSD 5.4 and above) of StoreGrid is available for download at the following URL: Download the zip file: 1. For FreeBSD 5.4 : VembuStoreGrid_2_4_Pro_FreeBSD.zip Vembu StoreGrid FreeBSD installation compiles and installs its own version of Apache, GD and PHP. So before installing StoreGrid in FreeBSD machines, please check that the following packages were installed. 1. make, available from 2. gcc, available from 3. g++, available from 4. libstdc++4, available from The following 3rd-party libraries will be used by gd if found by configure. While gd will compile and install even without these, we suggest that at least zlib and libpng are installed, and recommend that freetype and jpeg are installed as well: 1. Data compression library: zlib, available from 2. Portable Network Graphics library; requires libpng, available from 3. Free, high-quality, and portable font engine: FreeType 2.x, available from 4. Portable JPEG compression/decompression library: JPEG library, available from To install PHP following 3rd-party libraries are required : 1. Flex, available from -- Flex is a tool for generating programs that perform patternmatching on text. 2. Bison, available from -- Bison is a general-purpose parser generator that converts a grammar description for an LALR context-free grammar into a C program to parse that grammar. (OR) 3. libxml2, available from -- XML DOM library used by php's xml parser. 4. bzip2, available from -- Free, patent free, high-quality data compressor. 5. curl, available from -- Free, patent free, high-quality data compressor. 6. libmcrypt, available from -- A simple crypting program. 7. mhash, available from -- To support wide variety of hash algorithms. To install Apache with HTTPS support, Open SSL libraries are required : 1. To enable https support in StoreGrid, please ensure that openssl package is installed on your system before you enable https support. You can download the latest openssl version from Once you have ensured that the above packages are all available in your FreeBSD machine, follow the steps given below to install StoreGrid: 2. Unzip the downloaded ZIP file.

47 3. Execute the bin file VembuStoreGrid_2_4_FreeBSD.bin 4. The first step in the installation is to choose the type of installation. You will be given two options: a. You can install StoreGrid in a newly created StoreGrid user account, where the StoreGrid user account will be automatically created with root privileges b. 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 all the users 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/rc.d/storegrid start/stop". 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 5. 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/rc.d/storegrid start/stop". 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 6. 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. 7. 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. 8. Upgrading StoreGrid from to 2.4 Vembu/StoreGrid directory found in the installation path provides you with Yes/No options: Choosing 'Yes' will upgrade StoreGrid to the latest version. Choosing 'No' will skip the upgrade process. UPDATE Vembu StoreGrid by retaining the previous backup data. Note that all backup data in StoreGrid will be automatically migrated to 2.4 when StoreGrid 2.4 starts for the first time.[ Recommended ] Configure StoreGrid as : You need to choose one of the options (Client-Server, Client, Server, Replication Server). The four modes are explained in detail below. a. 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.

48 b. 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. c. 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. d. Replication Server Other StoreGrid backup servers can replicate their data to this server for redundancy. Assign A StoreGrid ID: StoreGrid ID is the unique name with which your StoreGrid installation is identified. By default, it takes your machine name as the StoreGrid ID. But we recommend giving your id as the StoreGrid ID so that it is globally unique. Here you will be provided with these options: "Do you want to identify your machine name by other than hostname" If you enter "y/y" then following text will displayed in terminal to enter StoreGrid ID. "Enter StoreGrid ID" Enter the StoreGrid ID for your installation. We recommend using your id for this. Note: The StoreGrid ID value is case insensitive. Hence, the 'StoreGrid ID' you have entered will be automatically converted to lower case. Group Name: Enter valid StoreGrid Group Name. The StoreGrid Group name is the 'name' under which your client is categorized (on the backup server). By default, this is set to "Default Group ". Please leave this as the default "Default Group". Configure StoreGrid Server backup location: By default, StoreGrid Server will store the backup data from the clients to the "<INSTALLATION_DIR>/Vembu/StoreGrid" directory. If you want to change the server's default backup location, here you will be provided with these options. "Do you want to change the server's default backup location" If you enter "y/y" then following text will displayed in terminal to enter StoreGrid Server backup location. "Enter the absolute path for StoreGrid Server's backup location" Enter the backup location for this server here. Enable HTTPS based StoreGrid WebConsole access: StoreGrid supports 'https protocol' to access the StoreGrid webconsole in a secured manner. HTTPS is nothing but a combination of normal HTTP interaction over an encrypted Secure Sockets Layer (SSL) to ensure reasonable protection from eavesdroppers and man-in-the-middle attacks. StoreGrid uses the TCP port 6061 for https based WebConsole access. Hence if you choose https support, then you can access the StoreGrid WebConsole through " or IP_address>:6061". And also, if you try to access the StoreGrid webconsole through name>:<webconsole port>, then you will be automaticaly redirected to name>:<https port> url. Note : To enable https support in StoreGrid, please ensure that openssl package is installed on your system before you enable https support. You can download the latest openssl version from 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.

49 Configure Backup Server Port and UI Communication Port By default StoreGrid uses the 'Backup Server Port' 32004, which is used for all the client-server communications like Backup/Restore, and the 'UI Communication Port' 32005, which is used for communication between the StoreGrid WebConsole and the StoreGrid Application. If you want to have StoreGrid using other than the default ports, here you will be provided with these options. "Do you want to change these ports from default value" If you enter "y/y" then following text will displayed in terminal to enter StoreGrid's Backup Server Port and the UI Communication Port. "Please enter a numerical whole number value for Backup Server Port" Enter the Backup Server Port value here. "Please enter a numerical whole number value for UI Communication Port" Enter the UI Communication Port value here. Web Server Port StoreGrid's user interface is browser based. By default StoreGrid Web server is configured to run on port 6060 and 6061 (for HTTPS). From your browser you will have to type Machine Name>:6060 to start the StoreGrid Web Console. This installs the product and complete 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 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.

50 StoreGrid Administration The StoreGrid Administration features (available under the Administration menu), are related broadly to administering and configuring a StoreGrid installation which is either operating as a Client or a Client-Server. But all administration and configuration related specifically to a StoreGrid Server are available under the "Server Admin" menu. Please go to the section StoreGrid Client User Guide->Administration to learn about administration and configuration options common to both StoreGrid Clients and Servers. If you want to learn about StoreGrid Server Administration go to the section StoreGrid Server User Guide->Server Administration.

51 Configure Storage Location This section describes the different Storage Locations that can be configured in StoreGrid. Global Backup Data Storage Location While installing StoreGrid you can specify the backup storage location to be used by StoreGrid. StoreGrid will use this location as the Storage location for all the clients and its internal database. You can modify this storage location from the "Server Settings" UI page. But note that modifying the "server settings" page will not change the existing clients' backup storage location nor it will change the StoreGrid internal database storage location. Client Based Storage Location In StoreGrid, each client under a group can be configured with a different backup location. By default all clients will use the same location as the Global Backup Data Storage Location. If a client is created manually, then you can provide a different backup location for the client. But you will never have to create a client manually in StoreGrid. Clients are created under a group automatically when the client backs up first time. So the clients will automatically use the Storage location configured globally for the Server. You can edit the backup location of the client using Edit Client Configuration. After update of the backup location the new backup schedules will backup to the newer location and the existing backup schedules will continue to backup to the older backup location. StoreGrid Database Location StoreGrid uses an embedded database which creates *.db files. By default the *.db files will be created under the Global Storage Location configured during installation. But if you change the Global Storage Location from the "Server Settings" UI Page after StoreGrid starts, then the database location will not be changed. It will still use the old location. The reason is that StoreGrid embedded database cannot move its *.db files to a new location when StoreGrid is running. If you want to change the database location to a new location, then you need to follow the below steps: 1. Stop the StoreGrid server. 2. Open the file SGConfiguration.conf. 3. Edit the attribute Path to have the new storage location (Path = <New Storage Location>) 4. Copy all the *.db, *.db.bak, *.db-journal files from the old location to the new location. 5. Restart StoreGrid.

52 Server Settings How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Server Management->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 and availability for each partition. The table on the left (titled: Server Settings) gives the various options for server settings, some of which are configurable: Server Settings Server Name - Non-editable field displaying the StoreGrid peer name. Backup Location - This is the directory into which all the client backups are stored. Note that if we change this location, 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. You can edit this directory location either manually or by selecting the backup location from the directory tree by clicking the button provided at the end of the text box. 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). CPU Utilization Settings - 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. Replication Status - This is used to know whether Replication is enabled for the BackupServer. Replication Server - If Replication is enabled, this field displays the Replication Server Name. You can choose the replication server from the "Server Admin->Replication Management->Configure Replication" page. You can learn more about how StoreGrid server replication works from the section Replication of StoreGrid server. Replication Password (Applicable only to Replication server) - This is the password that backup servers need to authenticate against before replicating to this replication server. Bandwidth Throttling (Applicable only to Backup server) - StoreGrid's Bandwidth Throttling feature enables the user to limit the bandwidth usage for a backup schedule. Bandwidth can be configured at the backup server level, group and client levels. The user needs to specify the following fields: Enable bandwidth throttling: Choose to enable or disable bandwidth throttling. If enabled, there are again two options: o Throttle bandwidth always: Choose to enable bandwidth throttling every time the transfer of data takes place. o Throttle bandwidth from: Specify the time period when bandwidth throttling is enabled. Throttle each backup to maximum of: Rate to limit bandwidth usage. Save Button - Once all the above options are set, click the "Save" button to save the server settings.

53 Note that the backup location, backup space etc. can be individually configured for each of the StoreGrid clients from the Client Backup Configuration page. Server Disk Space Utilization This displays the disk space details of the machine. 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. Backup Location Details In StoreGrid, multiple backup locations can be configured to store the backup data. This page gives information about these different backup locations on the backup server. Backup Location - Location on the backup server where the backup data is stored. Used Space - Total space occupied by the backup data in the given location. Number of Backups - Total number of backups in the given location.

54 Authentication of Backup Server with Replication Server Overview You can prevent unauthorized backup server from replicating to your replication server by protecting the replication server with a password. Once a password is set in the replication server, backup servers will not be able to replicate to the replication server unless the backup servers authenticate themselves by providing the password. How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Admin -> Server Management -> Authenticate Backup Server for Replication" page. Authenticate Backup Server Backup Server Authentication is an optional security feature. By default, a Backup Server can replicate to and restore from a Replication Server. However, if a password is set in the Replication Server, then the backup server should first authenticate with the replication server with that password before it can start replicating its backup data to the replication server You can configure the password in the Replication Server from the "Server Admin -> Server Settings" page. The Backup Server can then authenticate with the Replication Server through the "Server Admin -> Server Management -> Authenticate Backup Server for Replication" page with the same password which was configured in the Replication Server

55 Disk Space Management How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> Server Management -> Disk Space Management" This page lists the groups, clients and their backups in a tree format. It also shows the allotted and used disk space and MSPEUs for the server, groups and clients. Clicking on the Groups root node in the tree will display the List of Groups. Clicking on a Group node in the tree will display the List of Clients under the group. Clicking on a Client node in the tree will display the List of Backup Schedules under the client. Clicking on a Backup Schedule node in the tree will display the Server Side Backup Reports (Backup Report, Restore Report, Deleted and Replication Reports) for the backup schedule. The table for the list of groups/clients is described below: Group/Client Name - This is the name of the group/client provided when the group/client was added to the server. Allotted Space - The disk space allotted in the backup server. Used Space - The disk space currently being used. Actions - Click on the Edit link against the Server, Group or Client to change the disk space allotted for them.

56 Retention Schedule Configuration Overview StoreGrid cleans up the version files as per the retention policy configured for the backup in the client machine. These policies can be configured such that the StoreGrid replication server cleans up the version files either immediately or on a daily, weekly or monthly basis. How to get here in the StoreGrid Web Console? In the top menu, select "Server Admin -> Server Management -> Retention Schedule Configuration(Icon)" Retention Schedule Configuration The description of the table columns are given below. Clean up immediately after completion of each replication schedule: Choose this option to schedule the configured retention policy immediately after the completion of each replication schedule. Run Daily: Select a time of the day when the retention policy should run daily. This will schedule retention everyday at the configured time. Run Weekly: Select a time and day of the week when the retention policy should run. StoreGrid will schedule the retention every week on the chosen day and time. Multiple days of the week can also be selected. Run Monthly: Select the time and particular day of a month when the retention policy should run. This will schedule retention every month on the configured day and time. Note: Apart from the configurations in this page, retention policy can also be manually scheduled from "Server Admin -> Group Management -> [Group Name] -> [Client Name] -> Run Retention Cleanup (Action for particular Backup)" page.

57 Server Side Filtering How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Server Management->" and click on 'Server Filters' on the left hand side. Please note that the "Configure Filtering" link is activated only after you've enabled your basic configuration. By default when Configuration is enabled, reports are sent for all "conditions" that are applicable to the "modules" (backup/restore/delete/replication) selected. The Filtering feature allows you specify specific conditions for which reports need to be ed for the modules selected in " Configuration". Server Side Filter Settings: There are two filters that can be applied here. With the first, reports will be ed to specified recipients for each selected module (backup/restore/delete/replication) depending on the conditions selected, as listed below. 1. When Backup/Restore/Delete/Replication completes successfully. 2. When Backup/Restore/Delete fails. 3. When there are no new or modified files for Replication. 4. When Backup is manually suspended. 5. When Backup/Restore is partially completed. The second filter allows you to Backup, Restore, Delete & Replication Reports only for specific Backup Schedules, Clients or Groups. By default reports are sent for all Backups Schedules, Clients & Groups. Manually selecting some backup schedules / clients / groups and "Disabling Reports" for them will prevent reports associated with those from being ed.

58 Client Information Report Overview This report provides details of the clients backing up to the backup server. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> Server Management -> Client Information Report (Icon)" Client Information Report The Client Information Report has the following details: OS Type - Type of operating system running in the client machine [ Windows/ Linux/ FreeBSD/ Mac ] Client Name - Name of the client. Group Name - Name of the group to which the client belongs to. Version - Version of StoreGrid running in the client machine. Build No. - The build number of StoreGrid running in the client machine. Allotted Space - Total space allotted to the client in the backup server. Used Space - Total space used by the client. License Type - License type of the client [Desktop/Server OS license] with plugin details Plugin Type - Plugin details - if used by the client [Basic/Advanced plugin] Limitations 1. This report will contain the details of a client only when the client is running or a higher version. 2. If a client is added in the backup server manually or by using Local to Remote Server Migration feature, then only the client name, group name, version, license type and plugin type details will be available in the report. Other details will be available only when the client connects to the backup server and authenticates. 3. In the replication server, the client information is available only after the client s backed up data is replicated to the replication server.

59 Adding a Software Update in the backup server Overview StoreGrid supports Automatic Software Update from v2.3. When client updates are added in the backup server, the clients automatically can download the update from the backup server and upgrade themselves. Software updates can be added in the backup server through this page. Client machines check the backup server for available updates every one hour (when the client is not backing up/when there is no client activity). If an update is available in the backup server, the client will automatically download and install it. Note: Software update is available only for clients running StoreGrid v2.3 or higher. If a client is running a version older than v2.3, then it should upgraded manually to v2.3 and upgrade to the later versions can then be done through the software update feature. How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Admin -> Server Management -> Add Builds for Automatic Software Updates" page. Adding a Software Update in the backup server Add new build/patch to the backup server: With every new patch/build released, installation and configuration files will be provided in exe/bin & xml file format respectively. These files should be copied to the client update location in the backup server. The configuration file [.xml] will have the version and build details of the new build/patch. Once the build and configuration files are copied to a location in the backup server, select the location where the update is stored and then click on 'List Build File(s)' button. This will list the updates available. You can then select the ones you want to expose to the clients and click 'Add Build Files' button. Troubleshooting Tips No build file(s) available in the entered location.. Solution 1: Check if the Update files and their corresponding configuration files exist in the entered/selected build files location. The update's StoreGrid_<NewVersion>.exe file and StoreGrid_<NewVersion>.xml files should be present in the same location.

60 Solution 2:Check if the update files in the specified folder are already added in the backup server. Limitations 1. The automatic software update feature in the client machine checks for new updates available in the configured update server [backup server] every 1 hour and this schedule is not configurable. 2. The automatic software update will download and update the latest build only if there is no backup/restore/delete activity at the client side. 3. If there exists any application for intrusion detection [such as Zone Alarm], StoreGrid application may not start automatically after auto upgrading to the latest version. You need to manually start StoreGrid application.

61 Alert Settings Overview StoreGrid can be configured to send out alerts for the following conditions 1. Server, group or a client is running out of backup space in the backup server 2. Backup Server s license has expired or is about to expire How to configure alerts by using the StoreGrid Web Console? On the top menu, select: Server Admin > Server Management > Alert Settings Server /Group/ Client "Used Space Alert" StoreGrid can be configured to send alerts when the disk space available for storing the backup data in the backup server is low. These alerts will be sent when there is a space shortage at the server, group or at the client level. Additionally, you can configure it to send alerts when the backup space used up is nearing a certain percentage of the total space configured for the server, groups and clients. The alert s will be sent once every day till more space is allocated for the server, group or the client. Backup Server License Alert alerts can be configured to be sent when a backup server license expires or when its expiry date is nearing (optional). The alert s will be sent once every day till the backup server license is renewed. Replication Server License Alert (Applicable only for replication server) StoreGrid can send alerts when the replication server license expires or its expiry date is nearing (optional). The alert s will be sent once every day till the replication server license is renewed. This alert is generated by the replication server and sent to the id(s) configured as recipients. Alert s are sent as the license expires. The user can also choose to get an alert if the license is approaching its expiration period. The default number of days to alert for server license is 7 days prior to the expiry date. Limitations 1. If StoreGrid is stopped before the trial period expiry date of a client and restarted again after the expiry date, then two alerts (one alert that expiry date is nearing and the other that the trial period has expired) will be sent. 2. s are sent once every 24 hours and not immediately when the alert condition occurs.

62 Delete Replication Server Data How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Admin -> Server Management -> Delete Replication Server Data" page. Delete Data of Primary Server This feature can be used to delete unwanted data in the replication server. You can choose to delete all the replication data from a particular backup server or delete the replication data of specific groups or specific clients. This page shows a 'tree' listing of backup servers, groups and clients whose data is present in the Replication Server. Select the backup servers/groups/clients that need to be deleted. Limitations 1. Replication data for backup server/group/client cannot be deleted if restore, replication or data deletion is in progress for them in the replication server. 2. You cannot delete just a backup schedule under a client.

63 Replication Server Data Deletion Report How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Admin -> Server Management -> Replication Server Data Deletion Report" page. Replication Server Data Deletion Report The report shows the list of backup servers, groups and clients whose data was deleted from the Replication Server. Server Name - Backup Server of the deleted replication data. Deleted Group/Client Name - Name of the group or the client whose data was deleted. Total Clients - Total number of clients for whom deletion was attempted. Deleted Clients - Clients whose data was successfully deleted from the replication server. Failed Clients - Clients whose data could not be deleted from the replication server. Time taken - Total time taken to delete the data.

64 Group Management in StoreGrid Server How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin-> Group Management" This UI page is where group administration/management is done in the StoreGrid server. In the Group Management page, the list of groups and default group are listed in a tree format in the left hand side and in a table format in the right hand side. The group tree will have list of clients under each group node and the list of backup schedules configured under each client node. Clicking on the Groups root node in the tree will display the List Of Groups in a table format on the right hand side. Clicking on a Group node in the tree will display the List Of Clients under the group in a table format on the right hand side. Clicking on a Client node in the tree will display the List Of Backup Schedules under the client in a table format on the right hand side. Clicking on a Backup Schedule node in the tree will display the different Server Side Backup Reports (Backup Report, Restore Report and Deleted Reports) for the backup schedule. The table columns and the actions for the list of groups table on the right hand side is described below: Group Name - This is the name of the group you provided when the group was added to the server. Allotted Space - This is the total space allotted to the group. Used Space - The total disk space currently used by the group. Actions - The icons under this column are links to various features to enable you to administer and manage your groups. Allow / Deny Auto Authorization - Clicking on this icon will toggle between enabling and disabling automatic authorization for this group. The automatic authorization feature is described in more detail in the Create A Group section. Activate/Deactivate - Clicking on this icon will toggle between activating and deactivating a group. If a group is deactivated then no client from the group can backup to the server. Edit Group - Clicking on this icon will take you to the Edit Group page. You can edit all configurations of a group from this page. Add New Clients - Clicking on this icon will take you to the Add New Client page. You can add a client to the group and configure it. Proceed to Delete Group - Clicking on this icon will take you to the Delete Group Page. Edit Replication - Clicking on this icon will take you to configure Group Replication Scheduling. Note that you can configure different scheduling options and replication servers for different groups. By default all groups will be replicated to the globally configured, replication configuration from the Replication Management UI page. Deleted Client/Backup Report - Clicking on this icon will take you to the "Deleted Backup Report", which will list in a table format the list of backup clients and the data that has been deleted by the server administrator.

65 Some of the features like Creating a new Group, Local To Remote Server Migration, etc on the left bottom are described below. Add New Group - Clicking on this icon will take you to the 'Add New Group' UI page. You can add a new group in the StoreGrid Server from this page. Client Migration - Clicking on this icon will take you to the 'Client Migration' page. Using this feature you can migrate the trial clients to the paid Group and also the clients from one Group to another Group. configuration for Consolidated Group Report - Clicking on this icon will take you to the ' Configuration for Consolidated Group Report' page. Using this feature addresses to which the Consolidated Reports is sent for the different group can be specified. Local To Remote Server Migration - Clicking on this icon will take you to the 'Local To Remote Server Migration' page. Using this feature you can migrate the backup data from one server to another server and then having the clients do the subsequent backups (incremental) to the new server.

66 Add a New Group How to get here in the StoreGrid Web Console? side. In the top menu, select: "Server Admin->Group Management" and click on the "Add New Group" Icon on the left hand While you have the option of retaining all your clients under the 'Default Group', you may find it more manageable to segregate your groups. Note that a group can have multiple PCs/servers (clients) which need to be backed up. You need to add the group to the server first before adding the clients under the group. Clients can easily be shifted from one group to another. You need to provide the following information while adding a new group: Set Group Information - At the bare minimum, you need to give the group a name. Other group information like , Postal Address, Phone etc is primarily to help you keep 'organized' records. Set Basic Configuration - Here's where you configure some basic server settings specific to the group: authentication requirements, default starting state, etc. You can configure the following settings for the group: Allow / Deny Auto Authorization : If you want the clients in this group site to backup without your adding the client names (StoreGrid IDs) manually in the server, then keep the Auto Authorization enabled for this group (RECOMMENDED OPTION). The Clients will be automatically created in the server when the clients backup to this server for the first time. Please note that only StoreGrid clients tagged with the group name ABC Inc. (entered during installation) will be allowed to backup to this server under the group ABC Inc. Clients without a valid group name would come under the Default Group. Default Status when starting: Activate /Deactivate : Only active groups' clients are allowed to backup to the server. By default all groups start off 'Activated'. If you prefer to start this group in a deactivated state, you can do so. Of course, you can prevent a group (and hence all the clients under the group) from backing up to the server by simply deactivating the group at any time. Consolidated Report : You can choose to send a Consolidated Group Report of all clients under this group. Specify the ID of the recipient(s) and the frequency of generation of the consolidated group report (Daily/Weekly/Monthly) Space Utilization Snapshot : Total Backup Space On Server - The total disk space configured in the Server for the backup data. Total Backup Space Allotted to Groups - The sum of the disk space allotted to the different groups in the Server. Free Backup Space available in server - The free space available in the server that is not allocated to any group. It is difference between total backup space in the server and the total backup space allotted to group. Backup Location - The backup data of all the clients under this group is stored in this location. Allotted Space - The disk space allotted for the backups from the clients under this group. The link Edit Disk Space Allotted for Server/Group/Client takes the user to Server Admin -> Disk Space Management.. This lists the groups, their clients and their backup schedules with their Space details. The space settings can be edited here.

67 Bandwidth Throttling : StoreGrid's Bandwidth Throttling feature enables the user to limit the bandwidth usage for a backup schedule. Bandwidth can be configured at the backup server level, group and client levels. Use server's global configuration - Select server's bandwidth throttling configurations by choosing the option Yes or select No to manually configure bandwidth for this group. To manually configure bandwidth, enter the fields listed below: o o o o Enable bandwidth throttling for this group - Choose to enable or disable bandwidth throttling. Throttle bandwidth always - Choose this option to enable bandwidth throttling throughout the day. Throttle bandwidth from - Choose this option to enable bandwidth throttling only during the specified hours of the day. Throttle each backup to maximum of - The rate to which bandwidth should be throttled.

68 Client Migration How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Client Migration" icon on the left hand side. Clients listed under one group in the backup server can be migrated to another group through the Client Migration feature. The steps to follow for the moving of data from one group to another are given below: Step 1: Select the group name (from which the clients are to be migrated) from the select box on the left hand side.(i.e Migrate from). Step 2: All the Clients under the group(selected in the previous step) will be listed. Note that by default all the clients' will be checked. (i.e all the clients under this group will be migrated). You can also select particularly the clients you wish to migrate. Check the clients, you wish to migrate. Step 3: Select the group name to which the clients to be migrated from the check box on the right hand side.(i.e Migrate to) Incase if you wish to migrate to a new group, first add the group by clicking on "Server Admin->Group Management->Add New Group" icon. Then proceed with the above steps. Step 4: Press the migrate button to finish the migration. Once you press the migrate button the migration operation should finish in a few seconds. Note if any of the clients' are active, (i.e Backup, Restore, Delete, Replication is in progress) that particular client will not be migrated.

69 Local to Remote Server Migration Overview Local to Remote Server Migration is a useful feature to quickly move large backup data from the client machine to the backup server. Using this feature, the initial seed backup can be taken in a local external drive connected to the client machine and the external drive can then be physically moved to the remote backup server s environment to migrate the data into the backup server. After the data migration and after performing the server side and client side Local to Remote server migration steps, the incremental backups can run directly from the client to the remote backup Server. How to get here in the StoreGrid Web Console? For Server: In the top menu, select: "Server Admin->Group Management" and click on the "Local To Remote Server Migration" icon on the left hand side. For Client: In the top menu, select: "Administration->Advanced Options" and click on the "Local To Remote Server Migration" icon in the left hand side. Local to Remote Server Migration 1. Configure a backup schedule in the StoreGrid client system. Log into client s StoreGrid web console page and select Backup -> Add Backup Schedule' from the top menu. Add Backup Schedule link will take you to Create a new Backup Schedule page. 2. Select the Backup Type as Same Machine in Step 3 and enter the external drive location for the Local Backup Location. After entering all the other backup details, save the backup schedule.

70 Note : Same Machine' backup feature is available only from 2.3 release. It can be used only for 'Local to Remote Server Migration'; you cannot restore from the Same Machine backup. 3. Run the backup, check the progress and make sure the backup runs to completion. 4. When the backup is complete, suspend the backup schedule. 5. Disconnect the external drive from the client machine and connect the external device to the remote backup server.

71 6. Copy the client's data (Z:\backup\1) from the external device to some temporary location in the drive where you are planning to store the backup data in the remote backup server. Like for example, if you storage device is the E: drive, then copy the data to say E:\LTOR. You don t have to copy the data to the temporary location and you can migrate the data directly from the external drive itself. However, the migration might take a little longer to complete, based on the speed of the external drive. 7. Go to the remote backup server s web console "Server Admin-> Group Management -> Local to Remote Server Migration (Icon)" page. Enter the location of the client's data followed by the 1/ directory. For example, if you have copied the client's data from the external drive to the temporary E:\LTOR location in the backup server, enter location as E:/LTOR/1/ in this page. If you have not copied the data to a temporary location, enter the location of the external drive, like for example Z:/backup/1. After entering the path, click on the "Submit Location" button. 8. The client name will be displayed. Select the client. If you are doing the data migration from this client for the first time, enter the target group under which the client is to be migrated and the location where the backup data is to be stored. Click the "Migrate" button.

72 9. In the client system, take a backup of the <StoreGrid Installation Location>/data/<backup name>/sgprp.db file. This is just to ensure you can recover this DB file if you need to do the client side migration again, if required. 10. Go to Administration -> Advanced Options -> Local to Remote Server Migration (Icon) page in the client machine. Enter the remote backup server name for the new backup server name. Choose the option No, backup only to new server. In table listing the backup schedules, select the backup schedule(s) whose data has been moved to the new backup server. You can select all the backup schedules by checking the checkbox against the "Available Backups" column name. Confirm that the backup data of the selected schedules has already been moved to the new server and that you have run the server side local-to-remote-server migration module in the remote backup server (confirm from the check box).click the Migrate button to complete the migration. 11. To confirm that the migration has been successful, try running an incremental backup. If the incremental backup runs fine, the migration is successful and you can delete the backup of the db file that you created in step 9 above.

73 If the client starts taking a full backup, then suspend the backup, replace the sgprp.db file with its backup that you created in step 9 and check the server migration steps again. Troubleshooting Tips No Clients for migration. Cause 1: Backups are not present in the location "<LocalServerDataLocation>/<Client_Name>/" where 'LocalServerDataLocation' is the location entered in the remote backup server web console "Server Admin -> Group Management -> Local to Remote Server Migration(Icon)" page. 'Client_Name' is the client name of the backups which is to be migrated. Solution : Delete the client data from the remote server 'LocalServerDataLocation' and recopy the data from the USB device. Cause 2 : Client's data are not copied from a StoreGrid or later version of backup server. Solution : Server side "Local to Remote Server Migration" can be done only with StoreGrid or later version of backup server clients alone. Unable to list the Directory. Permission denied. Cause : StoreGrid does not have the read permission for the location entered in the remote backup server web console "Server Admin -> Group Management -> Local to Remote Server Migration(Icon)" page. Solution : Move the data to a location where StoreGrid can access the data without any permission problem or change the permission for that directory so that StoreGrid can read the data. Migration failed. Please check local Server Data Location for the read access and the target location for Read/Write access. Cause 1: StoreGrid does not have the read permission for the location entered in the remote backup server web console "Server Admin -> Group Management -> Local to Remote Server Migration(Icon)" page. Solution : Move the data to a location where StoreGrid can access the data without any permission problem or change the permission for that directory so that StoreGrid can read the data. Cause 2 : StoreGrid does not have the read and write permissions for the client location entered in the list of clients migration page that comes after clicking the "Submit Location" button in server side "Local to Remote Server Migration" page. Solution : Provide enough permission for the location you have given for the client or choose any other location where StoreGrid has the read and write permissions. Limitations 1. When StoreGrid is stopped during Server side "Local To Remote Migration", it cannot be resumed later from where it has been left. It has to be run afresh again. 2. Server side "Local To Remote Migration" report cannot be seen once you leave the web console page. 3. When there isn t enough Space in the remote backup server, migration will still proceed to completion by automatically taking the necessary space. 4. File version migration is not supported. Only full backups and incremental backups can be migrated.

74 Server Side Local to Remote Server Migration Progress Summary of progress This gives the total summary of the Migration progress. Success Rate : This gives the total success rate. Elapsed Time : This gives the total time taken after the migration started. No of clients migrated : This gives the total number of clients migrated out of the total clients for migration. Messages : Messages regarding the Migration. Warning : Warnings regarding the migration progress. Overall migration progress. Clients scheduled for migration This lists the client lists for migration, their total number of backups for migration, their total migrated backups, their target group and their migration status. Details of current migration activity This gives the information about the migration of the currently migrating client and its current backup, time taken after the current client migration started and its migration progress.

75 Replication Server Migration Overview Replication Server Migration is a feature to avoid bandwidth usage and reduce the replication time needed for a full backup over Internet. Using this feature, you can transfer the backup data from the backup server into a local external drive and then physically move the drive to the Replication Server environment to migrate the data into the replication server. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Replication Server Migration" icon on the left hand side. Instructions for Replication Server Migration 1. Make sure the backup data that you want to migrate to the replication server is complete and the client machines are not backing up. To make sure the client machines (whose backup data you are trying migrate) don t during the migration, deactivate the clients in the backup server. Please note: If a full backup already exists in the Replication Server then you cannot migrate just the incremental backup data of this full backup. Also, additional full backups along with its incremental backups cannot be migrated. Only additional full backup data without incremental backups can be migrated. Therefore as soon as the additional full backup is complete, deactivate the backup schedule in the backup server. This is to ensure that there are no further incremental backup is run from the client. Then start the replication migration process for that additional full backup. 2. Disable replication in the Backup Server from the Server Admin > Replication Management > Configure Replication page. 3. Connect an external device to the local backup server.

76 4. Copy the clients data (<Server_Location>/1 directory) to it. For example, if the backups are stored in a location "C:\LocalStorage", copy the "C:\LocalStorage\1" folder to the external device. 5. After copying the client data on an external drive, you can activate the clients in the backup server by going to Server Admin-> Customer Management page; so that backups from the clients can resume. 6. Next connect the external drive to the remote Replication Server. 7. Copy the data from the external drive to some location in the remote Replication Server, say C:\MigrateData\1. You can leave it in the external drive itself and migrate directly from the external drive but the migration might take a little longer. 8. In the top menu in the remote replication server StoreGrid web console, go to Server Admin->Group Management and click on the Replication Server Migration icon on the left hand side.

77 9. Enter the location of the 1/ folder (for e.g.: C:\MigrateData\1) and click the Submit Location button. 10. The list of clients along with their backup server name is shown.

78 11. Choose the clients which are to be migrated and select their respective groups. If a client is already replicating under a particular group, then the Migrate to Group and the New Location fields will not be selectable for that client. 12. If the target group is not listed, choose Default Group as the target group and migrate the client to it. Once the replication runs from the backup server (after doing Replication Server Migration) to the replication server for the migrated clients, the group under which the client is listed in the backup server will be automatically created in the Replication Server and the client will be moved from Default Group to the particular group under which the client is backing up in the Backup Server. 13. After configuring all the necessary details, click the "Migrate" button. 14. The backup data (data in the 1/ folder) will be migrated to the remote replication server.

79 15. Enable replication status in the backup server by going to Server Admin > Replication Management > Configure Replication page in the backup server. 16. To make sure the data has been migrated successfully to the replication server, try scheduling a replication for one of the clients by clicking the Replicate Now icon in the Group Management > Group > Client > List of Backup Schedules page in the backup server s web console. It should not replicate anything or just replicate the additional backup data that came into the backup server since replication migration. Note: You cannot migrate two clients with the same StoreGrid ID existing in two different backup servers into one replication server. The migration of the second client will fail. Troubleshooting Tips No Clients for migration. Cause 1: Backups are not present in the location "<LocalServerDataLocation>/<Client_Name>/" where 'LocalServerDataLocation' is the location entered in the remote replication server web console "Server Admin -> Group Management -> Replication Server Migration(Icon)" page. 'Client_Name' is the client name of the backups which is to be

80 migrated. Solution : Delete the client data from the remote Replication Server 'LocalServerDataLocation' and recopy the data from the USB device. Cause 2 : Client's data are not copied from a backup server running StoreGrid 2.3 or later. Solution : Replication Server Migration can be done only with StoreGrid 2.3 (or later) backup data. Unable to list the Directory. Permission denied. Cause : StoreGrid does not have the read permission for the location entered in the remote replication server web console "Server Admin -> Group Management -> Replication Server Migration (Icon)" page. Solution : Provide enough permission for the location you have given for the client or choose any other location where StoreGrid has the read and write permissions. Limitations 1. If a full backup already exists in the Replication Server then the incremental backup data for this full backup cannot be migrated. 2. Similarly, additional full backups along with its incremental backups cannot be migrated. Only additional full backup data without incremental backups can be migrated. 3. You cannot migrate two clients with the same StoreGrid ID existing in two different backup servers into one replication server. The migration of the second client will fail. 4. If StoreGrid is stopped during the Server side "Replication Server Migration" progress, migration cannot continue from the place where it stopped. 5. No Replication Server migration report is available in remote Replication Server. 6. When there is not enough space in the remote replication server, migration will complete taking the necessary space. It does not throw an error or warning. 7. File version migration is not supported. 8. Backup data copied from one Replication Server cannot be migrated to another Replication Server.

81 Delete Group How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management". Click on the "Delete Group" icon in the action column of the Group row. If you click the option 'Delete group but retain clients and data under the group', only the group will be deleted and the clients and their data will be moved to 'Default group' in Backup Server. If you click the option 'Delete group, clients and data under the group', then the group and the clients and their backup data will be permanently deleted from the Backup Server. Default Groups cannot be deleted. Please note that if any one of the group's backup is active, then you cannot delete the group. When a group is not deleted, you can see the reason why the group could not be deleted in Server Server Side Deleted Backup Reports present in the group row. Cancel button will take you to the 'Server Admin -> Group Management' page.

82 Consolidated Group Report Overview The Consolidated Group Report is a cumulative report of all backups and restores that have run on the backup server for all the clients under the particular group for the last one day, one week or one month. The report will be sent to the group in an automatically on a daily, weekly or monthly basis. Click here for sample of the report The ' configuration for Consolidated Group Report' page lists all the groups and for each group the IDs to which the consolidated report should be sent and the schedule (daily, weekly or monthly) for sending the reports can be specified. The consolidated report can be manually generated and sent to the specified addresses by clicking on the 'Generate and Instant Report' link against the particular group. The Consolidated Group Report can also be enabled for a group while adding a new group in the 'Server Admin -> Group Management -> Add New Group' page or by editing a particular group by going to the 'Server Admin -> Group Management -> Edit Group Details (Action for the particular Group) page. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the " configuration for Consolidated Group Report " Icon on the left hand side. The Consolidated Group Report has the following sections: 1. Consolidated Group Statistics across all Clients 2. Consolidated Client Report 3. Individual Client Backup Reports 4. Individual Client Restore Reports Consolidated Group Statistics across all Clients The Consolidated Group statistics has the following details for a particular group. Server backed up to : The name of the backup server from which the report is generated. Number of full backups done : Total number of full backups done during the specified period. Number of restores done : Total number of restores performed during the specified period. % of files successfully backed up : Success percentage of backups from the particular group. Allotted Disk Space : Total space allotted to the group. Disk space used as on <Date> : Total disk space used as of the beginning of the specified time period. Average disk usage : Average (calculated on daily basis) of the disk space used over the specified time period. Number of clients connected during the period : Total number of clients connected to the group in the specified period. Number of incremental backups done: Total number of incremental backups done during the specified period. Group Status: A ctive/deactivated state of the Group. % of files successfully restored : Success percentage of restore from the particular group. Disk space used as on <Date> : Total disk space used as of the ending of specified time period. % of Disk Space Used: Percentage of the disk space used by the group. Consolidated Client Report

83 The consolidated client report has individual client reports with the details of their entire backup schedules. Client Name: Name of the client. Allotted disk space: Space allotted to this client under the group. Disk space used as on <Date> : Total disk space already used up to the specified date (beginning). Disk space used as on <Date> : Total disk space used up to the specified date (end). Average disk usage : Average of the disk space used over the selected period. % of Disk Space Used : Percentage of the space used out of the total space allotted to this client. Num of new backups configured during the period : Number of new backups configured during the reporting time. Num of full backups done : Total number of full backups done. Num of incremental backups done : Total number of incremental backups done. Last backup date : Date when the last backup was scheduled in the client. Client Status : Indicates the client status (active/deactivated). Individual Client Backup Reports The consolidated client report has individual client reports with the details of their entire backup schedules. Client Name: Name of the Client. Backup Name: Name of the backup. Last Backup: Last backup date for the particular backup schedule. Total Files: Total number of files in the backup schedule. Protected Files: Total number of files backed up to the backup server. Skipped Files: Files skipped during backup. Skipped Folders: Folders skipped during backup. Success Rate: Success percentage of the backups for the particular backup schedule. Individual Client Restore Reports Client Name: Name of the client. Backup Name: Name of the backup selected for restore. Last Restore: Last restore date for the particular backup schedule. Total Files: Total number of files in the backup schedule. Restored Files: Total number of files restored. Skipped Files: Files skipped during restore. Success Rate: Success percentage of the restore for the particular restore attempt. Limitations The reports of deleted clients will not be available in the Consolidated Group Reports If a client is migrated from one group to a new group, then the client's old reports will also be migrated to the new group. Average Disk Usage details will not be available for daily reports. Instant report can be generated for previous 6 months alone. The consolidated reports are generated on a daily/weekly/monthly basis at the following specified times: Report schedule Time Day

84 Daily report Weekly report Monthly report 11:57 PM All days of the week 11:57 PM Every Saturday of the week 11:57 PM Last day of the month

85 Replication Management Overview This where all aspects related to Replication Management are configured. From here, Replication can be scheduled, the Backup Server can be recovered (in case of a disaster). How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin-> Replication Management" Replication Management Configure Replication - Clicking on this icon will take you to the "Replication Configuration" page. You can configure and schedule replication of backup data from this page. Server Disaster Recovery - Clicking on this icon will take you to the "Server Disaster Recovery" page. You can recover the backup server from the Replication Server in case of any catastrophe affecting the backup server thereby necessitating a Disaster Recovery operation. Server Disaster Recovery Reports - This icon will only show up if the server was previously restored from the replication server. Clicking on this will take you to the "Server Disaster Recovery Reports" page where you can view reports for all backups that were recovered from the Replication Server.

86 Replication Configuration Overview StoreGrid supports replicating a backup server to a replication server. Replicating the backup data in the backup server is done to create redundant copies of the backup data. The replication configuration UI page is used to configure and schedule replication of backup data as per the user/administrator requirements. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Replication Management". Click on 'Configure Replication' tab. Replication Configuration Step 1 Enable Replication : By checking or un-checking the checkbox, you can enable or disable replication for the Backup Server. Replication Server : From the choice box, choose the replication server to which this backup server's data should be replicated. Step 2 Set CPU Utilization - This is used to specify how this server s CPU should be utilized by the StoreGrid process when the backup server replicates the backed up data to the Replication Server. Setting it to low will make the StoreGrid process do the replication slowly without taking much CPU so that it is least intrusive. But replication will take longer to complete if low CPU settings is chosen. Attempt to replicate the backed up data every 5 minutes in case of non completion because of a problem (Network error etc.) : If enabled, then the replication schedule, irrespective of the schedule time/interval, will be scheduled every 5 minutes whenever replication is incomplete because of a network error, server crash etc. Note that this option is enabled by default. Step 3 Replicate While Receiving a Backup: Choosing this option will schedule the replication as soon as the backup server starts receiving the backup data from the client. Note: 1. Changing the schedule type from any other option to 'Replicate While Receiving a Backup' will cause the immediate scheduling of all the backups. 2. Disabling and then enabling replication with 'Replicate While Receiving a Backup' will cause the immediate scheduling of all the backups. Replicate Immediately After Receiving a Backup: Choosing this option will schedule the replication after the client's backup schedule is completed. 1. Changing the schedule type from any other option to 'Replicate Immediately After Receiving a Backup' will cause the immediate scheduling of all the backups. 2. Disabling and then enabling replication with 'Replicate Immediately After Receiving a Backup' will cause the immediate scheduling of all the backups.

87 Replicate Every Few Hours: Choose the hours/minutes to schedule replication periodically. If StoreGrid is restarted in the interim, the replication will be scheduled as soon as StoreGrid starts. Thereafter, StoreGrid will automatically reschedule the next replication after the time period you ve set. For example, if the backup server receives a backup at 8 am and the backup completes at am, and if you have set replication to run every 1 hour, StoreGrid will first run the replication schedule at 8 am (i.e as soon as the backup server starts receiving the data for the first time) and the next replication will be scheduled at am. However, if at 8.30 am, StoreGrid is restarted, then the replication will be scheduled once at 8.30 am and the next replication will be scheduled 1 hr after the current replication schedule completes. Additionally, you can also select the days in which replication should run. For example, if you do not want replication to run on Saturdays and Sundays, uncheck the checkbox against these days. If the "Select all days" checkbox is checked, then all the schedules will be scheduled on all the days of the week. Note: Disabling and then enabling replication with 'Replicate Every Few Hours' will cause the immediate scheduling of all the backups. Replicate Daily: Choose the time at which the backup should run daily. All the backup schedules will be replicated everyday at the time you have provided. Replicate Weekly: Choose the time and the day of the week replication should be scheduled. All the schedules will be replicated every week on the particular day and time chosen. Troubleshooting Tips When Replication does not happen at the scheduled time. Cause 1: If Replication is not enabled. Solution : In the Replication Management UI page, check the enable replication check box and save the configuration. Cause 2 : If Replication Server Name is not displayed in the UI. Solution : Add the Replication Server Name from the 'Administration->Add/Delete Peer' UI page. Then select the Replication Server name in Replication Management and save the configuration. Cause 3 : If the Replication thread count is limited to 1 or a limited number of threads, and if there are more (than the thread count) number of backup schedules to be replicated at the same time, then the replication schedules will be put in a queue and scheduled for replication one after the other. Hence all the schedules will not be replicated simultaneously at the particular time provided. Solution : Open the SGConfiguration.conf file located in <StoreGrid Home/conf> directory. Edit the Replication Thread count tag to desired number. Note: By default Replication Thread count is -1, which will allow infinite number of backups to be replicated simultaneously. For fresh installation of StoreGrid (since version 2.2.1) Thread count will be 5 in Linux machines and -1 in Windows machines. Limitations The global Replication configuration in StoreGrid is applicable to all the group, the clients under a group and the backup schedules under the client. StoreGrid additionally supports configuring replication at the group level which is then applicable to the clients under the group. StoreGrid does not support separate replication configuration at

88 the client and the backup schedule level.

89 Server Disaster Recovery Overview This feature helps you recover the Backup Server and its data from the Replication Server. If your Backup Server had been replicating to a StoreGrid Replication Server, then, in case of any crash/disaster at your Backup Server, the StoreGrid Backup Server can be rebuilt from the Replication Server. You can either recover the backup data and the Groups/clients configurations OR you could recover only the Group configurations and copy the backup data separately from the Replication Server. After copying the backup data from the replication server, you would need to do a "Local To Remote Server Migration". How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> Replication Management -> Server Disaster Recovery (Icon)" Server Disaster Recovery To provide redundancy for the backup data, the StoreGrid backup server can be configured to replicate all its backup data to a replication server. If the backup server crashes, the backup server can be restored back by retrieving the replicated data from the replication server using the Server Disaster Recovery(SDR) feature. The following are the steps to reconstruct the backup server after a crash, through the Server Disaster Recovery feature: 1. Disable the network in the backup server so that the clients don't connect to the backup server during the disaster recovery 2. Install StoreGrid in the backup server with the same StoreGrid ID as before. 3. Apply the same backup server license key by going to Administration -> Apply License Key page. Copy and paste the license key details and register. 4. Go to the Server Admin -> Replication Management -> Server Disaster Recovery page. This opens the Server Disaster Recovery screen which has the following fields: a. Select replication server: Select the replication server name from the drop down list.

90 b. Select data to recover. i. Group & Client configurations and Client data: This recovers the Client and group configurations along with the clients' backup data. ii. Group & Client configurations Only: This recovers only the backup server configurations like group details, disk space allotted, MSPEUs added etc. The backup data is not recovered. This option is helpful when the amount of data is huge and restoring it from the replication server to the backup server over the internet or a WAN may be slow. Instead, the data (the entire 1/ folder in the storage location in the replication server) can be copied into an external drive and then shipped to the backup server location. The data from the external drive can then be attached to the backup server through the server side Local to Remote Server Migration. This is explained in steps 6, 7 and 8 in the Local to Remote Server Migration help document. c. Next specify if you are restoring the data afresh to the backup server or just continuing from the previous interruption of the recovery process. d. Parallel Threads: Number of simultaneous backups that should be recovered from the replication server. By default, it is set to 5.

91 5. Click on the Recover data from the replication server to start the recovery process. 6. If the first option recover Group & Client configurations and Client data was selected, then the progress chart will be as shown below: After completion of recovery process, a Server Disaster Recovery Reports tab appears in the Server Admin -> Replication Management page. Clicking the tab gives the details of the data recovered from the Replication server. If the second option Group and Client configurations only was selected in step 4b above, then only the backup server details are recovered.

92 Once the group & client configurations are recovered from the replication server, you can manually ship the backup data from the Replication Server to the Backup Server and then do Local to Remote Server Migration in the backup server. Once the Backup Server is successfully recovered, you can enable the network in the backup server and resume the backups from the clients. 7. Enable replication in the restored backup server by going through Server Admin -> Replication Management page in the backup server web console. Troubleshooting Tips Could not find any configurations to restore in the Replication Server. Cause : This error would occur if there were no replicated backups available on the Replication Server (for the Backup Server). Solution : Please try recovering data from the replication server where the backup server was previously replicating. Problem in performing Server Disaster Recovery with error :: Replication Server's StoreGrid license has expired. Number of StoreGrid Installations exceeded 5. Replication Server connections disabled! Cause : This error occur if the Replication Server's license has expired/count exceeded. Solution : Please apply a valid license key to the Replication Server and thereafter try recovering data from the Replication Server.

93 Server Disaster Recovery Reports Overview This report provides information about the number of group, clients, backups and files recovered from the replication server. This report will be available only if the backup server was previously restored from its replication server. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> Replication Management -> Server Disaster Recovery Reports (Icon)" (icon will be visible only if a server recovery was previously done) Server Disaster Recovery Reports This report primarily displays the total number of files to be recovered (from the replication server), the number of files retrieved, and the number of files skipped (if any). 'Data' represents the actual backed up files and 'Meta-Data' represents the configuration files. Success Rate : Measure of the restore operation's success, this is based on the number of total files in the replication server and the number of files actually retrieved from the replication server. No of backups retrieved : This denotes the number of backups that were retrieved from the replication server. No of clients retrieved : This denotes the number of clients that were retrieved from the replication server. Start Time : This denotes the time at which the server disaster recovery started. End Time : This denotes the time at which the server disaster recovery completed. Time Taken : This indicates the actual time taken for the server disaster recovery operation. Data Transferred : This denotes the actual number of bytes transferred from the replication server after server disaster recovery. Troubleshooting Tips SG0136/SG0147 (OR) SG0134/SG0145: Unable to connect to the backup server. Cause : This error occurs if the backup server is not able to connect to the replication server. Solution : Check if the replication server name is available for lookup and also check if StoreGrid is running in the replication server and then try restoring the data from the replication server.

94 View List of Backup Clients How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "GroupName" link in the left hand side tree. This page lists the StoreGrid clients under the selected group that are backing up on to this server and provides the following information about each client. Client Name - This is the StoreGrid ID of the client backing up to the server. Clicking on the link here will open the list of backup schedules page. Allotted Space - The disk space allotted for this client in the server. Used Space - The disk space used by the backup data from this client. Number of backups - Number of times the client has backed up to the server. Actions - The icons under this column are links to various features to enable you to administer and manage the backup clients. Allow/Deny Automatic Authorization - If a client is set to 'Allow Auto Authorization', then the client can backup to the backup server without having to authenticate with the backup server. If the client is set to 'Deny Auto Authorization', then the client has to be first added in the backup server and then the client should authenticate itself with the backup server before it can start backing up to the backup server. Activate/Deactivate Client - This Activate/Deactivate action can help the Backup Server administrator to decide whether to accept/reject the individual client's backing up to the server. If a client is Deactivated on the Backup Server, further backup schedules from the StoreGrid client is rejected by the backup server. StoreGrid Backup Server Administrator can Activate the client again by clicking the same action. Edit Configuration - Clicking on this icon will take you to the "Edit Client Configuration" page, where you can specify specific configuration options (backup location, disk space, client password etc.) for this client in the server. Reset Password - Clicking on this icon will reset the password for this client in this server. Once the password is reset, the client, if it uses the old password, will not be allowed to backup. If auto-authorization is enabled, the client can in turn reset the password in the client and continue backing up to the server. Delete Client - Clicking on this icon will take you to the Delete Client page from where you can delete the clients and all its backup data. Deleted Report - Clicking on this icon will take you to the "Deleted Backup Report", which will list in a table format the list of backup schedules and data that has been deleted by the server administrator.

95 Add New Client for a Group (in the StoreGrid Server) How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Add Client" icon (in the action columns) in the row corresponding to the group. From this page you can add a new client under a group and configure the backup space, backup location and an optional password for the client (backing up to this server). If you have enabled Auto Authorization for this group, then you don t really need to add clients manually. Your group can add clients and StoreGrid automatically adds clients to the server whenever the clients backup to the server. However, if you have disabled Auto Authorization for this group or if you d prefer to set disk space & password individually for each client of your group(s), you can add the client from this page. Server Name - A non-editable field displaying the name of this StoreGrid server. Group Name - A non-editable field displaying the name of the group. Client name - You should input the StoreGrid ID of the client that will backup to the server. Note that this StoreGrid ID should exactly match the ID the client will use to identify itself. So make sure, the client uses the correct StoreGrid ID when he/she installs the StoreGrid client. Backup Location - This field is used to set the backup location where the selected client's backup data needs to be stored. You can edit this directory location either manually or by selecting the backup location from the directory tree by clicking the button provided at the end of the text box. Space Allotted - This field is used to set the backup space allotted for this client. The space allotted can be given either in GB or MB or TB by clicking the appropriate button. By default, the total backup space configured to the Group will be used on a first come, first served basis with any new client backing up to this server. Password - If you are manually adding the client to the server, and Auto Authorization is disabled for this group, then you need to provide a password for authorizing the client with this server. The client should be given the StoreGrid ID and the password and the StoreGrid client should authorize itself once with this password (the one you set here) before the client is allowed to backup to the server. Bandwidth Throttling - StoreGrid's Bandwidth Throttling feature enables the user to limit the bandwidth usage for a backup schedule. Bandwidth can be configured at the backup server level, group and client levels. Use group's configuration/use server's global configuration - If the option Yes is selected, then the bandwidth throttling for the client will be set as per the setting of the group or if there is no specific setting for the group, then as per the backup server setting. If the option No is selected, then you can setup bandwidth throttling specific to this client by entering the following details: o o o o Enable bandwidth throttling for this client - Choose to enable or disable bandwidth throttling. Throttle bandwidth always - Choose this option to enable bandwidth throttling throughout the day. Throttle bandwidth from - Choose this option to enable bandwidth throttling only during the specified hours of the day. Throttle each backup to maximum of - The rate to which bandwidth should be throttled.

96 Edit Client Backup Configuration How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on a group name. This will list you the list of clients under that group. Now click on the "Edit Configuration" icon in the action column of the client row. 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) shows information about the the disk space in each disk partition in the server. 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. Group Name - A non-editable field displaying the name of Group under which this client belongs. Client Name - A non-editable field displaying the StoreGrid ID of this Client Backup Location - This is the location where backups from the client will be stored. If the client has already backed up to the server and if the backup location is changed, then there is an option to move the existing backups to the new location. If the user opts for Move backup data and update the databases option, then all the existing backup data will be moved to the new backup location. Data from all backup schedules from the client will hereafter be stored in new backup location. If the user opts for I have manually moved the backup data to the new location. Just update the databases option, then only the database entries are updated for the already moved backup schedules. If the data is moved manually only for some backup schedules, then the database in the new location is updated only for these selected backup schedules. Backup data of a client resides under the folder [Old Backup Location/1/Client Name/] Steps to manually move the backup data and update databases: 1. To move ALL the existing backup schedules to a new location: i. Create a folder with a name 1 in the new location. ii. Under this folder, move the <Client Name> folder from Old Backup Location/1/ location to the new 1 folder. 2. To move a particular backup schedule: i. Create a folder named 1 in the new location. ii. Under this folder, create a sub-folder with exactly the same client name as in the Old Backup Location/1/<Client Name> folder. Please note that folder names are case sensitive. iii. In this sub-folder, copy the Backup Name folder (backup data) and the sgclient.txt file available under Old Backup Location/1/<Client Name>/ folder.

97 If the user opts for Leave the backup data in the old location option, then data from new backup schedules in the client will be stored in the new location. The existing backup data will remain in the old location and data from the existing backup schedules (full or incremental) will continue to be stored in the old location Space Allotted - This field can be edited to modify the backup space allotted for this client. The space allotted can be given either in MB, GB or TB. By default, the total backup space configured for backups in this Group 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. Password - If you do not want to change the password, leave this field blank. If you change the password, then you need to send the new password to the user of this StoreGrid client and she in turn should change the password in the client and authorize the client once with the server. 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 allotted for the client, the server will not allow the client to backup thereafter. The client s backups will be aborted and StoreGrid will generate an event indicating the space issue. Backup can proceed only after the client is allotted more space on the server. If backup/restore/replication/delete is active for a client, StoreGrid gives the following error message: Backup, restore, replication or deletion is in progress for the client whose data you are trying to move. Please make sure it is completed before you try moving the data. Bandwidth Throttling (applicable only for backup server) - StoreGrid's Bandwidth Throttling feature enables the user to limit the bandwidth usage for a backup schedule. Bandwidth can be configured at the backup server level, group and client levels. Use group's configuration/use server's global configuration - If the option Yes is selected, then the bandwidth throttling for the client will be set as per the setting of the group or if there is no specific setting for the group, then as per the backup server setting. If the option No is selected, then you can setup bandwidth throttling specific to this client by entering the following details: o o o o Enable bandwidth throttling for this client - Choose to enable or disable bandwidth throttling. Throttle bandwidth always - Choose this option to enable bandwidth throttling throughout the day. Throttle bandwidth from - Choose this option to enable bandwidth throttling only during the specified hours of the day. Throttle each backup to maximum of - The rate to which bandwidth should be throttled.

98 Delete a Client How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" link. This will list you the list of clients under that group. Now click on the "Delete Client" icon in the action column of the client row. If you want to delete a client permanently from a group, then you can do that from this page. All the backup data from the client will be deleted permanently from the server. If the Client still has the license key and you have enabled Auto Authorization for this Group, then the Client will be re-created under this group if the Client tries a backup again. But if you have disabled Auto Authorization for this group and if you want this Client to backup to the server again, you need to manually add the client again from the "Add Clients To Group" page. You can see the status of the deletion operation from the Server Side Deleted Backup Reports.

99 View List of Client Backup Schedules How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" link in the left hand side tree. This will list the clients under this group. Now click on the client name to view the list of backups for that client. This page lists the backup schedules from the client in a table format. The following information is showed for each backup schedule: Backup Name - The name of the backup schedule as configured by the client. Clicking on the link here will open the Server Side Backup Schedule Report page which will give detailed Backup Reports, Restore Reports, Delete Reports and Retention Reports for the backup schedule. And the icon in this column can be in different state. The following describes the different state the backup schedule can be in: Backup : Triangle icon Restore : Inverted triangle icon Delete : Cross icon Replication : Play Triangle icon Move Backup : Double Triangle icon Running Retention Cleanup : Rotating arrows icon Server disaster recovery : CPU icon Backup Location - The directory in which the backup data from this backup schedule is stored. The details are available in the mouse over-pop-up dialog over the backup name link. Status - The status of the backup indicates whether the backup is idle or backup is in progress or restore is in progress or replication is in progress or delete is in progress or move backup is in progress or retention cleanup is in progress or Server disaster recovery is in progress. Last Backed up Time - The completed time of the last backup when the client backed up at least one file. Last connected time - The time the client last connected to the backup server for running a backup process. This will include backups where client connected to the server but didn't upload anything to the server. Files - Total number of files backed up as part of this backup schedule. Used Space - The total amount of disk space used by the backup data from this backup schedule. Original Size - The original size of this schedule's backup data in the client. Actions - The icons under this column are links to various features to enable you to administer and manage the backup schedule of clients. 1. Abort Backup (Applicable only to Backup server) - Clicking on this icon will abort the backup immediately and no further data will be transferred to the backup server. However the backup will resume at the next scheduled time. 2. Suspend Client Side Restore (Applicable only to Backup server) - Clicking on this icon will suspend the Client Side Restore (Restore initiated from the client), but can be resumed only from the client side. The suspended restore process will remain suspended till it is resumed from the client again.

100 3. Suspend Server Side Restore - Clicking on this icon will suspend the Server Side Restore (Restore initiated from the server). The suspended restore process will remain suspended till it is resumed from the server again. 4. Resume Server Side Restore - Clicking on this icon will resume the Server Side Restore (Restore initiated from the server). 5. Activate/Deactivate Backup - This Activate/Deactivate action can help the Backup Server administrator to decide whether to accept/reject the individual client's backup. If a backup is Deactivated for a client on the Backup Server, further backup schedules from the StoreGrid client for that backup is rejected by the backup server. StoreGrid Backup Server Administrator can Activate the client backup again by clicking the same action. 6. Replicate Now - This "Replicate Now" action will immediately schedule Replication for a particular backup if the replication for the backup is in idle status. 7. Resume/Suspend Replication - This "Resume/Suspend Replication" action is used to resume a suspended backup (for replication) or to suspend a backup (for replication) when it is either idle or in replication progress. 8. Proceed to Restore Backup - Clicking on this icon will take you to the server side restore page where you can restore the backed up data. 9. Proceed to Delete Backup - Clicking on this icon will take you to the delete backup page from where you can delete the backup data associated with the schedule. 10. Run Retention Cleanup - You can run the retention cleanup process by clicking on this action. The retention cleanup process will delete any excess version files present in the server. Like for example, if the retention version count or retention period configuration is reduced in the client machine, then the backup server can be forced to clean up these excess versions of the files by running the Run Retention Cleanup(the client should have connected at least once after the retention was changed for the backup schedule in the client)

101 Server Side Backup Reports How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on a group name. This will list the clients under that group. Now click on a client to view the list of backups for that client. Now click on the backup to view the report. This page gives a historical report of backups done by the client to the server as part of this backup schedule. The report is shown in a table format with each row representing a backup done by the client. If there are multiple full backups done, then the top row will appear with a plus (+) sign. Clicking on the plus sign will show the incremental backups done between two successive full backups. The description of the columns in the report table are given below: Start Time - The time at which the backup started. End Time - The time at which the backup ended. Added Files - The number of new files backed up in this schedule. Note that this is the total number of files backed up whenever a full backup was done. Deleted Files - The number of deleted files backed up. Note that this number is zero for all full backups. Only for incremental backups this can have a positive value. Modified Files - The number of modified files backed up. Note that this number is zero for all full backups. Only for incremental backups this can have a positive value. Skipped Files - The number of files (that were new or modified since last backup) that StoreGrid failed to backup during this schedule. Clicking on the 'View' link will take you to a page which lists the files that were skipped and the reason StoreGrid skipped the files. Skipped Folders - The number of folders that could not be backed up. Some of the reasons why a folder may not be backed up are: 1. The folder did not have appropriate permissions for StoreGrid to read. 2. The folder may have been modified while StoreGrid is trying to backup it up. 3. The folder may have temporarily available when StoreGrid listed the files/folders to backup but was later not available when StoreGrid tried to backup. Clicking on the 'View' link will take you to a page which lists the folders that were skipped and the reason StoreGrid skipped the folders. Used Space Added - The amount of disk space that was used up in the server by the new files and by the new versions of existing files backed up during this schedule. Used Space Removed - The amount of disk space that was occupied by the file versions that were deleted during this backup schedule. For example, if the backup schedule was configured to retain 5 versions and if the 6th version of a file was added during this backup schedule, then the first version of the file will be deleted. If the first version was of say 30KB, then that 30KB will be included in the Used Space Removed.

102 Change in Used Space - This is the difference between the Used Space Added and Used Space Removed. A positive value indicates that additional disk space was used up in this backup schedule. If the Change in Used Space is negative, then the size of the deleted file versions was more than the size of the new files and new versions added during the schedule. Size of Uncompressed Added/Modified Data - The original size (as exists in client) of the new files or new file versions created during the schedule. Remarks - The final result of the backup operation. Whether successful, failure, or incomplete etc. Delete Button - The "Delete Button" is meant for deleting a older full backup data. If you have more than one full backup present in the server, then you have the option of deleting the older ones manually from this interface. Choose the full backup to be deleted by checking the corresponding check box in the table and click the "Delete Button".

103 Server Side Backup/Restore Progress How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" in this group row. This lists the clients under this group. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Now click on the "Progress" icon in the Backup Name column. Server Side Backup Progress This popup gives a progress of the backup schedule currently active. Note that the progress icon will be green if the backup is active. The percentage progress is based on the disk space allotted vs. disk space used and not based on the total data to be backed up vs. total data already backed up as part of the current schedule. When backup is in progress, 'Abort Backup' icon will be displayed in the progress window. Click on the 'Abort Backup' icon to stop the backup. The server side backup progress window has the following fields: 1. Backup Schedule : Displays the name of active backup schedule. 2. Client Name : Displays the name of the client whose backup data is being transferred. 3. Backup Location : Displays the directory in which the backup data for this backup schedule is stored. 4. Current File : Displays the file which is presently being backed up. 5. Schedule Type : Full backup/incremental Backup. 6. Bandwidth Throttling : Details of the bandwidth throttling applied for this backup. The bandwidth throttling could be set in the client or in the backup server. 7. Used Space : Total data size backed up so far - size based on the space occupied by the files in the client machine. 8. Transfer Rate : The average rate at which backup data is been transferred - calculated as size of total backup data transferred divided by the total time taken so far for the backup. 9. Added Files : Displays the number of newly added files (since last backup) backed up so far. 10. Modified Files : Displays the number of files which were modified since the last backup schedule and have been backed up in the current backup schedule. 11. Deleted Files : Displays the number of files which were deleted since the last backup schedule and the delete notifications have been processed in the current backup schedule. 12. Skipped Files : Displays the number of files that could not be backed up so far. 13. Skipped Folders : The number of folders that could not be backed up. Some of the reasons why a folder may not be backed up are: o The folder did not have appropriate permissions for StoreGrid to read.

104 o The folder may have been modified while StoreGrid is trying to backup it up. o The folder may have been temporarily available when StoreGrid listed the folders to backup but was later not available when StoreGrid tried to backup. 14. Abort Backup : The backup process can be aborted by clicking this icon. When aborted, the backup will then run during the next scheduled time. Server Side Restore Progress This popup gives a progress of restore operation currently active. Note that the progress icon will be green if the restore is active. The percentage progress is shown based on the number of files to be restored and the number of files already restored. When restore is in progress, 'Suspend Restore' icon will be displayed in the progress window. Click on the 'Suspend Restore' icon to stop the restore process. Restore initiated from the client can be suspended from the client as well as from the backup server but the suspended restore can be resumed only from the client. The restore progress window has the following fields: 1. Backup Schedule : Displays the name of backup schedule which is being restored. 2. Client Name : Displays the name of the client whose backup data is being restored. 3. Current File : Displays the file which is presently being restored. 4. Total Files : Displays total number of files available for restore. 5. Transfer Rate : Displays the transfer rate of the backup data being restored from the backup server. 6. Files Restored : Displays the total number of files restored from the backup server. 7. Suspend Restore : Clicking on this icon will suspend the restore process.

105 Backup Server Replication Progress Overview This popup gives a progress of the replication schedule currently active. Note that the progress icon will be green if the replication is active. The progress is based on the number of files already replicated vs. total number of files to be replicated as part of the current schedule. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" in this group row. This lists the clients under this group. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Now click on the "Progress" icon in the Backup Name column. What does the Backup Server Replication Progress window tell you? Transfer Rate - Displays the transfer rate of the replication data being transferred to the backup server. Backup Schedule - Displays the backup schedule name. Client Name - Displays the client name from which the backup data is being transferred. Backup Server - Displays the backup server name from which the backup data is being replicated. Replication Server - Displays the replication server name to which the backed up data is being replicated. Messages - Displays the current replication progress message. Transferred - Displays the number of files that are transferred so far in comparison with the total number of files gathered. Added Files - Displays the number of newly added/created files being replicated. Modified Files - Displays the number of files that are modified after the last replication. Files Skipped - Number of files skipped during the replication process. Number of Directories - Number of backup directories replicated - directory details alone, not the files under the directory. Warning - Displays the warning message, if any, when the backup is in progress. Current File - Displays the current file that is being transferred. Replicated (so far) - Displays the number of bytes transferred so far in comparison with the file size of the current file being replicated. Transfer Rate - Displays the current transfer rate of the current file. Time Left - Displays the time left to complete the replication of the current file. Uploaded Size - Displays the number of compressed bytes of the current file transferred. Limitations The backup server replication progress window polls the StoreGrid Backup Server every single second to get the progress of replication. 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 server replication progress window closed and open it only occasionally to check the replication progress.

106 Replication Server Replication Progress Overview This popup gives a progress of the replication schedule currently active. Note that the progress icon will be green if the replication is active. The percentage progress is based on the total files already replicated vs. total files to be replicated as part of the current schedule. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" in this group row. This lists the clients under this group. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Now click on the "Progress" icon in the Backup Name column. What does the Replication Server Replication Progress window tell you? Transfer Rate - Displays the transfer rate of the replication data being transferred to the Replication Server. Backup Schedule - Displays the name of the backup schedule which is being replicated. Client Name - Displays the client name whose backup data is being replicated. Messages - Displays the current replication progress message. Files Processed - Displays the number of files replicated so far in comparison with the total number of files gathered. Added Files - Displays the number of files newly added/created for replication. Modified Files - Displays the number of files that are modified in the client after the last replication. Protected Files - Displays the number of files protected/replicated to the replication server. Deleted Files - Displays the number of files that are deleted after the last replication. Configuration Files - Display the number of StoreGrid configuration files replicated. Configuration files includes the StoreGrid created internal files during a backup. Bytes Transferred - The number of bytes transferred for replication. Current File - Displays the current file that is being replicated. Backup Location - Displays the location the replicated data is stored in the replication server. Warning - Displays the warning message, if any, when the replication is in progress. Limitations The replication server replication progress window polls the StoreGrid Replication Server every single second to get the progress of replicate. 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 replication server progress window closed and open it only occasionally to check the replication server replication progress.

107 Run Retention Cleanup Overview Older versions of a file are automatically cleaned up from the StoreGrid server when the later versions of the file are backed up in the subsequent incremental backups. In addition to the retention schedule configured in the server, you can manually run the retention cleanup process using 'Run Retention Cleanup' feature to delete the older version of the files from the server. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> Group Management" and click on the "Group Name" link in the left hand side tree. This will list the clients under this group. Now click on the client name to view the list of backups for that client. Click on the "Run Retention Cleanup" icon in the action column of the Backup row. Running Retention Cleanup Retention cleanup process can be run either for the version files or for the deleted files. Backed up version files: Cleans up the backed up version files that have exceeded retention policy count configured in a backup schedule. Deleted Files: Cleans up the deleted files that have exceeded retention policy count configured in a backup schedule. Retention Cleanup Progress Client Name: StoreGrid ID of the client backing up to the server. Backup Name: Name of the backup schedule which is being processed for retention cleanup. Retention policy configured: Version-based or time-based retention. Current File: Displays the file which is being processed for retention. Backup Location: Displays the location where the selected client's backup data is stored. Message: Displays the status of the retention cleanup process. Deleted Files cleaned up Total Files: Displays the number of deleted files removed from the backup server location. Disk Space freed up: Total size of the version files that were cleaned up. This is the total space freed up by the cleanup process. Backup version files cleaned up Total files: Displays the number of version files removed from the backup server. Disk space freed up: Total size of the deleted files that were cleaned up. This is the total space freed up by the cleanup process.

108 Abort Cleanup: You can manually abort the retention cleanup process by clicking on the abort icon in the retention progress window. Cleanup Report Backup version files cleaned up: Total number of backup version files cleaned up from the backup server. Disk space recovered after version files cleanup: Total disk space recovered after the cleanup of backup version files. Deleted files cleaned up: Total number of deleted files cleaned up from the backup server. Disk space recovered after deleted files cleanup: Total disk space recovered after the cleanup of deleted files.

109 Server Side Restore Report How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" in this group row. This lists the clients under this group. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Click on the "Backup Schedule Name" to fetch this backup schedule reports. Now click on the "Restore Report" tab. This page provides details on all the restore operations done for this backup schedule. The report is generated in a table format with each row representing a restore operation. The description of the table columns are given below. Restored to - The StoreGrid client to which this backup schedule data was restored to. Last Restored on - The time at which the restore operation finished. Time Taken - Total time taken for the restore operation to finish. Total Files - Total number of files present in the backup server that need to be restored. Restored Files - The number of files successfully restored. Skipped Files - The number of files that could not be restored. Size - The total size of data transferred to the client machine. Restore Location - The directory location in the client where the restore data was copied. Message - Message about the restore operation. Useful when there are errors.

110 Server Side Delete Report How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" in this group row. This lists the clients under this group. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Click on the "Backup Schedule Name" to fetch this backup schedule reports. Now click on the "Deleted Report" tab. This page provides details on all the delete operations done for this backup schedule. The report is generated in a table format with each row representing a delete operation. The description of the table columns are given below. Server Name - The StoreGrid Server Name to which this backup schedule data is backing up to. Client Name - The StoreGrid client from which this backup schedule is backing up from. Backup Name - the name of the backup schedule. Status - Status of the delete operation. Deleted Time - The time at which the delete operation was performed. Message - Message about the delete operation. Useful when there are errors.

111 Server Side Replication Report How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" in this group row. This lists the clients under this group. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Click on the "Backup Schedule Name" to fetch this backup schedule reports. Now click on the "Replication Report" tab. This page provides a historical report on replication of the primary server to the replication server. The report is generated in a table format with each row representing a replication schedule. A replication report is generated for each backup schedule from each client backing up to the server. The description of the table columns are given below. Client Name - The StoreGrid client whose backups to this server are being replicated. Backup Name - The backup schedule for which this replication report is created for. Server Name - The replication server to which the server's data is being replicated to. Start Time - The time at which the replication operation started. End Time - The time at which the replication operation completed. Total Time Taken - The total time taken for the replication to complete. Files Protected - The total number of backup files successfully replicated. Modified Files - The total number of version backup files successfully replicated. Files Skipped - The number of files that could not be replicated. Skipped files will be rescheduled for replication every minute. Bytes Transferred - The number of bytes transferred for replication. Bytes Processed - The number of bytes processed for replication. Remarks - Messages about the replication schedule. Warning - Error messages during the replication.

112 Retention Report Overview This page provides details on all the completed retention cleanup processes for the backup schedule. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> Group Management" and click on the "Group Name" in the group row. This will list the clients under the particular group. Click on the "Client Name" in the client row. This lists the backup schedules for the particular client. Click on the "Backup Schedule Name" to fetch the retention schedule reports. Retention Report The description of the table columns are given below. Cleanup Deleted Files o o Count: Number of deleted files cleaned up during the retention cleanup. Disk Space Freed: Disk space freed in the backup server after deletion of deleted files. CleanupVersion Files o o Count: Number of backed up version files deleted during the retention cleanup. Disk Space Freed: Disk space freed in the backup server after deletion of backed up version files. Total Disk Space Freed: Sum of disk space freed due to removal of deleted files and backed up version files. Start Time: Time when retention cleanup process started. End Time: Time when retention cleanup process ended. Total Time Taken: Total time taken for retention cleanup operation. Remarks: Status of retention cleanup process.

113 Move Client Backup Report Overview This section reports the status of moving the backup data to a new location. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" in this group row. This lists the clients under the group. Go to "Client Report" action corresponding to the client name and click on the "Move Client backup(s) report " tab.. Move Client Backup Report Backup Name: Backup name for which the location is to be changed. Start Time: Time at which the process of moving the backup data started. End Time: Time at which the process of moving the backup data ended. Remarks: Success or Failure. Old Backup Location: The old location for the backup. New Backup Location: The new location for the backup. Warning: The following warning messages may be shown if the move backup fails. 1. Lack of available space: Space is not available to move the backup. Please choose another location. StoreGrid checks for available space in the new location individually for all the backups. If sufficient space is available, StoreGrid will move the backup data for that backup. If sufficient space is not available for a particular backup, it reports an error and then moves on to the next backup. 2. Insufficient permission: The backup could not be moved if it doesn t have enough permission. Please check the permissions. 3. DB Update Failed: i. The backup data in the new location is not in the right directory structure. Please make sure that the backup data is under the folder structure [New Storage Location]/1/[client name] ii. File 'sgclient.txt' is missing in the new backup location New Storage Location]/1/[client name]/ iii. Cannot find the backup data in the new location. Please make sure that the backup data is under the folder [New Storage Location]/1/[client name]/[backup name]

114 Skipped File Report in Backup Server How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" in this group row. This lists the clients under this group. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Click on the "Backup Schedule Name" to fetch this backup schedule reports. Now click on the View link under the skipped file count. This page shows the list of files that StoreGrid could not backup during the backup schedule. The page lists the files in groups of 100. If the number of files skipped is more than 100, then you can browse through the lists by clicking 'First', 'Prev', 'Next' and 'Last' links at the bottom of the table. This tabular summary of each schedule s backup status includes the following: File Name: The name of the file in the client machine that was not backed up. Location: Location of the skipped file in the client machine. Fresh Upload: Indicates whether this particular file was backed up in an earlier schedule or it is a newly added file that StoreGrid is trying to backup for the first time. Remarks: The reason why the file was skipped.

115 Skipped Folder Report in Backup Server How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management" and click on the "Group Name" in this group row. This lists the clients under this group. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Click on the "Backup Schedule Name" to fetch this backup schedule reports. Now click on the View link under the skipped folder count. This page shows the list of folders that StoreGrid could not backup during the backup schedule. The page lists the folders in groups of 100. If the number of folders skipped is more than 100, then you can browse through the lists by clicking 'First', 'Prev', 'Next' and 'Last' links at the bottom of the table. Folder Name: The name of the folder in the client machine that was not backed up. Location: Location of the skipped folder in the client machine. Remarks: The reason why the folder was skipped.

116 Restore client's Backup Data using StoreGrid Server WebConsole Overview StoreGrid supports restoring any client's backup data from the StoreGrid backup server. This is useful when a backup server administrator has to restore a client's backup schedule without having access to the client's StoreGrid installation. But in order to do a server side restore, the administrator should know the encryption password used by the client. How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management". From the list of group displayed in the table, click on the Group Name. This lists the clients under this Group. Now, click on a client name. This will open a page which lists the backup schedules backing up to this server (from the selected client). Now click on the "Restore" action icon. If you had password protected the backup schedule, StoreGrid will ask the password for that backup schedule. Restore Client's Backup Data The following are the steps to be followed while restoring data: Step 1: Select Version To Restore - Here you will see a tree with each parent node representing a full backup that has been done with the time stamp of the last incremental backup performed for this full backup. If the backup schedule was not configured with multiple full backups, then this list will have only one parent node- that of the first full backup. Under each parent node, a leaf node with timestamp represents an incremental backup that has been done. The leaf-node with the earliest timestamp represents the time when the full backup was done and all other time stamps represent an incremental backup on top of the full backup. You can choose any version based on timestamp for restoring. Note that the tree in Step 2 loads with the files/folders based on what timestamp/version you choose here. Also, by default the tree in step 2 is loaded for the latest backup of the backup schedule. Step 2: Select Files And Folders - You could select the files/folders and their versions to restore from the file/folder tree. You can also specify the files/folder you want to restore in two other ways: 1. Either by using filter in the tree by entering a wild card (*.doc etc.) in the Filter files/folders text field. Note that the tree will also list the number of versions of each file as of the timestamp chosen in Step 1. You can either choose a specific version of a file to restore or choose the root node to restore the latest version (as of the timestamp chosen in Step 1) of all the files. 2. You can also enter the names of the files and folders directly. Click on the Let me directly enter the file/folder names instead of selecting them from the tree view link in step 2. Enter the complete path of the file/folder to restore and click the Add button. You can remove the selected files and folders by clicking the Remove button. Please note that while restoring files this way, you will be able to restore only the latest version of the file that was available at the backup time that you selected in Step 1. If you are trying to restore a delete file, then you should enter the path to the file's parent folder and not the path of the delete file. Step 3: The following are the options you have to provide in this step Restore Deleted Files - This has three options to choose from: 1. Skip Deleted Files - Choosing this option will skip the deleted files and restore the rest. 2. Deleted Files Only - Choosing this option will restore only the deleted files. 3. Include Deleted Files - Choosing this option will restore all the files including the deleted files. Restore Location - You can specify the 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!

117 Advanced Options - 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 behavior, 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 lost. 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. Limitations 1. Files/Folders entered manually for restore are case sensitive. Also, ensure that the complete path of the files/folders to be restored is entered. 2. A single deleted file/folder cannot be restored by entering the complete path to the deleted file in step 2. Instead, the path to the parent folder name that contains the deleted files/folders and then select the "Deleted Files Only" option in Step No error message will be displayed in the webconsole, if the files/folders entered manually for restore do not exist in the backup server or is not a part of the configured backup schedule. However, the error message will be reported in the restore progress and report. 4. Only the latest version will be restored if the files/folders to be restored is specified by entering the complete file/folder path in step 2. For example, if a file (image.jpg) has 4 versions (*.ver_001, *.ver_002, *.ver_003, *.ver_004), then by default the latest version (*.ver_004) will be restored for the selected timestamp.

118 Delete a Backup from the Server How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Group Management". From the list of group displayed in the table, click on the Group Name. This lists the clients under this Group. Now, click on a client name. This will open a page which lists the backup schedules backing up to this server (from the selected client). Now click on the "Delete Backup" action icon. If you want to delete a client's backup data associated with this backup schedule, then you can do that from this page. All the backup data associated with this backup schedule will be deleted permanently from the server. If your server can directly reach the client, then the client will also be notified about this deletion. Whether the client gets notified or not about the deletion, the client will take a new full backup to the server, if the same backup scheduled is scheduled again in the client. You can see the status of the deletion operation from the Server Side Deleted Backup Reports.

119 Aborting Backup from backup server Overview A backup process can be aborted from the backup server. When aborted, the backup will then run during the next schedule. How to get here in the StoreGrid Web Console? In the top menu select: "Server Admin -> Group Management > Group [group name] > Client [client name]- > List of Backup Schedules from client"in the backup server's web console. Aborting Backup from backup server To abort a backup from the backup server, go to the 'Server Management -> Group Management > Group [group name] > Client [client name]- > List of Backup Schedules from client' page in the backup server's web console. When a backup is in progress, 'Abort Backup' icon will be displayed under 'Actions' against that backup schedule. Click the 'Abort Backup' icon to stop the backup process. When aborted, the backup will then run during the next schedule. Limitations Aborting a backup from the backup server will work only if the client is running StoreGrid version 2.3 or above.

120 Suspending Server Side Restore (Restore initiated from the backup server) Overview Server Side Restore (Restore initiated from the backup server) can be suspended from the backup server. How to get here in the StoreGrid Web Console? In the top menu select: "Server Admin -> Group Management > Group [group name] > Client [client name] > List of Backup Schedules" page. Suspending Server Side Restore (Restore initiated from the backup server) To suspend a Server Side Restore, go to the 'Server Management -> Group Management > Group [group name] > Client [client name] > List of Backup Schedules' page in the backup server's web console. When restore is in progress, 'Suspend Server Side Restore' icon will be displayed under 'Actions' against that backup schedule. Click on the 'Suspend Server Side Restore' icon to suspend the Server Side Restore. You can resume the restore process using the 'Resume Server Side Restore' icon.

121 Configure Backup Schedule Overview This page enables the user to configure backup schedules. Once the schedule is configured, the client's data is backed up to the selected Backup Server(s). How to get here in the StoreGrid Web Console? In the top menu, select: "Backup->Add Backup Schedule" Configure Backup Schedule Step 1: Enter Backup Schedule Name The first step in configuring a backup is to give a name for the backup schedule. StoreGrid supports creating multiple backup schedules each with its own configuration. The backup schedule name will uniquely identify the backup. While restoring your backup data, you need to choose the data to be restored using its schedule name Step 2: Select Files And Folders To Backup 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. Outlook backup, IE/Firefox settings, windows registry, etc. Files/Folders Filter Settings (optional) Standard 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 Sub-folders - Check this option if you want to exclude all the sub-folders under your selected folders for backup. Advanced Settings

122 In advanced file/folder filters you can either specify text patterns or enter the file/folder name you want to include/exclude. You can specify text patterns matching specific file and folder names that you want to include or exclude. Like for example, you can add a filter to include only those files whose names start with 'a' under the selected folders or in their immediate sub folders. As another example, you could specify a filter to exclude folders whose names contain the text 'temp'. You can also enter the file/folder name with or without absolute path. Like for example, if you enter the filename test.txt, then all files with the name "test.txt" under the selected directories will be matched. If you enter the entire path C:/Document and Settings/temp/test.txt, then only that specific file will be matched. You can specify maximum 5 filters. The filters work independently of each other; i.e., if you have a filter to include files starting with 'a' and another filter to include files starting with 'b', then the backup will include files starting with 'a' and files starting with 'b'. Map External Drive If you want to backup files and folders present in an external drive and if that drive is not listed in the file/folder selection tree, then you can map a drive letter to the UNC path of the external drive. Like for example you could assign letter X to an external drive's UNC path //SERVER_A/DATA. Once added, the mapped drive letter will appear in the file/folder selection tree and the files/folders in the external drive will be listed under the corresponding drive letter. This feature is especially useful while configuring backups for files in external drives on Windows XP/2003/Vista where the mapped drives will not be listed in the file/folder selection tree if StoreGrid is run as a service. NTFS Backup StoreGrid uses a third party tool called Subinacl to backup and restore the NTFS Permissions. Users must install Subinacl tool before using this feature. StoreGrid uses the Subinacl tool to dump the NTFS permissions and uploads the dump file to the backup server. During restore, StoreGrid will restore the dump file first and then using Subinacl it will restore the NTFS permissions of the files and folders automatically. Server Side and Third party Restore are not supported with this plugin. Also, it cannot backup the permissions of the parent directory. Step 3: Set Basic Configuration Backup Type Same Machine - When large amount of data has to be backed up, it might take significant amount of time to transfer all the data to a remote backup server over WAN/Internet. You can take backup to a local external drive connected to the client machine and then physically move the external drive to the backup server location to migrate the data into the backup server. In such cases, you can select the backup type to be 'Same Machine'. Once the data is migrated to the backup server using the Server Side Local to Remote Migration, you will have to perform Local to Remote Migration (under Administration -> Advanced Options) in the client machine to make it to run its backups to the remote server directly thereafter. Please note: You will not be able to restore from the backup data present in the local external drive. It is meant only for quickly moving the large amount data to the remote backup server. Once the data is migrated to the remote server from the external drive, the client can restore from the remote server. Remote Server - Select this option if you want the backup data to be transferred to a backup server directly when the backup schedule runs. Select Backup Server(s)

123 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. The client will run the backup to one backup server at a time. Test connectivity to Backup Server - Before you select the backup server for this backup schedule, you can check the connectivity to backup server. It also checks the different settings configured in the backup server for this client and confirms if this client can backup to the chosen backup server or not. Add Backup Server- If you don't see a particular backup server listed, you need to first add it by following this link before you can select it for this backup schedule. Set 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. 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. Set Compression Should the data be compressed or not. Enable - Compresses the data to the maximum. It might reduce the rate at which the client can send data to the backup server but it might save significant bandwidth and time when the data is backed up to a remote server over a WAN/Internet with limited bandwidth speed. Also, this saves disk space in the backup server. Disable - This option is suitable (fastest) for backing up data within a local network where bandwidth is not the limitation, but occupies more space on destination machine as no compression is being done. Intelli-Delta 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 "Intelli-Delta 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. Temporary location for backup dumps Enter the location/directory path where the System State dumps are to be stored temporarily before uploading them to the backup server. Ensure that there is enough disk space in the configured temporary dump location. The backup dumps stored in the temporary location will be deleted once they are transferred successfully to remote backup server. Note: StoreGrid does not support system root drive or mapped drive or StoreGrid installation location to be configured as the dump location for system state backup in Windows Step 4: Set Password Protection Password Protect This Backup

124 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 for generating the encryption key. 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. Encryption Key Size StoreGrid supports encryption using variable length (64 to 448 bits) keys. The key is generated using the password you provide. Basically the longer the key size you give the more difficult it is for someone to decrypt the encrypted files. For normal backup purposes the default 64 bit encryption should be good enough. Type Password Provide a password here to generate the encryption key. 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. Step 5: Scheduling (Decide When To Backup) This field has the following options from which any one can be chosen. 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 Few Hours Choose the hours/minutes interval between each time StoreGrid must run. If StoreGrid is restarted in the interim, the backup will run once StoreGrid starts. Thereafter, StoreGrid automatically reschedules the next backup after the period you ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, StoreGrid will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, StoreGrid is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am. Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the checkbox against these days. If the "Select all days" checkbox is checked, then the schedule will be run on all the days of the week. Run Daily Choose the time at which the backup should run daily. This will execute the backup everyday at the time you have provided. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options, StoreGrid will run at the stipulated time only. Run Weekly Choose the time and the day of the week the backup should run. StoreGrid will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options, StoreGrid will run at the stipulated time/day only. Run Once Only Choosing this option will do the backup only once immediately. 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.

125 Advanced Options (Optional) If you want to configure some additional advanced options - like, Multiple Full Backups etc. click on the Advanced Options button. Advanced Backup Schedule Settings There are four 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. In case of the Continuous backup or Run every scheduling options, backups will run each time StoreGrid restarts by default. 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 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 AM). Attempt to run this backup every 5 minutes in case of non completion because of a problem (Network error etc.) - If enabled, the user can choose to reschedule this backup every 5/10/15/20/25/30 minutes, whenever an attempted backup is incomplete because of a network error, server crash etc. The number of times the backup will be rescheduled (due to an error) can be configured to be in between 1-5 or unlimited, with the default setting as 5. This is to ensure that an incomplete backup is completed as soon as possible without waiting for the next actual schedule time. Note that this option is enabled by default. Enable Automatic Directory Monitoring - If enabled, StoreGrid will be automatically notified by Windows OS of any file/folder changes. This will help StoreGrid efficiently identify changed files when it does the rsync based delta backup for changed files. If this option is disabled, then StoreGrid has to scan all the configured files/folders every time a backup is scheduled to detect changed files. So it is recommended that in Windows OS this option is enabled. In Linux and Mac OS X, this option should be disabled as there is no automatic directory monitoring support in Linux and Mac OS X. Note that even if directory monitoring is disabled StoreGrid will still do the rsync based delta back for changed files. Volume Shadow Copy Service (VSS) - If enabled, StoreGrid will create snapshot(a read only copy) of the volume(s) corresponding to the configured folders/files and backup using the snapshot of the volume. Volume Shadow copy allows StoreGrid in creation of consistent backups, ensuring that the contents cannot change while the backup is being made, avoiding problems with file locking, as StoreGrid uses a read-only copy of the volume, it is able to access every file without interfering with other programs writing to those same files. Requirements 1. StoreGrid uses the Microsoft's 'Volume Shadow Copy'(installed by default when Windows XP and later versions installed) Service to create snapshot. Hence, StoreGrid needs 'Volume Shadow Copy' Service to be configured with service start type 'Automatic' or 'Manual'. 2. Volume Shadow Copy Service needs at least 100 MB free disk space. Backup NTFS Permissions for the files and folders configured (if applicable) - When this option is enabled, StoreGrid backs up the NTFS file permissions along with the files. The user needs to enable the option 'Backup NTFS Permissions for the files and folders configured (if applicable).' in 'advanced option' while configuring a backup schedule. By default this option will be disabled. During restore, the files are restored along with their permissions. StoreGrid will not restore the NTFS Permissions during Server-Side and Third Party Restore.

126 Configure Additional Full Backups Typically, you would do a full backup the first time you backup your data and thereafter only do incremental backups. However, like in a typical enterprise scenario, if you want to run full backups periodically and run the incremental backups in between two full backups, then you can configure the scheduling for how to run the full backups here. For Continuous, Run Every Few Hours and Run Daily backups, the Additional Full Backup settings will allow you to configure daily/weekly/monthly additional full backups. For weekly backups, only Monthly additional full backups are possible. For Run Once Only backup, you cannot configure additional full backups. Additionally you can specify the maximum number of full backups that need to be stored in the server. For example if you configured a weekly backup and additionally if you configure a monthly full backup, then StoreGrid will take a full backup the first time and then weekly do an incremental backup. The next month, StoreGrid will do a new full backup and subsequently run the weekly incremental backup over this full backup. After 6 months you will have 6 separate full backups in the backup server along with weekly incremental versions under each of the 6 full backups. If your policy is to retain only backup data for 6 months, then you can configure "Store maximum of 6 full backups" here. On the 7th month, StoreGrid, after finishing the 7th full backup, will delete the first full backup along with its weekly incremental backups thus retaining always the last 6 month backups. Retention Policies (Optional) StoreGrid provides the retention feature where backups of multiple versions of a file can be maintain at the backup server. StoreGrid cleans up the version files in the backup server based on two major retention policies: 1. Version-Based Retention - Retains multiple version files in the backup server based on the version file count. 2. Time-Based Retention - Retains multiple version files in the backup up server based on the age of the version files. Retention policy for backed up files Version-Based Retention StoreGrid can retain backups of multiple versions of a file based on the version retention count specified. The number of version files to be retained can be specified as any value from 0 to 99 with a default setting of 5. The backup version count can be 0 when the Intelli-Delta Backup is disabled in Step 3. This option is useful when you wish to store just the complete latest version of a file. For example, if the version file retention count is specified as 5, then StoreGrid retains the latest five version files. These files can be restored from the backup server at any point of time. When the sixth version of the file is created, StoreGrid backup server automatically deletes the first version. Note: When Intelli-Delta option is disabled for a backup schedule, StoreGrid will back up the entire file if the file was modified since the last backup schedule. In such a case, StoreGrid will retain multiple versions of the entire file as per the version retention count configure for that backup. Time-Based Retention StoreGrid can retain version files in the backup server based on the age of version files. Default setting is for 1 month, meaning the version files will be retained in the backup server for 1 month(30 days) and then will be removed automatically. The maximum number of versions that can be created during the retention period can also be optionally further configured. There are two options: Any number of versions can be created within this retention period - This is the default setting. If enabled, StoreGrid retains all the versions created during the specified retention time period. Restrict the maximum number of versions that can be created within this retention period to 'n'. - If this option is enabled, StoreGrid will clean up the version files based on both; retention time period and

127 maximum version file count. For example, if the retention time period is set to 1 month and maximum version file count is 5, StoreGrid will retain only the last five version files created within the last one month and versions older than one month with be deleted. Retention policy for deleted files[for Windows only] If the files configured for backup are deleted at the client side after a backup schedule, then the backed up data of those files will not be deleted in the backup server. It will be just flagged as "Deleted" during subsequent backup schedule. StoreGrid allows the user to choose whether or not to retain these "Deleted"(flagged as deleted) files in the Backup Server. Note: This option is enabled only in Windows client machines and not supported in client machines running Linux, Mac or Free BSD operating systems. Version-Based Retention: Retains the specified versions(default is 5) of deleted files in the backup server. Time-Based Retention: Retains all available versions for the specified time period. The default setting is for one month, which means StoreGrid will keep all available versions for a month. Don't retain deleted files: If files are deleted in the client machine, all backed up versions of these files will be deleted from the server as well in the subsequent backup schedules. This is not recommended as you lose the data permanently. Pre & Post Backup Commands (Optional) This feature provides the ability to configure running custom actions before and after executing a backup schedule. The custom actions may include running an application or some script files. Pre & Post Backup Commands When is this feature useful? If an application has exclusively locked a file and you need to close the application before StoreGrid can backup that file, then you can run a pre-backup command to close the application and then a post-backup command to open the application again after StoreGrid successfully backs up the file. How does this feature work? When ever a backup schedule starts, StoreGrid will start the Pre Backup commands and wait till the timeout value. After completing the Pre Backup commands, StoreGrid will transfer the configured files & folders to the backup server. After transferring the configured files and folders, StoreGrid will run the Post Backup Commands. If multiple servers are configured for the backup schedule, then both the Pre and Post Backup commands will run while backing up to each of the servers. Pre & Post Backup command settings: You can provide maximum of 5 Pre Backup commands and maximum of 5 Post Backup commands for each backup schedule. Both the Pre and Post Backup commands are optional. Command Name: This filed is mandatory. This is the command that should be run. The command should be provided with full path. If the command name is in the system command path, then providing full path for the command is not necessary. The command can be an executable file such as application exe, batch files, script files etc. Example: C:\MyTools\myzip.exe. A simple zip tool which compresses the given files or folders.

128 Arguments: You can provide any command line arguments for the command to be executed. Example: For the Command C:\MyTools\myzip.exe, the arguments may be 'High Zip Replace "D:\Project" myproject.zip' [with out quotes]. Here, the High may denote high compression, Zip denotes zip file format, Replace denotes replacing existing files, 'D:\Project' denotes folder to compress and 'myproject.zip' denotes the target compressed file name. Working Path: This field specifies the directory path from which the Command has to be run. If this field is left empty, then the command will be executed from the StoreGrid working path [StoreGrid Home] Example: 'D:\Project'. The command will be executed from the directory D:\Project. Timeout: This filed is used to specify a timeout value, in seconds, for the command to finish execution. StoreGrid will wait for so many seconds for the pre and post command to finish running. If the command still runs beyond the timeout period, then StoreGrid will abruptly terminate the command and will continue with the backup schedule. Please note that if you provide -1 value, then the command will run till completion and StoreGrid will wait till the command completes. If command never completes, then StoreGrid may just infinitely wait without proceeding with the backup schedule. Example: 60. For the myzip.exe command, the myzip.exe command will compress the given project folder up to 60 seconds. If the myzip.exe completes before the timeout period, say 15 seconds, then StoreGrid will immediately continue the next Pre Backup Command [if configured] or continue with the backup schedule. So, the example command will look like below: Command Name : C:\MyTools\myzip.exe Arguments : High Zip Replace Working Path : D:\Project Time out : 60 The whole command will be run up to 60 seconds as below: C:\MyTools\myzip.exe High Zip Replace "D:\Project" 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/Save 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. So when a folder has 1000s of files, then the java script takes time to load the tree. Please be patient

129 Configure Exchange Server Backup Overview StoreGrid supports backup of Microsoft Exchange servers using two types of plug-ins: 1. The Basic Plugin and 2. Advanced Plugin. Advanced Plugin is much more flexible and efficient while backing up exchange servers than the basic plugin though basic plugin may be good enough for backing up exchange servers with relatively less amount of data. The Basic (Plugin) Exchange Server backup uses the NTBackup utility to dump the Storage Groups' data and thereafter uploads the locally dumped file to the backup server. Furthermore, this dump file will be maintained locally in client machine for further differential log backups. The Advanced (Plugin) Exchange Server backup uses the ESE API to backup Storage Groups and Mail Stores. In the Advanced Exchange Server backup, the initial backup will be compressed and dumped locally and thereafter transferred to the backup server. Locally dumped files will be deleted once the files are successfully transferred to the backup server thus releasing disk space in the local exchange server. The Advanced Exchange Server Plugin ESE API backup supports backup of storage groups in entirety, as well as individual databases within the storage groups. Because each storage group uses a single set of log files covering all of the databases in the storage group, restore and recovery operations should be done for the entire storage group. Backing up databases individually provides greater storage management flexibility. For example, critical databases might be backed up more frequently. Infrequently used or less critical databases might be backed up less frequently. Restoration of the storage group, however, should combine the archives and logs from all of the appropriate storage media, so that the database can be restored and recovered with minimal data loss. IMPORTANT: Please ensure the following before configuring a Exchange Server backup. i. Ensure that the Storage Group/Mail Store configured for backup is mounted. A database must be online to be backed up. If a database has been dismounted it cannot be backed up, and the log sequence will not be truncated. ii. If the Storage Group is configured for either incremental or differential log backups, then the circular logging option should be disabled for the Storage Group. Once you disable circular logging, we recommend that you run a fresh full backup before running an incremental or differential backup. How to get here in the StoreGrid Web Console? In the top menu, select: "Backup-> Create Exchange Server Backup" Requirements Exchange Server 2000 with Service Pack 3 / Exchange Server 2003 / Exchange Server Exchange Server Backup Configuration Step 1: Schedule Name Enter Backup Schedule Name: The first step in configuring the Exchange Server backup is to give a name for the backup schedule. StoreGrid supports creating multiple backup schedules each with its own configuration. The backup schedule name will uniquely identify the backup. While restoring your backup data, you need to choose the data to be restored using its schedule name.

130 Step 2: Select Backup Source On the left side of the "Create Exchange Server backup schedule" Page, is the tree with a list of Storage Group and Mail Stores of the Exchange Server detected in the client machine. If the Storage Group or Mail Store is already configured as part of another schedule, it will not be possible to include it in other backup schedules. In this case, the Checkbox will be displayed as an image. Granularity up to Mail Store level backup is supported with the Advanced Exchange Server Plugin. Granularity up to Storage Group level backup is supported with the Basic Exchange Server plugin. Step 3: Set Basic Configuration Plugin Type : Drop-down box will, by default, opt for the "Advanced Exchange Server Plugin", if the advanced version of the (SQL + Exchange) plugin is currently enabled in "Advanced Options > Plugin Settings" page. With the advanced version of the plugin enabled, you will have an option to choose either the Basic or the Advanced plugin backup for "Exchange Server Backup". The tree listed on the left side of the "Create Exchange Server backup schedule" page content will be refreshed when the Backup Type is changed from "Advanced Exchange Server Plugin" to "Basic Exchange Server Plugin" and vice versa. If the advanced version of the (SQL + Exchange) plugin is currently disabled in "Advanced Options > Plugin Settings" page, then this field will be non-editable and set to the "Basic Exchange Server Plugin". Backup Type Same Machine: When the Exchange Server databases contain large amount of data, it might take significant amount of time to transfer all the data to a remote backup server over WAN/Internet. In such cases, you can take backup of the Exchange Server databases to a local external drive connected to the client machine and then physically move the external drive to the backup server location to migrate the data into the backup server. In such cases, you can select the backup type to be 'Same Machine'. Once the data is migrated to the backup server, you will have to perform Local to Remote Migration (under Administration -> Advanced Options) in the client machine to make it to run its backups to the remote server directly thereafter. Please note: You will not be able to restore from the backup data present in the local external drive. It is meant only for quickly moving the large amount data to the remote backup server. Once the data is migrated to the remote server from the external drive, the client can restore from it. Local Backup location: Enter the location/directory path to which the backup has to be stored in the same machine. Please ensure that you have enough disk space in the configured location (where the Exchange Server backup has to be saved). Remote Server: Select this option if you want the backup data to be transferred to a remote backup server directly when the backup schedule runs. Select Backup Server : This is the list of peers/backup servers on which the backup data can be stored. Only one backup server is allowed for a Exchange Server backup schedule. Unlike regular data backup schedules in StoreGrid(where multiple backup servers are supported), only one backup server is allowed for an Exchange Server backup schedules. This is due to the reason as follows :- 1. Exchange Server database dump transferred to multiple server might get inconsistent when the backup to one of the servers fail with network errors or server unavailable. 2. Exchange Server changes the reference of the database dump when two schedules try to backup the same Information Storage Group or Mail Store. Hence both the backed up data might get inconsistent when backed up across two schedules. Set 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

131 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. 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. Set Compression : Should the data be compressed or not. Enable - Compresses the data to the maximum. It might reduce the rate at which the client can send data to the backup server but it might save significant bandwidth and time when the data is backed up to a remote server over a WAN/Internet with limited bandwidth speed. Also, this saves disk space in the backup server. Disable - This option is suitable (fastest) for backing up data within a local network where bandwidth is not the limitation, but occupies more space on destination machine as no compression is being done. Temporary location to store the backup dumps - Enter the location/directory path to which the Exchange Server database dumps has to be stored temporarily before uploading to the backup server. Please ensure that you have enough disk space in the configured temporary location (where the backup dump has to be saved). If the Advanced Exchange Server Plugin is enabled, backup dumps stored in the temporary location will be deleted once backup dumps are transferred successfully to the remote backup server. For the Basic Exchange Server Plugin backup, this dump file will be maintained locally in client machine for further differential log backups. Step 4: Set Password Protection Password Protect This Backup - This option is to enable or disable encryption of the data that is being backed up. StoreGrid uses the well known encryption algorithm, Blowfish. If enabled, a password has to be specified which will be used for generating the encryption key. 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. Encryption Key Size - StoreGrid supports encryption using variable length (64 to 448 bits) keys. The key is generated using the password you provide. Basically the longer the key size you give the more difficult it is for someone to decrypt the encrypted files. For normal backup purposes the default 64 bit encryption should be good enough. Type Password - Provide a password here to generate the encryption key. 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. Step 5: Full Backup Scheduling (Decide When To Do Full Backup) This step allows you to configure the frequency at which a full backup of the selected database has to be done. A full backup is a complete backup of the selected databases and all necessary log files. Once full backup completes, all log files older than the time when full backup started would be deleted. Since full backups take more time to complete than a differential or incremental log backup, a full backup is typically configured to run weekly or monthly or much less frequently than differential or an incremental backup. Configuring a full backup scheduling is mandatory, i.e. this step cannot be skipped. StoreGrid will do a full backup dump of the Exchange Server database(s) whenever the full backup is scheduled and back it up. This step has the following options from which any one can be chosen. Run Monthly At - Choose the time and day of the month the backup should run. StoreGrid will run the backup every month on the particular day and time chosen. StoreGrid will run at the stipulated time/day only. Run Weekly - Choose the time and the day of the week the backup should run. StoreGrid will execute the backup

132 every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. StoreGrid will run at the stipulated time/day only. Run Daily - Choose the time at which the backup should run daily. This will execute the backup everyday at the time you have provided. StoreGrid will run at the stipulated time only. Run Every Few Hours - Choose the hours/minutes interval between each time StoreGrid must run. If StoreGrid is restarted in the interim, the backup will run once StoreGrid starts. Thereafter, StoreGrid automatically reschedules the next backup after the period you ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, StoreGrid will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, StoreGrid is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am. Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the checkbox against these days. Run Once Only - Choosing this option will do the backup only once at the stipulated time. Step 6: Log Backup Scheduling (Optional Step) Advanced Exchange Server Plugin users will have a drop-down box to optionally choose between Incremental/Differential Log Backups. Basic Exchange Plugin users will be allowed to configure only a Differential Log Backup. StoreGrid will do a Incremental/Differential log backup dump of the database with respect to the previous full or incremental log backup whenever this Incremental/Differential log backup is scheduled. Incremental Log Backup : An incremental log backup backs up only the log files since the last full or incremental backup. Once an incremental backup completes, all log files older than the time when incremental backup started would be deleted. You cannot perform an incremental backup when circular logging is enabled in your exchange server settings. Since only changes are backed up, incremental backups typically run faster than full backups. Also, as only the log files since the last backup are backed up, incremental backups will run faster than differential backups too. Hence incremental backups are always configured to be scheduled more frequently than a full backup. Configuring incremental backup scheduling is optional. Differential Log Backup : A differential backup backs up only the log files since the last full backup even when the last backup was a incremental backup. The logs are not deleted after the differential backup completes. You cannot perform a differential backup when circular logging is enabled in your exchange server settings. Since only changes are backed up, differential log backups typically run faster than full backups. But, as all the log files since the last full backup are backed up, differential backups will take longer to finish than an incremental backup. Hence differential backups are configured to be scheduled more frequently than a full backup. Configuring differential backup scheduling is optional. This step has the following options from which any one can be chosen. Run Weekly - Choose the time and the day of the week the backup should run. StoreGrid will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. StoreGrid will run at the stipulated time/day only. Run Daily - Choose the time at which the backup should run daily. This will execute the backup everyday at the time you have provided. StoreGrid will run at the stipulated time only. Run Every Few Hours - Choose the hours/minutes interval between each time StoreGrid must run. If StoreGrid is restarted in the interim, the backup will run once StoreGrid starts. Thereafter, StoreGrid automatically reschedules the next backup after the period you ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, StoreGrid will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, StoreGrid is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am.

133 Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the checkbox against these days. Step 7: Advanced Options There are four options here on how the backup should be scheduled. Maximum Number Of Full Backups : You can specify the maximum number of full backups that need to be stored in the server. For example if you configured a monthly full backup, then StoreGrid will take a full backup every month. After 6 months you will have 6 separate full backups in the backup server along with differential or incremental logs under each of the 6 full backups. If your policy is to retain only backup data for 6 months, then you can configure "Store maximum of 6 full backups" here. On the 7th month, StoreGrid, after finishing the 7th full backup, will delete the first full backup along with its differential or incremental log backups thus retaining the last 6 months (full) backups. Differential Backup Count : If the Exchange Server differential log backups are configured more frequently [Run every few hours] in StoreGrid Exchange Server backup and the Exchange Server database(s) are changing rapidly, then the clients backup space usage will grow faster. To avoid this, you can specify maximum number of Differential backups to be kept in the server. If the number of differential backups count exceeds this count then the oldest differential backup files are deleted. This option is available only for Basic Exchange Plugin users. 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 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 AM). Attempt to run this backup every 5 minutes in case of non completion because of a problem (Network error etc.) : If enabled, the user can choose to reschedule this backup every 5/10/15/20/25/30 minutes, whenever an attempted backup is incomplete because of a network error, server crash etc. The number of times the backup will be rescheduled (due to an error) can be configured to be in between 1-5 or unlimited, with the default setting as 5. This is to ensure that an incomplete backup is completed as soon as possible without waiting for the next actual schedule time. Note that this option is enabled by default. Saving the configured backup Once all the Exchange Server Storage Group(s)/Mail Store(s) to be backed up are chosen and the configuration options are set, you simply need to click on the "Configure/Save Backup button to activate the backup as per the schedule- on to the configured backup servers. Troubleshooting Tips Exchange Server is not installed or not available in the system. Cause : If Exchange Server services running in the local machine were not detected during StoreGrid installation process. Solution 1: Please verify that the following files "XchangeServer.sgpl" & "ExchangeServer.sgpl" exist in "<StoreGrid_Home>\Vembu\StoreGrid\plugins" folder. If these files don't exist in the location, please try installing StoreGrid on top of the existing installation and check if you were able to create Exchange Server Backup schedule without errors. Solution 2: Open the file "SGConfiguration.conf" file present in "<StoreGrid_Home>\Vembu\StoreGrid\conf\" folder and check the "PluginLicense" attribute value. If the "PluginLicense" attribute value is set to "0", change this attribute value to "1". And then restart StoreGrid from system tray and check if you were able to create Exchange Server Backup schedule without errors.

134 The following message is displayed in the backup report "The database missed a previous full backup before the incremental backup". Cause 1: After a successful restore, if incremental or differential logs backup is performed before running a full backup then Exchange Server backup report will display the above error message. Solution 1: Check the option "Run additional full backup after saving this configuration" in the "Edit Exchange Server Backup Schedule" page to run additional full backup and then proceed with the incremental or differential log backup. Cause 2: If a new MailStore is added to existing Storage Group which was already configured for backup. Solution 2: Check the option "Run additional full backup after saving this configuration" in the "Edit Exchange Server Backup Schedule" page to run additional full backup and then proceed with the incremental or differential log backup. Cause 3: This issue could arise when StoreGrid is trying to run an incremental backup on an Information Store in a Storage Group when at least one of the remaining Information Stores in the Storage Group had not been configured for full backup at least once. In such a situation, Exchange Server will not allow StoreGrid to purge the logs files for the configured Information Store. Solution 3: Configure full backup for the remaining Information Stores temporarily. And later you can delete this backup schedule if this backup is not needed. The following message is displayed in the backup report. "No new/modified files for backup". Additionally in Basic Exchange plugin, Backup report displays "Error occurred while dumping Exchange Server data in [Path *.bkf] file. Please refer the NTBackup log file for error details." Cause 1 : If you try to do an incremental or a differential log backup on a exchange server that has circular logging enabled, Exchange server generates the above error message that the incremental or differential backup cannot be done. Solution 1 : Turn off circular logging do an incremental or a differential log backup. To verify that circular logging is disabled, open Exchange System Manager and navigate through the console tree to Administrative Groups -> your administrative group -> Servers -> your server -> the storage group you want to check. Right click on the storage group, select properties, and verify that the "Enable Circular Logging" checkbox is not selected. Cause 2 : If the temporary dump directory configured for backup schedule doesn't have enough space. Solution 2 : Please ensure that you have enough disk space in the configured temporary location (where the backup dump has to be saved). In Basic Exchange Server plugin backup, dumps stored in the temporary location will be retained for further differential log backup and hence enough disk space should be available in disk before transferring files to remote server. The following message is displayed in the backup report. "Backup is already active". Cause : This message would be displayed in the client backup report in the following conditions : i. If the same Storage Group or the Mail Stores from the same Storage Group configured for backup is backed up by some other process. ii. If StoreGrid is killed or stopped and started immediately, while exchange server data dump was in progress. Then a previous instance of Backup (Ntbackup.exe/ESE API) could still be running in the background and it still has a connection open to the specified service. In this case a second instance will not be able to connect to the exchange server. Solution : Use Task Manager to identify and stop any other instances of Ntbackup.exe that are not responding. In ESE API case, if the failed backup is a full backup, then edit the backup schedule to take an immediate full backup. For other backup schedules click schedule now button in the "List of Backup Schedule" for the backup schedule to take the backup.

135 In NTBackup log file the following message is displayed "NTBackup error: 'The saved selection file "<INSTALL_HOME>\plugins\ExchangeServer\ExchangeServer_<BACKUP_NAME>.bkf" cannot be found.' Cause : This message would be displayed in the NTBackup log files ["C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data" location] in the following conditions: i. The NTBackup's saved selection file does not exist in the basic Exchange Server backup plugin folder "<StoreGrid Home>\plugins\ExchangeServer\" ii. The NTBackup's saved selection file is empty in the basic Exchange Server backup plugin folder "<StoreGrid Home>\plugins\ExchangeServer\" Solution : 1. If the.bkf file doesn't exist, delete the backup schedule and recreate the Exchange Server backup schedule afresh. Please ensure the Exchange Server Information Stores and Mail Stores are listed correctly while configuring Exchange Server backup schedule. 2. If the.bkf file is empty, you can follow either the above step 1 or manually edit the.bkf file to fix this issue by following the instructions given below: i. Open the "<StoreGrid Home>\plugins\ExchangeServer\ExchangeServer_<backup name>.bkf" file in Notepad. ii. Add the Information stores/mail stores details in the following format. a. For configuring all Exchange Server Information Stores, add all the information stores in the following format: JET <Exchange Server Name>\Microsoft Information Store\<Information Store Name 1> JET <Exchange Server Name>\Microsoft Information Store\<Information Store Name 2> JET <Exchange Server Name>\Microsoft Information Store\<Information Store Name 3>... b. For configuring all Mail Stores under a particular Information Stores: JET <Exchange Server Name>\Microsoft Information Store\<Information Store Name>\ c. For configuring particular Mail Stores under a particular Information Stores: JET <Exchange Server Name>\Microsoft Information Store\<Information Store Name>\<Mail Store Name> You can add multiple Information Stores/Mail Stores entries in the.bkf file in each line. d. Save the.bkf file in "Unicode" text encoding format and reschedule the Exchange Server backup schedules. The backup schedule fails with connection failure message [SG083, SG132...] in the backup report. Cause : When StoreGrid is doing the local dump of the exchange server data, the client's socket connection to the backup server will be idle. Depending upon the time the dump process takes, some firewall/router/nat settings may close this idle socket connection after a timeout period. Hence, after the dump process, when StoreGrid tries to transfer the dump file to the backup server, the connection is found to be invalid and the backup schedule fails. Solution : Enable the Keep Alive setting for the backup in the StoreGrid configuration file [<StoreGrid Path>\conf\SGConfiguration.conf] by following the instructions given below:

136 Stop StoreGrid Edit <StoreGrid Path>\conf\SGConfiguration.conf Set the <StoreGrid><Configuration><Module> tag, "KeepAliveEnabled" attribute's value as "1" and set the "KeepAliveTime" attribute value to desired value. Save the configuration file and restart StoreGrid. When I try to create a Exchange Server backup, i can see the Exchange Information Stores but the check box to click on is all greyed out. Reason : If you had configured a Exchange Server Storage Group or an Information Store for backup in a backup schedule, the same should not be configured as a part of another backup schedule [either using Basic/Advanced Plugin] and therefore the checkboxes will be greyed out. The other backup schedule should be deleted first and there after it can be configured for backup in another backup schedule. Exchange server changes the reference of the database dump when two schedules try to backup the same Exchange Database and hence the backed up data of both the backup schedules might become inconsistent and therefore cannot be restored when backed up across two schedules. Limitations 1. If locally dumped Exchange Server backup data is deleted manually while backup is in progress, then StoreGrid will not have the information about the manually deleted file in client machine backup report and in server backup report. 2. Local Dump path configured for Exchange Server backup should not contain special characters like single quote('), double quote("), forward slash(/), backward slash(\), question(?), colon(:), asterisk(*), lesser than(<), greater than(>), pipe( ) and plus(+). 3. If Exchange Server backup schedule is suspended while local dump is in progress, then StoreGrid will suspend the transfer of files to the backup server (till after the local dump process is completed). On resuming the same backup schedule, the dump process will not occur in the next schedule; instead, the locally dumped files will be transferred to server and an error message will be reported in backup report. 4. Please ensure that the dump location configured for the backup schedule has enough space and has valid read and write permission to accommodate the exchange dump data. Also, the dump location (full path) should be less than 256 characters. 5. If the Storage Group or Mail Store is configured as part of one schedule, then it cannot be included in other backup schedules. If Mail Stores under same Storage Group are configured as separate schedules, then enabling Multithreaded scheduling in StoreGrid is not recommended for Exchange Server backups. 6. A Storage Group configured for backup using the Basic Exchange Server plugin cannot be configured with the Advanced Exchange Server Plugin. If required, the schedule has to be deleted first and thereafter configured using the Advanced Exchange Server Plugin. 7. Everytime a new Mail Store is added under a Storage Group of the Exchange Server, then before running a differential or incremental backup, "Additional Full Backup" should be configured to run through the "Edit Exchange Server Backup" configuration. 8. When you try to restore an Exchange Mail Store's full backup which was empty during its first full backup, then restore operation will fail. Hence you should ensure that Exchange Mail Store is not empty when a full backup is scheduled. 9. If NT Backup utility is killed or NT Backup utility is interrupted due to insufficient space in the dump location, then StoreGrid will incorrectly report the Exchange backup status as 'Successfully Completed' in its client side and

137 server side reports.

138 Configure Exchange Mailbox Backup Overview StoreGrid Advanced Exchange Mailbox Plugin backs up users' mailboxes. It can backup at a folder level. You can backup all the data of a particular user (mailbox) or you can backup just a folder (like for example the inbox of an user) or you could backup a sub-folder (like for example, a sub-folder in the inbox). StoreGrid should be running in the machine where Exchange Server is installed to create Exchange Mailbox backups. If multiple Exchange servers are used, then StoreGrid should be installed in all of them. While StoreGrid is backing up, Exchange Server should be running. When StoreGrid is performing a backup, all the services including information store will continue to run normally. StoreGrid Exchange Mailbox Plugin extracts user's mailbox, folder or sub-folder data into separate PST files. The Advanced Exchange Mailbox backup is not an alternative to Exchange Server backup. It instead provides optional granularity to the data to be backed up. Please note that an Exchange Mailbox restore alone cannot recover the Information Store after a disaster. It is most helpful in situations where an user loses an individual mailbox (like contacts, mails, calendar, tasks etc), in which case you don't have to restore the entire server to retrieve the mailbox. It lets you selectively restore just the mailbox, folder or sub-folder you want. The Advanced (Plugin) Exchange Mailbox backup uses MAPI to backup users' Mailbox folders. In the Advanced Exchange Mailbox backup, the data (mailbox, folder or sub-folder) is extracted from the Exchange Server into *.PST files, which are dumped locally and then transferred to the backup server. The locally dumped files are deleted once the files are successfully transferred to the backup server. Note: 1. Usually it is not enough to just backup mail boxes alone. It is recommended that you always configure the storage group for backups. You can have additional mailbox backups under the storage group so that you get additional granularity during restores wherein you can restore only a mailbox that is required. 2. If you just configure only mailbox backups and not configure the full storage group, then if your full exchange server crashes then you will not be able to restore your exchange server at all. 3. The best practice is to configure storage group backups and then configure additional mailbox backups for quick restores. Also for mailbox backups it is better to configure only critical mailboxes and not all mailboxes for backups as the mailbox backups takes a lot of time to backup than the full storage group itself. How to get here in the StoreGrid Web Console? In the top menu, select: "Backup-> Create Exchange Mailbox Backup" Requirements Exchange Server 2000 with Service Pack 3 / Exchange Server 2003 / Exchange Server Exchange Server 2007 support - Since Exchange MAPI interface that StoreGrid uses for mailbox backup is available only in 32-bit version (though Exchange Server 2007 is a 64-bit application), you need to install the Microsoft's 32-bit MAPI client component and 32-bit ESEBCLI2.DLL.

139 Another important requirement is that the user account under which StoreGrid is installed should have enough permissions to access the users' mailboxes. Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access the mailboxes. Exchange Mailbox Backup Configuration Step 1: Schedule Name Enter Backup Schedule Name: Give a name for the backup schedule. StoreGrid supports creating multiple backup schedules each with its own configuration. The backup schedule name uniquely identifies the backup. You can restore the data using the backup schedule name. Step 2: Select Backup Source On the left side of the "Create Exchange Mailbox backup" Page, is the tree with the list of Users and their mailboxes and folders available in the Exchange Server. Select the Users' mailboxes or their folders or their subfolders that need to be backed up as a part of this schedule. The mailboxes, folders and sub-folders will be listed only if advanced version of the SQL + Exchange Plugin is enabled in "Advanced Options > Plugin Settings" page. Step 3: Set Basic Configuration Plugin Type : By default, "Advanced Exchange Mailbox Plugin" label will be listed for this field. This field is noneditable. Backup Type Same Machine: When the users mailbox contain large amount of data, it might take significant amount of time to transfer all the data to a remote backup server over WAN/Internet. In such cases, you can take backup of the Exchange mailbox data to a local external drive connected to the client machine and then physically move the external drive to the backup server location to migrate the data into the backup server. In such cases, you can select the backup type to be 'Same Machine'. Once the data is migrated to the backup server, you will have to perform Local to Remote Migration (under Administration -> Advanced Options) in the client machine to make it to run its backups to the remote server directly thereafter. Please note: You will not be able to restore from the backup data present in the local external drive. It is meant only for quickly moving the large amount data to the remote backup server. Once the data is migrated to the remote server from the external drive, the client can restore from it. Local Backup location: Enter the location/directory path to which the backup has to be stored in the same machine. Please ensure that you have enough disk space in the configured location (where the Exchange Mailbox backup has to be saved). Remote Server: Select this option if you want the backup data to be transferred to a backup server directly when the backup schedule runs. Select Backup Server : This is the list of peers/backup servers on which the backup data can be stored. Unlike the regular data backup schedules in StoreGrid where multiple backup servers are supported, only one backup server is allowed for an Exchange Server backup job. If you wish to configure backup to multiple backup servers, please create separate backup jobs for each server. Set 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

140 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. 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. Set Compression : Should the data be compressed or not. Enable - Compresses the data to the maximum. It might reduce the rate at which the client can send data to the backup server but it might save significant bandwidth and time when the data is backed up to a remote server over a WAN/Internet with limited bandwidth speed. Also, this saves disk space in the backup server. Disable - This option is suitable (fastest) for backing up data within a local network where bandwidth is not the limitation, but occupies more space on destination machine as no compression is being done. Temporary location to store the backup dumps - Enter the location/directory path to which the Exchange Mailbox dumps has to be stored temporarily before uploading to the backup server. Please ensure that you have enough disk space in the configured temporary location (where the backup dump has to be saved). Please note that, backup dumps stored in the temporary location will be deleted once backup dumps are transferred successfully to the remote backup server. Step 4: Set Password Protection Password Protect This Backup - This option is to enable or disable encryption of the data that is being backed up. StoreGrid uses the well known encryption algorithm, Blowfish. If enabled, a password has to be specified which will be used for generating the encryption key. Encrypting data ensures that it cannot be read in the destination machine (backup server) where your backup is stored and this is especially relevant for sensitive information. Encryption Key Size - StoreGrid supports encryption using variable length (64 to 448 bits) keys. The key is generated using the password you provide. Basically longer the key size you give, the more difficult it is for someone to decrypt the encrypted files. For normal backup purposes, the default 64 bit encryption should be good enough. Type Password - Provide a password here to generate the encryption key. 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. Step 5: Full Backup Scheduling (Decide When To Do Full Backup) This step allows you to configure the frequency at which a full backup of the selected users mailboxes has to be done. A full backup is a complete backup of the selected users mailboxe folders. Since full backups take more time to complete than an incremental backup, a full backup is typically configured to run weekly or monthly or much less frequently than the incremental backup. Configuring a full backup schedule is mandatory, i.e. this step cannot be skipped. StoreGrid will do a full backup dump of the Exchange Mailboxes whenever the full backup is scheduled and back it up. This step has the following options from which any one can be chosen. Run Monthly At - Choose the time and day of the month the backup should run. StoreGrid will run the backup every month on the particular day and time chosen. StoreGrid will run at the stipulated time/day only. Run Weekly - Choose the time and the day of the week the backup should run. StoreGrid will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. StoreGrid will run at the stipulated time/day only.

141 Run Daily - Choose the time at which the backup should run daily. This will execute the backup everyday at a time you have provided. StoreGrid will run at the stipulated time only. Run Every Few Hours - Choose the hours/minutes interval between each time StoreGrid must run. If StoreGrid is restarted in the interim, the backup will run once the StoreGrid starts. Thereafter, StoreGrid automatically reschedules the next backup after the period you ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, StoreGrid will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, StoreGrid is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am. Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the checkbox against these days. Run Once Only - Choosing this option will do the backup only once at the stipulated time. Step 6: Incremental Backup Scheduling StoreGrid will do a Incremental backup dump of the users mailbox with respect to the previous full or incremental backup; whenever the Incremental log backup is scheduled. This step has the following options to choose from: Run Weekly - Choose the time and the day of the week when the backup should run. StoreGrid will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of a week. StoreGrid will run at the stipulated time/day only. Run Daily - Choose the time at which the backup should run daily. This will execute the backup everyday at the time you have provided. StoreGrid will run at the stipulated time only. Run Every Few Hours - Choose the hours/minutes interval between each time StoreGrid must run. If StoreGrid is restarted in the interim, the backup will run once StoreGrid starts. Thereafter, StoreGrid automatically reschedules the next backup after the period you ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, StoreGrid will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, StoreGrid is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am. Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the checkbox against these days. Step 7: Advanced Settings There are four options here on how the backup should be scheduled. Maximum Number Of Full Backups : You can specify the maximum number of full backups that need to be stored in the server. For example if you have configured a monthly full backup, then StoreGrid will take a full backup every month. After 6 months you will have 6 separate full backups in the backup server along with incremental backups under each of these 6 full backups. If your policy is to retain only backup data for 6 months, then you can configure "Store maximum of 6 full backups" here. In the 7th month, StoreGrid after finishing the 7th full backup, will delete the first full backup along with its incremental backups and retain the last 6 full backups. Run this backup immediately after saving this configuration (thereafter, Backups will be scheduled as per the schedule stipulated) : If you enable this option, then the backup will be executed once immediately after you save the backup schedule even if it is not the scheduled time. For example, if you configure a daily backup at AM but you have configured the backup at 8.00 AM, then the backup schedule will be run once immediately at 8.00 AM and then as per the daily schedule at AM).

142 Attempt to run this backup every 5 minutes in case of non completion because of a problem (Network error etc.) : If enabled, the user can choose to reschedule this backup every 5/10/15/20/25/30 minutes, whenever an attempted backup is incomplete because of a network error, server crash etc. The number of times a backup will be rescheduled due to an error can be configured to be in between 1-5 or unlimited, with the default setting as 5. This is to ensure that an incomplete backup is completed as soon as possible without waiting for the next actual schedule time. Note that this option is enabled by default. Saving the configured backup Once all the Exchange Mailboxes, folders and/or sub-folders that are to be backed up are selected and the configuration options are set, you simply need to click on the "Configure/Save Backup button to activate the backup. Troubleshooting Tips Advanced Plugin Option is not enabled. You can enable this option from the 'Administration -> Advanced Options -> Plugin Settings' page first before creating an Exchange Mailbox backup. [for Service Provider Edition] Cause : If "Backup -> Create Exchange Mailbox backup" screen is accessed without enabling Advanced Plugin. Solution : Enable Advanced Plugin from the menu "Administration -> Advanced Options -> Plugin Settings". In some cases you may not be able to expand any of the mailbox folders listed in the "Create Exchange Mailbox Backup" page. Cause : This is due to insufficient permissions of the logon account used to perform the Exchange Mailbox backup. Solution : If StoreGrid is installed as service, please ensure that StoreGrid service have full administrative privileges. If StoreGrid is installed with Administrator logon account and still you were not are able to expand the mailbox folders other than your own, please check that the StoreGrid service is configured to start with full administrative rights over the Exchange Server. Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access the mailboxes. Users Mailbox/folder are not listed in the "Create Exchange Mailbox Backup" page. Cause : StoreGrid would fail to list the Exchange Users Mailbox folders for the following reasons. 1. Mailbox which was accessed does not exist in the Exchange Server or invalid logon information being used to list the users Mailbox. 2. Insufficient rights on the Exchange user mailbox. Solution : Exchange Mail Level Backup requires "Full Control" access on the Exchange Server for the user account under which StoreGrid service is running. Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access the mailboxes. Error while dumping the Exchange Mail Boxes. Unable to create the PST file [or] "No new/modified files for backup" Cause : 'MSPST MS' is not configured in the Exchange Server. Solution : Add the 'MSPST MS' service by modifying the MAPISVC.INF file. The MAPISVC.INF file should have the information of the Microsoft Personal Folder store service. If this file does not have this information, then the Exchange Mailbox dump will fail with an error indicating that it was "Unable to create the PST

143 file" [or] "No new/modified files for backup". The MAPISVC.INF file is usually located in the Windows system directory (e.g.c:\winnt\system32\ or C:\Windows\System32\). Verify the file has an entry for the Microsoft Personal Folder store service. You can determine this by looking for the following information. If this information is not in the file then you need to add it in the proper sections: [Services] MSPST MS=Personal Folders File (.pst) [MSPST MS] Providers=MSPST MSP PR_SERVICE_DLL_NAME=mspst.dll PR_SERVICE_INSTALL_ID={6485D262-C2AC-11D1-AD3E-10A0C911C9C0} PR_SERVICE_SUPPORT_FILES=mspst.dll PR_SERVICE_ENTRY_NAME=PSTServiceEntry PR_RESOURCE_FLAGS=SERVICE_NO_PRIMARY_IDENTITY [MSPST MSP] =4e495441f9bfb80100aa0037d96e0000 PR_PROVIDER_DLL_NAME=mspst.dll PR_SERVICE_INSTALL_ID={6485D262-C2AC-11D1-AD3E-10A0C911C9C0} PR_RESOURCE_TYPE=MAPI_STORE_PROVIDER PR_RESOURCE_FLAGS=STATUS_DEFAULT_STORE PR_DISPLAY_NAME=Personal Folders PR_PROVIDER_DISPLAY=Personal Folders File (.pst) For more information about the format of the MAPISVC.INF file see the following Microsoft article: Dump location does not have enough space to export the PST file. Cause : The dump location configured for this backup schedule doesn't have enough free space to store the *.PST files. Solution : Increase the free space or cleanup the used space for the drive which is configured as dump location for this backup schedule. Location configured for dump process can be viewed from the view backup configuration of that backup schedule. Error while creating the dump location <Dump_Location> Cause : The configured dump location for that particular backup schedule is not accessible or StoreGrid does not have enough permission to access the directory. Solution : - Make sure that the dump location drive exist in your StoreGrid client. If that drive exist, provide enough write permission to the user under which StoreGrid is installed. Limitations 1. It is recommended that only critical mailboxes be configured for backup using the StoreGrid Exchange Mailbox Backup. Backing up all the mail boxes individually takes much longer time than backing up the Entire database due

144 to limitations of the MAPI protocol. 2. Local temporary dump location configured for Exchange Server backup should not contain special characters like single quote('), double quote("), forward slash(/), backward slash(\), question(?), colon(:), asterisk(*), lesser than(<), greater than(>), pipe( ) and plus(+). 3. If Exchange Mailbox backup schedule is suspended while local dump is in progress, then on resuming the same backup schedule, the dump process will not occur for the next schedule; instead the partially dumped files will be transferred to server and an error message will be reported in backup report. The schedule after that will proceed to completion. 4. Please ensure that the dump location configured for the backup schedule has enough space and has valid read and write permissions to accommodate the users mailbox dump data. Also, the dump location full path should be less than 256 characters. 5. If an Exchange Mailbox name(user name) contains forward slash(/) or reverse slash(\), that mailbox might not be backed up. You will need to change the full name of that mailbox without the slash characters to get them backed up. 6. If any special charatacter is present in any folder name (present under a user), that character will be replaced with other set of valid characters while creating the dump file.

145 Configure SQL Server Backup Overview StoreGrid supports backup of Microsoft SQL servers using two types of plug-ins: 1. The Basic Plugin and 2. Advanced Plugin. Advanced Plugin is much more flexible and efficient while backing up SQL servers than the basic plugin though basic plugin may be good enough for backing up SQL servers with relatively less amount of data. Basic SQL Server Plugin uses OSQL utility to dump the database(s) and then uploads the locally dumped file to the backup server. Advanced SQL Server plugin uses VDI API to backup database(s) and then uploads the locally dumped file to the backup server. StoreGrid provides three types of backups for SQL Server database : Full, Differential and Transaction Log. Full backup type backs up the entire database. Differential backup type backs up only modified extents since the previous full backup. And Transaction log backup backs up the active portion and truncates the inactive portion of the transaction log. This section will give you information about how to configure MSSQL Server 2000/2005/2008 database(s) backup using StoreGrid. How to get here in the StoreGrid Web Console? In the top menu, select: "Backup->Create SQL Server Backup". SQL Server Connection Settings "SQL Server Connection Properties" page is used to configure StoreGrid with SQL Server connection properties. StoreGrid will use the connection properties to connect to the SQL server while listing the database(s) or while taking SQL Server database(s) backup. SQL Server Instance Name This choice-box will list all the SQL Server instances detected in the local machine. You should choose the instance of SQL Server StoreGrid should connect to. StoreGrid will connect to this instance and list the databases in this instance to enable you to configure backup schedules for the databases. Continue with previous authentication for this SQL Server Instance This option is provided if a user name and password have already been configured for the SQL-Server instance. By default "Yes" option is selected and the "No" option could be used to change the previously saved "User Name" and "Password" values. Authentication Choose the authentication type to connect to the SQL Server instance selected. Windows Authentication : Select this option if you have automatic access to the SQL Server through Microsoft Windows user names and passwords. SQL Server Authentication : Select this option to access the SQL Server with a user name and password that the SQL Server manages. User Name If you have selected the SQL Server Authentication option, specify the user name here.

146 Password If you have selected the SQL Server Authentication option, specify the password here. Next Button If all the authentication parameters are correctly set then clicking the Next button will take you to the SQL Server Backup Configuration page. Cancel Button Closes the "SQL Server Connection Properties" page without accepting the selections. And the UI will display the "List of Backup Schedules already created" page. SQL Server Backup Configuration Step 1: Schedule Name And Database Enter Backup Schedule Name: The first step in configuring the SQL Server backup is to give a name for the backup schedule. StoreGrid supports creating multiple backup schedules each with its own configuration. The backup schedule name will uniquely identify the backup. While restoring your backup data, you need to choose the data to be restored using its schedule name. Plugin Type: Drop-down box will be listed with default value as "Advanced SQL Server Plugin" if the advanced version of the (SQL + Exchange) plugin is currently enabled in "Advanced Options > Plugin Settings" page. With the advanced version of the plugin enabled, user will have an option to choose either the Basic or the Advanced plugin backup for "SQL Server Backup". If the advanced version of the (SQL + Exchange) plugin is currently disabled in "Advanced Options > Plugin Settings" page, then this field will be a non-editable name and set to "Basic SQL Server Plugin". SQL Server Instance Name: This field is a non-editable name of the SQL Server Instance for which the backup needs to be configured. If you want to change the SQL Server instance you need to go back to the SQL Server Connection Properties UI and choose the instance name again. Select Database(s): Select the database name that needs to be backed up. SQL Server databases are classified as Full Recovery, Bulk-Logged Recovery and Simple Recovery Models. When a particular Recovery Model is selected, the databases in the SQL server falling under that Recovery Model will be listed for backup. You can select all of them or individually select the ones you want to backup. If a database is included in a backup schedule, then that particular database cannot be selected in another backup schedule; as the data might get inconsistent when backed up across two different backup schedules. Similarly, a database should not be configured with more than one backup software for the same reason. Select All Databases for this schedule If "Select All Databases for this Schedule" option is chosen, it will include all the databases present in the SQL server. If a new database is later added to the SQL Server, it will be automatically included in this backup schedule. Select All Full Recovery Model databases If "Select All Full Recovery Model databases" option is chosen, it will include all the databases with Full Recovery model from the SQL Server. If a new Full Recovery model database is later added to SQL Server, it will be automatically included in this schedule. The Full Recovery Model provides extensive backup and restore capabilities. Full, differential and Transaction Log backup of the databases are supported.

147 To restore a Full Recovery Model database, a full backup has to be first restored. On top of the full backup, differential and/or Transaction Log backups could be restored to recover the database to the latest backup state. Select All Simple Recovery Model databases If "Select All Simple Recovery Model databases" option is chosen, it will include all the databases with Simple Recovery Model from the SQL Server. If a new Simple Recovery model database is later added to SQL Server instance, it will be automatically included in the backup schedule. The Simple Recovery Model provides the simplest form of backup and restore. Full or differential backup of the databases could be done. Transaction log backups are not available for databases belonging to this model. To restore a Simple Recovery Model database, a full backup has to be first restored. On top of the full backup, differential backups could be restored to recover the database to the latest backup state. Select All Bulk-Logged Recovery Model databases If "Select All Bulk-Logged Recovery Model databases" option is chosen, it will include all the databases with Bulk- Logged recovery model from the SQL Server. If a new Bulk-Logged recovery model database is later added to SQL Server, it will be automatically included in the backup schedule. Similar to a Full Recovery Model database, Bulk Logged Model databases provide extensive backup and restore capabilities. Full, differential and Transaction Log backup of the databases are supported. However, compared to the Full recovery model, which logs all transactions, the bulk-logged recovery model minimally logs bulk operations. Therefore, recovery is possible only to the end of a transaction log backup when the log backup contains bulk changes. Like Full Recovery Model database, to restore a Bulk Logged Model database, a full backup has to be first restored. On top of the full backup, differential and/or Transaction Log backups could be restored to recover the database to the latest backup state. Let me manually choose databases If "Let me manually choose databases" option is chosen, then any databases can be selected for backup irrespective of the recovery model they belong to. If a database does not support Differential/Transaction Log backups, then that Differential/Transaction Log backup will be skipped for that database and the error message will be reported in backup report. The database 'tempdb' need not be configured as part of any of the above mentioned schedules. However, if it was configured for a backup, it will be skipped internally when the backup is scheduled. 'tempdb' is used internally by SQL Server just for saving temporary data. Step 2: Set Basic Configuration Backup Type : In StoreGrid, there are two ways of configuring a SQL Server backup: Same Machine: When the databases contain large amount of data, it might take significant amount of time to transfer all the data to a remote backup server over WAN/Internet. In such cases, you can take backup of the databases to a local external drive connected to the client machine and then physically move the external drive to the backup server location to migrate the data into the backup server. In such cases, you can select the backup type to be 'Same Machine'. Once the data is migrated to the backup server, you will have to perform Local to Remote Migration (under Administration -> Advanced Options) in the client machine to make it to run its backups to the remote server directly thereafter. Please note: You will not be able to restore from the backup data present in the local external drive. It is meant only for quickly moving the large amount data to the remote backup server.

148 Once the data is migrated to the remote server from the external drive, the client can restore from it. Local Backup location:enter the location/directory path to which the backup has to be stored in the same machine. Please ensure that you have enough disk space in the configured location (where the SQL Server database backup has to be saved). Remote Server: Select this option if you want the backup of the databases to be transferred to the remote backup server directly when the backup schedule runs. Select Backup Server - This is the list of peers/backup servers in which the backup data can be stored. Only one backup server is allowed for a MS SQL Server backup job. Unlike regular data backup schedules in StoreGrid(where multiple backup servers are supported), only one backup server is allowed for an MS SQL Server backup schedules. This is due to the reason as follows :- 1. MS SQL server database dump transferred to multiple server might get inconsistent when the backup to one of the servers fail with network errors or server unavailable. 2. MS SQL server changes the reference of the database dump when two schedules try to backup the same MS SQL Server database. Hence both the backed up data might get inconsistent when backed up across two schedules. Set 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. 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. Set Compression : Should the data be compressed or not. Enable - Compresses the data to the maximum. It might reduce the rate at which the client can send data to the backup server but it might save significant bandwidth and time when the data is backed up to a remote server over a WAN/Internet with limited bandwidth speed. Also, this saves disk space in the backup server. Disable - This option is suitable (fastest) for backing up data within a local network where bandwidth is not the limitation, but occupies more space on destination machine as no compression is being done. Temporary location to store the backup dumps - Enter the location/directory path to which the MSSQL Server database dumps has to be stored temporarily before uploading to the backup server. Please ensure that you have enough disk space in the configured temporary location (where the backup dump has to be saved). Please note that, backup dumps stored in the temporary location will be deleted once backup dumps are transferred successfully to the remote backup server. Note - Basic SQL Server Plugin users should configure the temporary dump location in a local drive and not a mapped network drive. Step 3: Set Password Protection Password Protect This Backup - 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 for generating the encryption key. 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. Encryption Key Size - StoreGrid supports encryption using variable length (64 to 448 bits) keys. The key is generated using the password you provide. Basically the longer the key size you give the more difficult it is for

149 someone to decrypt the encrypted files. For normal backup purposes the default 64 bit encryption should be good enough. Type Password - Provide a password here to generate the encryption key. 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. Step 4: Full Backup Scheduling (Decide When To Do Full Backup) Configuring this step is mandatory. StoreGrid will do a full backup dump of the database whenever the full backup is scheduled and back it up. This step has the following options from which any one can be chosen. Run Monthly At - Choose the time and day of the month the backup should run. StoreGrid will run the backup every month on the particular day and time chosen. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Settings, StoreGrid will run at the stipulated time/day only. Run Weekly - Choose the time and the day of the week the backup should run. StoreGrid will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options, StoreGrid will run at the stipulated time/day only. Run Daily - Choose the time at which the backup should run daily. This will execute the backup everyday at the time you have provided. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options, StoreGrid will run at the stipulated time only. Run Every Few Hours - Choose the hours/minutes interval between each time StoreGrid must run. If StoreGrid is restarted in the interim, the backup will run once StoreGrid starts. Thereafter, StoreGrid automatically reschedules the next backup after the period you ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, StoreGrid will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, StoreGrid is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am. Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the checkbox against these days. If the "Select all days" checkbox is checked, then the schedule will be run on all the days of the week. Run Once Only - Choosing this option will do the backup only once at the stipulated time. Step 5: Differential Backup Scheduling (Optional) Configuring this step is optional. StoreGrid will do a differential backup dump of the database with respect to the previous full backup whenever this differential backup is scheduled. This step has the following options from which any one can be chosen. Run Weekly - Choose the time and the day of the week the backup should run. StoreGrid will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options, StoreGrid will run at the stipulated time/day only. Run Daily - Choose the time at which the backup should run daily. This will execute the backup everyday at the time you have provided. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options, StoreGrid will run at the stipulated time only.

150 Run Every Few Hours - Choose the hours/minutes interval between each time StoreGrid must run. If StoreGrid is restarted in the interim, the backup will run once StoreGrid starts. Thereafter, StoreGrid automatically reschedules the next backup after the period you ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, StoreGrid will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, StoreGrid is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am. Step 6: Transaction Log Backup Scheduling (Optional) Configuring this step is optional. StoreGrid will do a transaction log backup dump of the database with respect to the previous backup (full/differential/transaction log) whenever this transaction log backup is scheduled. This step has the following options from which any one can be chosen. Run Weekly - Choose the time and the day of the week the backup should run. StoreGrid will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options, StoreGrid will run at the stipulated time/day only. Run Daily - Choose the time at which the backup should run daily. This will execute the backup everyday at the time you have provided. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options, StoreGrid will run at the stipulated time only. Run Every Few Hours - Choose the hours/minutes interval between each time StoreGrid must run. If StoreGrid is restarted in the interim, the backup will run once StoreGrid starts. Thereafter, StoreGrid automatically reschedules the next backup after the period you ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, StoreGrid will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, StoreGrid is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am. Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the checkbox against these days. If the "Select all days" checkbox is checked, then the schedule will be run on all the days of the week. Step 7: Advanced Options There are four options here on how the backup should be scheduled. Maximum Number Of Full Backups : You can specify the maximum number of full backups that need to be stored in the server. For example if you configured a monthly full backup, then StoreGrid will take a full backup every month. After 6 months you will have 6 separate full backups in the backup server along with differential and transaction logs under each of the 6 full backups. If your policy is to retain only backup data for 6 months, then you can configure "Store maximum of 6 full backups" here. On the 7th month, StoreGrid, after finishing the 7th full backup, will delete the first full backup along with its differential and transaction log backups thus retaining always the last 6 month backups. Differential Backup Count : If the MSSQL Server differential backups are configured more frequently [Run every few hours] in StoreGrid SQL Server backup and the MSSQL Server databases are changing rapidly, then the clients backup space usage will grow faster. To avoid this, you can specify maximum number of Differential backups to be kept in the server. If the number of differential backups count exceeds this count then the oldest differential backup file and the transactions logs taken between that differential backup and its successive differential/full backup job are deleted. The default value is 5 and minimum value is 2. If you are upgraded from StoreGrid 2.1 version, then the older SQL Server backup differential backup files will be deleted automatically when a new differential backup configure.

151 Read and verify the integrity of the backup on completion : If you enable this option, then SQL Server will perform a verification of the backup once it completes. 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 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 AM). Attempt to run this backup every 5 minutes in case of non completion because of a problem (Network error etc.) : If enabled, the user can choose to reschedule this backup every 5/10/15/20/25/30 minutes, whenever an attempted backup is incomplete because of a network error, server crash etc. The number of times the backup will be rescheduled (due to an error) can be configured to be in between 1-5 or unlimited, with the default setting as 5. This is to ensure that an incomplete backup is completed as soon as possible without waiting for the next actual schedule time. Note that this option is enabled by default. Saving the configured backup Once all the SQL Server database(s) to be backed up are chosen and the configuration options are set, you simply need to click on the "Configure/Save Backup button to activate the backup as per the schedule- on to the configured backup servers. Troubleshooting Tips The following message is displayed in the backup report. "SQL Server Backup aborted because of error in getting the virtual device backup configuration. Check your database properties.". Cause : If System resource utilization is high or Multithread backup is enabled in StoreGrid and one more backup is trying to start database dump process at a time. Solution : Adjust the "TimeOut" attribute value of "BeforeRun" tag in the plugin configuration file [<StoreGrid Path>/plugins/AdvMSSQLServer.sgpl] by following the instructions given below: - Stop StoreGrid - Edit <StoreGrid Path>/plugins/AdvMSSQLServer.sgpl - Set the <StoreGrid><Configuration><Module> tag, "TimeOut" attributes value to desired value. - Save the configuration file and restart StoreGrid The following message is displayed in the backup report. "Check registration of SQLVDI.DLL and value of IID. This failure might happen if the DLL was not registered.". Cause : If the mssql server being upgraded from MSSQL Server 7, then there will be a problem in loading dll required for VDI backup. Solution : You need to change the threading model in the registry entry. For more details about this, please refer the following url :- The backup schedule fails with connection failure message [SG083, SG132...] in the backup report. Cause : When StoreGrid is doing the local dump of the SQL server data, the client's socket connection to the backup server will be idle. Depending upon the time the dump process takes, some firewall/router/nat settings may close this idle socket connection after a timeout period. Hence, after the dump process, when StoreGrid tries to transfer the dump file to the backup server, the connection is found to be invalid and the backup schedule fails. Solution : Enable the Keep Alive setting for the backup in the StoreGrid configuration file [<StoreGrid

152 Path>\conf\SGConfiguration.conf] by following the instructions given below: - Stop StoreGrid - Edit <StoreGrid Path>\conf\SGConfiguration.conf - Set the <StoreGrid><Configuration><Module> tag, "KeepAliveEnabled" attribute's value as "1" and set the "KeepAliveTime" attribute value to desired value - Save the configuration file and restart StoreGrid The Basic SQL Server Plugin backup schedule fails with "FULL backup failed for database(s) [DB_NAME]. Check the log file [mssqlsvr_<backup_name>.sql.log] in [LOG_PATH] directory path." error message in the backup report. Cause : If OSQL Utility location is not correct in the "MSSQLServer.sgpl" file located in "<StoreGrid_Home>\plugins\" directory. Solution : Set the OSQL utility location in the Basic plugin configuration file [<StoreGrid_Home>\plugins\MSSQLServer.sgpl] by following the instructions given below: - Stop the StoreGrid application - Find the OSQL utility location. Generally, in the SQL Server 2008 version the OSQL utility will available at "<Installation drive>\program Files\Microsoft SQL Server\100\Tools\Binn" location, in the SQL Server 2005 the OSQL utility will available at "<Installation drive>\program Files\Microsoft SQL Server\90\Tools\Binn" location and in the SQL Server 2000 the OSQL utility will available at "<Installation drive>\program Files\Microsoft SQL Server\80\Tools\Binn" location. - Open the StoreGrid SQL Server plugin configuration xml file located in "<StoreGrid_Home>\plugins\MSSQLServer.sgpl" - Set the value of <BeforeRun> tag "WorkingDir" attribute to OSQL utility location - Save the configuration file - Delete the "<StoreGrid Home>\plugins\mssqlserver" folder - Save the configuration file and restart StoreGrid When I try to create a MSSQL Server backup, i can see the SQL Server database(s) but the check box to click on is all greyed out. Reason : If you had configured a MSSQL Server database(s) for backup in a backup schedule, the same should not be configured as a part of another backup schedule [either using Basic/Advanced Plugin] and therefore the checkboxes will be greyed out. The other backup schedule should be deleted first and there after it can be configured for backup in another backup schedule. MSSQL Server changes the reference of the database dump when two schedules try to backup the same SQL Server Database and hence the backed up data of both the backup schedules might become inconsistent and therefore cannot be restored when backed up across two schedules. Limitations 1. If locally dumped SQL Server database(s) backup data is deleted manually while backup is in progress, then StoreGrid will not have the information about the manually deleted file in client machine backup report and in server backup report. 2. Local Dump path configured for SQL Server database(s) backup is not recommended to have special characters like single quote('), double quote("), forward slash(/), backward slash(\), question(?), colon(:), asterisk(*), lesser than(<), greater than(>), pipe( ) and plus(+). 3. Please ensure that the dump location configured for the backup schedule has enough space and has valid read and write permission to accommodate the SQL Server database dump data. Also, the dump location (full path) should be less than 256 characters. 4. If StoreGrid is killed while SQL Server database(s) backup schedule configured with multiple database(s) dump process is active, then in the next schedule locally dumped files for the database will be transferred to backup

153 server and dump process for the remaining database(s) will be processed in the next schedule. 5. If SQL Server database(s) backup schedule is suspended while local dump is in progress, then StoreGrid will suspend the transfer of files to the backup server (till after the local dump process is completed). On resuming the same backup schedule, the dump process will not occur in the next schedule; instead, the locally dumped files will be transferred to server and an error message will be reported in backup report. 6. In multiple databases backup, if a database does not support Differential/Transaction Log backups, then that Differential/Transaction Log backup will be skipped for that database and the error message will be reported in backup report. 7. Number of differential backups count should be greater than or equal to If the local dump location is configured as a FAT32 disk partition, then the local dump file size should not exceed 4 GB as the FAT32 file system cannot hold file size more than 4 GB. In this case, StoreGrid cannot dump the data files and the backup schedule will fail. 9. If MS SQL Server 2005 Instance is installed along with the MS SQL Server 2008 Instance in the Windows Server 2008 machine, then the value of the "WorkingDir" attribute of "Command" tag will be saved with the MS SQL Server 2008 "OSQL.exe" utility path in the "<Installation_Path>/plugins/MSSQLServer.sgpl" file. If you need to configure MS SQL Server 2005 database(s) for backup using Basic Plugin then the "WorkingDir" attribute value should be changed with the MS SQL Server 2005 "OSQL.exe" utility path in the "<Installation_Path>/plugins/MSSQLServer.sgpl" file. 10. After migrating from older versions of StoreGrid to v2.4, the "OSQL.exe" utility path will not updated automatically in the "<Installation_Path>/plugins/MSSQLServer.sgpl" file for the MS SQL Server 2008 Instance.

154 Configure MySQL Database Backup Overview StoreGrid supports backup of MySQL database(s) using the internal MySQLDump utility(mysqldump) available in the local machine. StoreGrid supports Full and Incremental MySQL database backups while data is online and accessible. Full backup type backs up the entire MySQL database. Incremental backup type backs up only modified extents since the previous Full backup. StoreGrid uses the internal MySQLDump utility(mysqldump) to dump the database(s) and then uploads the locally dumped file to the backup server. During Full backup, the entire database(s) is dumped locally and then transfer the dumped file to the backup server. During Incremental backup, the entire database(s) is dumped locally and then transfer only the modified content since the previous Full backup to the backup server. This section will give you information about how to configure MySQL database(s) backup using StoreGrid. How to get here in the StoreGrid Web Console? In the top menu, select: "Backup->Create MySQL Database Backup" Requirements Windows, Linux or FreeBSD MySQL 4.0 and later. MySQL Backup [For Linux/FreeBSD] To backup the MySQL databases, you need to install StoreGrid with root privileges in your Linux, FreeBSD system and you should know the user name and password for MySQL. By default, StoreGrid checks for 'mysql' under '/var/lib' folder in the system during the installation process. StoreGrid uses the internal MySQLDump utility (mysqldump) to backup MySQL Database(s) in the Linux/FreeBSD machines. Please note that you need to install StoreGrid as root user to list the mysql databases for backup in the 'Backup -> Create MySQL Database Backup' page. If you have installed StoreGrid with root user privilege and if you have installed MySQL in your Linux/FreeBSD machine, then the MySQL databases will be listed in the Step 2 of the 'Backup -> Create MySQL Database Backup' page. Then, you can configure the listed database(s) for backup. Please note that you have to provide MySQL database username and password for the mysql backup to successfully dump the database data. MySQL Backup [For Windows] StoreGrid can be configured to backup the MySQL Database(s) available in the local machine. StoreGrid uses the internal MySQLDump utility (mysqldump.exe) to backup MySQL Database(s) and it uses the MySQL Exe (mysql.exe) to list the database names in the Step 2 of the 'Backup -> Create MySQL Database Backup' page. In Windows, before a MySQL backup can be configured in StoreGrid, you should configure the MySQL settings through "Administration->Advanced Options" and click on the "MySQL Settings" icon in the left hand side. Without correct values for

155 MySQL settings, StoreGrid will not be able to list the databases to be configured for backups in "Backup -> Create MySQL Database Backup" page. If "MySQL" database(s) is not listed in the Step 2 of the 'Backup -> Create MySQL Database Backup' page, then refer the MySQL Settings[For Windows] help for more details. MySQL Backup Configuration Step 1: Schedule Name Enter Backup Schedule Name: The first step in configuring the MySQL backup is to give a name for the backup schedule. StoreGrid supports creating multiple backup schedules each with its own configuration. The backup schedule name will uniquely identify the backup. While restoring your backup data, you need to choose the data to be restored using its schedule name. Step 2: Select Database(s) Select Database(s): Select the database name that needs to be backed up. Select All Databases for this schedule If "Select All Databases for this Schedule" option is chosen, it will include all the databases present in the MySQL server. If a new database is later added to the MySQL Server, it will be automatically included in this backup schedule. Let me manually choose databases If "Let me manually choose databases" option is chosen, then any databases can be selected for backup. However, if a new database is later added to the MySQL Server, it will not be automatically included in this backup schedule. Step 3: Set Basic Configuration Backup Type : In StoreGrid, there are two ways of configuring a MySQL Server backup: Same Machine: When the databases contain large amount of data, it might take significant amount of time to transfer all the data to a remote backup server over WAN/Internet. In such cases, you can take backup of the databases to a local external drive connected to the client machine and then physically move the external drive to the backup server location to migrate the data into the backup server. In such cases, you can select the backup type to be 'Same Machine'. Once the data is migrated to the backup server, you will have to perform Local to Remote Migration (under Administration -> Advanced Options) in the client machine to make it to run its backups to the remote server directly thereafter. Please note: You will not be able to restore from the backup data present in the local external drive. It is meant only for quickly moving the large amount data to the remote backup server. Once the data is migrated to the remote server from the external drive, the client can restore from it. Local Backup location:enter the location/directory path to which the backup has to be stored in the same machine. Please ensure that you have enough disk space in the configured location (where the MySQL database(s) backup has to be saved). Remote Server: Select this option if you want the backup of the databases to be transferred to the remote backup server directly when the backup schedule runs. Select Backup Server - This is the list of peers/backup servers in which the backup data can be stored. Only one backup server is allowed for a MySQL Server backup job. If you wish to configure backup to multiple backup servers, please create separate backup jobs for each server.

156 Set 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 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. Set Compression : Should the data be compressed or not. Enable - Compresses the data to the maximum. It might reduce the rate at which the client can send data to the backup server but it might save significant bandwidth and time when the data is backed up to a remote server over a WAN/Internet with limited bandwidth speed. Also, this saves disk space in the backup server. Disable - This option is suitable (fastest) for backing up data within a local network where bandwidth is not the limitation, but occupies more space on destination machine as no compression is being done. Intelli-Delta 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 "Intelli-Delta 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. Step 4: Set Password Protection Password Protect This Backup - 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 for generating the encryption key. 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. Encryption Key Size - StoreGrid supports encryption using variable length (64 to 448 bits) keys. The key is generated using the password you provide. Basically the longer the key size you give the more difficult it is for someone to decrypt the encrypted files. For normal backup purposes the default 64 bit encryption should be good enough. Type Password - Provide a password here to generate the encryption key. 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. Step 5: Scheduling [Decide when to Backup] This field has the following options from which any one can be chosen. Run Every Few Hours Choose the hours/minutes interval between each time StoreGrid must run. If StoreGrid is restarted in the interim, the backup will run once StoreGrid starts. Thereafter, StoreGrid automatically reschedules the next backup after the period you ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, StoreGrid will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, StoreGrid is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am. Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the checkbox against these days. If the "Select all days" checkbox is checked, then the schedule will be run on all the days of the week. Run Daily Choose the time at which the backup should run daily. This will execute the backup everyday at the

157 time you have provided. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options, StoreGrid will run at the stipulated time only. Run Weekly Choose the time and the day of the week the backup should run. StoreGrid will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. Unless you ve selected the Run this Backup each time StoreGrid restarts option in Advanced Options, StoreGrid will run at the stipulated time/day only. Run Once Only Choosing this option will do the backup only once immediately. 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. Step 6: Pre & Post Backup Commands(Optional) When is this feature useful? If an application has exclusively locked a file and you need to close the application before StoreGrid can backup that file, then you can run a pre-backup command to close the application and then a post-backup command to open the application again after StoreGrid successfully backs up the file. How does this feature work? When ever a backup schedule starts, StoreGrid will start the Pre Backup commands and wait till the timeout value. After completing the Pre Backup commands, StoreGrid will transfer the MySQL database dump files to the backup server. After transferring the MySQL database dump files, StoreGrid will run the Post Backup Commands. Pre & Post Backup command settings: You can provide maximum of 5 Pre Backup commands and maximum of 5 Post Backup commands for each backup schedule. Both the Pre and Post Backup commands are optional. Command Name: This filed is mandatory. This is the command that should be run. The command should be provided with full path. If the command name is in the system command path, then providing full path for the command is not necessary. The command can be an executable file such as application exe, batch files, script files etc. Example: C:\MyTools\myzip.exe. A simple zip tool which compresses the given files or folders. Arguments: You can provide any command line arguments for the command to be executed. Example: For the Command C:\MyTools\myzip.exe, the arguments may be 'High Zip Replace "D:\Project" myproject.zip' [with out quotes]. Here, the High may denote high compression, Zip denotes zip file format, Replace denotes replacing existing files, 'D:\Project' denotes folder to compress and 'myproject.zip' denotes the target compressed file name. Working Path: This field specifies the directory path from which the Command has to be run. If this field is left empty, then the command will be executed from the StoreGrid working path [StoreGrid Home] Example: 'D:\Project'. The command will be executed from the directory D:\Project. Timeout: This filed is used to specify a timeout value, in seconds, for the command to finish execution. StoreGrid will wait for so many seconds for the pre and post command to finish running. If the command still runs beyond the timeout period, then StoreGrid will abruptly terminate the command and will continue with the backup schedule.

158 Please note that if you provide -1 value, then the command will run till completion and StoreGrid will wait till the command completes. If command never completes, then StoreGrid may just infinitely wait without proceeding with the backup schedule. Example: 60. For the myzip.exe command, the myzip.exe command will compress the given project folder up to 60 seconds. If the myzip.exe completes before the timeout period, say 15 seconds, then StoreGrid will immediately continue the next Pre Backup Command [if configured] or continue with the backup schedule. So, the example command will look like below: Command Name : C:\MyTools\myzip.exe Arguments : High Zip Replace Working Path : D:\Project Time out : 60 The whole command will be run up to 60 seconds as below: C:\MyTools\myzip.exe High Zip Replace "D:\Project" Step 7: Retention Policies (Optional) MySQL database(s) are dumped locally and transferred as *.sql files to the backup server. The database dump files are treated as regular files and during Incremental backup, modified content of the dump files since the previous full backup is transferred to the backup server. Therefore multiple versions of MySQL database(s) can be retained in the backup server. StoreGrid cleans up the version files in the backup server based on two major retention policies: 1. Version-Based Retention - Retains multiple version files in the backup server based on the version file count. 2. Time-Based Retention - Retains multiple version files in the backup up server based on the age of the version files. Retention policy for backed up files Version-Based Retention StoreGrid can retain backups of multiple versions of a file based on the version retention count specified. The number of version files to be retained can be specified as any value from 0 to 99 with a default setting of 5. The backup version count can be 0 when the Intelli-Delta Backup is disabled in Step 3. This option is useful when you wish to store just the complete latest version of a file. For example, if the version file retention count is specified as 5, then StoreGrid retains the latest five version files. These files can be restored from the backup server at any point of time. When the sixth version of the file is created, StoreGrid backup server automatically deletes the first version. Note: When Intelli-Delta option is disabled for a backup schedule, StoreGrid will back up the entire file if the file was modified since the last backup schedule. In such a case, StoreGrid will retain multiple versions of the entire file as per the version retention count configure for that backup. Time-Based Retention StoreGrid can retain version files in the backup server based on the age of version files. Default setting is for 1 month, meaning the version files will be retained in the backup server for 1 month(30 days) and then will be removed automatically. The maximum number of versions that can be created during the retention period can also be optionally further configured. There are two options:

159 o o Any number of versions can be created within this retention period - This is the default setting. If enabled, StoreGrid retains all the versions created during the specified retention time period. Restrict the maximum number of versions that can be created within this retention period to 'n'. - If this option is enabled, StoreGrid will clean up the version files based on both; retention time period and maximum version file count. For example, if the retention time period is set to 1 month and maximum version file count is 5, StoreGrid will retain only the last five version files created within the last one month and versions older than one month with be deleted. Retention policy for deleted files This feature is not supported for MySQL database backups. Step 8: Advanced Options If you want to configure some additional advanced options - like, Multiple Full Backups etc. click on the Advanced Options button. 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. In case of the Continuous backup or Run every scheduling options, backups will run each time StoreGrid restarts by default. 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 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 AM). Attempt to run this backup every 5 minutes in case of non completion because of a problem (Network error etc.) : If enabled, the user can choose to reschedule this backup every 5/10/15/20/25/30 minutes, whenever an attempted backup is incomplete because of a network error, server crash etc. The number of times the backup will be rescheduled (due to an error) can be configured to be in between 1-5 or unlimited, with the default setting as 5. This is to ensure that an incomplete backup is completed as soon as possible without waiting for the next actual schedule time. Note that this option is enabled by default. Configure Additional Full Backups Typically, you would do a full backup the first time you backup your data and thereafter only do incremental backups. However, like in a typical enterprise scenario, if you want to run full backups periodically and run the incremental backups in between two full backups, then you can configure the scheduling for how to run the full backups here. For Run Every Few Hours and Run Daily backups, the Additional Full Backup settings will allow you to configure daily/weekly/monthly additional full backups. For weekly backups, only Monthly additional full backups are possible. For Run Once Only backup, you cannot configure additional full backups. Additionally you can specify the maximum number of full backups that need to be stored in the server. For example if you configured a weekly backup and additionally if you configure a monthly full backup, then StoreGrid will take a full backup the first time and then weekly do an incremental backup. The next month, StoreGrid will do a new full backup and subsequently run the weekly incremental backup over this full backup. After 6 months you will have 6 separate full backups in the backup server along with weekly incremental versions under each of the 6 full backups. If your policy is to retain only backup data for 6 months, then you can configure "Store maximum of 6 full backups" here. On the 7th month, StoreGrid, after finishing the 7th full backup, will delete the first full backup along with its weekly incremental backups thus retaining always the last 6 month backups.

160 Saving the configured backup Once all the MySQL Server database(s) to be backed up are chosen and the configuration options are set, you simply need to click on the "Configure/Save Backup button to activate the backup as per the schedule- on to the configured backup servers. Troubleshooting Tips Database names are not listed in the Step 2 of the 'Backup -> Create MySQL Database Backup' page(for windows). Cause 1: If MySQL Settings for StoreGrid is not configured. Solution : Configure MySQL settings from "Administration->Advanced Options" menu "MySQL Settings" icon in the left hand side and then check if MySQL database(s) are listed in the "Backup -> Create MySQL Database Backup" page (for windows). Cause 2 : If MySQL service is not started in the machine. Solution : Start the MySQL service and then check if MySQL database(s) are listed in the "Backup -> Create MySQL Database Backup" page (for windows). Cause 3 : When the last time MySQL Settings was saved for mysql server instance port, MySQL Exe path field value was not modified/edited, or may be an older version (MySQL 4) exe path value was entered for the newer version (MySQL 5) port. Solution : Enter the correct MySQL(version) Exe path value for the mysql server instance port selected. Cause 4 : mysqldatabase.lst file present in the "<SG_HOME>/plugins/MySQLServer/" folder does not have the database list. Solution : Check the MySQL version running in the machine (4.x or 5.x). StoreGrid only supports listing MySQL 4.x and 5.x database(s) for backup. Database names are listed in the Step 2 of the 'Backup -> Create MySQL Database Backup' page, but backup dump is not created. Cause : Configured username and password in the MySQL settings page may not have access to the database(s) configured for the backup schedule. Solution : Check if the user name and password entered in the MySQL settings have appropriate permissions to take a backup dump of the database(s). MySQL Server backups failed after recovering StoreGrid client configurations from backup server through Client Disaster Recovery option.(for Windows) Cause : MySQL Server details(username, Password, PortNumber) are not available in StoreGrid client machine. Solution : In this case, save the MySQL Server details in MySQL Settings[For Windows] page before retrieving client configuration through Disaster Recovery option. Limitations 1. Databases listed in the "Backup -> Create MySQL Database Backup" page(for Windows) will be for the the last saved MySQL Server instance port in the MySQL Settings. 2. MySQL Settings edited/modified will not affect the mysql database backup schedules configured previously and

161 changes will take effect only for the new mysql database backup schedules created. 3. Backup Report/View Backup/Edit Backup UI pages does not provide the details like MySQL Server name, port etc.

162 System State Backup/Restore for Windows 2008 Overview Unlike System State backup in older version of Windows (which uses NTBackup), System State backup in Windows 2008 is supported through a command line backup utility called WBAdmin.exe. NTBackup is not supported on Windows It is not just the utility that is different for System State backup in Windows This document describes the aspects of System State backup that is specific to Windows System State Backup 1. The dump location should be in a non-critical drive For the Windows 2008 system state backup, the dump location in the client machine where the WBAdmin will dump the data (before StoreGrid backs up to the backup server) should be a non critical drive it cannot be the drive where Windows is installed and it cannot be the drive where StoreGrid is installed. Like for example, if Windows is installed in C:\ drive in a machine and if StoreGrid is installed in D:\ drive, then neither the C:\ nor the D:\ can be specified as the dump location. Also, the location specified has to be the root of the drive, not a folder inside the drive. For example, you cannot specify the dump location as D:\dump_loc; it has to be just D:\. 2. Size of the dump could be huge System State in Windows Server 2008 backup is typically huge. The number of files backed up could be as many as 50,000 or even higher. The backup could take an hour or more to complete. The size of each backup (full or incremental) could easily be several GBs in size. 3. Incremental backups will upload the entire data WBAdmin, which dumps the Windows 2008 system state data, creates the dump files and folders with distinct names during each backup (full or incremental). During every back the file/folder names of the dump are different and also the file/folder names have to be preserved as created by WBAdmin for the backup data to be restorable. Since the file/folder names change during each backup, StoreGrid will not be able to run Intelli-delta (backup only changed bytes) on them and will therefore upload the entire data every backup (full or incremental).

163 4. Running additional full backups may be unnecessary As explained above, since even the incremental backups always upload the entire backup data, doing additional full backups may not be required. Restoring System State backup Restoring Windows 2008 system state backup is a 2 step process. Restore the system state backup data from the backup server into a folder in the client machine. Using wbadmin tool apply the restored backup data into the machine. (Details on restoring System State data on windows 2003) Note: Before restoring the system state backup from StoreGrid, please confirm whether the backup contains *.vhd files by expanding the restore tree in the restore backup page. If vhd file is not listed, then it could be that the backup failed and is incomplete. Please follow the below steps to recover the system state: i. Restore System State backup data from StoreGrid web console. ii. wbadmin identifies the restored system state backup data if it has the following directory structure. <Restore_drive>/Windows Image Backup/ If you have restored the system state backup in alternate location, then copy Windows Image Backup folder to the parent drive. Once the dump is available in restore location, using wbadmin tool you can restore the system state. Follow the steps mentioned below to restore the system state from the restored backup data. a. At the command prompt, type wbadmin get versions -backuptarget:<restore_drive> to get the version of the backed up system state data and press Enter. For example, consider you have the restored dump data in <restore_drive>/windows Image Backup then give the command as shown in the screen shot below:

164 This gives the backed up version of the system state backup. b. Copy the Version Identifier value. c. In the Command Prompt window, enter the command wbadmin Start SystemStateRecovery -version:<version Identifier> -backuptarget:<restore_drive> For example: wbadmin Start SystemStateRecovery -version:11/25/ :30 -backuptarget:d: d. If the command was entered properly, a confirmation will be required to start the System State recovery. Type in 'Y' to accept the System State recovery, and press Enter to start the System State recovery process. e. The System State recovery will take several minutes to complete. f. Once the system state recovery completed, it will prompt you to reboot the system g. After the machine reboots, it confirms the system state recovery is completed and press Enter to continue. Press Enter.

165 Troubleshooting Tips Please enter the drive name as dump location for Windows2008 System State backup. Folder/filepath cannot be entered as the dump location. Cause : StoreGrid uses the wbadmin tool to dump the system state which dumps the system state backups under the parent drive only. Like for example, the dump location can be D:\ and not D:\dump_loc\. Also, the dump location cannot be a mapped drives or a network shared folder. Solution : Please give the root location of the drive as the dump location. Like for example, the dump location can be D:\ (provided D: is a non-critical drive where neither Windows nor StoreGrid is not installed) The system root drive cannot be configured as the System State backup's dump location in Windows 2008 client machines. Cause : The dump location for Windows 2008 System State backup cannot be the drive where Windows is installed. Solution : Provide the dump location as the drive where neither Windows nor StoreGrid is installed (non critical drive). Windows Server Backup is not installed in your System. Please install and try again. Cause : StoreGrid uses Windows server backup feature to backup the system state in Windows If this is feature is not installed then you will get this error. Solution : Windows server backup is available in windows 2008 by default. However, if it is not installed, then you need to install it. Please follow the below steps to install Windows server backup feature a. Click Start, click Server Manager, in the left pane and then click Features. Then in the right panel click Add Features. This opens the Add Features Wizard b. In the Add Features Wizard, on the Select Features page, expand Windows Server Backup Features, and then select the check boxes for Windows Server Backup and Command-line Tools. You will receive a message that Windows PowerShell is also required to be installed with these features

166 c. Click Add Required Features, and then click Next. d. On the Confirm Installation Selections page, review the choices that you made, and then click Install If there is an error during the installation, it will be shown in the Installation Results page. Please check dump location has enough space or any other dump is in progress. To identify the reason run StoreGrid in command prompt

167 Cause 1: If the dump location doesn't have enough space to store the dump data. Solution : Please give drive name that has enough space to store the dump files. Cause 2: If already system state dump is in progress. Solution : Open Task Manager and check whether the process 'Wbengine.exe' or 'wbadmin.exe' is running. If so, kill those processes and schedule the backup again. Cause 3: If the dump location is the StoreGrid installation location. Solution : Run StoreGrid in command line and schedule the system state backup and check if any error message shows up. If it shows that the given dump location is a critical volume (i.e., other than system drive) then check StoreGrid installation location. Make sure you give the dump location as the drive where neither Windows nor StoreGrid is installed. Cause 4: If VSS is diabled. Solution : Run StoreGrid in command line and schedule the system state backup and check if an error message Catastrophic failure (as shown in the screen shot below) shows up. Please enable VSS and try again. Limitations 1. You can't dump System State data to Critical volume (system drive). 2. You can't dump System State data to the drive where the StoreGrid is installed. 3. The dump location should have enough space. On a 32-bit system, the system state image runs about 6.5GB!. 4. wbadmin tool need to be enabled manually. 5. You can't configure the dump location as a network shared folder/ mapped drive /tape drive. 6. If the given dump location is CD/DVD, confirm that there is a media which is writable during backup. 7. VSS services must be enabled.

168 8. wbadmin tool always gives full dump of the system state with the folder name as backup-timestamp and StoreGrid treats this folder as new folder. Hence it consumes space as much as the full backup consumes. 9. Do not restore the incomplete backups. Before you restore please check whether *.vhd file is available in restore tree. 10. While restoring, make sure you select one incremental to restore. If you select multiple incremental backups in a single restore, the restore data size will be huge. Remember, each incremental could be as large as 6 GB.

169 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 or to use the Volume Shadow Copy Service. Please note that, since StoreGrid 2.2 Release, StoreGrid supports Volume Shadow Copy Service based open file backups in Windows XP/2003/Vista OSes. For other Windows OSes, you have to use the StoreGrid's Open File Plugin. 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

170 Outlook Backup If you ve created a StoreGrid schedule to backup your Outlook data ( s, 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 or to use the Volume Shadow Copy Service. Please note that, since StoreGrid 2.2 Release, StoreGrid supports Volume Shadow Copy Service based open file backups in Windows XP/2003/Vista OSes. For other Windows OSes, you have to use the StoreGrid's Open File Plugin. Please see 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.

171 Windows Mail Backup Overview As a part of Windows Mail backup StoreGrid can backup mails, accounts, Windows Mail settings, calendar and contacts. While configuring Windows Mail Backup with StoreGrid, one should be aware of the following points: 1. To backup Windows Mail, VSS option should be enabled to backup the data without having to shutdown Windows Mail. This is because Windows Mail database and temporary log files are exclusively locked by Windows Mail application. 2. Database and log files might be skipped if VSS is disabled and if the backup is run while the Windows application is running. To run a successful backup with VSS disabled, Windows Mail application should be closed before the backup process starts. 3. In Windows Vista, to initiate VSS based Backup, windows user needs Administrator user privileges (or at least Administrator group privileges) to run StoreGrid. Otherwise, StoreGrid will skip the Windows Mail database and other log files for backup. If the user doesn't have administrator privileges, then Windows Mail should be closed before the backup process to complete the backup successfully without skipping any files. Backup Privilege In Windows Vista, there are two types of Users - Standard Users and Administrator. Standard Users have less privilege and they don't have access to the system resources such as ("%programfiles%", "%windir%" and "HKLM\Software" in Registry entries). Accessing these files/folders needs security elevation. "Administrator" user has rights to access all system resources. In Windows Vista, if administrator user is logged in as a Standard user, the Administrator user gets only Standard access token and when the Administrator user accesses those resources, the use would also need security elevation. Deleted/Moved Mails Notification Windows Mail uses ESE (Extensible Storage Engine) Technology for indexing. Every single mail is stored as a flat file (*.eml file). If a user deletes a mail from "Inbox" folder, then the.eml file corresponding to that mail will be deleted from the "Windows Mail" folder. Directory Monitoring should be enabled in StoreGrid to notify if mails were deleted/moved to other folder in the Windows Mail application. Backup process while Windows Mail application is in use (open) Windows Mail uses ESE(Extensible Storage Engine) Technology to store the mails in the client system. ESE Technology uses edb.log and edb.chk point files to avoid the database inconsistency caused by power failure, system crash and archive the ACID Prosperity. Hence, Windows Mail logs all the transactions in the log file and at the end, updates all the transaction to Windows Mail database while closing the Windows Mail application. The details of mails deleted or moved are initially stored in the log files by Windows Mail application. These log files will be committed to the database files when the Windows Mail application is closed. StoreGrid will backup the database files as well as the log files. During restore, StoreGrid will restore the database as well as the log files. However, after restore, unless the log files are committed to the database (by closing the Windows Mail application), the information stored in the log files such as read mails, deleted mails, mail moved to different folder etc will

172 not be available. Therefore, after restore read mails may show up as unread, deleted mails may be still present and moved mails may still be in the old location. However, these details will be appropriately updated once the Windows Mail application is closed and opened once. Best Practice Configure Windows Mail backup using StoreGrid with "Automatic Directory Monitoring" and "Volume Shadow Copy Service (VSS)" options enabled in Windows Vista machines. Configure hourly/daily/weekly incremental backups with weekly/monthly additional full backups. Trouble shooting Tips I have deleted some mails from my inbox folder, but still these mails are listed in the restore tree and not showing up as deleted. Cause 1: This problem will occur if Automatic Directory Monitoring option has been disabled for the Windows Mail backup schedule. Solution 1: Edit and save the configured Windows Mail backup schedule by enabling "Automatic Directory Monitoring" option in the "Advanced Options". The deleted mail notification will then be propagated to the backup server and the mails will be listed as deleted files in the restore page. Cause 2: If Windows Mail default storage location had been changed after configuring the Windows Mail backup using StoreGrid. Since StoreGrid will look for the deleted/moved mail notifications in the old Windows Storage location, this new Storage location will not be updated in the "Automatic Directory Monitoring" list. Solution 2: Edit and save the configured Windows Mail backup schedule without modifying existing backup configurations. The new Windows Mail storage location will then be updated in the "Automatic Directory Monitoring" list. Now the deleted mail notification should be propagated to the backup server and should list them as deleted files in the restore page. Windows Mail Backup fails to dump the registry entries in the local dump location <SG_HOME>/data/Windows Mail/{UserName}/WindowsMailBackup.reg. Cause : Windows user may not be having enough permissions to access the {SG_HOME} Dir. Solution : StoreGrid should be run with Administrator privileges. Windows mail does not shutdown properly. Cause : After restoring the files from Windows Mail backup, sometimes you might see the error "Windows mail does not shutdown properly" on starting Windows Mail application. Solution : This is a harmless error and Windows Mail will recover automatically. Problem occurs in backing up the Windows mail files and folders while Windows Mail application is in use. Cause : Windows Mail databases, logs and check point files are exclusively locked by Windows Mail when it is open. To backup those files using StoreGrid, Windows Mail should be closed or StoreGrid should use Volume Shadow copy Services to backup. Solution : Enable Volume Shadow copy Services for that backup configuration. Note :If the backup skips some files even after enabling VSS, then check whether the user has Administrator privileges. Limitations

173 1. Windows Mail database and temporary log file might be skipped even if VSS is enabled for backup when Windows Mail rejects StoreGrid's read request of its database. This might happen when Windows mail is about to open the database while StoreGrid backup is in progress. The files that are skipped will however be backed up in the next schedule. 2. VSS snapshot error might occur for Windows Mail temporary files(tmp.edb) and some deleted mails. These temporary files will be created at the time of closing/opening the Windows Mail application. StoreGrid will search for these temporary files listed for backup and generate VSS snapshot error if these files were not found for backup. 3. Temporary files(tmp.edb) may be sometimes skipped with the error "Error in Signature file"

174 NTFS Permission Backup Overview NTFS permission backup feature has been designed to backup and restore users/groups NTFS permissions of the files configured for backup. This feature will work only on a Windows OS with NTFS file system. How to get here in the StoreGrid Web Console? In the top menu of Backup Client, select: "Backup -> Add Backup Schedule". page. NTFS Permission Backup Backup/Restore of NTFS permission is of two types: Plugin and File level. Plugin Type StoreGrid uses a third party tool called "Subinacl" to backup and restore the NTFS Permissions. Users must install Subinacl tool before using this feature. StoreGrid uses the "Subinacl" tool to dump the NTFS permissions and uploads the dump file to the backup server. During restore, StoreGrid will restore the dump file first and then using "Subinacl" it will restore the NTFS permissions of the files and folders automatically. Click here to download Subinacl. Server Side and Third party Restore are not supported with this plugin. Also, it cannot backup the permissions of the parent directory File Level In this type of NTFS permission backup, StoreGrid backs up the NTFS Permissions as it backs up the files. The user needs to enable the option "Backup NTFS Permissions for the files and folders configured (if applicable)." in "advanced option" while configuring a backup schedule. By default this option will be disabled. The permissions are restored along with files. StoreGrid will not restore the NTFS Permissions during Server-Side and Third Party Restore.

175 Advanced Filter Settings Overview This feature enables you to filter files/folders in a backup schedule by choosing the appropriate options in the available select boxes and entering the plain text that should be matched with the file/folder name "starts with/contains/ends with" that text. How to get here in the StoreGrid Web Console? In the top menu of Backup Client, select: "Backup -> Add Backup Schedule" page. Then click the "Files/Folders Filter" button available below the files/folders tree in Step 2. Or select "Backup -> List Backup Schedules" page. Here click on the Edit icon and then the "Files/Folders Filter" button available below "List of files and folders selected for backup". Advanced Filter Settings In advanced file/folder filters you can either specify text patterns or enter the file/folder name you want to include/exclude. You can specify text patterns matching specific file and folder names that you want to include or exclude. Like for example, you can add a filter to include only those files whose names start with 'a' under the selected folders or in their immediate sub folders. As another example, you could specify a filter to exclude folders whose names contain the text 'temp'. You can also enter the file/folder name with or without absolute path. Like for example, if you enter the filename test.txt, then all files with the name "test.txt" under the selected directories will be matched. If you enter the entire path C:/Document and Settings/temp/test.txt, then only that specific file will be matched. You can specify maximum 5 filters. The filters work independently of each other; i.e., if you have a filter to include files starting with 'a' and another filter to include files starting with 'b', then the backup will include files starting with 'a' and files starting with 'b'.

176 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? Overall Progress Backup Name - Displays the backup schedule name. Backup Server - Displays the name of the backup server to which the backup data is being transferred. Warning - Displays any error or warning messages generated during the current backup progress. Reconnection Error - When the connection between the client and the backup server is interrupted, the appropriate error message is shown here. Reconnection Attempts - The number of times the connection between the client and the backup server was interrupted. Bandwidth Throttling - Rate configured at the client/server to restrict the bandwidth usage. Files Processed - The total number of files that StoreGrid has uploaded (new files or modified files) or ignored (unmodified since last backup) so far. Transfer Rate - Displays the transfer rate of the backup data being transferred to the server. Original Size - The original size of the backup data transferred so far. Compressed Size - Displays the compressed size of the original backup data. Messages - Displays the current backup progress message. Added Files - Displays the number of newly added files backed up so far. Modified Files - Displays number of files which were modified since the last backup schedule and have been backed up in the current backup schedule. Skipped Files - Displays the number of files that is skipped for backup. StoreGrid could skip a file for reasons such as: a. Not enough permission to read the file,

177 b. The file is being modified when the backup of the file happens. Skipped Folders - The number of folders that could not be backed up. Some of the reasons why a folder may not be backed up are: a. The folder did not have appropriate permissions for StoreGrid to read. b. The folder may have been modified while StoreGrid is trying to backup it up. c. The folder may have been temporarily available when StoreGrid listed the folders to backup but was later not available when StoreGrid tried to backup. Current Progress Deleted Files - Displays number of files which were deleted since the last backup schedule and the delete notifications have been processed in the current backup schedule. Processed (so far) - Displays the size of the file being processed for transfer with the original file size. Transfer Rate - Displays the transfer rate of the file currently being transferred to the server. Time Left - Displays the estimated time of completion of file transfer for the file which is currently being transferred. Uploaded Size - Displays the total number of bytes transferred to the server as part of the current file. Current File - Displays the current file that is being transferred. 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.

178 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 "Action", you will see a suspend/resume icon for each backup schedule listed. Clicking on the suspend icon will suspend the backup (and the icon will change to resume icon ). Clicking on the resume icon will resume the backup and schedule it as per its schedule. However, a resumed backup will also run once immediately and thereafter as scheduled. 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, click on the edit icon in the Action column of the backup schedule that you want to edit. This page is used to edit a configured backup schedule. Note that only some of the configuration options are editable. More specifically, the following options are not editable: 1. Backup name 2. Backup Type 3. Local Backup location (for Same Machine backup) 4. Intelli-Delta Backup 5. Compression type 6. Encryption (and password) Note: If the hostname of the backup server has changed, don't change the backup server by editing the backup schedule. Perform Client Side Local to Remote migration instead Limitations - Some of the backup schedule parameters cannot be edited as allowing these to be edited could make the new backup data and the old backup data (already backed up) incompatible.

179 Edit SQL Server Backup Schedule Overview This section will give you information about how to edit a configured Basic/Advanced SQL Server backup schedule in StoreGrid. How to get here in the StoreGrid Web Console? In the top menu, select: "Backup->List Backup Schedules". From the list of backup schedules, click on the edit icon in the Action column of the MS SQL Server backup schedule that you want to edit. Edit SQL Server Backup Schedule This page is used to edit a configured MS SQL Server backup schedule. Note that only some of the configuration options are editable. Edit the SQL Server backup schedule details as required. The following options are editable: Select Database(s) - This option allows you to add/remove SQL database[s] from an existing backup schedule. The database(s) can be selected based on recovery model. CPU Utilization settings. Full Backup Scheduling settings. Differential Backup Scheduling settings. Transaction Log Backup Scheduling settings. Max. No. of Full backups to be retained in the server. Max. No. of Differential backups to be retained in the server. Read and verify the integrity of the backup on completion. Run this backup every 5/10/15/20/25/30 minutes in case of non completion because of a problem(network error etc.). The number of times the backup will be rescheduled(due to an error) can be configured to be in between 1-5 or unlimited, with the default setting as 5. Temporary location for backup dumps. The following options are additional configurable options: Run additional full backup after saving this configuration : When this option is selected StoreGrid will take an additional full backup for the SQL Server database(s) configured in this schedule after saving this configuration. Suspend Backup This option shows the status of this backup schedule, whether it is suspended or not. And the same option can be used to suspend the backup schedule. Please note that the following options are not editable:

180 1. Compression type. 2. Encryption (and password). 3. Backup Server(s). Limitations Some of the backup schedule parameters cannot be edited. Editing settings like compression and encryption will make the new backup data and the old backup data (already backed up) incompatible.

181 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, click on the view icon in the Action column of the backup schedule that you want to view. Very simply, this page displays details on schedules you ve previously configured!

182 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, click on the delete icon in the Action column of the backup schedule that you want to delete. From this page you can delete the backup schedule in the client along its backup data in the backup server. The following options are configurable before proceeding with the delete operation: 1. What to delete i. Backup Schedule & Data - If you choose this option, the backup schedule in the client and the backup data in the backup server will be deleted. Delete backup schedule (from client) even if server is down If you select yes, then the backup schedule in the client will be immediately deleted and a request to delete the backup data will sent to the backup server. If the backup server is down, an alert will be shown that the backup data could not be deleted and you will then have to manually delete the backup data from the backup server. If you select 'No' for this option, the backup schedule in the client will not be deleted unless the backup data in the backup server is deleted. The client will send a request to the backup server to delete the data and if the backup server is down, the client will again send the request after 5 minutes. The number of times the client should try resending the delete request can be configured through the DeleteSchedule entry in the SGConfiguration.conf file. By default, it is 5. ii. Backup Data only - If you choose this option, it will only delete the backup data from the server and the backup schedule will remain in the client. Delete specific files only No, delete all files in this schedule - All the backup data of this backup schedule will be deleted in the backup server. Yes, let me choose files to delete - You will be taken to a different page where you can select the specific files that you want to delete. This option will not be available for 'Same Machine' backups. 2. Backup server(s) from which the backup data is to be deleted. 3. If the backup is password enabled, then you need to provide the password too. 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.

183 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. Permanently Deleting Only Specific Files from the Server After providing the required parameters, select the radio button "Backup Data only". You will see a choice "Delete specific files only?". Select the radio button "Yes, let me choose files to delete" for that choice. When you select that radio button, StoreGrid will list the backup data tree which will help you to filter the files and then delete the data. Permanently Deleting All Files from the Server After providing the required parameters, select the option "Backup Data only" and then select "No, delete all files in this schedule" and then click the delete button. Your backup data will be deleted in the selected backup servers. 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. The number of times the delete operation will be rescheduled depends upon the DeleteSchedule entry in the SGConfiguration.conf file.

184 Permanently Delete Files from Server How to get here in the StoreGrid Web Console? In the top menu, select: "Backup->List Backup Schedule". This will list the list of backup schedules configured in a table format. From the backup schedule row for which files have to be deleted permanently from the server, click on the delete icon in the Action column. This will take you to the "Delete Backup Data/Schedule" page. select the radio button "Backup Data only". You will see a choice asking as "Delete specific files only?". Select the radio button "Yes, let me choose files to delete" for that choice. To delete specific files and folders of a backup schedule permanently from the backup server, you need to follow the steps below: Step 1: Select The Backup Name And The Backup Server - The backup name is a non editable field here. The backup server will also be non-editable if the backup schedule is backing up to only one server. If the backup schedule is backing up to more than one server, then you need to choose the server here from the choice box. Step 2: Select Version To Delete - Here all the full backups that have been taken are listed with the timestamp when each of these full backups was taken. If the backup schedule was not configured with multiple full backups, then this list will have only one entry - that of the first full backup. You can choose any full backup based on the timestamp for deletion. Note that the tree in Step 3 loads with the files/folders based on what full backup you choose here. Also, by default the tree in step 3 is loaded for the latest full backup of the backup schedule. Step 3: Select Files And Folders - Here is where you have to select the files/folders to be permanently deleted from the server. You can filter the tree by entering a wild card (*.doc etc.) in the Filter files/folders text field. Note that the tree will not list the number of versions of each file. The idea is if you delete a file permanently from the server, then all its versions under the chosen full backup (in Step 2) will be deleted. Step 4: Confirm Delete Settings - You need to provide the following inputs here: 1. If your backup schedule is password protected, you need to provide the password here. 2. If you check the "Remove Deleted Files Only" checkbox, then the delete operation will delete only the files on the server that have been deleted in the the client machine. That is, if a file has been deleted by the user in the client, then StoreGrid client would have saved the information that the file has been deleted in the client. The StoreGrid server in turn would tag the file as deleted. So, by checking this checkbox, you are configuring deletion of only deleted files. This feature is useful as you can select the entire Root Drive in the tree and check this checkbox and perform the delete operation. The server will only permanently delete the files tagged as deleted in the client.

185 Client Deleted Backup Report How to get here in the StoreGrid Web Console? In the top menu, select: "Backup->Deleted Backups" This page gives a status report of the delete backup operations initiated by this StoreGrid Client. The following information is provided in the report for each delete operation scheduled/executed. Backup Schedule Name - This is the backup schedule name (for which the delete operation was scheduled) Backup Server(s) - The backup server on which this schedule's backup data is to be deleted. Status - This gives the status of the delete operation. Deleted Time - The time at which the delete operation was scheduled. Total Time Taken - Time taken to execute the delete operation. Attempts - The number of times StoreGrid attempted to execute the delete operation (this is more than 1, if there was a problem performing the delete). Deleted Files - When few files are permanently deleted from the server, the file count is listed here. If all backup data is deleted, the file count will not be available. Message - This is any remarks StoreGrid has on the delete operation.

186 StoreGrid User Plugins for Backups StoreGrid supports creating custom plugins for backups. These plugins are useful where before and after a backup is done you need to run a command. For example, the command may interface with an application and create some files/folders which need to be backed up by StoreGrid. The user plugin is configured by creating an XML file. The following describes with an example how the XML file is created and how you can integrate the plug-in with StoreGrid. Step 1: Creating the plugin XML file The plugin XML file (say, TestPlugin.sgpl) has to be created under the "plugins" directory under the StoreGrid Installation Directory. Note that you can create any number of plugins and each plugin file has to be in a different name. The plugin created here will automatically appear in the Backup Configuration Tree in the "Add Backup Schedule" page. Step 2: Editing the plugin XML file The following plugin XML file is used to illustrate how a user plugin is created in StoreGrid. <StoreGrid> <SGPlugins> <Plugin Name="TestPlugin" IsValid="1"> <BeforeRun Command="D:\joe\work\zipSource.bat" WorkingDir="D:\joe\Backup" TimeOut="180000"/> <BeforeRun Command="D:\joe\work\zipData.bat" WorkingDir="D:\joe\Backup" TimeOut="180000"/> <AfterRun Command="D:\joe\work\cleanSourceBk.bat" WorkingDir="D:\joe\Backup" TimeOut="180000"/> <AfterRun Command="D:\joe\work\cleanDataBk.bat" WorkingDir="D:\joe\Backup" TimeOut="180000"/> <BackupPath> <Path Name="D:\joe\Backup\workSource.zip"/> <Path Name="D:\joe\Backup\workData.zip"/> <Path Name="D:\joe\Backup\MiscFiles"/> </BackupPath> </Plugin> </SGPlugins> </StoreGrid> Plugin Tag : This tag is used to configure the following attributes for the plugin Name - This is used to give a name for the plugin. This name will appear in the backup configuration tree in the "Add Backup Schedule" page. IsValid - A value of 1 means the plugin is active and will be displayed in the tree. A value of zero means the plugin is inactive and will not be displayed in the tree. BeforeRun Tag: This tag is used to configure the command that needs to be run before StoreGrid runs the backup schedule for this plugin. You can run multiple commands by giving each command under a BeforeRun XML tag. Command - The command that needs to be run is given here. In the above example the batch files zipsource.bat

187 and zipdata.bat are run. WorkingDir - This is the directory from which the command has to be run. TimeOut - StoreGrid will timeout the command if the command does not finish within this time. This timeout value in milliseconds. "-1" denotes infinite timeout value. AfterRun Tag: This tag is used to configure the command that needs to be run after StoreGrid finishes the backup schedule for this plugin. You can run multiple commands by giving each command under a AfterRun XML tag. Command - The command that needs to be run is given here. In the above example the batch files cleansourcebk.bat and cleandatabk.bat are run. WorkingDir - This is the directory from which the command has to be run. TimeOut - StoreGrid will timeout the command if the command does not finish within this time. This timeout value in milliseconds. "-1" denotes infinite timeout value. BackupPath Tag: This is the list of files and folders that needs to be backed by StoreGrid after running the BeforeRun commands and before running the AfterRun commands. In the above example, StoreGrid will backup the files "D:\joe\Backup\workSource.zip", "D:\joe\Backup\workData.zip", and the folder "D:\joe\Backup\MiscFiles". Configuring The Plugin Backup Once the XML is created in the plugins directory, go to the Add Backup Schedule page in the StoreGrid webconsole. You will notice that the plugin name is displayed in the "Files/Folder" tree. You can select the plugin name in the tree and configure a backup schedule.

188 Restore Backup Data Overview In StoreGrid, restoring files and directories is quite simple and can easily be done by end users themselves without the help of System Administrators. StoreGrid can restore more than one backup at a time from the backup server. Therefore, you don't have to wait for the first restore operation to complete before starting the next one. 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. In the Action Column of the backup schedule you want to restore, click on the Restore icon. Restore Backup Data The following are the steps to be followed while restoring data: Step 1: Select The Backup Name And The Backup Server - The backup name is a non editable field here. The backup server will also be non-editable if the backup schedule is backing up to only one server. If the backup schedule is backing up to more than one server, then you need to choose the server here from the choice box. Step 2: Select Version To Restore - Here you will see a tree with each parent node representing a full backup that has been done with the time stamp of the last incremental backup performed for this full backup. If the backup schedule was not configured with multiple full backups, then this list will have only one parent node- that of the first full backup. Under each parent node, a leaf node with timestamp represents an incremental backup that has been done. The leaf-node with the earliest timestamp represents the time when the full backup was done and all other time stamps represent an incremental backup on top of the full backup. You can choose any version based on timestamp for restoring. Note that the tree in Step 3 loads with the files/folders based on what timestamp/version you choose here. Also, by default the tree in step 3 is loaded for the latest backup of the backup schedule. Step 3: Select Files And Folders - You could select the files/folders and their versions to restore from the file/folder tree. You can also specify the files/folder you want to restore in two other ways: You can filter the tree by entering a wild card (*.doc etc.) in the Filter files/folders text field. Note that the tree will also list the number of versions of each file as of the timestamp chosen in Step 2. You can either choose a specific version of a file to restore or choose the root node to restore the latest version (as of the timestamp chosen in Step 2) of all the files. You can also enter the names of the files and folders directly. Click on the Let me directly enter the file/folder names instead of selecting them from the tree view link in step 3. Enter the complete path of the file/folder to restore and click the Add button. You can remove the selected files and folders by clicking the Remove button. Please note that while restoring files this way, you will be able to restore only the latest version of the file that was available at the backup time that you selected in Step 2. If you are trying to restore a delete file, then you should enter the path to the file's parent folder and not the path of the delete file. Step 4: The following are the options you have to provide in this step. Password - If you had password protected the backup schedule, you will need to provide the password here. Restore Machine - This is the StoreGrid client to which the backup data has to be restored to. The data can be moved either to the same machine or to a different (remote) machine. If the files have to be restored to a remote machine, you need to specify the remote machine's StoreGrid web console username and password.

189 Restore Deleted Files - This has three options to choose from: 1. Skip Deleted Files - Choosing this option will skip the deleted files and restore the rest. 2. Deleted Files Only - Choosing this option will restore only the deleted files. 3. Include Deleted Files - Choosing this option will restore all the files including the deleted files. Restore Location - You have two options: 1. Original: This option is applicable only if the data is restored to the same machine. 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 Options - 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 behavior, 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 lost. 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. Limitations 1. Files/Folders entered manually for restore are case sensitive. Also, ensure that the complete path of the files/folders to be restored is entered. 2. A single deleted file/folder cannot be restored by entering the complete path to the deleted file in step 3. Instead, the path to the parent folder name that contains the deleted files/folders and then select the "Deleted Files Only" option in Step No error message will be displayed in the webconsole, if the files/folders entered manually for restore do not exist in the backup server or is not a part of the configured backup schedule. However, the error message will be reported in the restore progress and report. 4. Only the latest version will be restored if the files/folders to be restored is specified by entering the complete file/folder path in step 3. For example, if a file (image.jpg) has 4 versions (*.ver_001, *.ver_002, *.ver_003, *.ver_004), then by default the latest version (*.ver_004) will be restored for the selected timestamp.

190 Restore Exchange Server Backup Data Overview Restoring a storage group or database is sometimes necessary when a database becomes corrupt. You can restore your Exchange databases using your most recent full backup and incremental or differential backups. This section will give you information on how to restore Exchange Server databases using StoreGrid. Before you can attempt to restore a database in Exchange Server, please ensure that the following conditions are satisfied: 1. The Exchange Server must be running. 2. The database to be restored must be dismounted. 3. "This Database Can be overwritten by a restore" option must be checked for each Information Store. (Right click the store->properties->database) 4. Copies of the current *.edb, *.stm and other related files from the db storage location have been taken. It is possible to restore multiple databases from the same storage group as part of a single restore job. The transaction log files in the backup set and the patch files are restored to the temporary disk location specified by the user. If you selected Mount Database after restore, the database is automatically mounted in the target storage group. The restore process relies on the user to provide a path to a temporary location that will be used during the restore. Separate Exchange restore processes running at the same time must use different disk locations. The temporary disk space required is about 10 megabytes (MB) more than the size of the transaction log files and patch files that are being restored. 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. In the Action Column of the (Exchange) Backup Schedule you want to restore, click on the Restore icon. Requirements Exchange Server 2000 with Service Pack 3/ Exchange Server 2003 / Exchange Server Restore Exchange Server Backup Data In StoreGrid, restoring Exchange Server database is quite simple and can easily be done. The following are the steps to be followed while restoring an Exchange Server: Step 0: Decide how to restore Decide between restoring the Exchange Server directly from the backup server or if use data which has been previously restored from the backup server (to a local folder). This step has the following options : - Restore data from backup server - I have previously restored data from my backup server to a local folder. I now want to use this data to restore the Exchange Server database.

191 1. If the second option is selected (to restore Exchange Server data from the previously restored data), then ensure that : i. Exchange Server backup data was restored from backup server locally through the menu "Group Management->Group Name->Client Name->List of Backups->Actions->Proceed to Restore Backup" and transferred to client machine. or ii. You had previously chosen the option "Restore data from backup server only (I will separately run StoreGrid through the 'locally restored files' to restore the Exchange Server later)" in "STEP 4: Confirm Exchange Server Restore Settings" of the Restore Exchange Server Data page (during your previous restore). 2. Enter the local restore location and click "Submit Location" button to restore Exchange Server data from the local folder. Step 1: Choose backup server (in case of multiple servers) This step allows you to choose the backup server (if the backup schedule was configured to multiple servers). This step has the following options: o o Backup Name - The backup name is a non editable field here. Backup Server - The backup server is non-editable if the backup schedule is backing up to only one server. But if the replication feature is enabled in the backup server for the client and replication server name is added/discovered in client machine, then choose the server from the choice box. Step 2: Select backups for Exchange Server restore This step allows you to choose the full backup version based on timestamp. This step has the following options: o o o Show backups after - From the drop-down list, select the most recent full backup version based on timestamp to restore from. Once recent full backup version is selected and if "Load" button is clicked, StoreGrid will list the files available in the backup server. Load - Once you have selected the required timestamp in the field "Show backups after", this button can be used to list the files backed up to the backup server for restore (satisfying the timestamp criterion). Select Files for Exchange Server restore - StoreGrid will list the files based on what timestamp/version you have chosen in the "Show backups after" fields. Now, you will have to select the Storage Groups / Mail Stores to be restored from the server. Step 3: Confirm Restore Settings o o Password - If you had password protected the backup schedule, you will need to provide the password here. Restore Location - You can specify the 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! Step 4: Confirm Exchange Server Restore Settings

192 This step helps you restore backed up data right into the Exchange Server database. By default the option "After restoring data from my backup server, continue to restore the data into the Exchange Server" is selected. Alternatively you can also choose the option "Restore data from backup server only (I will separately run StoreGrid through the 'locally restored files' to restore the Exchange Server later)". This step has the following option: o o Exchange Server Name - Name of the Exchange Server from which Storage Group(s)/MailStore(s) were configured for backup (and to which data has to be restored). Temporary location for log and patch files - Enter a directory name in the Temporary location for log and patch files. This directory should be different from the one where the original log files are to be stored and should have sufficient disk space to store the files. During the restore process, Exchange will first apply the older transaction logs from the temporary directory and then apply the more recent logs from the original location. To perform the restore, you must have sufficient space in the directory to store the files. The disk space requirement is about 10 MB more than the size of the transaction log files that are being restored. This temporary directory should be different from the restore location you provided in step 3. And this temporary directory should be a local drive and not a mapped network drive. Important : The directory that you specify in the Temporary location for log and patch files box must not contain the original database or log files or the restore might fail. Note : It is recommended that you create an empty temporary folder for this procedure. Because transaction logs are written per storage group, and not per database, using a temporary folder ensures that transaction log replay is isolated and will not interfere with undamaged databases that are still running in a storage group during recovery. o o Last Restore Set(Log file replay will start after this restore completes.) - Select the Last Restore Set check box only if this is the last backup set that you have to restore before you remount your databases. Mount Database after restore - Select the Mount Database After Restore check box, if this is the last backup set that you plan to restore, and you are sure that you are ready to mount the databases. It is recommended that you do not select this check box unless if this is the last backup set. Select the Last Restore Set check box and the Mount Database After Restore check box if any of the following conditions apply: You are restoring from a normal (full) backup without any incremental or differential backups You are restoring from the final incremental backup You are restoring from the final differential backup 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 in a pop-up browser window. Troubleshooting Tips Exchange Server data restore fails with one of the following errors. i. "Error returned from a callback function call (0x%X)." ii. "Restore ended with error 0xC Existing log file is not contiguous" Cause 1: This would occur, if a full backup of the entire storage group is done, then the log files are purged and

193 thereafter, a previous backup of the Storage Group (before the last full backup is restored) is performed. This produces a gap in the log files that were purged. Solution : If the Entire Storage Groups is scheduled for restore. i. Dismount all Stores in that particular storage group. ii. Move the existing data *.edb, *.stm and other related files from the db storage location to another location. iii. Restore Exchange Server data. Cause 2 : It can also happen if there is more than one database in a storage group, and only one of the databases is restored to the storage group. Solution : If only one or two Stores are going to be restored while the other Stores remain mounted: i. Dismount the particular store (that has to be restored). ii. Move the existing data *.edb, *.stm and other related files from the db storage location to another location. iii. Configure Exchange Server restore by deselecting the "Last Restore Set" option in restore page. iv. Once restore is completed successfully, view the contents of the restore.env file available in the location given in the "Temporary location for log and patch files" option by using the command "eseutil.exe /cm". Take a note of the log file sequence in the restore.env file. v. Move the log files in the database storage location of Exchange Information Storage group. vi. Perform a manual hard recovery with the /cc and /t switches of the eseutil command. For example: eseutil /cc temporary_folder /t (where temporary_folder is the folder that is specified in the Temporary location for log and patch files dialog box, such as C:\Temp\My Backup). vii. Mount the database. Click here for more details about these steps. <Information Storage Groups> and <Information Stores> might have not been dismounted yet. Cause 1: The Information Stores selected for restore was not dismounted before restore. Solution : Dismount the respective Information Stores before restore operation. Cause 2: The restored Exchange Server data does not have *.edb/*.stm files. Solution : While restoring the Exchange Server data in StoreGrid, verify that *.edb, *.stm and *.GUID files are listed under Information Stores. If these files was not listed in please try listing these files from the other full backup timestamp/version and proceed with restore. Limitations 1. Multiple incremental backup sets can only be restored as single restore set. 2. It is recommended to provide an empty directory for the local restore location with sufficient space in the directory to store the files and ensure that the local restore location does not exceed the 256 character limit. 3. It is recommended that you provide an empty directory in the "Temporary location for log and patch files" option. And this temporary directory should be a local drive and not a mapped network drive. 4. Previous schedules cannot be restored in the client side after changing the dump location.

194 Restore Exchange Mailbox Backup Data Overview StoreGrid can restore mailbox data to an Exchange Server. This section gives the details on restoring individual or multiple users' mailbox to an Exchange Server. It can be done from a StoreGrid backup server using recent full or incremental backups. The data is first restored to a local drive and then to an Exchange Server without any interruption to the live Exchange Server. The mailbox restore cannot be used to recover Exchange Server Information Store(s). During disaster recovery, mailbox can be restored to an Exchange Server only after the Storage Group(s)/MailStore(s) are recovered. Before restoring mailboxes, please ensure the following: 1. The Exchange Server must be running. 2. Select just the specific mailboxes that you want to restore instead of the entire Mailbox Store /Public Folder. 3. Ensure that the Default Information Store[i.e. MailBox Store in First Storage Group] and the user's Information Store are mounted in your exchange server. Note: 1. Usually it is not enough to just backup mail boxes alone. It is recommended that you always configure the storage group for backups. You can have additional mailbox backups under the storage group so that you get additional granularity during restores wherein you can restore only a mailbox that is required. 2. If you just configure only mailbox backups and not configure the full storage group, then if your full exchange server crashes then you will not be able to restore your exchange server at all. 3. The best practice is to configure storage group backups and then configure additional mailbox backups for quick restores. Also for mailbox backups it is better to configure only critical mailboxes and not all mailboxes for backups as the mailbox backups takes a lot of time to backup than the full storage group itself. 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. In the Action column of the (Exchange Mailbox) Backup Schedule, click on the Restore icon. Requirements Exchange Server 2000 with Service Pack 3 / Exchange Server 2003 / Exchange Server Restore Exchange Mailbox Backup Data Restoring Exchange Mailbox in StoreGrid is quite simple and can be easily done following the steps mentioned below: Step 0: Decide how to restore The user can select to restore the exchange mailbox directly from the backup server or from the previously restored data stored in the local folder. This step has two options : - Restore data from backup server

195 - I have previously restored data from my backup server to a local folder. I now want to use this data to restore the Exchange Mailbox. 1. If the second option is selected (to restore user mailbox data to Exchange Server from the previously restored data), then please ensure i. Exchange Mailbox backup data was restored from backup server locally through the menu "Group Management->Group Name->Client Name->List of Backups->Actions->Proceed to Restore Backup" and transferred to client machine. or ii. You had previously chosen the option "Restore the data to the local disk only and do not automatically restore the data into the exchange server (I will separately restore the 'locally restored data' into the Exchange Server later). 2. Enter the local restore location and click "Submit Location" button to restore user mailbox data to Exchange Server from the local folder. Step 1: Choose a backup server in case of multiple servers. This step allows you to choose the backup server if the replication feature was enabled in backup server for this client. This step has the following options: o o Backup Name - The backup name is a non-editable field. Backup Server - The backup server is non-editable if the backup schedule is backing up to only one server. But if the replication feature is enabled in the backup server for the client and replication server name is added/discovered in client machine, then choose the server from the choice box. Step 2: Select Version To Restore Choose full or incremental backup versions based on the timestamp. A tree with a parent node represents a full backup and under it is a leaf node with timestamp representing an incremental backup. The leaf-node with the earliest timestamp represents the time when the full backup was done and all other time stamps represent incremental backup on top of that full backup. You can choose any version based on the timestamp for restore. Note that the tree in Step 3 loads the users' mailbox files based on the timestamp/version selected here. By default, the tree in step 3 is loaded for the latest backup of the backup schedule. Step 3: Select backups for Exchange Mailbox restore StoreGrid will list the files based on the timestamp/version you have chosen in the "Step 2". Choose appropriate mailbox to be recovered/restored to an Exchange Server from StoreGrid backup server. In this step select the users' mailbox folders to be restored from the server. Step 4: Confirm Restore Settings o o Password - If the backup schedule is password protected, provide the password here. Restore Location - Specify the location for restore. 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!. Make sure the directory you provide for restore has enough disk space and has valid read and write permissions. It is recommended to provide an empty directory or a new directory path for the local restore location. Important : The directory specified in the restore location for restoring mailbox data must not contain the original or previously restored files or else the restore will fail.

196 Step 5: Confirm Exchange Mailbox Restore Settings This step restores the backed up mailbox data to the Exchange Server. By default the option "After restoring data from the backup server, continue to automatically restore the data into the Exchange Mailbox" is selected. This will restore the data to the Exchange Server. Alternatively, if you choose "Restore the data to the local disk only and do not automatically restore the data into the exchange server (I will separately restore the 'locally restored data' into the Exchange Server later)" the data will be in the specified restore location and will not be restored to the Exchange Server. o Exchange Server Name - Name of the Exchange Server from which users' mailboxes were configured for backup and to which data is to be restored. Restore and Cancel Button - Once all the options are set and the users' mailbox to be restored are selected, click on the Restore button to restore the Exchange Mailbox. The status of the restore operation will be displayed in a pop-up browser window. Limitations 1. The local restore location path name should not exceed the 256 character limit. 2. The local restore location and the directory should not contain any of the previously restored files in it. 3. StoreGrid does not allow restoring the selected mailbox to an alternate Exchange Server. If needed,.pst files can be restored to alternate Exchange Server manually after restoring the files to local disk from backup server. 4. While restoring the complete contents of the selected folder to the original mailbox folder, the existing folder contents will not be deleted prior to performing the restore and restore process will append all s to the folders. It may result in duplicate items within the original folder. 5. Search and restoring individual mails is not supported, however restoring up to mailbox folders is supported using StoreGrid Advanced Exchange Mailbox plugin. 6. StoreGrid will not be able to restore the user mailbox, if the user is deleted from the Active Directory and from the Exchange Server. 7. Previous schedules cannot be restored in the client side after changing the dump location.

197 Restore SQL Server Backup Data Overview You can restore your SQL Server databases using your most recent full backup. This section provides information on restoring SQL Server databases using StoreGrid. 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. In the Action Column of the (SQL) backup schedule you want to restore, click on the Restore icon. Requirements SQL Server 2000 / 2005 / Restore SQL Server Backup Data In StoreGrid, restoring SQL Server database is quite simple. The following are the steps to be followed while restoring SQL Server data: Step 0: Decide how to restore Decide on whether the SQL Server database data has to be restored from the backup server or if you wish to use data which had been previously restored from the backup server to a local folder. This step has the following options: - Restore data from backup server - I have previously restored data from my backup server to a local folder. I now want to use this data to restore the SQL Server database. If the second option is selected to restore SQL Server database from the previously restored data, then ensure that : SQL Server database was restored from backup server locally through the menu "Group Management->Group Name->Client Name->List of Backups->Actions->Proceed to Restore Backup" and transferred to client machine. or You had chosen the option "Restore data from backup server only (I will separately run StoreGrid through the 'locally restored files' to restore the SQL Server later)" in "Confirm SQL Server Restore Settings" of the Restore SQL Server Database page in the previous restore. Enter the local restore location and click "Submit Location" button to restore SQL Server data from the local folder. Step 1: Choose the backup server (in case of multiple servers) This step allows you to choose the backup server if the backup schedule was configured to multiple servers. This

198 step has the following options: o o Backup Name - The backup name is a non editable field here. Backup Server - The backup server is non-editable if the backup schedule is backing up to only one server. But if the replication feature is enabled in the backup server for the client and replication server name is added/discovered in client machine, then choose the server from the choice box. Step 2: Select backups for database restore This step allows you to choose the database name and full backup version based on timestamp. This step has the following options: o o o o o SQL Server Instance Name - The SQL Server Instance name is a non editable field here and this will display the instance name from which SQL Server database was configured. Database Name - The database name will also be a non-editable if the backup schedule is configured with single database. If the schedule is configured with multiple database, then you need to choose the database name here from the choice box. Select the database you wish to restore. Show backups after - From the drop-down list, select the most recent full backup version based on timestamp to restore from. Once recent full backup version is selected and the "Load" button is clicked, StoreGrid will list all the backups for the selected database, starting with the one selected in this field. Load - Based on the values selected in the fields"database Name" and "Show backups after", clicking this button will list the files backed up to the backup server (available for restore). Select Files for database restore - This section will list the files based on what timestamp/version and database name you choose in the "Database Name" and "Show backups after" fields. Here is where you have to select the files to be restored from the server. StoreGrid displays a list of the backups available for the database selected in "Database Name", starting from the first backup selected in "Show backups after" fields. This section has the following fields: Type - The type of backup, value can be either FULL/DIFFERENTIAL/TRANSACTION-LOG backups. Backup Date - The time at which the backup was transferred to backup server. File Name - The name of the file backed up. Step 3: Confirm Restore Settings o o Password - If you had password protected the backup schedule, you will need to provide the password here. Restore Location - You can specify the 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! Step 4: Configure SQL Server Database Restore This step helps you to restore backed up data right into the SQL Server database. By default, the option "After

199 restoring data from my backup server, continue to restore the data into the SQL Server database" is selected. Alternatively you can also choose the option "Restore data from backup server only (I will separately run StoreGrid through the 'locally restored files' to restore the SQL Server database later)". This step has the following option: o o o o Restore as database - This drop-down list allows you to select an existing database, or, if you want to restore to a new database, type in a new database name. For a new database, the database will be created and then the contents of the backup will be restored. For an existing database, the contents of the backup will be restored over the existing database. Overwrite the existing database - If you are restoring backups and you want to overwrite an existing database with a different name, you must use choose this option. If you are restoring backups to the same database, this option is not required. Restore the database file as - This displays the name and location of the physical files used when you restore your database. The location and names of the files are stored in the backup file, so if you are restoring to a different server or to a different database name, you must change these options for both the data file and the transaction log file. Recovery State - The Recovery state panel determines the state of the database after the restore operation. The default behavior is: Leave the database ready to use by rolling back uncommitted transactions. Additional transaction logs cannot be restored.(restore WITH RECOVERY) Note: Choose this option only if you are restoring all of the necessary backups now. Alternatively, you can choose either of the following options: Leave the database non-operational, and do not roll back the uncommitted transactions. Additional transaction logs can be restored. (RESTORE WITH NORECOVERY) Leave the database in read-only mode. Undo uncommitted transactions, but save the undo actions in a standby file so that recovery effects can be reverted. (RESTORE WITH STANDBY) StandBy file A file required by SQL Server to track incomplete transactions if the backup is restored in standby state. The Standby file is used to undo uncommitted transactions when the database is brought fully online. If the Standby file does not exist, it will be automatically created. 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. Troubleshooting Tips SQL Server restore fails with one of the following errors. i. "SQL Server restore aborted because of error in getting the virtual device backup configuration. Check your database properties. Check your database properties." ii. "Exclusive access could not be obtained because the database is in use." Cause : If more than one connection was opened to the database which was configured for restore. Solution 1: Make sure that no other user is connected to that database. If possible close the connections open to that

200 database. Solution 2: Alternatively, change the database property to single user mode before restore operation and change the database property again to multiple user mode after restore. Restore SQL Server Database page is not listing database available to restore. Cause : This would occur, if StoreGrid client configurations are recovered from backup server through Client Disaster Recovery option. Solution : Please re-enter the SQL Server Instance login details in "SQL Server Connection Properties" page through the menu "Backup->Create SQL Server Backup Schedule" once and then try to restore the SQL Server database. Restore SQL Server Database page is not listing databases available to restore. Cause 1: If backed up SQL Server databases are Unavailable(OFFLINE/DETACHED/DELETED) to perform restore. Hence logical file name is not available to perform restore. Cause 2: Check if backed up SQL Server databases contain any special characters like forward slash(/), backward slash(\), question(?), colon(:), asterisk(*), lesser than(<), greater than(>), pipe( ) and plus(+). Solution : Download the backed up SQL Server database dump file to client machine using the following steps: i. Restore SQL Server database locally in backup server through the menu "Group Management->Group Name- >Client Name->List of Backups->Actions->Proceed to Restore Backup" and transfer the restored data to client machine. or ii. Choose the option "Restore data from backup server only (I will separately run StoreGrid through the 'locally restored files' to restore the SQL Server later)" in "Confirm SQL Server Restore Settings" of the Restore SQL Server Database page to restore the SQL Server database locally in client machine. iii. After downloading the files from server, use second option (I have previously restored data from my backup server to a local folder. I now want to use this data to restore the SQL Server database) in Step 0 of the "Restore SQL Server Database" page to restore the SQL Server database. I am backing up SQL-Server using the Advanced plugin. How do I restore the SQL Server database in a different machine. For Example - If MACHINE A is configured to backup SQL Server database to SERVER A, how do I restore the backup from SERVER A to MACHINE B. Solution : To restore SQL Server database in MACHINE B, please follow the steps given below: i. SQL-Server data could be restored from backup server A to MACHINE B in one of the following ways:- a. Restore SQL Server database backup schedule data locally in backup server A through the menu "Group Management->Group Name->Client Name->List of Backups->Actions->Proceed to Restore Backup" and then manually transfer the data to MACHINE B. OR b. From MACHINE A itself, do a regular restore by choosing the option "Restore data from backup server only (I will separately run StoreGrid through the 'locally restored files' to restore the SQL Server later)" in Step 4. And then manually transfer the data to MACHINE B.

201 ii. Once the data has been transferred to MACHINE B, you need to edit the restore.conf located in "<RESTORED_LOCATION>/plugin/" folder. a. Open the restore.conf located in "<RESTORED_LOCATION>/plugin/" folder. b. Change the SqlInstanceName attribute value to MACHINE B SQL Server Instance name. And before restoring the SQL-Server, go to the "SQL Server connection properties" page and then login to MACHINE B SQL Server Instance at least once. c. Change the ClientIdentity attribute value to MACHINE B StoreGrid Identity. d. Save and close the file. iii. Database to be restored should not exists in the Mapped Drive of the MACHINE B. Please check that database files to be restored exists in the Local Drive of the MACHINE B, if not please transfer the restored data to the Local Drive of the MACHINE B. iv. In the top menu of the StoreGrid WebConsole, select: "Restore". It will display the "List Of Backup For Restore" page. In the Action Column of the any SQL backup schedule, click on the Restore icon. v. Choose the second option in "Step 0: Decide how to restore" settings to restore SQL Server database from the previously restored data. And then enter the local restore location and click "Submit Location" button to restore SQL Server data from the local folder. vi. And Proceed with the remaining steps in Restore SQL Server Database [Advanced Plugin] page to restore the SQL Server database. Note : The above solution is applicable when the sql-server backup is configured using the Advanced Plugin. In the case of SQL Server Basic Plugin, check the Restore SQL Server Database [Basic Plugin] page. Limitations 1. If a backup schedule is configured with multiple database(s) (in client-side) only a single database is allowed to restore to the SQL Server at a time. 2. It is recommended that you provide an empty directory for the local restore location. There must be sufficient space in the directory to store the files; also ensure that the local restore location does not exceeds the 256 character limit. 3. Previous schedules cannot be restored in the client side after changing the dump location. 4. While restoring the deleted MS SQL Server database(s) using Advanced Plugin, the same cannot be restored directly to the MS SQL Server. First the deleted database(s) should be restored locally in the client machine and then should proceed with the 'Plugin local restore' feature to restore the deleted MS SQL Server database(s).

202 Restore Exchange Server StoreGrid uses the Windows NT backup utility to backup MS Exchange Server. So restoring exchange server is a two step process, 1. You should restore the NT backup generated bkf file first and 2. input the bkf file to the NT backup utility to restore the exchange information stores. Step 1: Restore the exchange backup bkf file from the StoreGrid server to the machine in which exchange is installed. Follow the steps described in the "Restore Data" section to restore a version of the bkf file. Step 2: Restoring Exchange from the bkf file using the NTBackup utility 1. Let us say the bkf file is restored to the location C:\Exchange-Restore directory. 2. Open the Microsoft Exchange System Manager from Windows "Start->Programs->Microsoft Exchange" menu. 3. In the left side tree, under the "Servers" node open the "exchange server name" to which the bkf has to be restored. Under the "exchange server name" node the following nodes will be present: a. "First Storage Group" node under which you will have "First Mailbox Store" node and "Public Folder Store" node. b. You may have other Storage Group (eg. Second Storage Group) with corresponding mailbox stores under each information store. 4. Select the "First Mailbox Store" node and "Public Folder Store" node and Dismount them by right clicking the mouse. 5. Select any other mail box stores available under other Information Stores and dismount them. 6. The next step is to backup the existing database files (*.edb, *.stm, *.log, *.chk etc.). For each of the dismounted mail box stores, you can find the database location by right clicking the mouse and then choosing the properties. In the dialog that opens, select the "Database" tab and note down the database location for each of the mailbox stores. 7. Go to the database locations and move all the files (*.edb, *.stm, *.log, *.chk etc.) to a new location as a backup. 8. Open the NTBackup utility from Windows "Start->Programs->Accessories->System Tools->Backup" menu. 9. In the NTBackup UI, open the Restore Wizard from the "Tools->Restore Wizard" menu item. 10. In the "Restore Wizard", click on the "Import File" button and choose the bkf file from C:\Exchange-Restore directory (from step 1). 11. Once the bkf file is imported the left side tree (in the NTBackup restore wizard) will show the Exchange Information Stores that have been backed up. If your Exchange Server does not have those information stores already, you should create them first and then follow the steps from 4 to 7 above, i.e. dismounting and moving the database files.

203 12. The "What To Restore" tree in NTBackup will list the mail box stored and the logs for each of the information stores. You need to select the mailbox store and all the logs (typically the latest under a information store) for restore. The following example is used to clarify how to choose the nodes in the tree for restore. Let us say the tree has the following nodes: First Storage Group First Mailbox Store Log Files Public Folder Store First Storage Group Log Files Second Storage Group Log Files Second Mailbox Store Second Storage Group Log Files The above tree means the Exchange backup has been done twice and the first time the Storage group shows the mailbox store and the log files and for the second backup only the log files are being shown. You should always select the Mailbox store from the storage group for restore and then select all the log files from the corresponding backup. Note that you should always select the Mailbox store and all the log files for the default Information store "First Storage Group" - i.e. the default information store, "First Storage Group" should always be selected for restore. 13. In the next "Restore Database Server" UI in NTBackup, provide a temporary location (directory) for log and patch files. Also check the "Last Backup Set" checkbox. Do not check the "Mount Database For Restore" checkbox. 14. Skip the next "Advanced Restore Option" UI. 15. In the next screen, click Finish to start the exchange database restore process. If you are asked to confirm the location of the bkf file, confirm by clicking the OK button. 16. Once the NTBackup completes the restore operation, wait for a couple of minutes before mounting the information stores that have been restored into your Exchange Server. 17. Go to the Exchange System Manager and mount the "First Mailbox Store", "Public Folder Store" and all other mailbox stores under other information stores that have been restored.

204 Restore MS SQL Server StoreGrid backs up SQL server by creating a dump file using the sql-server internal commands. StoreGrid supports full backup, differential backup and transaction log backups. Restoring sql-server is a two step process, 1. Restore the full/differential/transaction log dump files and 2. Use the SQL Server Enterprise Manager and restore the sql-server database from the backup dump files. Step 1: Restore the SQL-Server backup dumps. From the "Restore Data" UI page in StoreGrid, you have to restore the sql-server backup dumps from the backup server to the local machine first. You can learn more about that in "Restore Data" section of the help documentation. The following describes how the backup dump is stored in the backup server and how you have to choose the appropriate dump files for restore. The sql-server backup dump are stored in the backup server with the following directory and file naming convention. Full Backup Directory Name: A full backup will be stored under a directory ID_FULL_DDMMYYYY_H_M_S, where a. ID is the unique id generated by sql-server for the backup. The ID for a current backup will always be greater than the ID for a previous backup. So the ID can be used to identify the sequence in which the backups were done. This is especially useful while restoring database transaction logs as they have to be restored in sequence on a database b. FULL is meant to identify that this is a full backup directory. c. DDMMYY_H_M_S is the Day, Month, Year, Hour, Minute and Seconds when the backup was done. Full Backup File Name: The full backup file dump will be under the full backup directory. The file name for a full backup dump file will be ID_DBNAME_DDMMYYYY_H_M_S_FULL.dump, where a. DBNAME is the name of the database that is being backed up. Differential Backup Directory Name: All Differential backups are stored under a directory ID_DIFFERENTIAL_DDMMYYYY_H_M_S. Note that for every full backup there can be multiple differential backup directories. Differential Backup File Name: The differential backup file dump will be under the corresponding differential backup directory. The file name for a differential backup dump file will be ID_DBNAME_DDMMYYYY_H_M_S_DIFFERENTIAL.dump. Transaction Log File Name: All transaction logs will be either stored under a FULL backup directory or a DIFFERENTIAL backup directory depending upon whether the transaction log is being done after a full backup or a differential backup. The file name for a transaction log dump file will be ID_DBNAME_DDMMYYYY_H_M_S_LOG.dump. While restoring these sql-server backup dumps, you need to be aware of the following: a. You should restore the full backup dump file as differential backups and transaction logs have to be always applied on top a full backup.

205 b. You can choose any one differential backup (or none at all) for restore depending upon your requirement. c. For transaction logs you should restore all the transaction logs under the chosen differential backup in (b) above. OR, you need to restore all transaction logs under the full backup if no differential backup was selected in (b) above. Step 2: Restore the SQL Server Database using SQL Server Enterprise Manager 1. Open the SQL Server Enterprise manager from the Windows "System->Programs->SQL Server->Enterprise Manager". 2. Create a database with the same name as the original database. If the original database already exists then you have to delete the database or move the tables to another database. Otherwise you will have to create the database with a different name than the original database name. 3. After creating the database, right click that node. And in the popup menu, choose "All Tasks->Restore Database" menu item. 4. In the "Restore Database" dialog, choose "From Device" and click on the "Select Device" button. 5. In the "Choose Restore Devices" dialog, add the database dump file. Note that for full backup and differential backup, you have to just add the full backup or the differential backup dump file alone and for transaction logs you can add all the transaction logs except the last transaction log together (but in sequence based on the unique ID in the file name). Also you will have to first restore the full backup, then the differential backup on top of it and then restore the transaction logs under the differential backup. 6. In the General Tab, choose the appropriate option from the available options : Database Complete: If you are restoring a full backup, then choose this option. Database Differential: If you are restoring a differential backup, then choose this option. Transaction Log: If you are restoring transaction logs, then choose this option. In the Options Tab, choose the following options: Select "Force Restore over existing database". Select "Leave database read-only and able to restore additional transaction logs". 7. While restoring the last transaction log, you need to follow step 3 to step 5 again and in the options tab in Step 5, you have to select the "Leave Database operational. No additional transaction logs can be restored".

206 System State Restore Overview System state restores the critical operating system configuration files. These backup files can be used to recover the system components after a server crash. StoreGrid uses Windows NT backup utility to backup System State and Active Directories. System State Components The following system components are restored through System State restore Boot files, including the system files, and all files protected by Windows File Protection (WFP). Active Directory (on a domain controller only). Sysvol (on a domain controller only). Certificate Services (on certification authority only). Cluster database (on a cluster node only). Registry. Performance counter configuration information. Component Services Class registration database. The list of system state components is dynamic and may change depending on service pack and operating system features installed. With a system state backup, you cannot restore an individual file or system component due to the dependencies among the system state components. StoreGrid can backup and restore System State files. System State Backup is configured like any other files and folder backup from the "Add Backup Schedule" page. Choose the "System State" entry in the tree and configure the backup. StoreGrid uses the NTBackup utility tool to extract the System State data and store it as.bkf file in the directory where StoreGrid is installed. By default, the dump location will be <StoreGrid_Home>/plugin-data/SystemState/. Restoring System State Before restoring the files backed up, ensure the following: 1. Install the operating system, service packs and patches as installed before. 2. Install the applications including StoreGrid with same StoreGrid ID as before. 3. Configure the network settings as before. 4. Install the Active Directory with the same settings like FQDN name, SYSVOL, and SYSLOG path etc. 5. Restore the System State.bkf file into a separate directory. Restoring System State backup using StoreGrid is a two step process: 1. Restoring System State backup generated bkf file from the StoreGrid backup server to the machine where system state is to be restored. 2. Restoring System State into the system from the.bkf file using NT backup utility. Restoring System State.bkf file from the StoreGrid Backup Server i. In client machine s StoreGrid web console top menu, select "Restore". Under it choose "List Backups For Restore".

207 ii. It takes you to the list of backup schedules available for restore. iii. Click the Restore icon under the action column of the system-state backup schedule. iv. Restore Backup Data page opens. Step 1: Select the Backup Server from the dropdown list of servers. Step 2: Next, select version to restore. Step 3: Select Files and Folders: Here either you can directly select from Let me select the file/folders from the tree view Or give the complete path for the file/folder to be restored.

208 Step 4: o o o Provide the password if the backup schedule is password protected. Specify the machine where the data is to be restored. By default it is the client machine from which the backup was scheduled. Specify the location where the.bkf file to be restored to. Restoring the.bkf file into the system through NTBackup utility The procedures for System State restore differs depending on whether the restore is to a domain controller or to a nondomain controller. The system configured as domain controller must be restarted in the "Directory Services Restore mode" to restore Active Directory. There is no need to boot in a special mode in the non-domain controller configured systems. To restore the system state, follow the steps mentioned below: 1. If it is a Domain Controller system, start the system in "Directory Services Restore Mode" by the selecting the Directory Services Restore Mode in the BIOS 2. Log into system with an administrative account 3. Open the NTBackup utility from the Windows "Startup->Programs->Accessories->System Tools->Backup" menu. 4. In the NTBackup UI, open the Restore Wizard from the "Tools->Restore Wizard" menu item. 5. In the Backup or Restore Wizard window, click Next.

209 6. In the Backup or Restore wizard window, select Restore files and settings and click Next. 7. It will take you to the "Restore Wizard". Click on the "Import File" button and choose the system state bkf file from D:\dontdelete\ directory (from step 1).

210 8. The tree will show a System State entry. Select the System State entry and click Next. NOTE: If the system state is not restored in Directory Services Mode (in domain controller system), the restore operation will fail with the following pop up.

211 Restart the system in the "Directory Services Restore mode" and restore. 9. On completion of restore operation, the following window will be displayed. 10. In the advanced options, select the following fields:

212 11. The Where to Restore window is displayed. In the Restore files to field, choose Original location, and then click Next. 12. The How to Restore window will be displayed. Select Replace existing files, and then click Next. 13. Click Finish to begin the restore process and then click OK.

213 14. Now the registry and system files will be restored in this machine. Restart your system after the restore is complete.

214 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 a. when prompted for Restore Location, you select the Original location. b. 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: 1. Internet Explorer Settings: <Vembu_StoreGrid_Installed_Path>\data\IESettings\<Login_User_Name>\IEBackupFile.reg 2. Outlook Express: <Vembu_StoreGrid_Installed_Path>\data\OutlookExpress\<Login_User_Name>\OutlookExpressBackupFile.reg 3. 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)

215 Windows Mail Restore Overview To restore the backed up Windows Mail settings, contacts (WAB), calendar, s etc., Windows Mail application should be closed properly before proceeding with the restore. Ignoring this might cause problems in restoring the files/folders backed up by StoreGrid. Restore Options 1. Restoring the entire Windows Mail Follow the steps below to restore Windows Mail Completely. Step 1: Ensure the following settings for a regular Windows Mail restore: i. Set restore location as "Original Location". ii. Set restore option as "Overwrite existing file with restored file". Step 2: Registry file will be restored to the location {SG_HOME}\data\WindowsMail\{userName}. Right click the registry file and click "Merge". If it prompts for UAC (User Account Control), then Click "Continue". Click "Yes" in the message box prompt that follows next. 2. To Restore Mails Only Follow the steps given below to restore your mails: Step 1: Go to the restore tree of the particular backup that you want to restore and type *.eml in restore filter and Click "Go". Step 2: Then select restore location as "Alternate Location" and provide the new restore location. Step 3: After the restore has been successfully completed, open Windows Mail. Go to "File" menu and select import -} Message (file -} Import -} Message). Step 4: The wizard that opens will ask you to select the format type of mail you would like to import. Select "Windows Mail 7" and Click "Next". Step 5: It will ask for the location from which the mail is to be imported and select the location where you have restored the.eml file and click "Next". The mail folders will be listed and Click "Finish" to import the mails. 3. To Restore Windows Mail Accounts Follow the steps given below to restore the Windows Mail account settings: Step 1: Go to the restore tree of the particular backup that you want to restore and enter *.oeaccount in restore filter and Click "Go". Step 2: Restore the whole tree that is listed to the "Original Location" with the option "Overwrite Existing File".

216 4. To Restore Windows Contacts Follow any of the restore procedures given below to restore the Windows Contacts completely: Restore Procedure #1: Restore the "Contacts" folder listed in the restore tree with the option "Overwrite the existing file with the restored file". OR Restore Procedure #2: Step 1: Go to the restore tree of the particular backup and type "*.contact" or "*.group" in the restore filter and click "Go". Step 2: Restore the tree listed to the "Original Location" with option "Overwrite Existing File". 5. To Restore Windows Calendar Follow any of the restore procedures given below to restore the Windows Calendar completely. Restore Procedure #1: Restore the "Calendar" folder listed in the restore tree with the option "Overwrite the existing file with the restored file". Restore Procedure #2: Step 1: Go to the restore tree of that particular backup and type "*.ics" in restore filter and click "Go". Step 2: Restore the tree listed to the "Original Location" with the option "Overwrite Existing File". 6. To Restore Windows Mail Settings Follow the steps below to restore the Windows Mail settings such as *.mail rules and mail views *.Junk mail settings[safe Sender List and Block sender list] *Other Windows mail settings Step 1: Go to the restore tree of the particular backup and type "*.reg" in restore filter and click "Go". Step 2: Restore the tree listed to the "Original Location" with the option "Overwrite Existing File". Step 3: If you restore the *.reg file to the original location, then it will be restored in the {SG_HOME}\data\WindowsMail\{UserName}\WindowsMailBackupFile.reg. Step 4: Right click registry file and click "Merge". If it prompts for UAC, click "Continue". Click "Yes" for message box prompt that follows next.

217 Trouble shooting Tips Message Not Found Cause 1: This Problem occurs when a particular (.eml file) is deleted by the user and the status of deletion of that mail is not updated in the Windows Mail database. This Problem commonly occurs when backup is done while Windows Mail application remains open. Windows Mail logs each and every transaction in a log file and later updates it to the database file. Normally, windows Mail database file is updated from log files When Windows Mail is shutdown. When the backup is done at this time where transaction is still held in the log file and yet not updated to windows Mail database, then restoring this backup can lead to an error: 'Message not Found' when the user tries to open a mail that had already been deleted. This may happen if any of the following operations was performed earlier: Deleting Mail(s) Moving Mail(s) to any other folder Solution: To get rid of this error message "Message not found", you may follow any of the resolution strategies given below: Solution #1[Recommended]: Restore Windows Mails (*.eml files) to an alternate location and follow the restore procedure given for "To Restore Mails Only". Solution #2: Restore windows mail backup with option "Include Deleted Files". NOTE: All the deleted mails will be restored. Windows mail shows the error "The message store has been corrupted by an application external to Windows Mail. Windows Mail has been able to successfully recover from the corruption." Cause : Sometimes after restore when Windows mail is started, it might throw this error This happens in rare situations. Solution : Go ahead and allow the Windows Mail to recover the corrupted database files. Limitations While restoring Windows Mail with option "Include Deleted Files", then it will restore the deleted mails and moved mails. Moved mails might be duplicated in the destination and source.

218 Restore MySQL database [For Windows] Overview Restoring a database is sometimes necessary when a database becomes corrupt. You can restore your MySQL Server databases using your most recent full backup. This section gives you information on how to restore MySQL Server database using StoreGrid in Windows. Restore MySQL database [For Windows] Restoring MySQL databases in Windows require a couple of extra steps. Please follow the instructions detailed below in sequential order. Follow the steps for a regular restore operation and restore the required database backup files. Once restored, the required files are now in their designated locations: <Restore Path>\<Temp_Dump_Location>\<Backup_Name>\<Database_Name>\<Restore_File_Name> The restored MySQL database files end with an extension ".sql". In order to use the restored database, please follow the steps given below: If the restoring database is unavailable in MySQL Server, create the database using the command "CREATE DATABASE <DB_NAME>". Reload the database with the data using mysql -u [username] -p[password] [<DB_NAME>] < [<Restore Path>\<Dump_Location>\<Backup_Name>\<Database_Name>\<Database_Name>.sql]. This will dump the sql back to the database.

219 Restoring MySQL databases in Linux/FreeBSD Overview Restoring a database is sometimes necessary when a database becomes corrupt. You can restore your MySQL Server databases using your most recent full backup. This section gives you information on how to restore MySQL Server database using StoreGrid in Linux/FreeBSD. Restore MySQL database [For Linux/FreeBSD] Restoring MySQL databases in Linux/FreeBSD require a couple of extra steps. Please follow the instructions detailed below in sequential order. Follow the steps for a regular restore operation and restore the required database backup files. Restore! Once restored, the required files are now in their designated locations: <Restore Path>/<SG_Installed_Path>/mysqlbackup/<Backup_Name>/<Database_Name>/<Restore_File_Name>.sql The restored MySQL database files end with an extension ".sql". In order to use the restored database, please follow the steps given below: If the restoring database is unavailable in MySQL Server, create the database using the command "CREATE DATABASE <DB_NAME>". Reload the database with the data using mysql -u [username] -p[password] [<DB_NAME>] < [<Restore Path>/<SG_Installed_Path>/mysqlbackup/<Backup_Name>/<Database_Name>/<Restore_Fil e_name>.sql]. This will dump the sql back to the database.

220 Suspending a Client Side Restore (Restore initiated from the client) Overview Client Side Restore (Restore initiated from the client) process can be suspended either from the backup server or from the client, but can be resumed only from the client side. The suspended restore process will remain suspended till it is resumed from the client again. How to get here in the StoreGrid Web Console? In the top menu of Backup Client, select: "Restore -> List Backup For Restore". page. Suspending a Client Side Restore (Restore initiated from the client) To suspend a Client Side Restore, go to 'Restore -> List Backup For Restore' page in the client web console. If restore is in progress, click the 'Suspend Restore' icon displayed under 'Actions' against that backup schedule to suspend it. To resume the restore operation which is suspended either from the client or server, click the 'Resume Restore' icon displayed under 'Actions' against that backup schedule. Client Side restore can be suspended from the server-side web console as well. Go to 'Server Management -> Group Management > Group [group name] > Client [client name] > List of Backup Schedules from client' page in the backup server's web console. If restore is in progress, click the 'Suspend Client Side Restore' icon displayed under 'Actions' against that backup schedule to suspend it. Limitations Client initiated restore can be suspended from the backup server only if the client is running StoreGrid version 2.3 or higher.

221 StoreGrid Server Dashboard Overview The Server dashboard has four sections Snapshot of recent 5 successful/failed backups. Client Activity - status of clients currently connected to the server. Disk space utilization for the server with Alert Settings. Licensing details. How to get here in the StoreGrid Web Console? In the top menu, select: "Reports->Server Dashboard" Snapshot of recent backups This table gives snapshot of 5 last successful/failed backups. The table has the following details: Group Name - The group from which this backup schedule's StoreGrid client is backing up from. Client Name - This is the StoreGrid client from which this backup schedule is backing up from. Backup Name - The name of the backup schedule. Start Time - The time at which the backup schedule started to backup. End Time - The time at which the backup completed. Files - The total number of files available for backup in this backup schedule. Skipped Files - The number of files that could not be backed up. Some of the reasons a file may not be backed up are: The file is being modified. The file did not have appropriate permissions and hence could not be read. Skipped Folders - The number of folders that could not be backed up. Some of the reasons why a folder may not be backed up are: The folder did not have appropriate permissions for StoreGrid to read. The folder may have been modified while StoreGrid is trying to backup it up. The folder may have temporarily available when StoreGrid listed the files/folders to backup but was later not available when StoreGrid tried to backup. Clicking on the 'View' link will take you to a page which lists the folders that were skipped and the reason StoreGrid skipped the folders. No. Of Full backups - This total number of full backup that has been taken.

222 Remarks - The final result of the backup operation. Whether successful, failure, or incomplete etc. The More Details page lists all the successful/failed backups with Start time, End time, Number of files, Number of full backups, Skipped files, Skipped folders and any remarks from the backup report. Also, there is an option to view successful/failed backups in the last 1 day, 1 week, 1 month etc. 'Select Columns' Icon - This will list all the available columns. User can choose the columns to be displayed. Current Client Activity This table provides details on the clients connected to the server currently. The table has the following details : Group Name - The group from which this backup schedule's StoreGrid client is backing up from. Client Name - This is the StoreGrid client from which this backup schedule is backing up from. Backup Name - The name of the backup schedule detailed in this row. Status - This shows the status of the client activity. And the six icons in this column represent the current status of backup, restore, delete, replication operations, retention and moving backup data from one location to other location for this backup schedule. The following describes the different icons: Backup : Triangle icon Restore : Inverted triangle icon Delete : Cross icon Replication : Play Triangle icon Move Backup : Double Triangle icon Running Retention Cleanup : Rotating arrows icon Storage Disk space used on / by this server : Graphical chart - This provides information about disk space used by all the clients backing up to this server. The pie chart shows the cumulative total disk space allotted and used by all the clients backing up to this server. Alert Settings - StoreGrid can alert you whenever the used space on the server goes beyond certain level. By default it will be set to 75%, so that an alert message will be displayed if the usage goes over 75% of allocated storage in server. You can set this to your desired level. To change this, enter the numeric value inside the text box and click "Ok" to save the settings. Licensing This StoreGrid server's license - This shows the expiry date of this StoreGrid server's license.

223 Client Dashboard Overview The client dashboard has two sections 1. Snapshot of last 10 backups 2. Current Client Activity How to get here in the StoreGrid Web Console? In the top menu, select: "Reports->Client Dashboard" Snapshot of last 10 backups This table provides summary of the last 10 backup schedules executed by the client. The table has the following details: Backup Name - The name of the backup schedule Backup Server(s) - 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. Last Backup - The time at which the Last backup was done on to the backup server for this backup schedule. Total Files Listed - The total number of files listed by StoreGrid for backup. Unprocessed Files - The number of files that were listed by StoreGrid but not backed up. StoreGrid makes a list of files to be backed up and simultaneously starts backing up the listed files one at a time. If the StoreGrid client abruptly stops backing up, then may not be few unprocessed files the files that StoreGrid listed for backup but could not complete backing up the files. Some of the reasons why the StoreGrid client would stop backing up abruptly are listed below: 1. Client exceeded the allotted backup space on server. 2. No drive space available in the server. 3. Active backup schedule was aborted at the Server side. 4. Active backup schedule was suspended in the client. 5. StoreGrid was stopped in the server or the client side. Protected Files - Total number of files that have successfully backed up. 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. Skipped Folders - The number of folders that could not be backed up. Some of the reasons why a folder may not be backed up are: 1. The folder did not have appropriate permissions for StoreGrid to read. 2. The folder may have been modified while StoreGrid is trying to backup it up. 3. The folder may have been temporarily available when StoreGrid listed the folders to backup but was later not available when StoreGrid tried to backup. Success Rate - This gives the percentage of total files that were successfully backed up. More details >> links to "Summary of Backup Reports (consolidated)" page which contains all backup schedules with schedule status and other details. Select Columns Icon - This will list the available columns and user can select the columns to be displayed in the table.

224 Client Activity [current] This table provides a summary of current activity (up to 10 records). The table has the following details: Backup Schedule - The name of the backup schedule Backup Server(s) - Backup server on to which this backup schedule backs up. Status - This shows the backup/restore/deletion status - a green icon indicates an operation in progress. Licensing This StoreGrid license - This shows the expiry date of this StoreGrid license.

225 Client Backup Report Overview This section will give you information about the client backup report for the configured backup schedule in StoreGrid. How to get here in the StoreGrid Web Console? In the top menu, select: "Reports->Backup Reports". This will list all the backup schedules in a table format. Click on the backup name link to see the detailed backup report. Client Backup Report The client backup report is organized into two sections as Summary Reports and Historical Backup Reports. Summary Reports Consolidated Report The Consolidated Report gives a cumulative report on backups done across schedules. The timestamp specified in the header "Consolidated Backup Report As On TIMESTAMP" is the time at which the backup was last scheduled. It is possible that there are no changed files to backup when the backup was scheduled last time. But the consolidated report would always show the time the backup was last scheduled, even if no files were backed up in the last scheduled backup. Below are other information shown in this section: Total Files Listed - The total number of files that StoreGrid listed over the different schedules of this backup. Unprocessed Files - The number of files that were listed by StoreGrid but not backed up. StoreGrid makes a list of files to be backed up and simultaneously starts backing up the listed files one at a time. If the StoreGrid client stops backing up abruptly, then there may be some unprocessed files the files that StoreGrid listed for backup but could not complete backing up the files. Some of the reasons why the StoreGrid client would stop backing up abruptly are listed below: Client exceeded the allotted backup space on server. No drive space available in the server. Active backup schedule was aborted at the Server side. Active backup schedule was suspended in the client. StoreGrid was stopped in the server or the client side. Total Files Protected - The number of files that were successfully backed up to the backup server over the different schedules of this backup. Skipped Files - The number of files that could not be backed up. Some of the reasons a file may not be backed up are: The file is being modified.

226 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 was skipped. Skipped Folders - The number of folders that could not be backed up. Some of the reasons why a folder may not be backed up are: The folder did not have appropriate permissions for StoreGrid to read. The folder may have been modified while StoreGrid is trying to backup it up. The folder may have been temporarily available when StoreGrid listed the folders to backup but was later not available when StoreGrid tried to backup. Clicking on the 'View' link will take you to a page which lists the folders that were skipped and the reason StoreGrid skipped the folders. 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 & Directories List - Clicking the "Show" button here will list the files and folders configured for the backup with their Files/Folders filter settings. Database List - Clicking the "Show" button here will list the SQL Server database(s) configured for backup. This will be listed for Basic and Advanced SQL Server backup schedules. Mailbox Details - Clicking on the "Show" button here will list the users configured for Advanced Exchange Mailbox backup with their total number of mailbox folders, items(messages, calendar and etc.,) and size. Last Backup Report The Last Backup Report gives a report on the last time some files were actually backed up. It is possible that this time is different from the time shown in the Consolidated Report. The reason is that the last backup time will not get updated when in the last schedule no files were backed up. For example, if the first backup is done at 1-Jan-2006 and the backup is configured to be scheduled daily, on 2-Jan-2006, the backup would be scheduled and if no files had changed then StoreGrid would not backup any file on 2-Jan In this case the Last Backup Time would show 1- Jan-2006 and the Consolidated Report Time would show 2-Jan Below are other information shown in this section: Total Files Listed - The total number of files backed up when the backup during the last backup. Unprocessed Files - The total number of files backed up when the backup during the last backup. Client exceeded the allotted backup space on server. No drive space available in the server. Active backup schedule was aborted at the Server side. Active backup schedule was suspended in the client. StoreGrid was stopped in the server or the client side.

227 Total Files Protected - The number of files that were successfully backed up to the 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: The file is being modified. 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. Skipped Folders - The number of folders that could not be backed up. Some of the reasons why a folder may not be backed up are : The folder did not have appropriate permissions for StoreGrid to read. The folder may have been modified while StoreGrid is trying to backup it up. The folder may have been temporarily available when StoreGrid listed the folders to backup but was later not available when StoreGrid tried to backup. Clicking on the 'View' link will take you to a page which lists the folders that were skipped and the reason StoreGrid skipped the folders. 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. Time Taken - Total time taken for the last backup to complete. Last Schedule Summary The Last Schedule Summary gives a report on the last time backup was scheduled. It is possible that this time is different from the time shown in the Last Backup Report. The reason is that the last backup time will not get updated when in the last schedule no files were backed up. For example, if the first backup is done at 1-Jan-2006 and the backup is configured to be scheduled daily, on 2-Jan-2006, the backup would be scheduled and if no files had changed then StoreGrid would not backup any file on 2-Jan In this case the Last Backup Time would show 1- Jan-2006 and the Last Schedule Time would show 2-Jan Below are other information shown in this section: Last Schedule Start Time - The time at which the backup was last scheduled. It is possible that there are no changed files to backup when the backup was scheduled last time. Last Schedule Time Taken - Total time taken for the last schedule to complete. Remarks - Remarks from StoreGrid about last schedule backup. Warning Messages - Messages from StoreGrid about any problems during backup. Disk Space Utilization This section displays the information disk space used by this client [ CLIENT_NAME ] in Server [ BACKUP_SERVER_NAME ] as shown below:

228 Allotted Space[for client] - The space allotted for the client in the backup server. Used Space[for client] - Field displaying the used backup space by this client in the backup server. Used Space[for this backup schedule] - Field displaying the used backup space for the selected backup schedule in backup server. Other Relevant Reporting Information Original files size - The total size of all the files transferred including the deltas transferred during incremental backups. Transferred size - The total number of bytes transferred to the server as part of this backup. Compression ratio - The percentage compression achieved. No. of Schedule Completed - This is the total number of times the backup has been scheduled. No. of Full Backups - This is the total number of full backup that has been taken. Backup Type - Type of backup will be displayed for the Basic and Advanced Plugin backups. Automatic Directory Monitoring - This shows whether Automatic Directory Monitoring is enabled or disabled for the backup. Historical Backup report The historical backup report gives a report for each of the completed schedules the backup. The full backups and their respective incremental are shown from latest to oldest in a table format. Each row of the table represents a report for a backup schedule. Clicking on the "arrow" link on the left side of a row will expand the row and show more details about the backup schedule. The following information is shown in each row of the table: Backup Name - The name of the backup schedule. Backup Server - The name of the backup server to which the backup is being done. Start Time - The time at which the backup schedule started backing up the data. End Time - The time at which the backup schedule completed backing up the data. Schedule Type - The type of the schedule.( Full Backup or Incremental or (Log or Differential for SQL/Exchange Sever backups). Time Taken - The total time taken for the backup schedule to complete. Total Files Listed - The total number of files listed for backup in this backup schedule. Protected Files - The number of files that were successfully backed up to the backup server. Skipped Files - The number of files that could not be backed up. Skipped Folders - The number of folders that could not be backed up. Some of the reasons why a folder may not be backed up are: The folder did not have appropriate permissions for StoreGrid to read.

229 The folder may have been modified while StoreGrid is trying to backup it up. The folder may have been temporarily available when StoreGrid listed the folders to backup but was later not available when StoreGrid tried to backup. Clicking on the 'View' link will take you to a page which lists the folders that were skipped and the reason StoreGrid skipped the folders. Success Rate - This gives the percentage of total files that were successfully backed up. Original Size - The original size of the backup data transferred so far. Compressed Size - Displays the compressed size of the original backup data. Compression Ratio - Displays the compression ratio of the original and compressed backup data. Result Messages - The final result of the backup operation; successful/ failure/ incomplete etc. Added Files - The number of new files backed up in this schedule. Note that this is the total number of files backed up whenever a full backup was done. Unprocessed Files - The number of files that were listed by StoreGrid but not backed up. StoreGrid makes a list of files to be backed up and simultaneously starts backing up the listed files one at a time. If the StoreGrid client abruptly stops backing up, then may not be few unprocessed files the files that StoreGrid listed for backup but could not complete backing up the files. Some of the reasons why the StoreGrid client would stop backing up abruptly are listed below: Client exceeded the allotted backup space on server. No drive space available in the server. Active backup schedule was aborted at the Server side. Active backup schedule was suspended in the client. StoreGrid was stopped in the server or the client side. Modified Files - The number of modified files backed up. Note that this number is zero for all full backups. Deleted Files - The number of deleted files backed up. Note that this number is zero for all full backups. Only for incremental backup this can have a positive value. SQL Server Backup Details The SQL Server Backup details gives a report for each database configured for the backup schedule. Below are the informations shown in this section: SQL Server Instance Name - Name of the SQL Server Instance in which database backup was performed. Database Name - Name of the database configured for backup. Original Database Size - Size of the database configured for backup. Start Time - The time at which the backup schedule started dumping the data to the local temporary location.

230 End Time - The time at which the backup schedule completed the local dump process. Total Time Taken - The total time taken for the backup schedule to complete the local dump process. Size of backup before compression - The total size of the files locally dumped by the SQL Server dump utility in client which has to be transferred to backup server. Size of backup after compression - The compressed size of the files transferred to backup server. Compression ratio with original database size - The percentage compression achieved with the original size of the database. Compression ratio with size of backup before compression - The percentage compression achieved with the size of the dumped files. Status - Status will report the success or failure of local dump backup process. Verify integrity status - Displays status about verification of the backup once it completes. Result Messages - Messages from SQL Server dump utility about the local dump backup process. Exchange Server Backup Details The Exchange Server Backup details gives a report for Storage Group(s)/MailStore(s) configured for the backup schedule. Below are the informations shown in this section: Exchange Server Name - Name of the Exchange Server in which Storage Group(s)/MailStore(s) backup was performed. Start Time - The time at which the backup schedule started dumping the data to the local temporary location. End Time - The time at which the backup schedule completed the local dump process. Total Time Taken - The total time taken for the backup schedule to complete the local dump process. Size of backup before compression - The total size of the files locally dumped by the Exchange Server dump utility in client which has to be transferred to backup server. Size of backup after compression - The percentage compression achieved with the original size of the database. Compression ratio with size of backup before compression - The percentage compression achieved with the size of the dumped files. Status - Status will report the success or failure of local dump backup process. Result Messages - Messages from Exchange Server dump utility about the local dump backup process. Exchange Mailbox Backup Details The Exchange Mailbox Backup details gives a report for user's mailboxes configured for the backup schedule. Listed below is the information shown in this section: Exchange Server Name - Name of the Exchange Server in which Mailbox backup was performed.

231 Start Time - The time at which the backup schedule started dumping the data to the local temporary location. End Time - The time at which the backup schedule completed the local dump process. Total Time Taken - The total time taken for the backup schedule to complete the local dump process. Status - Status will report the success or failure of local dump backup process. Result Messages - Messages from Exchange Server Mailbox dump utility about the local dump backup process. Backed up Exchange User Mailbox Details This tabular summary of each user's mailbox backup includes the following: User Name - The mailbox user for which backup report information is generated. Folder Name - Name of the user's mailbox folders such as Inbox, Contacts, Tasks and etc., Total Items - Total No. of items (messages, contacts and etc.,) that were successfully backed up to the backup server. Size - The total size of the user's mailbox folder items locally dumped by the Exchange Mailbox dump utility in client before transferring to the backup server. Limitations 1. Exchange Backup Report will not have details about the Storage Group(s)/MailStore(s) configured for backup. 2. List of Protected/Skipped file(s) list will be available only for the last backup in the historical backup report.

232 Detailed Restore Report Overview This section will give you information about the detailed restore report for the restored backup data in StoreGrid. How to get here in the StoreGrid Web Console? In the top menu, select: "Reports->Restore Reports". This will list all the backup schedules (in a tabular format) for which a restore operation has been performed. Click on the backup name link to see the detailed restore report. Restore Report This page gives a detailed report of all the restore operations done for this backup. The restore reports are displayed in a table format with each row representing a restore operation. Click on the "Show Report" icon at the start of each row to show/hide a detailed restore report for that restore operation. Summary of Restore Report The following summary is provided in each row of the restore report table: Backup Server Name - The backup server from which the restore was done. Start Time - The time at which the restore operation was started. End Time - The time at which the restore operation was completed. Total Files - Total number of files present in the backup server that need to be restored. Number Of Files Restored - The number of files successfully restored. Number Of Files Skipped - The number of files that could not be restored. Some of the reasons a file may not be restored are: Error in opening the original file in the server. Error in opening the version file in the server. Error in creating the file in the client. Error in writing to the file in the client. Error in decompressing the original file. Error in decompressing the version file. Error in loading the original file for applying the rsync delta patch. Error occurred while applying the rsync delta patch on the original file. 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 as to why the file was skipped.

233 Success Rate - The percentage of files that were successfully restored. Detailed Restore Report The following additional details are given in the detailed restore report which is shown when you click on the left hand side icon "Show Report" in the respective restore report table row. Restore Location - The destination 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! If the restore was done to the original location, then it simply says so! Total Time Taken - The time taken for the full restore operation to complete. Selected Version For Restore - The timestamp based version selected for restore. Restore Deleted Files - Whether the deleted files were restored or not. Restore Advanced Option Selected - Which of the advanced options were selected for restore. Total Remaining Files - Number of files that could not be restored. Transferred Size - The total bytes transferred from the server to the client. Original Size - The original size of the data that was restored. Warning Messages - If there was a problem during restore, warning messages would be generated to identify the problem. Remarks - The final result of the restore operation. Whether successful, failure, or incomplete etc. View List of Skipped Files This page lists all the files that could not be restored to client machine. The table is shown 100 files at a time. You can browse through the files using the "Next" and "Last" links on the top. SNo. - The serial number column to keep track of the number of files. File Name - The name of the file backed up. Location - The directory in which the file is present. Remarks - This will give the reason why the file could not be restored to client machine. SQL Server Restore Details The following details are given in the detailed restore report of SQL Server Restore Details section, which is shown when you click on the left hand side icon "Show Report" in the respective restore report table row. SQL Server Instance Name - Name of the SQL Server Instance in which database restore was performed. Original Database Name - Name of the database configured for backup.

234 Restored Database Name - Name of the database selected in the "Restore as database" drop-down option will be displayed. For a new database, the database will be created and then the contents of the backup will be restored. Database Restore Start Time - The time at which the SQL Server restore operation was started. Database Restore End Time - The time at which the SQL Server restore operation was completed. Total Time Taken - The time taken for the SQL Server database restore operation to complete. Original Database Size - The size of the original database configured for restore. For an existing database, the size of the database before restore operation will be displayed. Restored Database Size - The size of the database after restore operation. Force Restore - The status of the option "Overwrite the existing database" selected while restoring database. This option will be selected, if the existing database name should be replaced with a different name. Recovery State - This displays the "Recovery State" option selected while restoring database as "Restore with Recovery"/"Restore with Norecovery"/"Restore with Standby". Database Physical Files - This displays the name and location of the physical files used when database is restored. This field will be displayed in report, if you are restoring to a different server or to a different database name, or you have changed these options for both the data file and the transaction log file while configuring restore. Standby file - This displays the standby file and location used to undo uncommitted transactions when the database is brought fully online. This field will be displayed if the "Recovery State" option is selected as "Leave the database in read-only mode". Database Restore Status - Displays the database status{online/offline/restoring/recovering/suspect} after restore operation. Result Messages - Messages generated from SQL Server during restore operation will be displayed here. Remarks - Remarks from StoreGrid about the SQL Server during restore operation. Exchange Server Restore Details The following details are given in the detailed restore report of Exchange Server Restore Details section, which is shown when you click on the left hand side icon "Show Report" in the respective restore report table row. Original Exchange Server Name - Name of the Exchange Server from which Storage Group(s)/MailStore(s) was configured for backup. Restored Exchange Server Name - Name of the Exchange Server in which Storage Group(s)/MailStore(s) restore operation was configured. by default both the original and restore Exchange Server name will be same. Mount Database after restore - Displays the status, whether the Mount Database After Restore check box was selected for restore operation. Exchange restore start time - The time at which the Exchange Server restore operation was started. Exchange restore end time - The time at which the Exchange Server restore operation was completed.

235 Total Time Taken - The time taken for the Exchange Server restore operation to complete. Temporary location for log and patch files - The temporary directory (in the client machine) where the log and patch files are temporarily stored. During the restore process, Exchange Server will first apply the older transaction logs from the temporary directory and then apply the more recent logs from the original location. This directory will be different from the one where the original log files are stored. Exchange restore status - Status will report the success or failure of the Exchange Server restore operation. Result Messages - Messages generated from Exchange Server during restore operation will be displayed here. Remarks - Remarks from StoreGrid about the Exchange Server during restore operation. Restored Exchange Server Mail Store Details This tabular summary of each Exchange Server restore includes the following: Mail Store Name - Name of the MailStore. Storage Group Name - Name of the Storage Group Name. Exchange Server Name - Name of the Exchange Server in which Storage Group(s)/MailStore(s) restore was configured. Status - This field will display the status of the database is mounted or dismounted after restore process. Exchange Mailbox Restore Details The following details are given in the detailed restore report of Exchange Mailbox Restore Details section, which is shown when you click on the left hand side icon "Show Report" in the respective restore report table row. Exchange Server Name - Name of the Exchange Server from which user's mailbox was configured for backup. Exchange restore start time - Time at which the Exchange Mailbox restore operation started. Exchange restore end time - Time at which the Exchange Mailbox restore operation completed. Total Time Taken - Time taken for the Exchange Mailbox restore operation to complete. Exchange restore status - Status reporting the success or failure of the Exchange Mailbox restore operation. Remarks - Remarks on the restore operation. Restored Exchange User Mailbox Details This tabular summary of each users mailbox restore includes the following: User Name - The mailbox users for which restore report information is generated. Folder Name - Name of the user's mailbox folders such as Inbox, Contacts, Tasks and etc., Total Items - Number of items (messages, contacts, etc.) restored. Size - User's mailbox folder size after the restore operation.

236 Client Backup Status Report Overview The Client Backup Status report lists the status of the backup schedules from the clients backing up to the backup server. The report can be filtered based on the status of the backup schedules, the date and the groups. Also this report can be scheduled to be sent in an on a daily or a weekly basis. How to get here in the StoreGrid Web Console? In the top menu, select: "Reports -> Client Backup Status Reports" View Report 'View Report' page has backup status reports for all clients. These reports can be filtered based on the backup status, group and date. By default, the reports will be show the status of all backup schedules of all groups for the last 24 hours. You can also select the columns that are to be displayed in the report. The default report that is shown in this page can be changed by creating a filter (click on the 'Filter' link) and setting the filter as the default by clicking on the 'Change settings for default view' icon in the top right corner of the report. Client Backup Status Report has the following fields: Status : Indicates backup status; Success/Failure/Partial/Missed. Failed: Failed, manually suspended from the client, manually aborted in the backup server. Missed: Didn't run at the scheduled time, and even in 1 hour after the scheduled time. Partially Completed: Some files or folders were skipped. Successfully Completed: Completed successfully, no new or modified files to backup. Group Name: Name of the group. Clients: StoreGrid ID of the client machine. Backup: Name of the backup schedule. Schedule Type: Full backup/incremental Backup. Backup Start Time: Time when the backup was scheduled. Backup End time: Time when the backup ended. Total Time Taken: Time taken for the backup schedule to complete. Next Schedule Time: Time when the backup is scheduled next. No of Attempts: Number of attempts StoreGrid made to run the backup schedule. In case of failure, StoreGrid will try to run the backup again after 5 minutes and the number of such attempts is captured here. Total Files Listed : Total number of files available for backup. Protected Files: Number of files that were successfully backed up to the backup server. Skipped Files: Number of files skipped in a particular backup schedule. Skipped Folders: Number of folders skipped in a particular backup schedule. Remarks: Warning message. Filter: The backup reports can be filtered by backup status, group and date of the backup schedule. You can create as many as ten filters. To create a filter, click on the 'Filter' link at the top of the status report and it will open the Filter Settings windows where you can enter the following details:

237 Filter by backup status: This section has the following options: o All: Will include report of all backup schedules o Failed: Will include the report of only those backup schedules that failed, were manually suspended from the client or were aborted in the backup server. o Missed: Will list backup schedules that didn't run at the scheduled time, and even in 1 hour after the scheduled time. o Partially Completed: Will list backups that completed partially i.e. some files or folders were skipped. o Successfully Completed: This includes backups which completed successfully, including those backups where there were no new or modified files to backup. Filter by group: Backup reports can be generated either for all the groups or for a particular group. Select the group [all groups/default/...] for which the report is to be generated. Filter by date: Backup reports can be filtered by date of the backup schedule. A data range can be also be specified and it should be within the current month and the previous month. Sort by Column: The reports can be sorted by various columns. By default, the report is sorted by the backup end time. The reports can not be sorted by the 'Total Time Taken'. Show: The number of reports to be listed per page, default been 25. Delete this Filter: To delete a filter, select the filter from the drop down and then click on the 'Delete this filter' link. Default filter (filter saved in 'Change Settings For Default View' page) cannot be deleted. Export: The status report that is currently listed in the 'View Report' page can be exported into a comma delimited (CSV) file by clicking on the 'Export' link at the top of the status report. The status report that is current listed in the 'View Report' page can be sent as an . Click on the ' ' link at the top right corner above the status report and enter the addresses to which this report should be sent. When entering more than one addresses, the addresses should separated by a comma. Change settings for default view (icon): By default the Client Backup Status Report shows the status of all the backup schedules from all groups for the last one day. You can configure it to show a different status report when the page loads by setting the appropriate filter in default settings page which can be accessed by clicking on the 'Change settings for default view' (icon) at the top right corner above the status report in the View Report page. Schedule Report StoreGrid can be scheduled to send report of the status of the backups on a daily or weekly basis. To schedule the reports, click on the 'Schedule Report' tab and enter the following details: To ID: Recipient IDs, multiple addresses should be separated by comma. Filter by backup status: Reports can be filtered on account of their backup status, Failed/Missed/Partially Completed/Successfully Completed. Filter by group: Select the group [all/default/...] for which the report is to be generated. Schedule: The reports can be ed either daily at a specified time or weekly at a given day and time. Limitations Reports older than the previous calendar month cannot be viewed. 'Total files listed' will not be available for clients running older version (< 2.3.5) of StoreGrid. For clients running older version (< 2.3.5), in error cases like authorization failure, group/client deactivated etc., the 'No of Attempts' value might not be correct. 'Next Schedule Time' will be calculated in the backup server based on the scheduling type of the backup. If a backup is interrupted in client side and is rescheduled after 5 minutes, the backup server may still show the next schedule time based on the backup schedule configuration.

238 List of Events How to get here in the StoreGrid Web Console? In the top menu, select "Events --> Events". 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. 4. 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. Filtering Events The Events UI allows you to filter events on one or more of the following event attributes: StoreGrid Module - You can filter based on which module of StoreGrid generated the events. Choose the module from the list in the drop down box. Event Type - You can filter events depending on the severity of the event. Choose the severity from the drop down box. Event Time - You can filter events based on a time range. Choose the From and To times by clicking on the "small box" adjacent to the text field. Description - You can filter events on the basis of the message attribute in the event. The message describes the problem because of which the events were generated. You might, for example, wish to see other events generated with a similar message.

239 Shared Events How to get here in the StoreGrid Web Console? Choose the menu item "Events->Shared Events". Any StoreGrid installation can share its events to a set of configured servers. This feature helps system administrators have a consolidated view of events in a central server from multiple StoreGrid installations. Note that StoreGrid can only send events to another StoreGrid which is operating either in a Server of Client-Serve mode. Hence a StoreGrid installation operating as a pure Client cannot be a recipient of Shared Events. So the Shared Events menu item will not be available in StoreGrid installations operating as pure Client. Filtering Shared Events The Shared Events UI allows you to filter events on one or more of the following event attributes: Source Machine - This is the source StoreGrid from which the events were generated and shared. You can filter using this attribute by providing the StoreGrid ID of the source. Before giving the source StoreGrid ID, you should also choose the Group to which the StoreGrid source belongs to from the choice box provided above the text field. Note that you can also just choose the Group and do a filter (without giving the source StoreGrid ID) to view a consolidated list of events from the chosen group. StoreGrid Module - You can filter based on which module of StoreGrid generated this events. Choose the module from the list in the choice box. Event Type - You can filter events using the severity of the event. Choose the severity from the choice box. Event Time - You can filter the events based on a time range. Choose the From and To time by clicking on the "small box" adjacent to the text field. Description - You can filter based on the message attribute in the event. Message describes the problem, because of which the events were generated.

240 StoreGrid Administration The StoreGrid Administration features (available under the Administration menu), are related broadly to administering and configuring a StoreGrid installation which is operating as a Client or a Client-Server. The following administration features are available in StoreGrid: Apply License Key Authenticate The Client With The Server Add/Delete a Peer (StoreGrid Clients or Servers) Settings Client Filters User Management Events Configuration Local To Remote Server Migration Plugin Settings [ For Windows ] Mysql Settings [ For Windows ] Discovery Configuration Mapped Drive Settings Backup Window Settings Configure Automatic Software Updates Client Software Update Reports Client Side Bandwidth Throttling Test connectivity to Backup Server

241 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 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. 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.

242 Authorization of Client with Server How to get here in the StoreGrid Web Console? In the top menu, select: "Administration->Authenticate Client". Client authorization is an optional security feature, unless the server you are backing up to has made it a strict requirement in the interest of providing additional layers of security. There are two scenarios described here to help you decide whether to configure your own password for client-server authorization. 1. If Auto Authorization is disabled in the server you are backing up to, then your client (StoreGrid ID) should have been added in the server by the server administrator before you can connect to the server. You should get your password from the server administrator and authorize yourself once. You can subsequently change the password from this page and authorize again. Note that you have to authorize your client with the server only once. The StoreGrid client will internally maintain this password and authorize itself automatically whenever it connects to the server. 2. If Auto Authorization is enabled in the server you are backing up to, then you don't need to configure your own password for authenticating this client with the backup server. Automatic authorization by the server does not mean that any client could backup to the backup server. Only the clients which uses a valid license key recognized by the backup server are allowed to backup to the server. So there is a level of authentication already, with the server enforcing it based on the license keys registered with server. If you rely on the Auto Authorization feature, then another user who has access to your license key could create a StoreGrid installation with your StoreGrid ID and possibly can restore your data. But if you configure your own password and authorize this password with the server, then no other client can spoof your StoreGrid ID (and license key) and connect to the server unless he/she also knows the password you used. In this page you can authenticate the client with a backup server by providing the password that is set in the backup server for this client. If there is no password set in the backup server for this client and if Auto-Authorization is enabled for this client in the backup server, then you can set a new password for this client in the backup server. Server Name: Select the backup server that you want this client to authenticate against. Once selected, StoreGrid will check if this client has already authenticated with the selected backup server. If the client had earlier authenticated and if the password was then changed in the backup server, then you can reauthenticate this client with the changed password. Enter the password and click on re-authenticate button. If the client had never authenticated with the backup server before or the password was cleared in the client, then you will prompted to enter the new password. After entering the new password and confirming it, press the Authenticate button. o o If the client is set with a password in the backup server, the new password will be verified against it to authenticate the client. If there is no password set for the client in the backup server and if Auto-Authorization is allowed for this client in the backup server, then the new password will be set for the client in the backup server. The table at the bottom of this page lists the backup servers that this client has authenticated against along with the servers this client is backing up to. Clicking on the reset password button icon will clear the client's password for that server.

243 Test connectivity to Backup Server Overview With this feature you can check the connectivity from the client to the Backup Server. It also checks the various settings in the backup server to identify if the client can backup to the backup server. How to get here in the StoreGrid Web Console? In the top menu, select: "Administration -> Test Connectivity to Backup Server". This is also available in step 3 in Backup - > Add Backup Schedule page. Test connectivity to Backup Server This feature checks for the following: DNS lookup - It checks if the client can resolve the backup server's hostname (FQDN). If this check fails, then check the DNS server in the client's network and make sure there is an entry for backup server's hostname. If the backup server has a static IP then try using that IP instead of the hostname. Telnet & Ping - It checks if the client is able to reach the server on the configured backup port. If this check fails, make sure the backup server is online and StoreGrid is running on it. Make sure that this client is configured with the same Backup Port number as the backup server. You can check the backup port from the <Ports Server="xxxx" entry in the SGConfiguration.conf file in the conf folder under StoreGrid installation directory. Also make sure that the firewall on both the client and the server side allows TCP/IP traffic from client to the server on the above port. Server Type - This checks if the server connected to is a backup server or a replication server. Clients can restore files from the replication server. Clients cannot backup to a replication server. StoreGrid Edition and Version - It checks the compatibility between StoreGrid editions/versions running in the client and the server. Client running SP edition cannot backup to a server running Pro Edition and vice versa. A client running a higher version of StoreGrid cannot backup to a backup server running a lower version of StoreGrid. For example, v2.2.5 client cannot backup to a backup server running StoreGrid v Is this client available in the server - This checks if the client is already added in the backup server. If the client is not in the backup server, it will be added when the client connects to the backup server for the first time. The client will be added under the group name that was specified during the installation of StoreGrid in the client. If that group is not available in the backup server, the client will be added under the 'Default Group'. License - This checks if the backup server has a valid server license installed. If this check fails, make sure a valid backup server license is installed in the backup server. Authentication - This checks if the client is authorized to backup to the server. If the client is set to 'Deny-Auto- Authorization' in the backup server, then the client has to be first authenticated with the backup server before it can start backing up. If the group that this client belongs is set to 'Deny-Auto-Authorization', then the client has to be first added in the backup server with a password and the client needs to authenticate itself with the backup server with that password. If the client is added to the backup server with a password, then the client has to first authenticate with the server even if the group and the client are set to 'Allow-Auto-Authorization'. Activated - Checks the activation status of group/client/server.

244 Add / 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 "Add Peer(s)" table. 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. StoreGrid ID - This is an optional field to enter the StoreGrid ID of the peer (if known) which needs to be added / discovered. If you do not give a StoreGrid ID, StoreGrid will try and discover the StoreGrid ID too, but it may take some time. Until StoreGrid discovers the ID, the discovered peer will be shown using its fully qualified machine name. 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 Peer Button - Once the machine name and the machine type are specified as described above, you can make StoreGrid discover it by clicking on the Add Peer Button. Delete Peer - Once added, the machines are listed in the table available below the Add Peer button with their corresponding details. The availability of the added machine can be interpreted from the image displayed before the StoreGrid ID; a blue icon indicates that the machine is available, and a black icon denotes that it's unavailable. To delete a StoreGrid peer, simply click on the delete icon in the row corresponding to the peer.

245 Settings How to get here in the StoreGrid Web Console? In the top menu, select: "Administration->Advanced Options" and click on the " Settings" icon in the left hand side. StoreGrid has the capability to all the client-side and server-side reports to interested recipients. The following describes the configuration options: Enable - First you need to check this checkbox to enable feature in StoreGrid and then provide inputs to the rest of the fields. Outgoing (SMTP) Server - This is the SMTP server StoreGrid should use to send the . This will most probably be the same server as the one you use in your client (Outlook, Eudora etc.). If you are not sure, check with your Systems Administrator. More Options Link - If you click on the "More Options" link you will be shown couple of more advanced options: Outgoing (SMTP) Server Port Number - By default SMTP servers use port number 25. If by any chance it is different in your case, you can provide the port number here. This SMTP Server Requires Authentication - If your outgoing server (SMTP server) requires authentication before it can accept an for sending out, you need to check this checkbox. You will get the following three options to configure the username, password and the authentication type. i. User Name - Enter the user name. This will most probably same as the user name you use in your client to receive mails. ii. Password - Enter the password for the above user name. iii. Authentication Type - Provide the type of authentication required by the SMTP server. If you are not sure leave it with the default value "AUTO". Sender Id - Provide the ID of the sender from which the reports should be ed. The will be delivered to the recipients as if coming from the Sender ID you provide here. Test Mail Server - Once you have entered the SMTP server details, click on the link "Test Mail Server" and check if it works by entering an ID in the 'To ID' field and then clicking on "Send Test ". A test will be sent to the 'To ID'. If you don't receive the test , check the SMTP server settings again. Recipients Id - Enter the recipients' IDs here. You can select a single address for all "Success" reports and for all "Failure" reports. Or, you could specify different IDs for different "Success" and "Failure" reports. In case you want to the reports to multiple recipients, specify the s IDs separated by commas. (for example: joe@gmail.com, smith@msn.com). You can also configure the conditions in which the reports should be sent by accessing the 'Client Filters' page through the 'Client Filters' icon in the left hand side of the "Administration->Advanced Options" page.

246 Client Side Filtering How to get here in the StoreGrid Web Console? In the top menu, select: "Administration->Advanced Options" and click on 'Client Filters' on the left hand side. Please note that the "Configure Filtering" link is activated only after you've enabled your basic configuration. By default when Configuration is enabled, reports are sent for all "conditions" that are applicable to the "modules" (backup/restore/delete) selected. The Filtering feature allows you to specify specific conditions for which reports need to be ed for the modules selected in " Configuration". Client Side Filter Settings: There are two filters that can be applied here. With the first, reports will be ed to specified recipients for each selected module (backup/restore/delete) depending on the conditions selected, as described below. 1. When Backup/Restore/Delete completes successfully. 2. When Backup/Restore/Delete fails. 3. When there are no New/Modified files for backup (when the backup is scheduled) 4. When backup is manually suspended 5. When Backup/Restore is partially completed The second filter allows you to backup, restore and delete reports only for specific backup schedules (those listed in the 'Enabled Backup Schedules' box). By default, reports are sent for all backup schedules in the client. Manually moving some backup schedules to the "Disabled Backup Schedules" window will prevent reports associated with those schedules from being ed.

247 Mapped Drive Settings (For Windows Only) Overview If StoreGrid is running as a Service in Windows XP/2003/Vista OS machines, mapped drives may not be recognized by StoreGrid and therefore that may not be listed. To resolve this, you can map the drives in this page and then used the mapped drives to configure backups from them. How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: " Administration -> Advanced Options" page and click on the 'Mapped Drive Settings' icon on the left hand side. Mapped Drive Settings 1. Install StoreGrid as a Service with the administrative privileges. 2. Go to the 'Administration -> Advanced Options -> Mapped Drive Settings' page. Give the Drive Name and drive path, i.e. the UNC Path (\\server\sharename) for the mapped drive. Note: The 'User Name' and 'Password' details are not mandatory. They are needed only if Windows OS requires the 'User Name' and 'Password' to access the mapped drive. 3. Add mapped drives by clicking on ' Add Mapped Drive' button. The mapped drives will get listed in the 'Add Backup Schedule' page and you can configure backup schedule to include files and folders in them. The mapped drives will be listed in other pages as well, e.g. 'Server Settings' page, 'Local To Remote Server Migration' page, 'Edit Client Configuration Page', etc Troubleshooting Tips Mapping the drive letter to the UNC path failed with the error: <Error> This error is generated from the Windows OS. Please check the Microsoft web site for this Windows OS generated error. Limitations 1. If you map an entire drive using StoreGrid, then you cannot map any particular folder present in that drive. For example, if you have mapped '<Machine_Name>\<Drive_Name>', then you cannot map '<Machine_Name>\<Drive_Name>\<Folder_Name>' separately 2. Similarly, if you have mapped a particular folder using StoreGrid, then it is not possible to map the entire drive of that folder. 3. Mapped drives cannot be added or listed when StoreGrid is installed as a service in a Local system account. StoreGrid Service should be run with the administrative privileges.

248 Backup Window Settings Overview Backup Window is the hours during which the StoreGrid client can run its backups. You can configure StoreGrid client to not backup during certain hours of the day. This is useful when the user doesn t want StoreGrid to backup, say, during the peak hours when the client machine is running several other applications and the hardware resources in the client machine are limited How to get here in the StoreGrid Web Console? On the top menu, select: Administration -> Advanced Options -> Backup Window Settings To set a backup window, go to the Backup Window Settings page, click on the Enable checkbox and select the From Time and the To Time between which you don t want StoreGrid to backup. You can also select if this time period should be applied on all days or only on week days (Monday to Friday). If you configure StoreGrid to not backup, say, between 8am and 6pm, then the backup window will be in between 6pm and 8am. If you have scheduled a backup to start at 2pm, then StoreGrid will start the backup only at 6pm. This is applicable to Additional Full Backup schedules as well. If you configure StoreGrid to not backup, say, between 8am and 6pm and if a backup is in progress, then at 8am StoreGrid will end the backup job. StoreGrid will add an entry in the client side backup report as shown below. Client Side

249 Also, it will add an entry in the backup server side report as shown below. Backup Server Side StoreGrid will then reschedule the backup to start at 6pm. When the backup starts at 6pm, it will then check for all new/modified files again and then start backing them up. It will not start from where it left off when it was last stopped (at 8am). For example, say the backup started at 6pm and continued to run till 8am. During this time, say 100,000 files were backed up and still 20,000 files are left to be backed up. When backup restarts the next day at 6 pm, StoreGrid will also try to backup the modified files among the 100,000 files that were backed up earlier along with the 20,000 files that were not backed up. Limitations 1. If a backup is stopped because the backup window ended, then when StoreGrid resumes the backup at the beginning of the next backup window, it cannot continue the backup from where it left off. StoreGrid will check all the files for changes including those that were earlier backed up.

250 Configure Automatic Software Updates Overview From StoreGrid v2.3, clients can automatically download updates from the backup server and upgrade themselves. The updates have to be first uploaded into the backup server and the uploaded files have to be selected from the backup server web console. Client machines will check the backup server for available updates every one hour (when the client is not backing up). If an update is available in the backup server, it will automatically download and install it. The client will download only compatible updates. How to get here in the StoreGrid Web Console? In the top menu, select: " Administration -> Advanced Options -> Configure Automatic Software Updates" page. Configure Automatic Software Updates Software update is enabled by default from StoreGrid If no backup schedule (not including same machine backup or remote server backup to the same machine) is configured in the client machine, the backup server for detecting new updates is not selected by default. If a backup schedule is created in this machine, that schedule's backup server will be automatically selected for detecting updates and it will show up in this page. If no backup schedule is configured in the client machine, the backup server value will be empty and the client will not check for the new updates. Only when a backup schedule is created in this client machine, the backup schedule's backup server value will be automatically selected for detecting updates and will be displayed in this page. If the user has manually disabled software update in the client machine, then it remains disabled when the client machine is upgraded to a higher version. The user will have to manually enable it. Turn on Automatic Software Update: Select this option to enable Automatic Software Update. Once enabled, the client machine, when not backing up, will check with the backup server once every hour for the availability of new updates. If updates are available in the backup server (selected below), it will automatically download it to the location (specified below) and then install the updates and restart StoreGrid automatically. o o Select the server to download update(s) from: The backup server from which the client will download the updates. Specify the location to store downloaded update(s): The location in the client system where the downloaded updates will be stored. Make sure StoreGrid can write to that location. By default, StoreGrid will store the downloaded updates in the "<StoreGrid Home>/downloadedUpdates/" folder. Turn off Automatic Updates: This option is to disable the automatic software update feature. Troubleshooting Tips

251 Unable to save the automatic software update configuration. Solution : Check if the update download location specified is a valid location and StoreGrid has write access to it.

252 User Management How to get here in the StoreGrid Web Console? side. In the top menu, select: "Administration->Advanced Options" and click on the "User Management" icon in the left hand 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. Limitations - You cannot delete the user name using which you are currently logged in.

253 StoreGrid Events Configuration How to get here in the StoreGrid Web Console? In the top menu, select: "Administration->Advanced Options" and click on the "Events Configuration" icon in the left hand side. StoreGrid generates events to alert the user about potential problems that may require attention. The events configuration UI is meant to configure parameters on how StoreGrid should handle its events. The following describes the configuration options: Local Events - Events that are generated locally by the StoreGrid installation. Here you can configure the following: a. Number of Events to Retain - The maximum number of events should StoreGrid retain in its database. The default value is Once the number of events crosses this maximum value, StoreGrid will start dropping older events from the database. b. Clean Up Frequency - This field is used to specify how often should StoreGrid check to see if the number of events to retain has been exceeded. It is not advisable to check and delete events frequently because this may cause performance issues. So the maximum frequency you can specify is a "Day". Shared Events StoreGrid has the capability to share all its local events to other StoreGrid servers. This feature will be useful if an administrator requires a consolidation of all events into a single server for easy identification of potential problems. The event sharing steps are described below: a. Enable Event Sharing - Check this checkbox if you want to share events from this StoreGrid installation to other StoreGrid servers. b. Select Servers - Check the checkbox corresponding to the servers to which the events should be sent. c. Select event type to share - You can specify which event type (severity) to be shared with the server. By default, all event type will be shared. d. Share Frequency - This field is to specify how often events should be sent to the configured server. It is not efficient to share the event as and when it is generated. It will be more efficient to share the events in a batch. The following options are provided. i. You can specify sharing after the number of events pending to be shared is more than a threshold. By default this threshold is OR ii. You can share the events periodically by specifying a time duration. The options for the time duration are

254 Hour, Day and Week.

255 Local to Remote Server Migration Overview Local to Remote Server Migration is a useful feature to quickly move large backup data from the client machine to the backup server. Using this feature, the initial seed backup can be taken in a local external drive connected to the client machine and the external drive can then be physically moved to the remote backup server s environment to migrate the data into the backup server. After the data migration and after performing the server side and client side Local to Remote server migration steps, the incremental backups can run directly from the client to the remote backup Server. How to get here in the StoreGrid Web Console? For Server: In the top menu, select: "Server Admin->Group Management" and click on the "Local To Remote Server Migration" icon on the left hand side. For Client: In the top menu, select: "Administration->Advanced Options" and click on the "Local To Remote Server Migration" icon in the left hand side. Local to Remote Server Migration 1. Configure a backup schedule in the StoreGrid client system. Log into client s StoreGrid web console page and select Backup -> Add Backup Schedule' from the top menu. Add Backup Schedule link will take you to Create a new Backup Schedule page. 2. Select the Backup Type as Same Machine in Step 3 and enter the external drive location for the Local Backup Location. After entering all the other backup details, save the backup schedule.

256 Note : Same Machine' backup feature is available only from 2.3 release. It can be used only for 'Local to Remote Server Migration'; you cannot restore from the Same Machine backup. 3. Run the backup, check the progress and make sure the backup runs to completion. 4. When the backup is complete, suspend the backup schedule. 5. Disconnect the external drive from the client machine and connect the external device to the remote backup server.

257 6. Copy the client's data (Z:\backup\1) from the external device to some temporary location in the drive where you are planning to store the backup data in the remote backup server. Like for example, if you storage device is the E: drive, then copy the data to say E:\LTOR. You don t have to copy the data to the temporary location and you can migrate the data directly from the external drive itself. However, the migration might take a little longer to complete, based on the speed of the external drive. 7. Go to the remote backup server s web console "Server Admin-> Group Management -> Local to Remote Server Migration (Icon)" page. Enter the location of the client's data followed by the 1/ directory. For example, if you have copied the client's data from the external drive to the temporary E:\LTOR location in the backup server, enter location as E:/LTOR/1/ in this page. If you have not copied the data to a temporary location, enter the location of the external drive, like for example Z:/backup/1. After entering the path, click on the "Submit Location" button. 8. The client name will be displayed. Select the client. If you are doing the data migration from this client for the first time, enter the target group under which the client is to be migrated and the location where the backup data is to be stored. Click the "Migrate" button.

258 9. In the client system, take a backup of the <StoreGrid Installation Location>/data/<backup name>/sgprp.db file. This is just to ensure you can recover this DB file if you need to do the client side migration again, if required. 10. Go to Administration -> Advanced Options -> Local to Remote Server Migration (Icon) page in the client machine. Enter the remote backup server name for the new backup server name. Choose the option No, backup only to new server. In table listing the backup schedules, select the backup schedule(s) whose data has been moved to the new backup server. You can select all the backup schedules by checking the checkbox against the "Available Backups" column name. Confirm that the backup data of the selected schedules has already been moved to the new server and that you have run the server side local-to-remote-server migration module in the remote backup server (confirm from the check box).click the Migrate button to complete the migration. 11. To confirm that the migration has been successful, try running an incremental backup. If the incremental backup runs fine, the migration is successful and you can delete the backup of the db file that you created in step 9 above.