7. 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.
14. Installation of StoreGrid Server The Windows StoreGrid installer, StoreGridSetup.exe, will first download and install compatible Relational DataBase Management Systems (RDBMS) and then download and install StoreGrid in this system.
22. Select how you’d like StoreGrid to run on this machine. You have two options, Backup Server – Other computers can back up on to this computer. Replication Server – Other StoreGrid backup servers can replicate their data to this server for redundancy. StoreGrid ODBC Settings : StoreGrid uses the system DSN to connect to the MySQL server to store the metadata information of the backup server/replication server.
23. Cluster Configuration : Clustering will be disabled by default. If you would like to enable Clustering in your backup server, enter a name for your Cluster. Also mention the external IP or DNS lookup name at which the clients will connect to this cluster node for backup. NOTE : If you are adding an addition cluster node for your cluster, make sure you enter the same cluster name as the previous cluster node installation.
25. StoreGrid Configuration Configure Web Server Port Username & Password Advanced Port Configuration Keep the Default settings. Select Program Folder
26. Click Next to review your settings. Thereafter, click Install, and proceed to install StoreGrid.
27. After copying the StoreGrid files, a page will show the progress of StoreGrid installation. Upon successful installation, you will be automatically redirected to the finished installation page.
28.
29.
30.
31.
32. Client Authorization The illustration shows the sequence of steps required by the admin on the backup server and the Group on the client side to register a client under a Group in the backup server. 1 ) Create the Group account in the backup server by going to the 'Add Group' page under Group Management page in the backup server web console. After entering the details of the Group account, click on the Save button. The backup server will prompt you if you want to send an Email to the Group with the account details. Choose OK.
33. 2 ) StoreGrid backup server creates the Group account and sends an Email to the Group with the details of the account, including the unique Group Passkey. 3) The Group will receive the Email with the Passkey. Group can then access the web console of the client machine that needs to be registered. In the login page in the client web console, the Group should click on the link Sign Up which takes the Group to the Client Registration page where a client Password can be chosen and the Passkey is entered. The StoreGrid ID of the client (user name) and the chosen client password can be used for the following: To log into the client web console with full access To log into the backup server (from anywhere) to access the backups of that client machine. Note: This is possible only if web access is enabled for the client in the backup server. 4) On receiving the registration request from the client machine, the backup server adds the Client under that particular Group.
37. By default all groups will use the same location as the "Global Backup Data Storage Location".
38. You can edit the existing Storage Location for the group by going to the "Edit Group Configuration" UI page. Note :if you modify the storage location, it will not change the existing clients' backup storage location. It will take effect only for the new clients backing up under the group.
39.
40. By default all clients will use the same location as the Global Backup Data Storage Location.
41. 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.
42.
43.
44.
45. Server Side Email Filtering How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Server Management->" and click on 'Server Email Filters' on the left hand side. Filter Email Reports by state of Backups With the first, reports will be emailed to specified recipients for each selected module (backup/restore/delete/replication) depending on the state of the backups as selected. For example, with this option you can select to send email reports when backup/restore process fail or get completed partially. The available options are: When Backup/Restore/Delete/Replication completes successfully (in Server). When Backup/Restore/Delete/Replication fails (in Server). When there are no new or modified files for replication. When Backup is manually suspended (in Client). When Backup/Restore is Partially Completed (in Server). When a Backup schedule is missed. Filter Email Reports by Group/Client/Backup names This filter allows you to email Backup, Restore, Delete & Replication Reports only for specific Backup Schedules, Clients or Groups. By default, email reports are sent for all Backups Schedules, Clients & Groups. Manually selecting some backup schedules / clients / groups and "Disabling Email Reports" for them will prevent reports associated with those from being emailed.
46. Email Alert Settings How to configure Email alerts by using the StoreGrid Web Console ? On the top menu, select: “Server Admin > Server Management > Email Alert Settings” StoreGrid can be configured to send out Email alerts for the following conditions Server, Group or a client is running out of backup space in the backup server ’Trial clients’ trial license period has expired or about to expire Note: You can also edit the Email Subject for the alerts using the edit option provided against the Email Subject field.
47. Consolidated Group Report How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Server Management" and click on the "Email configuration for Consolidated Group Report " Icon on the left hand side. The 'Email configuration for Consolidated Group Report' page, has two options for configuring the the consolidated reports to be sent. Global Configuration - which configures consolidated report to be sent to a common email id list at the same schedule for all the Groups. Group Level Configuration - this option can be used to configure different email IDs and schedules of the consolidated report for particular Groups.
48. Global Configuration: This option gets a global recipients email id and a global schedule and configures all the current available Groups with a global email id and schedule for generating the Consolidated Email Report for the group.
49. Group Level Configuration: This option lists all the groups and for each group the Email IDs to which the consolidated report should be sent and the schedule (daily, weekly or monthly) for sending the reports can be specified.
50.
51. How to get here in the StoreGrid Web Console? In the top menu, select: "Administration->Advanced Options" and click on the "User Management" icon on the left hand side. Role : By default, set to 'Admin', as only Admin users are created from this page. Users for Group/Client are created when Add Group/Client operation is performed. You can also Edit a Group/Client to enable Web Portal access. You are currently logged in as admin on this machine inception. If you wish, you can allow additional users (like your system administrator) to access StoreGrid on this computer by creating separate usernames and passwords for them.
53. StoreGrid Server Cluster Deployment StoreGrid supports installing multiple StoreGrid Server instances (Nodes) in a cluster to provide load balancing of the clients. Backup and Restore requests from the client machines are directed to one of the Nodes as per the load balancing algorithm (Node Locked, Round Robin or Load Based) configured for the cluster. New Backup Server machines (Nodes) can be added to the cluster anytime to increase the capacity. The Nodes share a common RDBMS database. If the load balancing algorithm configured in the cluster is 'Round Robin' or 'Load Based', then the Nodes have to share a common backup storage as well. NOTE: Only Node Locked algorithm for load balancing is currently supported
54.
55. 1) Here is how a client selects a backup server (Node) from the cluster to backup: A StoreGrid Client machine backing up to a Backup Server Cluster first sends a HTTPS (or HTTP request as configured in SGConfguration.conf file in the client machine; HTTPS been default) 'Server Lookup' Web Service request at the backup server address (say for example: backup.datamaniacs.com - as specified while configuring the backup schedule in the client machine). The default port at which the request is sent is 6061 for HTTPs and 6060 for HTTP. 2) The backup server that receives the 'Server Lookup' request assigns a backup server (Node) for the client based on the Load Balancing algorithm (described below) specified for the cluster. 3) The backup server sends the response back to the client with the details of the assigned Node like its public lookup name (say serverB.datamaniacs.com) or public IP address, backup ports etc. 4) The StoreGrid client opens a TCP connection with the assigned Node on port 32004 (if SSL is disabled in the client) or 32007 (if SSL is enabled) and starts backing up.
56. How does the StoreGrid Clustering Work? The illustration below shows how a new client machine registers with the Backup Server cluster and initiates its backup. Each StoreGrid Backup Server instance consists of StoreGrid Web Server and the StoreGrid Application. The StoreGrid Web Server by default listens on port 6060 (and 6061 if HTTPS is enabled) and addresses the Web Service requests from the clients. The StoreGrid Application listens on port 32004 (and 32007 if SSL is enabled) and accepts the backup and restore requests from the clients. The StoreGrid Application of each of the Backup Server instances access a common RDBMS database. This enables the StoreGrid Backup Server instances running from different systems to share the backend database and serve the backup/restore requests of the StoreGrid clients independently.
57. Seed Backup Migration Seed Backup Migration is a useful feature to quickly move large backup data from the client machine to the 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 "Seed Backup Migration" icon on the left hand side. For Client: In the top menu, select: "Administration->Seed Backup Migration".
58. Seed Backup Migration STEP : 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.
59. STEP : 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. Note : 'Same Machine' backup feature is available only from 2.3 release. It can be used only for 'Seed Backup Migration'.
60. STEP : 3 Run the backup, check the progress and make sure the backup runs to completion. STEP : 4 When the backup is complete, suspend the backup schedule.
61. STEP :5 (You can skip this step if you are migrating the backup data from a Client installation using local backup) If you are migrating the backup data from v3.1/later backup server using MySQL Server as the backend database, then the StoreGrid database 'sgbackup.db' file will not be available in the backup location since v3.1/later backup server uses MySQL as the backend database. You need to export the metadata from MySQL to SQLite database by following the below steps : Open a command prompt and go the <STOREGRID_HOME> folder. Execute the following command : 'bintoreGrid.exe ExportToSQLiteDatabase' (for Windows)'./bin/StoreGrid ExportToSQLiteDatabase' (for Linux) This will export all the clients and backups' to SQLite database (sgbackup.db) in the backup location. If you wish to migrate a particular client (or) backup, then you can execute the above command as follows : bintoreGrid.exe ExportToSQLiteDatabase<Client_Name>bintoreGrid.exe ExportToSQLiteDatabase<Client_Name> <Backup_Name>
62. STEP : 6 Disconnect the external drive from the client machine and connect the external device to the remote backup server.
63. STEP : 7 Copy the client's data (Z:ackup) 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 your storage device is the E: drive, then copy the data to say “E:TOR”. 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.
64. STEP : 8 Go to the remote backup server’s web console "Server Admin-> Group Management -> Seed Backup 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:TOR 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.
65. STEP : 9 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.
66.
67. STEP : 10 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.
68. STEP : 11 Go to “Administration -> Seed Backup Migration” page in the client machine. If the client machine is backing up locally, then select the backups that should continue with the incremental backups directly to the remote backup server. Provide the New Backup Server Name and confirm that the backup data of the selected schedules has already been moved to the new backup server and that you have run the Seed Backup Migration module in the remote backup server (confirm this from the check box). If the client machine is backing up to a remote Backup Server, then select the remote Backup Server from the list to where the client machine is currently backing up to and then: Choose the option 'Make this client machine backup to a different backup server from now on' to continue with the incremental backups directly to the remote backup server and provide the New Backup Server Name.
69. In the 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 backup server and that you have run the Seed Backup Migration module in the remote backup server (confirm this from the check box).
70. Choose the option 'Make this client machine backup locally (same machine) from now on' to make the client machine start backing up locally to itself. You can use this option to do 'Seed Backup Migration of Additional Fullbackup data'. After selecting this option, you need to provide the Local Backup Location for the selected backup schedule(s). In the table listing the backup schedules, select the backup schedule(s) to start backing up locally to the same machine. You can select all the backup schedules by checking the checkbox against the "Available Backups" column name. Confirm that you have opted to run Additional Full Backup locally in this machine to the specified backup location. (confirm this from the check box). Click the Migrate button to complete migration.
71. STEP : 12 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 10 above. 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 10 and check the server migration steps again.
73. Replication Management How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin-> Replication Management" 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. In case the backup server crashes, it can be restored from the replicated data in the replication server.
74. Replication Management How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin-> Replication Management" Configure Replication
75. 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. If you choose 's3-amazon-webservice' to replicate, the Backup Server data will be replicated to the Amazon S3 WebService. Please provide the following additional details to replicate to Amazon S3 AWS Access Key: The Amazon WebServices Access key to authorize the Server to replicate to S3. AWS Secret Key: The Amazon WebServices Secret key to authorize the Server to replicate to S3. Bucket Name: The Bucket name under which all the backup data has to be replicated.
76. 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.
78. Server Disaster Recovery How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> Replication Management -> Server Disaster Recovery (Icon)" 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.
79. 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.
80. b) Select data to recover. i) Group & Client configurations and Client data: ii) Group & Client configurations Only: This recovers only the backup server configurations like group details, disk space allotted, etc. The backup data is not recovered.
81. 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. 4) Click on the Recover data from the replication server to start the recovery process. 5) If the first option recover Group & Client configurations and Client data was selected, then the progress chart will be as shown below:
82. 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.
83. If the second option Group and Client configurations only was selected in step 4b above, then only the backup server details are recovered.
84. 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 Seed Backup 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. STEP 6 Enable replication in the restored backup server by going through Server Admin -> Replication Management page in the backup server web console.
85. Authentication of Backup Server with Replication Server How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Admin -> Replication 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 Management -> Server Settings" page. The Backup Server can then authenticate with the Replication Server through the "Server Admin -> Replication Management -> Authenticate Backup Server for Replication" page with the same password which was configured in the Replication Server
86. Authenticate Backup Server Backup Server Authentication is an optional security feature. You can configure the password in the Replication Server from the "Server Admin -> Server Management -> Server Settings" page. The Backup Server can then authenticate with the Replication Server through the "Server Admin -> Replication Management -> Authenticate Backup Server for Replication" page with the same password which was configured in the Replication Server
88. StoreGrid Server Dashboard How to get here in the StoreGrid Web Console? In the top menu, select: "Reports->Server Dashboard" The Server dashboard has five sections 1 )Snapshot of recent 5 successful/failed backups. 2) Client Activity - status of clients currently connected to the server. 3) Disk space utilization for the server with Alert Settings. 4) Licensing Details 5) Snapshot of recent alarms raised.
98. Configure Backup Schedule Step 1: Schedule Name Step 2: Select Files And Folders To Backup Step 3: Set Basic Configuration Step 4: Scheduling (Decide When To Backup) Step 5: Additional Full Backups
109. Restoring to a new machine (Disaster Recovery) This feature is used to retrieve client backup configuration and back up data from the backup server. Using the same StoreGrid ID as before, the backup data can be recovered in the client webconsole. In StoreGrid, without the backup schedule configurations, backed up data cannot be restored. How to get here in the StoreGrid Web Console? In the top menu, select: "Restore-> Disaster Recovery"
110.
111.
112.
113.
114. Client Dashboard The client dashboard has two sections Snapshot of last 10 backups Current Client Activity
118. TERMINOLOGY StoreGrid Server: A StoreGrid Server receives (and stores) backup data from StoreGrid Clients. StoreGrid Client: The StoreGrid Client backs up its data on to a machine running StoreGrid Server. StoreGrid ID: This is the unique ID each installation of StoreGrid is identified with. 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.
119. StoreGrid Cluster : The term specifies the deployment of StoreGrid in a cluster. A number of StoreGrid Servers [Backup & Replication] can be deployed to be run as a single entity and all storing and accessing the StoreGrid metadata in a centralized StoreGrid Database using ODBC. This will enable StoreGrid Server to scale to multiple StoreGrid clients to connect for backup/restore processes simultaneously. StoreGrid Cluster Node : This mentions one of the StoreGrid Server instances running inside the StoreGrid Cluster. They get registered to the Cluster configuration as an active node in the cluster at startup. Server Lookup : A client looking up to the Master Server in the cluster to determine whom to connect for backup and restore. 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. Remote / Online Backups : The same as client-server (see above), except that the ‘server’ is outside the clients’ network.
