vembu storegrid data backups - online | on-premise | cloud
TRANSCRIPT
Server User Guide
Service Provider Edition
Introduction
Vembu StoreGrid's Service Provider (SP) Edition is exactly that - an Edition specially built for Service Providers.
The remote backup service market is booming, and customers are becoming increasingly aware of the need to backuptheir valuable data off-site. At Vembu, we believe that Service Providers are best suited to offer remote backup services,provided they have the right tools. With StoreGrid SP, your hardware doesn't matter anymore. StoreGrid's flexibility takescare of everything. In fact, even with a simple desktop running as a server, you can get started with remote backups inunder 30 minutes!
StoreGrid's SP Edition builds upon months of experience with StoreGrid's other Editions, and incorporates valuablefeedback from users and other Service Providers who've put StoreGrid through a battery of tests and environments.Additionally, the Service Provider Edition includes a host of features that are especially relevant to you. Features like:
Extremely Easy Reseller & Customer Management
Remote License Management
Server Web Portal with access control for Reseller, Customer & Client.
Added levels of Authentication
Extensive Web Service APIs to monitor and export backup metadata.
Management of Trial Customers and one step conversion to Confirmed Customers
Extensive reporting from a powerful RDBMS
Seed Backup Migration - a useful feature that recognizes bandwidth problems some of your customers mayhave, and hence allows for a first 'local' backup followed by incremental backups to your remote server.
And much more...
So who is a Service Provider?
Very simply, anyone involved in providing IT services to their clients is a Service Provider. Our Service Providers'customers are typically SMBs, mid market companies, and divisions / branch offices of enterprise companies. Some ServiceProviders may even have Home Users and SoHos as customers.
To further elaborate:
If you are a Value Added Reseller or a System Integrator, you are a Service Provider!
If you are an MSP or an ISP, or an XSP for that matter, you are a Service Provider!
If you wish to provide your customers with a feature packed remote backup service, you are a Service Provider!
If you're planning on starting an online backup service: well, you're a Service Provider!
Do try out StoreGrid SP! Although 30 minutes can get you up and running, you'll need more time to discover andappreciate all its unique features.
This help document was designed to get you up and running ASAP. But do remember, fanatical support is just an emailaway at [email protected]
Terminology
These are some terms we use quite liberally – both in this document, and in our user interface. So here’s a shortdescription of what each of them means.
StoreGrid Service Provider Edition Terminology:
Service Provider - The provider who offers the online backup service.
Reseller - The reseller who sells the online backup service provided by the Service Provider to the endcustomers.
Customer - The end customer of the Reseller/Service Provider who is backing up online to the service provider'sdata center.
Client - PCs/Laptops/Servers in the customer site backing up to the StoreGrid server installed in the ServiceProvider's data center. These PCs have StoreGrid installed in the Client mode.
StoreGrid ID - This is the unique ID each installation of StoreGrid is identified with. StoreGrid will prompt you togive an ID during the installation. It will automatically take the machine name as the StoreGrid ID by default.
MCALs - MCALs are monthly licensing units. MCALs are added to the backup server by applying MCAL licensekeys. The added MCALs in the backup server are consumed on a monthly basis for licensing the clients that arebacking up to the backup server. No MCALs are needed to be added in the replication server.
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 youplan to store data on that PC.
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.
(anyone who purchases a paid license of Vembu StoreGrid is also a StoreGrid client )
Replication:
Term used for the process where a backup server sends its backup data to a replication server to create aredundant 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 berestored from the replicated data in the replication server. A backup server can replicate to only one replicationserver. A replication server can accept replication from more than one backup servers.
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 centralizedStoreGrid Database using ODBC. This will enable StoreGrid Server to scale to multiple StoreGrid clients to connectfor backup/restore processes simultaneously.
StoreGrid Cluster Node :
StoreGrid Deployment
Overview
StoreGrid supports several different deployments. This document gives the details of each of them and the advantages ofeach of these deployments.
Installing StoreGrid
StoreGrid Client: StoreGrid client build should be installed in the client machines (Desktops, Laptops & Servers) that needto be backed up. StoreGrid supports backing up of Servers such as File Servers, MS SQL Database Servers, ExchangeServers etc.
StoreGrid Backup Server: StoreGrid Server build should be installed in the StoreGrid backup server where the backed updata is to be stored. If the backed up data is to be stored in a SAN, NAS, USB Drives or some other disk based storagedevice, you can install StoreGrid in a machine and then mount the SAN, NAS devices using networking protocols (CIFS inwindows and NFS in Linux). The StoreGrid Backup Server can then be configured to store the data in the mounted device.
StoreGrid Replication Server: To provide redundancy to the backup server, a replication server can be setup and thebackup server can be configured to replicate to it. StoreGrid Server build should be installed in the replication servermachine and during installation, the installation type should be selected as 'Replication Server'. A typical deploymentwould be with the Replication Server installed in an offsite location (like a datacenter or a geographically remote location)to replicate a local backup server, to make sure there is an offsite copy of the backed up data in case of disaster recovery.
StoreGrid Cluster: StoreGrid Backup & Replication Servers can be setup as a cluster, deployed with a centralized RDBMSto serve 100s and 1000s of clients for backup/restore. More on cluster deployment of StoreGrid servers here.
Deployment Scenarios
The following are the major deployment scenarios
1. Local & Offsite Backups - Store the backup data locally and a redundant copy offsite.
2. Offsite Backups - Store all backup data offsite (via Internet/VPN).
3. Cloud Deployment - Backup or replicate to a server on Cloud.
Local & Offsite Backups
In this deployment, the StoreGrid Backup Server is setup in the local LAN and it is replicated to a Replication Server in ageographically remote location. This ensures that two copies of the backup data is present, one locally and the other in theremote location. This type of deployment is especially helpful when size of the datasets is huge and restoring it from aremote backup server might be slow due to limited available bandwidth.
As the backup server is local, the restores are fast, but the offsite redundant storage that the replication server provides isnecessary for disaster recovery.
Offsite Backups
In this deployment, the StoreGrid Backup Server is in an offsite location and it replicates to a Replication Server (optional)in a geographically different location. This provides two copies of backup data in remote locations.
The redundant storage of backup data in the replication server, though optional, is highly recommended. The ReplicationServer gives the option for the StoreGrid clients to restore the data from the Replication Server if the Backup Server isdown or inaccessible. Also, the backup server can be reconstructed back in case it crashes, from the data in the replicationserver through Server Disaster Recovery feature of StoreGrid.
Cloud Deployment
With the advent of cloud technologies (such as Amazon EC2 (Elastic Compute Cloud), Google AppEngine, Windows Azure,etc.), deploying StoreGrid on the cloud is one of the desirable deployment scenario. Initially, StoreGrid has been releasedfor the Amazon Cloud (EC2) and in future other cloud deployments will also explored and supported.
Amazon EC2 Deployment
StoreGrid Backup Server and StoreGrid Replication Server can be run on Amazon EC2. The StoreGrid Cloud AMI can beplaced as a Remote Backup Server and Remote Replication Server (as in offsite deployment), or as a Remote ReplicationServer (as in local & offsite deployment).
In StoreGrid deployment in the Amazon Cloud, the Amazon's EBS(Elastic Block Store) Volume is used as a local cache forimproved backup performance. Later, the data is uploaded to Amazon S3 (Simple Storage Service) and is then removedfrom the local cache. This enables an unlimited storage pool for StoreGrid Server using the available Amazon WebServices.StoreGrid Cloud AMIs are available for United States as well as the Europe datacenters of Amazon EC2.
StoreGrid can also be deployed in the cloud as a StoreGrid client to backup the Amazon EC2 instances and the dataavailable in the cloud to an offsite Backup Server.
StoreGrid Server Cluster Deployment
Overview
StoreGrid supports installing multiple StoreGrid Server instances (Nodes) in a cluster to provide load balancing of theclients. Backup and Restore requests from the client machines are directed to one of the Nodes as per the load balancingalgorithm (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.
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 WebServer by default listens on port 6060 (and 6061 if HTTPS is enabled) and addresses the Web Service requests from theclients. The StoreGrid Application listens on port 32004 (and 32007 if SSL is enabled) and accepts the backup and restorerequests from the clients. The StoreGrid Application of each of the Backup Server instances access a common RDBMSdatabase. This enables the StoreGrid Backup Server instances running from different systems to share the backenddatabase and serve the backup/restore requests of the StoreGrid clients independently.
Here is how a client selects a backup server (Node) from the cluster to backup:
1. A StoreGrid Client machine backing up to a Backup Server Cluster first sends a HTTPS (or HTTP request asconfigured in SGConfguration.conf file in the client machine; HTTPS been default) 'Server Lookup' Web Servicerequest at the backup server address (say for example: backup.datamaniacs.com - as specified while configuringthe backup schedule in the client machine). The default port at which the request is sent is 6061 for HTTPs and6060 for HTTP.
2. The backup server that receives the 'Server Lookup' request assigns a backup server (Node) for the client based onthe 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 lookupname (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.
Load Balancing Algorithms
The different load balancing algorithms and how they work are described below:
1. Node Locked Algorithm
2. Round Robin Algorithm (coming soon!)
3. Load based Algorithm (coming soon!)
Only Node Locked Algorithm of load balancing is supported currently.
Node Locked
In Node Locked algorithm, a Client machine backs up to the node to which the client is 'Node Locked' by the administratorof the backup server cluster. If the client machine is not 'Node Locked', then it backs up to the Node to which its parentCustomer or its parent Reseller account is Node Locked.
The administrator can 'Node Lock' a Reseller, Customer or a Client to a particular node in the cluster through 'ClusterManagement' page in the backup server's web console. If a Reseller account is Node Locked, all Clients under all theCustomers under that Reseller account will backup to that locked node (backup server instance) by default. However, if aCustomer is node locked to a different node, then all the Clients under that Customer will backup to that node, even if theparent Reseller account is Node Locked to a different node. Similarly if a Client is Node Locked, it will always backup tothat node even if its parent Customer is locked to a different node.
If neither the parent Reseller nor the parent Customer nor the Client is Node Locked, then the client will be automaticallynode locked to the first node (the backup server instance that was first added to the cluster) in the cluster, the secondclient will be automatically Node Locked to the second node and so on, in a Round Robin fashion. Thereafter, the client willalways backup to that locked node.
Round Robin
Unlike in Node Locked, in Round Robin algorithm, the client machines can backup to any node in the cluster and is notlocked to a node. The backup/restore requests from the clients are directed to the different nodes in Round-Robin fashion -first backup request is directed to the first node, second request to the second node and so on. This load balancingalgorithm needs centralized backup data storage solution such as SAN, NAS or Amazon S3. It supports dynamically takingdown and adding of nodes to the cluster on-the-fly. This algorithm will be supported in the future releases.
Load Based
This algorithm is very similar to Round Robin, but takes into account the current load in the nodes and assign thebackup/restore request to the least loaded node. Like Round Robin, Client is not locked on to a single server instance andthis load balancing algorithm needs centralized storage solution such as SAN, NAS or Amazon S3. It supports dynamically
taking down and adding of nodes to the cluster on-the-fly. This algorithm will be supported in the future releases.
Clustering requires a common RDBMS database that the cluster nodes share. For Round Robin and Load Load Basedclustering, the backup storage should also be common to the nodes.
NAT/Firewall ConfigurationThis page provides information about the ports used by StoreGrid, and the ports that need to be opened to enableStoreGrid to work across NAT/Firewall.
The following ports are needed to be opened up at the StoreGrid Backup/Replication Servers for StoreGrid server to beable to receive the backup/restore/delete/replication/webservice requests from the clients:
TCP Port 32004 - for processing Backup/Restore/Delete/Replication requests.
TCP Port 32007 - for processing Backup/Restore/Delete/Replication requests.
HTTP Port 6060 - for processing WebService requests.
HTTP Port 6061 - for processing WebService requests.
In some cases, ports will need to be added to the Firewall exception list to ensure StoreGrid functioning smoothly forbackups. As Windows XP SP2/SP3, Vista & Windows 7 OS have built in firewall which restrict ports opened by applications,the ports need to be added to the Firewall exception list. Hence, it is recommended to add the ports or StoreGrid.exe inthe Firewall exception list for these operating systems.
The following ports are needed to be added to the Firewall exception list at the StoreGrid Clients:
TCP Port 32005 - for processing Apache/PHP console requests to StoreGrid backend.
TCP Port 32008 - for processing StoreGrid Exchange Mailbox backups in Windows 64 bit OS.
HTTP Port 6060 - for processing WebConsole requests.
HTTP Port 6061 - for processing WebConsole requests.
The purpose of the above ports are mentioned in detail below.
TCP Port 32004
StoreGrid Server opens this port. All Client-Server communication including backups, restore etc. (except TCP discovery) isdone through this port. If a StoreGrid Server is behind a NAT/Firewall then this port needs to be opened to enableStoreGrid clients to backup to this server. Opening up this port is mandatory for the core functionality of backup andrestore 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 32007
From StoreGrid v2.3, StoreGrid clients can send the backup data to the backup server on secure SSL port 32007. This portis disabled in the backup server and the client by default. SSL port can be enabled by changing the Enabled attribute to 1in the SSL tag in the SGConfiguration.conf file. When enabled in the backup server, the StoreGrid backup server can acceptbackup requests on both port 32004 and the SSL port 32007. When enabled in the client, the client will start sending thebackup data on the SSL port.
If SSL port is enabled in the backup server and in the client, all Client-Server communication including backups, restoreetc. (except TCP discovery) from that client will be done through the SSL port 32007 and therefore if a StoreGrid Server isbehind 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 32007. 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 6060, 6061
These ports are used by the StoreGrid Web Server (Apache) to serve requests from StoreGrid WebConsole (UserInterface). These ports are configurable. When you first install StoreGrid you would have been given an option to changethese ports. The NAT/Firewall should also 'allow' these ports if you need the ability to connect/administer a StoreGrid peerbehind the NAT/Firewall.
In a Backup Server Cluster setup, client machines make web service requests to the Server instances on these ports forcluster node lookup. Therefore, in a cluster environment, it is recommended that the server side firewall is configured toallow incoming HTTP/HTTPS traffic on these ports and the client side firewall is setup to allow outgoing HTTP/HTTPS trafficon these ports. Similarly, in a Replication Server Cluster setup, the backup servers replicating to the cluster make
HTTP/HTTPS requests on these ports.
TCP Port 32008(Windows 64-bit OS)
From StoreGrid v2.4 Exchange Mailbox backup and restore is supported for Exchange Server 2007. StoreGrid 64-bit clientexe can send the backup request to the 32-bit client exe on port 32008 running in the same machine. If a StoreGrid Clientis behind a NAT/Firewall then this port needs to be opened to enable Exchange 2007 Mailbox backup and restore to beperformed. Opening up this port is mandatory for the core Exchange 2007 Mailbox functionality of backup and restore towork in StoreGrid. By default the port used by StoreGrid for Exchange 2007 Mailbox backup is 32008. But it can bemodified by changing the "MAPI32Bit" attribute in the "Ports" tag in the SGConfiguration.conf file located in<INSTALLATION_HOME>/conf folder.
TCP Port 32005
Both StoreGrid Client and Server open this port. This port is used for two purposes:
1. For all communication between the PHP module (invoked by the StoreGrid browser based WebConsole) and theStoreGrid C++ modules. In StoreGrid, all UI requests from the browser are served by PHP pages, which in turnconnect to this port to get the required data. By default the port used by StoreGrid is 32005, if you have modifiedthe '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 peersetc. 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 aStoreGrid peer behind the NAT/Firewall through the WebConsole of another StoreGrid peer outside the NAT/Firewall.
Multicast Ports (UDP) 6363, 6364 [optional, by default not used]
These two multicast ports are used by StoreGrid Clients and Servers for discovering peers within a subnet. In mostnetworks, multicasting will work only within a subnet. There is no need to open these ports in firewall or NAT devices asmulticast packets may not be sent across networks, anyway.
From StoreGrid v3.0, Multicast discovery is disabled by default. It can be enabled by changing the'SocketDiscoveryEnabled' attribute in the SGInformation.conf file.
UDP Port 32006 [optional, by default not used]
This UDP port is used in discovery of StoreGrid peers in a network. StoreGrid does a UDP scanning on port 32006 of allpossible IP Addresses in a network to detect the presence of other StoreGrid peers. There is no need to open this port inthe NAT/firewall as StoreGrid does the UDP scanning only within its subnet. By default, UDP network scanning is disabledin StoreGrid.
Vembu StoreGrid Troubleshooting Guide1. Description of the Error Codes
2. StoreGrid reports an error "Unable to list the Exchange mailbox users. Make sure sufficient permissions are available forthe user account under which StoreGrid service is running.
3. StoreGrid reports an error "Unable to list the Exchange mailbox users..." when trying to configure mailbox level backupin 2007 Exchange server (64 bit) machines.
4. SG0147/SG0136: Unable to connect to the Backup Server
5. SG0198: Connection failure error / SG0083: Unable to send backup details to server
6. SG0132: Invalid remote socket
7. SG0145/SG0134: Unable to get target machine
8. SGRP0001: No Server available for Replication
9. SG0083: Exceeding allotted backup space in the server
10. Server incorrectly shows that a backup is still in progress when the client has suspended the backup
11. Clients not backing up to the server after moving the clients from trial customer
12. Problem in accessing the snapshot device while opening a file
13. “Error Code 21 Cannot Start StoreGrid” message from the tray / “Error in Starting StoreGrid" message from StoreGridTray
14. Client did not receive a valid license from the Backup Server
15. Customer Migration failed. The target customer does not have enough licenses(MCALs)
16. Failed to authenticate this client with the Backup Server
17. Backup request failed for backup [Backup Name] To Server [Server Name] with Error : Unable to take backup toReplication Server
18. On backup completion, a message "there were no modified files" is shown though several files were actually modified
19. SG: Unable to allot backup space
20. StoreGrid not able to backup over the internet
21. StoreGrid doesn’t seem to work in XP SP2/SP3
22. Backup of trial customers stop at 100MB though enough space is allocated in the server
23. StoreGrid Server is not listed in the "Backup Servers" list
24. StoreGrid has exited, do you want to restart it
25. "Apache.exe could not be replaced" message during installation
26. Linux installation fails while installing GD/PHP (applicable only to versions older than 2.3)
27. Unable to log you in. Make sure StoreGrid is running. / No connection could be made because the target machineactively refused it
28. "Cannot export .\registry\regbackup.reg:Error opening the file. There may be a disk or file system error." error in Vista.
29. StoreGrid doesn't seem to run properly after upgrading Windows to Vista.
30. Error while dumping the Exchange Mail Boxes. Unable to create the PST file [or] "No new/modified files for backup"
31. Dump location does not have enough space to export the PST file
32. Error while creating the dump location <Dump_Location>
33. Users Mailbox/folder are not listed in the "Add Exchange Mailbox Backup" page.
34. StoreGrid fails to list some files/folders during a backup schedule.
35. I had changed the dump location and now I am not able to restore the previous backups.[Applicable for ExchangeServer, Exchange Mailbox and SQL Server backups.]
1. Description of the Error Codes
Common StoreGrid Error Codes and their corresponding description are listed below. If you require further clarificationon these or if you encounter a different error code from those listed below, contact us at [email protected]
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 Detectionsoftware, Antivirus software or NAT/Firewall Idle socket configuration. Clickhere for the resolution
ii. Exceeding allotted backup space in the server. Click here for the resolution
SG0198 This error occurs when the socket connection between the Client and the Servergets disconnected due to any external force such as a. Internet Link error, b.Intrusion Detection software, c. Antivirus software, d. NAT/Firewall Idle socketconfiguration. Click here for the resolution
SG0145/SG0134 Problem in resolving Backup Server Name and IP Address, DNS Lookup for BackupServer Name or IP Address failed. Click here for the resolution
SG0147/SG0136 Problem in connecting to Backup Server, Backup Port (32004) not opened up inNAT/Firewall or StoreGrid not running. Click here for the resolution
SG0200 No drive space available in the Backup Server to continue the backups
SG0191 Active backup is suspended in the client or the Backup Server
SG0178 Exceeding allotted backup space in Backup Server
SG0180 Backup space not configured for the client in the Backup Server
SG0601 Failed to initialize the compression module to compress file contents for backup
SG0094 Unable to read the file during time of backup
SG0290 Backup schedule is active during delete schedule configuration, suspend the backupand schedule delete
SG0291 Backup schedule Restore is active during delete schedule configuration, suspendthe backup and schedule delete
SG0292 Backup schedule Delete is in progress, Delete schedule updated
SG0170 Unable to send out delete request to Backup Server for deletion of backup datafrom client
SG0132 Invalid remote socket. Click here for the resolution
SGRP0001 No Server available for Replication. Click here for the resolution
Error Code 21 Cannot Start StoreGrid or Error in Starting StoreGrid. Click here for the resolution
Top
2. StoreGrid reports an error "Unable to list the Exchange mailbox users. Make sure sufficient permissions areavailable for the user account under which StoreGrid service is running.
Resolution :
If you encounter an error while accessing "Add 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. Use this new account with full mailbox rights as StoreGrid service's logon account and restart StoreGrid service.Specify the display name of this account [and global catalog server name in case of Windows Server 2008machines] in the configuration page that opens on clicking the link shown at the bottom of the tree view sectionand check if mailboxes are listed successfully.
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 "Add Exchange MailboxBackup" page. However 'MSPST MS' service should be added in the MAPISVC.INF file to successfully backupthe Exchange users mailbox).
Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access themailboxes.
Top
3. StoreGrid reports an error "Unable to list the Exchange mailbox users..." when trying to configureExchange Mailbox level backup in 2007 Exchange server (64 bit) machines.
Resolution :
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 exerequires 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 theExchange 2007 mailboxes.
Top
4. 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 byStoreGrid.
Resolution:
i. 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 commandprompt.
ii. If the telnet command doesn't work, then check the firewall configuration of the StoreGrid Server and make surethe Backup Port (default 32004) is open for the incoming traffic.
iii. Check that the StoreGrid server is running in your StoreGrid Server machine and the Backup Port is in LISTENstate by executing netstat -an | find <Backup Port> [in Windows OS] or netstat -an | grep <Backup Port> [inLinux OS] in StoreGrid Backup Server system.
iv. If Backup Port is not in LISTEN state, start the StoreGrid in the Backup Server. Also make sure StoreGrid isrunning as Server.
v. If the Backup Port is in LISTEN state and telnet command fails, make sure the Backup Port is open in theBackup Server network's NAT/Firewall settings.
vi. 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.
vii. Refer the following URL to know more about NAT/Firewall configurations. nat-firewall-configuration.html
Top
5. 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 externalforce, while the StoreGrid is actively processing the backup data to the Backup Server. The external forces may be:
a. NAT/Firewall configurations.
b. Low end routers/switches.
c. Intrusion detection software.
d. Internet-link error.
Resolution:
i. Most routers, NATs and firewalls keep a track of all connections made through them. They will assume aconnection to be dead if no data is transferred in either direction for a certain time interval and they may thenclose the network connection. Hence, check the “Idle Socket Timeout” configuration in the NAT/Firewall settings.
ii. The premature closure of the connection can be prevented by configuring either the Keep Alive Time in theWindows Registry or by configuring the Application Level Keep Alive Time (available since StoreGrid 2.2 Release)
Top
6. SG0132: Invalid remote socket
Cause:
This error message occurs when StoreGrid client exits or its connection is closed when the backup is in progress. Checkthe 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:
a. ' StoreGrid stopped during backup' – This error indicates that either the StoreGrid process was stopped duringbackup or the StoreGrid Client machine was shutdown/restarted while the backup was in progress.
b. '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 isclosed when the socket remains idle for a specified time period.
Resolution:
i. This problem occurs when the socket connection to the backup server from the client is disconnected for reason.When the connection between the client and the backup server is lost, the StoreGrid client will automatically tryto reestablish the connection and proceed with the backup from where it left off. However, if the client is notable to reestablish the connection after several attempts, then this error message is thrown In such a scenario,check the elements (NAT/firewall/Router) in the network and see if they are closing the connection for somereason.
Top
7. 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:
a. ping <Backup Server Name> command.
b. 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 abovecommands fail, then check the DNS configurations on the client side and make sure that the client is able to lookupBackup Server's hostname. Also, try running the telnet <Backup Server Name> <Backup Port> (by default the BackupPort is 32004) command in the client machine. If the telnet command works (shows a blank console screen), thenbackup should work.
Resolution:
If the client is not able to resolve the Backup Server's hostname, try configuring the backup with the Backup Server'sIP address as the server name by following the steps given below:
i. Go to the Settings -> Add/Delete peer page in the StoreGrid Client web console.
ii. Delete the Backup Server name from the list of StoreGrid running machines.
iii. Add the IP address of the Backup Server in the Add Peer. Now the IP address of the Backup Server will be listedin the list of backup servers in the Backup -> Add Backup page.
iv. Configure a backup using the Backup Server's IP from menu Backup -> Add Backup page.
Top
8. 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 processdue to one of the following reasons:
a. Replication Server is not running in the system.
b. Backup Server is not able to resolve the Replication Server's hostname due to DNS lookup issue.
c. 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:
i. ping <Replication Server Name>
ii. nslookup <Replication Server Name>
iii. 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 aDNS lookup issue for the Replication Server hostname from the Backup Server. If the telnet command fails, then checkif the Replication Port is open in the firewall at the Replication Server and make sure StoreGrid Replication Server isrunning in that port.
Top
9. 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:
i. Check the allotted space for the particular client in the Backup Server.
ii. To increase the space for the client in Backup Server, go to Server Admin -> Reseller Management -> List ofResellers -> [Reseller_Name] -> [Customer_Name] -> Edit Configuration (Action for the particular Client) pageand enter the required space in Space Allotted field. Refer to the URL PageHelp/client-backup-configuration.htmlfor more details.
Top
10. Server incorrectly shows that a backup is still in progress when the client has suspended the backup
Cause:
This error occurs when the TCP connection between the client and the server is closed prematurely, due to whichthough the backup was suspended in the client, the server thinks that the backup is still in progress. In the nextincremental backup schedule from the client, StoreGrid will reset the status of the backup schedule in the BackupServer. 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 inthe client's backup report.
Resolution:
i. This error should be cleared during the next backup schedule. If it doesn't, then try restarting the Backup Serveronce to see if this error goes off in the subsequent schedule.
ii. 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.
Top
11. Clients not backing up to the server after moving the clients from trial customer
Cause:
This error could occur if the client is deactivated or the customer doesn't have enough MCALs.
Resolution:
Make sure that the customer and client are not deactivated by going to the Server Admin -> Reseller Management ->Reseller [reseller name] page and then checking the action (activate/deactivate) for the particular customer. To checkthe client status, go to Server Admin -> Reseller Management -> Reseller [reseller name] -> Customer [customername] page and check the action (activate/deactivate) for the particular client.
i. Ensure sufficient MCALs are available for the customer.
ii. Check the MCAL's configuration to verify the MCAL's limit set to the particular customer.
iii. Increase the allotted MCAL or edit the MCAL configuration for the customer to AUTO by choosing the optionAutomatically use MCALs from the Server Admin -> Reseller Management -> Reseller [reseller name] -><Customer Name> -> Edit Configuration page.
iv. Now, try configuring the backups from the client to the server and check if the error is resolved.
Top
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, whenthe 'Volume Shadow Copy' option is enabled for the backup schedule. This happens if the file to be backed up doesn'texist 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
i. Check the skipped files count in the next schedule.
ii. If the problem persists, try disabling the 'Volume Shadow Copy' option for that backup schedule through theBackup -> List Backup Schedules -> Edit(Action for the particular backup) -> Advanced Options page.
Top
13. “Error Code 21 Cannot Start StoreGrid” message from the tray / “Error in Starting StoreGrid" message fromStoreGrid Tray
Cause:
These errors occur when the StoreGrid tray is unable to start the StoreGrid Application or the Service. The reason couldbe one of the following:
a. The StoreGrid Tray application doesn't have permissions to start the StoreGrid Service.
b. The StoreGrid Application file is not available at the StoreGrid Tray Applications path, i.e < StoreGrid Home>\binlocation.
c. Another instance of StoreGrid is already running in the machine.
Resolution:
i. Check if the StoreGrid Tray Application is running in an user account who has privileges to start the StoreGridService.
ii. Check if the StoreGrid service's logon user has enough privileges to start Windows services.
iii. Check if any other StoreGrid instance is already running in the system. You can verify this by checking for"StoreGrid.exe" process in the 'Task Manager' tool. If there is already another instance running, try stopping thatprocess and then starting it again.
Top
14. Client did not receive a valid license from the Backup Server
Cause:
This error occurs if the client does not have enough MCALs for the Customer in the Backup Server. StoreGrid willvalidate the MCAL allotted for the client based on the MCAL pool allotted to the Customer or globally on the Server. TheMCALs will be used every month for the clients in the Backup Server based on the client's operating system and theusage of SQL & Exchange Server Plugins in the client.
Resolution:
Apply MCALs for the customer. For more information on MCALs and their usage in the Backup Server, refer to thefollowing URLs:
i. For MCAL Management : PageHelp/mcal-management.html
ii. To Add MCALs : PageHelp/add-mcals.html
iii. For MCAL Utilization : PageHelp/mcal-utilization.html
Top
15. Customer Migration failed. The target customer does not have enough licenses (MCALs)
Cause:
The error message occurs when there are not enough MCALs available for the customer to which the clients are being
migrated.
Resolution:
i. If the paid customer doesn't have enough MCALs for the new clients, generate the necessary MCALs through thePartner Zone from your existing MCAL credits and add them to the Backup Server using Server Admin ->License management -> Add MCALs page in the StoreGrid Web console.
Top
16. Failed to authenticate this client with the Backup Server
Cause 1:
If Disable Auto Authorization is selected in the Backup Server.
Resolution:
Enable Auto Authorization option for the particular customer and check.
Cause 2:
If there is a password mismatch between the Backup Server and the Client.
Resolution:
If this is the case,
i. Reset the client's password in the StoreGrid Backup Server. Go to Server Admin -> Reseller Management -> Listof Resellers -> [Reseller Name] -> [Customer_Name] -> Reset Password (Action for the Backup Server) page inthe backup server's web console.
ii. Reset the server password for the client through Settings -> Authenticate Client -> Reset Password (Action forthe Backup Server) page in StoreGrid client's web console.
iii. Authorize a new password (for both client and server) by editing the password in the Backup Server in ServerAdmin -> Reseller Management -> List of Reseller -> [Reseller Name] -> [Customer_Name] -> Edit ClientConfiguration page in the server web console and then authorizing the client with the same password from theSettings -> Advanced Options -> Authorize Client page in the client web console.
iv. Resume the backup schedule and check if it works.
Top
17. Backup request failed for backup [Backup Name] To Server [Server Name] with Error : Unable to takebackup to Replication Server
Cause:
This error will occur if the Backup is configured directly from the StoreGrid client to the StoreGrid Replication Server.
a. The StoreGrid Replication Server will not accept the backup request from StoreGrid Clients.
b. StoreGrid Replication Server is designed only for receiving replication requests and replication data from theBackup Server and to handle restore requests from the client.
c. Similarly, the StoreGrid Backup Server is designed for receiving Backup/Restore Requests from the client.
d. Hence, Replication Server will not process the backup request from the StoreGrid client.
Resolution:
i. Configure backup from StoreGrid client to StoreGrid Backup Server.
ii. Enable replication in the StoreGrid Backup Server for the corresponding customer.
iii. The client will backup to their server and the backup data on the server will be replicated to Replication Server.
Top
18. On backup completion, a message "there were no modified files" is shown though several files wereactually modified
Cause:
This error might occur if files to be backed up are from a mapped drive and Automatic Directory Monitoring is enabledfor the backup.
a. StoreGrid client running on Windows OS can use the Windows Directory Monitoring to get a notification when afile configured for backup is added/deleted/modified.
b. These notifications are saved in the database to create the list of files that need to be backed up during the nextbackup schedule.
c. However, notifications are not sent by the Directory Monitoring when the files modified/deleted/updated are in amapped drive.
d. Therefore, StoreGrid will not be able to identify the changed files when Automatic Directory Monitoring isenabled for backup of files from a mapped drive.
Resolution:
i. Disabling Automatic Directory Monitoring should resolve this issue.
ii. Uncheck Automatic Directory Monitoring in the Backup -> List Backup Schedules -> Edit Backup Configuration(Action for particular backup) -> Advanced Options page.
iii. If the backup is already in progress, then suspending and resuming it manually will make the StoreGrid list allfiles/folders for backup again and therefore the files will get picked up.
Top
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 theBackup Server.
Resolution:
i. Before increasing the space for a client, confirm if the server has enough allotted space.
ii. Then increase the allotted space for the client.
iii. If the server does not have the necessary space, increase the allotted space for the Backup Server by going toSettings -> Server Settings page and then increase the allotted space for the client.
iv. After increasing the allotted space for the client in the Backup Server, schedule the backup from the client andcheck if the backup is successful.
Top
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:
i. Check the Backup Server side NAT/firewall settings. Make sure the incoming traffic on the Backup Port (default32004) to the Backup Server is not blocked.
ii. Run a quick check for the connectivity from the client with the command telnet <server name/server IPAddress> <Backup port>.
iii. If this command works, then the client should be able to backup to the server over the internet. If it fails, thenmake sure that Backup Port (32004) is open in the Firewall/NAT configuration in the network where the server isinstalled.
Top
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 itcan backup data to other machines.
Resolution:
Either disable the firewall settings or enable the ports for StoreGrid to work.
a. To disable the firewall, follow the steps below:
1. Open START->CONTROL PANEL->WINDOWS FIREWALL
2. Select Exceptions tab
3. Under 'Programs and Services', click on Add Programs button
4. Browse and choose the StoreGrid.exe and Apache.exe. StoreGrid.exe is located at "InstallDir"\Vembu\StoreGrid\bin directory. Apache.exe is located at "InstallDir"\ Vembu\StoreGrid\apache directory."InstallDir " is the location where StoreGrid is installed (by default it is C:\Program Files).
5. Select OK to save the configuration and exit. StoreGrid can now use any TCP/UDP ports as the firewallsettings have been disabled for the StoreGrid and Apache applications.
b. Enable to the following ports:
TCP Ports: 32004, 32005, 32007, 32008, 6060, 6061
UDP Ports: 32006, 6363, 6364
1. Open START->CONTROL PANEL->WINDOWS FIREWALL
2. Select Exceptions tab
3. Under Programs and Services, click Add Port button
4. Add 4 TCP Ports with unique names, allowing TCP Port numbers 32004,32005, 32007, 32008, 6060 and6061.
5. Add 3 UDP Ports with unique names, allowing UDP Port numbers 32006, 6363 and 6364.
6. Select OK to save the configuration and exit.
Top
22. Backup of trial customers stop at 100MB though enough space is allocated in the server
Cause:
From StoreGrid 2.2 release, StoreGrid Backup Server by default allocates 100 MB of disk space for the trial customers.
Resolution:
a. This default value can be changed through the server webconsole Server Admin -> Reseller Management ->Trial Client Settings (icon) page. However, the changed space allocation configuration will be applicable only tothe new trial clients
b. To change the space allocated for the existing trial customers, go to Server Admin -> Reseller Management -><Reseller_Name> (Link) -> <Customer_Name> (Link) -> Edit Configuration (Action for the particular client)page in the StoreGrid server webconsole.
Top
23. 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 inthe 'Backup Servers' list.
Resolution:
Manually add the StoreGrid peer to the list from the menu item Settings->Add Peer. In the "Add Peer" page, enter theStoreGrid peer’s name or IP address. This is especially relevant if some peers are outside the network (as in the case ofremote online backups).
Top
24. 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 networkconnections.
Resolution:
Run the command netstat -a from a command window (Start > All Programs > Accessories > Command Prompt) andcheck if the TCP ports 32004 or 32005 are in listening mode. If the ports are in listening mode, then the system has tobe restarted.
Top
25. "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 previousinstallation 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, openthe Control Panel->Administrator Tool->Services and stop the StoreGrid Web server service and then proceed with theinstall.
Top
26. 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 andPHP 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 therequired 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.
1. make, available from http://ftp.gnu.org/pub/gnu/make/
2. gcc, available from http://gcc.gnu.org/
3. g++, available from http://gcc.gnu.org/
4. libstdc++5, available from http://gcc.gnu.org/libstdc++/
The following third-party libraries will be used by GD if found by configure. While GD will compile and installeven without these, it is recommended that at least zlib, libpng, freetype and jpeg are installed as well:
1. Data compression library: zlib, available from http://www.gzip.org/zlib/
2. Portable Network Graphics library; requires libpng, available from http://http://www.libpng.org/pub/png/
3. Free, high-quality, and portable font engine: FreeType 2.x, available from http://www.freetype.org/
4. Portable JPEG compression/decompression library: JPEG library, available from http://www.ijg.org/
To install PHP following 3rd-party libraries are required :
1. Flex, available from http://lex.sourceforge.net/ Flex is a tool for generating programs that perform pattern-matching on text.
2. Bison, available from http://www.gnu.org/software/bison/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.
3. libxml2, available from http://www.xmlsoft.org/
Top
27. Unable to log you in. Make sure StoreGrid is running / No connection could be made because the targetmachine actively refused it
Cause 1:
StoreGrid application is not running in the system.
Resolution:
In Windows OS.
i. Confirm that the StoreGrid application [StoreGrid.exe] is running in the system by using "Task Manager".
ii. If the application is not running, start StoreGrid through the StoreGrid system tray application.
In Linux OS
i. Verify if the StoreGrid application is running in the system by executing the command 'ps -e |grep StoreGrid'.
ii. If the application is not running, start it with the command "sh start VembuStoreGrid.sh" in < StoreGrid_HOME>directory.
iii. If you see the following error message: "error while loading shared libraries: libstdc++.so.5..." while trying tostart StoreGrid, check whether the libstdc++.so.5 and other compatible libraries are installed in that system. Youcan check this by listing the libraries by "ls -l /usr/lib/libstdc++.so.5*" command.
iv. If it is a 64 bit system, make sure 32 bit compatible libraries are present in your 64 bit Linux OS as StoreGridruns as a 32 bit application in a 64 bit Linux machine. If the libraries are missing, please install 32 bitcompatible 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 thefollowing 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.
i. Verify this by running the command 'netstat -an | find "32005"' in the command prompt to check if the port32005 is in LISTEN state.
ii. Run the "telnet <machine name> 32005" command in command prompt to confirm if the web console canaccess the StoreGrid application UI communication port.
iii. If any personnel firewall/intrusion detection tools are installed in the system, try adding the StoreGrid.exe,SGTray.exe applications and 32005 default port in the NAT/Firewall configuration's exception list and then trylogging into the StoreGrid’s web console.
Top
28. 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, anapplication can be run as a service only by the Administrator account. A user account cannot run it as a service even ifit has all the administrative privileges.
Resolution:
i. Select StoreGrid build exe.
ii. Right click the exe and "run as an administrator".
Top
29. 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 failto 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 toaccess 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, makesure you install StoreGrid under your user account folder or install it in a folder which is not under 'Program Files'.
Top
30. Error while dumping the Exchange Mail Boxes. Unable to create the PST file [or] "No new/modified files forbackup"
Cause :
'MSPST MS' is not configured in the Exchange Server.
Solution :
The MAPISVC.INF file should have the information of the Microsoft Personal Folder store service. If this file does nothave this information, then the Exchange Mailbox dump will fail with an error indicating that it was "Unable to createthe 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\ orC:\Windows\System32\).
Verify the file has an entry for the Microsoft Personal Folder store service. You can determine this by looking for thefollowing information. If this information is not in the file then you need to add it in the proper sections:
Note: Please take copy of your "MAPISVC.INF" file before making any changes.
[Services]MSPST MS=Personal Folders File (.pst)
[MSPST MS]Providers=MSPST MSPPR_SERVICE_DLL_NAME=mspst.dllPR_SERVICE_INSTALL_ID={6485D262-C2AC-11D1-AD3E-10A0C911C9C0}PR_SERVICE_SUPPORT_FILES=mspst.dllPR_SERVICE_ENTRY_NAME=PSTServiceEntryPR_RESOURCE_FLAGS=SERVICE_NO_PRIMARY_IDENTITY
[MSPST MSP]34140102=4e495441f9bfb80100aa0037d96e0000PR_PROVIDER_DLL_NAME=mspst.dllPR_SERVICE_INSTALL_ID={6485D262-C2AC-11D1-AD3E-10A0C911C9C0}PR_RESOURCE_TYPE=MAPI_STORE_PROVIDERPR_RESOURCE_FLAGS=STATUS_DEFAULT_STOREPR_DISPLAY_NAME=Personal FoldersPR_PROVIDER_DISPLAY=Personal Folders File (.pst)
Points to remember regarding the above content:
a. In your MAPISVC.INF file, search for the text [Services]. If it is found in the file, just add the following lineunder [Services] if the following line does not exist under [Services].
MSPST MS=Personal Folders File (.pst)
If the text [Services] is not found in the file, then you can add both the lines given below to yourMAPISVC.INF file.
[Services]MSPST MS=Personal Folders File (.pst)
b. In your MAPISVC.INF file, search for the text [MSPST MS]. If it is found in the file, verify whether the contentunder this [MSPST MS] is the same as the content shown above. If the text [MSPST MS] is not found in thefile, then you can add the complete entry of [MSPST MS] as given above.
c. In your MAPISVC.INF file, search for the text [MSPST MSP]. If it is found in the file, verify whether the
content under this [MSPST MSP] is the same as the content shown above. If the text [MSPST MSP] is notfound in the file, then you can add the complete entry of [MSPST MSP] as given above.
For more information on the format of the MAPISVC.INF file see the following Microsoft article:http://support.microsoft.com/kb/294470
After modifying the MAPISVC.INF file, schedule the Exchange mailbox backup and check if the dump process runssuccessfully without any issues.
Top
31. 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 backupschedule. Location configured for dump process can be viewed from the view backup configuration of that backupschedule.
Top
32. 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 enoughpermission to access the directory.
Resolution :
Make sure that the dump location drive exist in your StoreGrid client. If that drive exist, provide enough writepermission to the user under which StoreGrid is installed.
Top
33. Users Mailbox/folder are not listed in the "Add 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 listthe users Mailbox.
2. 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 whichStoreGrid service is running. Please refer Granting Mailbox Rights document on creating a new user and granting thesufficient rights to access the mailboxes.
Top
34. StoreGrid fails to list some files/folders during a backup schedule.
StoreGrid fails to list the files/folders due to the following reasons:
Cause1:
If the file/folder doesn't have enough permission for the StoreGrid user.
Resolution1 :
i. Check if StoreGrid logon user has ‘Read’ and 'List Folder Contents' access permissions for the skipped folder bygoing to 'Folder Properties -> Security' dialog.
ii. If StoreGrid logon user doesn't have permission, enable the required permissions.
iii. Reschedule the backup and check.
Cause 2:
If the file/folder doesn't have enough permission for the StoreGrid user.
Resolution 2:
i. Check if StoreGrid logon user has ‘Read’ and 'List Folder Contents' access permissions for the skipped folder bygoing to 'Folder Properties -> Security' dialog.
ii. If StoreGrid logon user doesn't have permission, enable the required permissions.
iii. Reschedule the backup and check.
Top
35. I had changed the dump location and now I am not able to restore the previousbackups.[Applicable for Exchange Server, Exchange Mailbox and SQL Server backups.]
Resolution :
Please follow the steps below to restore the files from backup server to client and then to the Exchange Server/SQLServer.
i. Restore the files in the backup server side which were backed up before changing the dump location (i.e. backupfiles pertaining to the old dump location).
ii. Transfer the restored files from the backup server to the client machine, say by using an external USB drive.iii. Edit the 'restore.conf' available in "<Restored_location>/plugin/" folder in client machine.iv. Change the 'DumpLocation' attribute value to old dump location in <StoreGrid><Restore><Plugin> tag.v. Save the 'restore.conf' configuration file.vi. 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 theRestore Backup Data page and restore the files restored in step 2 by specifying the location of the files in'Restore Location' field.
Top
Vembu StoreGrid Server Windows Installation GuideBefore installing StoreGrid as Backup Server (or) Replication Server in your machine, you should install MySQL Server inyour machine (or) in any other dedicated machine where you wish to store StoreGrid's metadata information.
To know more about MySQL Server installation and configuration, please refer the following link : MySQL installation guidefor Windows
To install StoreGrid on Windows machines, follow the steps given below:
1. Download the Windows installer, VembuStoreGrid_4_2_0_SP.exe. Double click VembuStoreGrid_4_2_0_SP.exe andfollow the instructions in the installation wizard. Click Next to begin the installation process.
2. StoreGrid Service Type:
Select how you are going to provide backup service to your clients. You have two options,
Enable Reseller Management – If you are providing backup service through Resellers and would likecreate and manage Reseller accounts in the backup server, select this option.
Disable Reseller Management – If you are providing the backup server directly to your customers orusing it for your own needs without Resellers, select this option.
3. Vembu StoreGrid License Agreement:
Go through the license agreement, select "I accept the agreement" and proceed to the Next step.
4. Vembu StoreGrid - StoreGrid ID : ( StoreGrid will skip this step and retain existing settings if it detects anearlier version installed)
This will be used to identify this installation of StoreGrid. By default, StoreGrid takes the machine name. It isrecommended that you enter a unique ID, like machinename.domain.name of this particular machine.
Note: The StoreGrid ID value is case insensitive. The ID that you enter will be automatically converted to lowercase.
5. Vembu StoreGrid Service Configuration :
StoreGrid Servers are always installed as a Service. By default StoreGrid Service is selected to run from theWindows Local System Account. If you run StoreGrid service from the Local System Account, then StoreGrid will notbe able to access Mapped Drives and UNC Paths which need User Logon information for accessibility. Hence, youcan choose to run StoreGrid Service in a Windows User account.
If you want to run StoreGrid service from a Windows User account, then select this option and provide the UserName and the Password for the user account in the appropriate fields and click Next. In this case, StoreGrid Servicewill always run from this user account.
If your Windows user login is dependent on a Domain Controller, then install StoreGrid Service from the WindowsLocal System Account. You can then manually configure StoreGrid to run from a User account later by going toControl Panel -> Administrator Tools -> Services and changing the StoreGrid service options to run as a user.
NOTE : Please make sure, the User account configured for StoreGrid Service has 'Logon As Service' permission inWindows security policies.
6. Vembu StoreGrid Mode Configuration :
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 forredundancy.
Select one of the two options and click ‘Next’.
7. Vembu StoreGrid - StoreGrid ODBC Settings :
StoreGrid uses the system DSN to connect to the MySQL server to store the metadata information of the backupserver/replication server. Please enter the Data Source Name, Database Name which is already created duringMySQL server installation. Please enter the User Name and Password to connect to the MySQL Server.
8. Cluster Configuration :
Clustering will be disabled by default. If you would like to enable Clustering in your backup server, enter a namefor your Cluster. Also mention the external IP or DNS lookup name at which the clients will connect to this clusternode for backup.
NOTE : If you are adding an addition cluster node for your cluster, make sure you enter the same cluster name asthe previous cluster node installation.
9. Choose Installation Location : ( StoreGrid will skip this step and retain existing settings if it detects anearlier version installed)
By default, StoreGrid will be installed under " Vembu\StoreGrid" in the "C:\Program Files" directory. Click Next tocontinue installation in the default directory. Click Browse to choose a different directory. Note that this will createthe " Vembu\StoreGrid" directory under the directory you choose. Click Next to continue.
If StoreGrid detects existing data left behind from a previous installation of StoreGrid (wherein you uninstalled theprevious version but left some data behind) it will prompt you for a desired action. If no ‘old data’ was found in theinstallation directory or if you are simply upgrading from an existing installed version, StoreGrid will skip this step.
10. StoreGrid Server's Backup Storage Location : ( StoreGrid will skip this step and retain existing settingsif 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 differentdirectory from the tree. Click Next to continue.
11. Vembu StoreGrid Configuration : ( StoreGrid will skip this step and retain existing settings if it detects anearlier version installed)
There are three parts to this step.
i. Configure Web Server Port : StoreGrid's user interface is browser based. You have the option toconfigure the port used by StoreGrid web server here. Once configured you need to use this port to start theStoreGrid Web Console from your browser. By default StoreGrid Web server is configured to run on port6060. Unless you are an advanced user, please leave this as is.
ii. Username & Password : Since StoreGrid's user interface is browser based you need to configure ausername and password to login to StoreGrid Web Console. Note that you can add additional users, deleteusers, change password etc. from the Web Console UI after the installation. By default the username andpassword used by StoreGrid is "admin" and "admin". You have the option to change these default settingshere.
iii. Advanced Port Configuration (Including HTTPS): Click on the Advanced Port Configurations (IncludingHTTPS) link to configure StoreGrid backup server port, UI communication port and HTTPS port. Provide validTCP port numbers for Backup Server Port, UI Communication Port and HTTPS port. You will be able toconfigure 'Advanced Port Configuration' while upgrading StoreGrid too.
a. Backup Server Port is the port through which StoreGrid clients will backup the data to the backupserver. The default value is 32004.
b. UI Communication Port is the port through which StoreGrid Apache/PHP modules communicatewith StoreGrid to serve UI requests from the StoreGrid WebConsole. The default value is 32005.
c. HTTPS Port: HTTPS Port is the port used to access the StoreGrid Webconsole in a secured mannerthrough HTTPS protocol. Default value is 6061.
d. Enable HTTPS: HTTPS Port is the secure webconsole port through which you can access theStoreGrid 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 throughhttps://<machine name>:<HTTPS port> URL. And also, if you try to access the StoreGrid webconsolethrough http://<machine name>:<webconsole port>, then you will be automatically redirected tohttps://<machine name>:<HTTPS port> url.
e. Check Ports: You can use this small utility to check whether the configured StoreGrid ports areavailable for StoreGrid and not occupied by other applications. By clicking this button, it will popup a
small dialog and show the current status of the configured StoreGrid ports.
For example, if the Check Port Availability dialog shows status as "Webserver port: Available [6060]",it means, the 6060 TCP port is available for running StoreGrid Webserver.
12. Select Program Folder : ( StoreGrid will skip this step and retain existing settings if it detects an earlierversion installed)
Click Next to select the Programs Folder to add the StoreGrid shortcuts (ideally, leave it as it is). Proceed to thenext step to select required icons. For ease of use, allow the StoreGrid installer to create a desktop icon & a quicklaunch 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 theinstallation.
14. After copying the StoreGrid files, a page will show the progress of StoreGrid installation. If StoreGrid installationcompletes successfully, you will be automatically redirected to the finished installation page. Otherwise, theinstallation 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 getstarted real quick.
Note
A shortcut to start StoreGrid and StoreGrid Web Console will be created on the System Tray and in the Start >Programs > Vembu StoreGrid menu.
After successful installation, you can open the StoreGrid Web Console by right-clicking the StoreGrid icon in yoursystem tray and selecting the StoreGrid Web Console from the menu, or alternatively, doing the same through theStart > Programs > Vembu StoreGrid > StoreGrid Web Console menu. You will have to login to the Web Consoleusing the username and password you provided in the " Vembu StoreGrid Configuration" screen during theinstallation.
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 asAdministrator". The reason been, Vista allows an application to access the 'Program Files' folder only when run as anadministrator user. You can enable the 'Run as Administrator' option for the < StoreGrid Home>\bin\StoreGrid.exeapplication through it's file properties dialog through 'Compatibility' tab -> 'Privelege Level' -> 'Run this application asadministrator' option.
If you don't have administrator access or if you don't want to run StoreGrid under the administrator account, make sureyou install StoreGrid under your user account folder or other than the 'Program Files' folder.
StoreGrid Silent Installation1. What is a silent installation?
Some service providers prefer not to have their customers go through the step by step installation screens typicalof most installations from within the windows operating system, and instead would like to install StoreGrid directlyand 'silently' from the command line prompt.
2. How do I do a 'silent install' from the command line?
For command line/silent installation, just follow the simple steps below:
There are two options available: SILENT & VERYSILENT.In a SILENT installation, during installation, the Installation Progress page is displayed once installation hasstarted 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="< StoreGrid IDValue>" /DIR="< StoreGrid Home Path>" /SG_Mode=" StoreGrid Mode" /SG_ODBC_DSName="The ODBCDatasource Name." /SG_ODBC_HostName="The DB Server Host Name." /SG_ODBC_DBName="The ODBCDatabase Name." /SG_ODBC_User="The ODBC Datasource login User Name." /SG_ODBC_Pass="The ODBCDatasource login Password." /SG_Cluster_Enable="To enable clustering in this installation." /SG_Cluster_Name="Ifclustering is enabled, the cluster name for the cluster has to be provided." /SG_Public_LookupName_IP="Thislookup name or ip will be used to connect to this particular cluster node." /SG_User=" StoreGrid webconsole username" /SG_Pass=" StoreGrid webconsole Password" /SG_Port=" StoreGrid webconsole port"/SG_PrevDataOption="delete/rename" /SG_BackupPort="The Backup server port." /SG_UIPort="The UIcommunication port." /SG_HTTPS="0/1" /SG_HTTPSPort="The HTTPS port." [/SG_WUser="Windows logon username for StoreGrid service" /SG_WPass="Windows logon password for StoreGrid service"] /LOG="Installation logfile name".
Note:
/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 insensitiveWe recommend that you provide the /LOG option the first couple of times that you use the silent installationso you can identify issues during the silent installation, if any.
Description of Arguments, etc (Arguments with * are mandatory):
Argument Description ValuesDefaultValue
Note
*/SILENT*/VERYSILENT
You must specifyeither one of theseoptions
- - -
*AGREE_LICENSEDo you agree with theLicense Agreement?
Yes / No No
Hence this argument isnecessarily required to be set to"Yes" to run the installation.Please install StoreGrid fromwithin the Windows UI if youwould like to see the licenseagreement.You may want to copy & pastethis agreement on an html pageon your website for yourcustomers to read, if required.
*SG_ID
StoreGrid ID. Must notbe null or invalid id.Ideally, this should beanmachine.domain.nameas this is unique andeasily remembered forthis Server.
- -
More on valid StoreGrid IDs:
Allowed characters: [A-Z][a-z][0-9][ - .]Must not start or endwith special charactersLength must be 1 - 50characters.
DIR Installation location Any valid locationC:\Program
Files\ #This location is the StoreGridHome.
Mode of StoreGrid
SG_Modeinstallation
601/609 601 # 601 - Server Only609 - Replication Server
SG_WUser & SG_WPass
To run StoreGridservice in a specificWindows Logon UserAccount, pleaseprovide the logonaccount details.
Valid WindowsUser name andPassword
-No additional details are requiredfor running service under LocalSystem Account.
SG_ODBC_DSName,SG_ODBC_HostName,SG_ODBC_DBName,SG_ODBC_User &SG_ODBC_Pass
The ODBC parametersmention theDatasource Name,Host Name, DatabaseName, Login UserName and LoginPassword for theStoreGrid ODBCbackend.
Provide a validDatasource Namewhich is alreadyconfigured in the"Windows StartMenu -> ControlPanel ->AdministrativeTools -> ODBCDatasources".
- -
SG_Cluster_Enable,SG_Cluster_Name &SG_Public_LookupName_IP
To run StoreGrid in acluster, you need toenable cluster (0/1)and provide a uniquecluster name. Youshould also provide apublic DNS Lookupname or IP Address forthe installed clusternode.
0/1, cluster name& lookup name.
-The cluster name and lookupname are needed only ifclustering is enabled (1).
SG_User & SG_Pass
Authentication detailsfor StoreGridwebconsole [username& password]
-
Username:admin Password:admin
-
SG_PortStoreGrid Webconsoleport number.
Any valid TCPport number 6060 # -
SG_PrevDataOption
During installation, ifthere is existing datafrom a previousinstallation ofStoreGrid, what is tobe done?
Delete / Rename Rename -
SG_BackupPort
The port through whichStoreGrid clients willbackup the data to thebackup server.
Any valid TCPport numberbetween 1 to65535
32004 # -
SG_UIPort
The port through whichStoreGrid Apache/PHPmodules communicatewith StoreGrid to serveUI requests from theStoreGrid WebConsole.
Any valid TCPport numberbetween 1 to65535
32005 # -
SG_HTTPS
You can enable thesecure HTTPS webaccess by checking the"Enable HTTPS" checkbox.
0 / 1 1 #0 - Disable1 - Enable
SG_HTTPSPort
HTTPS Port is thesecure webconsole portthrough which you canaccess the StoreGrid
Any valid TCPport numberbetween 1 to 6061 #
Must not be same as theSG_Port / SG_UIPort /
webconsole in securemanner.
65535SG_BackupPort
SG_WValidateOption to enable ordisable validation ofWindows login details.
Enable - 1Disable - 0
Enable
Some machines do not validateWindows login details correctly –may reject even when the logindetails are right. In such cases,turning this option off may beadvisable. If this option is turnedoff and if the login detailsentered are wrong, then the usermay not be aware that the logindetails are wrong till the backupis scheduled and fails to run.
SG_SSL_SERVERPORT_STATUS
HTTPS Port is thesecure webconsole portthrough which you canaccess the StoreGridwebconsole in securemanner.
Enable - 1Disable - 0
0
This status tells if the clientneeds to connect to the backupserver through the SSL enabledbackup port or not. If this optionis enabled, valid SSL Backupport should be specified duringsilent installation. If this optionis not provided during upgrade,then the previous installationvalue is taken.
SG_SSL_SERVERPORTBackup port with SSLsecurity.
Valid port value 32007
The backup port value with SSLsecurity option. It should be thesame at backup server and clientsystem. If this option is notprovided then the previousinstallation value is taken.
# - While upgrading StoreGrid, if these arguments not provided, the values will be taken from the previous installation. If itis a new installation, the default values as mentioned in the table will be used.
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 StoreGrid ID: backup.billg.com ; installin Backup Server mode; as a Service, with WebConsole username: bill and password: abc123 to access theStoreGrid webconsole which must run on port 6087. Listens for backups/restores at 3344 port; Thewebconsole will communicate the StoreGrid through 3355 port. The user would like to see the progress ofthe installation as it happens
Required command line is:
VembuStoreGrid_4_2_0_SP.exe/SILENT/AGREE_LICENSE="yes"/SG_ID="backup.billg.com"/SG_Mode="601"/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 StoreGrid ID: replication.billg.com ;install in Replication Server mode; as a service, with WebConsole user name as default username: adminand default password: admin, to run StoreGrid WebConsole on the default port 6060. The user is notbothered about seeing the progress of the installation as it happens. Just install it!
Required command line is:
VembuStoreGrid_4_2_0_SP.exe/SILENT/AGREE_LICENSE="yes"/SG_ID="replication.billg.com"/SG_Mode="609"[Note: All the command line options should come in single line.]
Vembu StoreGrid Linux Server Installation GuideBefore installing StoreGrid as Backup Server (or) Replication Server in your machine , you should install MySQL Server inyour machine (or) in any other dedicated machine where you wish to store StoreGrid's metadata information.
To know more about MySQL Server installation and configuration, please refer the following link : MySQL installation guidefor Linux
Download the Linux installer,
For RedHat Linux 8.0, 9.0 and Later, RedHat EL 4 and Later, CentOS 4 and Later, Fedora Core 3 and Later, SuSELinux 9.x and Later: VembuStoreGrid_4_2_SP_RH.zip
For Debian Linux 4.0 and Later, Gentoo, Ubuntu 7.10 and Later : VembuStoreGrid_4_2_SP_DBN.zip
For Mandrake Linux 10.0 and Later: VembuStoreGrid_4_2_SP_MDK.zip
The Linux builds are pre-compiled and all the required dependencies are included in the build itself. You don't have toinstall the dependencies separately.
The libstdc++.so.5 is a run time compilation library required for StoreGrid Application to run in the machine. This librarycan be downloaded and installed from http://gcc.gnu.org/libstdc++/
Note: Linux installation should be run with the root user privileges.
To install StoreGrid server on Linux machines, follow the steps given below:
1. Unzip the downloaded ZIP file.
2. Execute the bin file
For RedHat Linux 8.0, 9.0 and Later, RedHat EL 4 and Later, CentOS 4 and Later, Fedora Core 3 and Later,SuSE Linux 9.x and Later: ./ VembuStoreGrid_4_2_SP_RH.bin
For Mandrake Linux 10.0 and Later: ./ VembuStoreGrid_4_2_SP_MDK.bin
For Debian Linux 4.0 and Later, Gentoo, Ubuntu 7.10 and Later : ./VembuStoreGrid_4_2_SP_DBN.bin
StoreGrid needs root user privileges. Hence if StoreGrid is installed as a 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 :
You can install StoreGrid in a newly created StoreGrid user account, where the StoreGrid user account willbe automatically created with root privileges
You can install StoreGrid in the current user account.
Choose option 1 (highly recommended), if you want StoreGrid to be installed as a daemon process and you want itto be automatically started when the system boots up. You can also START and STOP StoreGrid by running thecommand "/etc/init.d/ /etc/init.d/storegrid start/stop". You can check the status of StoreGrid application by runningthe command "/etc/init.d/ /etc/init.d/storegrid status".
Choose option 2, if you want StoreGrid to be installed as an application - if you want StoreGrid to be installed in thecurrent user directory and you don't want to start it automatically every time the machine is rebooted. You canSTART and STOP StoreGrid by running the script start VembuStoreGrid.sh and stop VembuStoreGrid.sh
4. If StoreGrid is installed fresh and you chose option 1 in the above step, then you will be asked to provide apassword for the StoreGrid user account which is created. Note that StoreGrid will be installed as a daemon processand will automatically start when the system boots up. You can START and STOP StoreGrid by running thecommand "/etc/init.d/ /etc/init.d/storegrid start/stop". You can check the status of StoreGrid application by runningthe command "/etc/init.d/ /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 thecurrent user directory and has to be manually started every time the machine is rebooted. You can START andSTOP StoreGrid by running the script start VembuStoreGrid.sh and stop VembuStoreGrid.sh
5. Read through the License Agreement carefully. If you agree, enter Yes to continue with the installation. If you donot 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. Bydefault 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 underthe directory you entered.
7. If StoreGrid is already in the installed location, StoreGrid will try to upgrade. The installation will ask the userwhether the previous setup can be migrated or not. Enter 'yes' to continue up gradation and 'no' to abort theinstallation.
StoreGrid can be upgraded to v4.2 from StoreGrid version 4.0 and 4.1
8. StoreGrid Service Type:
Select how you are going to provide backup service to your clients. You have two options,
Enable Reseller Management – If you are providing backup service through Resellers and would likecreate and manage Reseller accounts in the backup server, select this option.
Disable Reseller Management – If you are providing the backup server directly to your customers orusing it for your own needs without Resellers, select this option.
9. Configure StoreGrid as:
You need to choose one of the options ( Backup Server or Replication Server). The two modes are explained indetail below.
Backup Server - Choose this option to install StoreGrid as a backup server to which client machines canbackup to. Also, this backup server installation will be able to replicate to a StoreGrid replication server
Replication Server - Other StoreGrid backup servers can replicate their data to this server forredundancy but this server will not be able to accept backup data from StoreGrid clients.
10. ODBC Configurations:
StoreGrid uses the system DSN to connect to the MySQL server to store the metadata information of the backupserver/replication server. Please enter the Data Source Name, Database Name which is already created duringMySQL server installation. Please enter the User Name and Password to connect to the MySQL Server.
11. Assign a StoreGrid ID:
StoreGrid ID is the unique name with which your StoreGrid installation is identified. By default, it takes yourmachine name as the StoreGrid ID. But we recommend giving a globally unique ID (likemachinename.domainname). 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 an unique ID (likemachinename.domainname) for this.
Note : The StoreGrid ID value is case insensitive. Hence, the ' StoreGrid ID' you have entered will be automaticallyconverted to lower case.
12. 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 providedwith 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.
13. 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 consoleaccess. StoreGrid supports 'https protocol' to access the StoreGrid webconsole in a secured manner. Hence, if youtry to access the StoreGrid webconsole through http://<machine name>:<webconsole port>, then you will beautomatically redirected to https://<machine name>:<HTTPS port> url.
Note : StoreGrid Web Console access through HTTPS is enabled by default.
14. Vembu StoreGrid Web Console Authentication:
StoreGrid's Web Console user interface is browser based; you need to configure a username and password to loginto StoreGrid Web Console. Note that you can add additional users, delete users, change password etc. from theWeb Console UI after the installation.
15. 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 'UICommunication Port' 32005 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 :
"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 andthe 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.
16. This installs the product and completes the installation process. After successful installation, you are provided withan option to start the StoreGrid. After the installation, you can start StoreGrid by executing the script "startVembuStoreGrid.sh" from the directory "<INSTALLATION_HOME>/ Vembu/StoreGrid/".
Note:
After successful installation, you can open the StoreGrid Web Console from your browser by typing http://<Your MachineName>:6060. You will have to login to the Web Console using the username and password you provided in the " VembuStoreGrid Web Console Authentication" step during the installation.
Setting up MySQL on Windows as StoreGrid Backend Database
Overview
StoreGrid uses MySQL as the backend database in Backup Server and Replication Server installations to store all thebackup metadata information. To get StoreGrid to work with MySQL as a backend database, you need to install MySQLServer either in the same machine where StoreGrid backup server is installed or in another dedicated machine.
Note : The following steps are applicable to StoreGrid Backup Server and Replication Server installations.
Installing and Configuring MySQL Server on Windows
StoreGrid provides you an utility to install and customize the MySQL Server components for StoreGrid backend. This utilitywill download, install and customizes the MySQL Server v5.1.39, MySQL ODBC Driver v3.51.27 components, createsdatabase and system DSNs for StoreGrid. Since this utility downloads MySQL Server components from Internet, thebackup/replication server should have Internet connectivity. This utility is typically available from the same source fromwhere you downloaded the StoreGrid builds.
1. Download StoreGrid Online MySQL Components installer. The installer is typically available in the same sourcelocation from where the other StoreGrid builds you downloaded from.
2. Run the downloaded installer file.
3. In the MySQL Server Configuration wizard page, provide valid values for Port Number, MySQL Server rootpassword, installation and database storage location.
NOTE: StoreGrid's metadata stored in the MySQL databases could use up certain amount of space. To give arough estimation of the usage, if the backup server stores 1 million backed up files, then the MySQL DB could beof size 1.5 GB. For this disk size estimation, each version file is also considered as a separate file. Therefore, forexample, if a client is backing up 1 million files and for each file there are 3 versions stored in the backup serverthen there will be 3 million backed up files for that client machine. For these 3 million backed up files, the MySQLDB size could be about 4.5 GB. Please make sure that you have enough space in this location for allfuture backups from all the client machines. As MySQL Server runs as a Windows service, thislocation should be in local fixed disk drive.
4. If MySQL Server (of same version) is already installed in the system, this utility will show the previous MySQLServer installation details. You can continue the installation by clicking Next button.
IMPORTANT NOTE: StoreGrid is well tested with MySQL Server v5.1.39 & MySQL ODBC driver v3.51.27 only. Ifyou had already installed different MySQL Server and/or MySQL ODBC driver in the server system, werecommend you to install this MySQL Server components in different machine and configure StoreGrid to accessMySQL Server from that system.
5. Click on the Next button to start download, install and customize the MySQL Server components. Following are thedefault MySQL Server components settings created by this utility:
MySQL Server Instance Name: SGMySQL51MySQL Server Port Number: User Value [default: 3306]MySQL Server Installation Path: User Value [default: C:\Program Files\MySQL\MySQL Server 5.1\]MySQL Server Data Path: User Value [default: C:\Program Files\MySQL\MySQL Server 5.1\Data]MySQL Server Database Name: SGDatabaseMySQL Server DSN Name: SGDBConnectionMySQL Server Root User Name: rootMySQL Server Root User Password: User Value [default: admin]
Specify the attributes during StoreGrid installation
After installing MySQL Server components in the backup/replication server, you need to specify the above values duringthe StoreGrid installation in the backup/replication server.
Troubleshooting Tips
StoreGrid is not started (or) repeatedly crashes after startup
Solution : Stop StoreGrid application and start StoreGrid in command line by executing 'bin\ StoreGrid.exe' from [StoreGrid_Home] folder. Note the console print from the terminal. Please follow the solutions when the console print areas follows :
1. Can't connect to local MySQL server...
Make sure that the MySQL server is running in the machine where MySQL is installed. Execute 'netstat -an | grep3306' (for linux) or 'netstat -an | find "3306"' (for Windows) in the machine where MySQL server is running andcheck if the MySQL port 3306 (default mysql port) is in LISTEN state. If MySQL is not running, please start theMySQL Server and then try starting StoreGrid.
2. Data source name not found...
Make sure that you have given the correct DSN name during the StoreGrid installation.1. Open up the "Control Panel -> Administrative Tools -> DataSources (ODBC)" tool.2. Go to the tab 'System DSN' and select the Data Source Name.3. Click on the 'Configure ' button.4. Click on the 'Test' button. If there is any problem click on 'Diagnostics' button to get the exact error
message.
3. Access denied for user...
Check if you have given the correct user name and password for the MySQL Server during StoreGrid installation.1. Open up the "Control Panel -> Administrative Tools -> DataSources (ODBC)" tool.2. Go to the tab 'System DSN' and select the Data Source Name.3. Click on the 'Configure ' button.4. Click on the 'Test' button. If there is any problem click on 'Diagnostics' button to get the exact error
message.
4. Host 'xxxxx' is not allowed to connect to this MySQL server...
Provide the required permission in the MySQL to allow the backup server to connect the database. You can dothis by executing 'GRANT ALL PRIVILEGES ON *.* TO '[user name]'@'[backup server machine name]'IDENTIFIED BY '[password]' WITH GRANT OPTION;' in the MySQL prompt in the machine where MySQL Server isinstalled.
NOTE: If you are deploying the backup servers in a cluster, you need to execute the above command for eachof the backup server in the cluster replacing the 'backup server machine name' with the machine name of thebackup server. If you find it cumbersome to execute this for each backup server, you could replace the 'backupserver machine name' with '%' like:'GRANT ALL PRIVILEGES ON *.* TO '[user name]'@'%' IDENTIFIED BY '[password]' WITH GRANT OPTION;'
Installing and Configuring MySQL as StoreGrid Backend Database onLinux
Overview
StoreGrid uses MySQL as the backend database in Backup Server and Replication Server installations to store all thebackup metadata information. To get StoreGrid to work with MySQL as a backend database, you need to install MySQLServer either in the same machine where StoreGrid backup server is installed or in another dedicated machine.
Note : The following steps are applicable to StoreGrid Backup Server and Replication Server installations.
Install and Configure MySQL Server
StoreGrid provides you an utility to install and customize the MySQL Server components for StoreGrid backend. This utilitywill download, install and customizes the MySQL Server v5.1.39, unixODBC v2.2.14, MySQL ODBC Driver v3.51.27components, creates database and system DSNs for StoreGrid. As this utility downloads MySQL Server components fromInternet, the backup/replication server should have Internet connectivity.
1. Download StoreGrid's Online MySQL Components installer. The installer is typically available in the same sourcelocation from where the other StoreGrid builds you downloaded from.
2. Execute the downloaded script file "MySQLSetup_Simple_Web.sh" with root user privilege.3. Read the instructions carefully and provide the suitable options.
NOTE: MySQL Server components installer will check the missing packages for running MySQL Server in theLinux machine, and will ask confirmation to install missing packages. If you wish to install the missing packages,enter 'yes' to continue the installation. Otherwise, enter 'no' to abort the installation.
4. At the end of the installation, to check the database connectivity of the created DSN setting, the script will promptfor MySQL Server root user's password. Enter the correct MySQL Server root user password to check the createdDSN setting.
Specify the attributes during StoreGrid installation
After installing MySQL Server components, you need to specify DSN name, database name, user name and passwordduring the StoreGrid installation in the backup server.
Troubleshooting Tips
StoreGrid is not started (or) repeatedly crashes after startup
Solution : Stop StoreGrid application and start StoreGrid in command line by executing './bin/ StoreGrid' from [StoreGrid_Home] folder. Note the console print from the terminal. Please follow the solutions when the console print areas follows :
1. Can't connect to local MySQL server...
Make sure that the MySQL server is running in the machine where MySQL is installed. Execute 'netstat -an | grep3306' (for linux) or 'netstat -an | find "3306"' (for Windows) in the machine where MySQL server is running andcheck if the MySQL port 3306 (default mysql port) is in LISTEN state. If MySQL is not running, please start theMySQL Server and then try starting StoreGrid.
2. Data source name not found...
Make sure that you have given the correct DSN name during the StoreGrid installation. Please check the DSN byexecuting the command 'isql -v [dsn name] [user name] [password]' and check if you are able to connect to theMySQL server with the DSN name.
3. Access denied for user...
Check if you have given the correct user name and password for the MySQL Server during StoreGrid installation.Please check this by executing the command 'isql -v [dsn name] [user name] [password]' and check if you areable to connect to the MySQL server with the user name and password.
4. Host 'xxxxx' is not allowed to connect to this MySQL server...
Provide the required permission in the MySQL to allow the backup server to connect the database. You can dothis by executing 'GRANT ALL PRIVILEGES ON *.* TO '[user name]'@'[backup server machine name]'IDENTIFIED BY '[password]' WITH GRANT OPTION;' in the MySQL prompt in the machine where MySQL Server isinstalled.
NOTE: If you are deploying the backup servers in a cluster, you need to execute the above command for eachof the backup server in the cluster replacing the 'backup server machine name' with the machine name of thebackup server. If you find it cumbersome to execute this for each backup server, you could replace the 'backupserver machine name' with '%' like:'GRANT ALL PRIVILEGES ON *.* TO '[user name]'@'[%]'
Error: Starting MySQL...Manager of pid-file quit without updating.
Cause: If SELinux is enabled in your Linux system then you could get this error when SELinux aborts MySQL managerwhile it is updating the pid file. To confirm that SELinux is enabled, execute the command '/usr/sbin/sestatus' as a rootuser.
Solution : Execute the command 'setsebool -P mysqld_disable_trans=1 allow_user_mysql_connect=1' as root user andrestart the MySQL server.
Setting Up StoreGrid Server for Online Backups
Overview
This document details the step by step instructions on setting up a StoreGrid backup server for online backups.
Setting Up StoreGrid Server for Online Backups
Follow the below instructions to setup the backup server for online backup service:
Install StoreGrid Server build in your backup server in Server mode
During the installation of the server build in the backup server machine, assign a unique StoreGrid ID for the StoreGridServer installation. By default StoreGrid will take the machine name in which it is installed as its StoreGrid ID. But werecommend that you use a globally unique ID for all your StoreGrid installations. Since a StoreGrid server is not associatedwith any user, using a DNS name (e.g. server1.vembu.com) will make it globally unique. For more details on BackupServer installation please check the installation help document for Windows and Linux
Network Connectivity and Firewall Configurations
StoreGrid Server listens on the backup port [TCP: 32004, SSL TCP: 32007] for client requests. Make sure the firewall ofthe online backup server is open for the backup ports. Please refer Firewall Setup for more information. If the clientmachines are backing up from another network over the WAN/Internet, make sure the client machines can access thebackup server on the backup TCP ports (32004/32007) at a publicly available static IP address or a domain name. You cancheck the connectivity to the backup server from the client machine through Test Backup Server Connectivity featurethrough the client's StoreGrid web console.
Setting up the backup server so that a client can start backing up
By default the StoreGrid server creates a Default Reseller and a Default Customer under the Default Reseller. By default,the Default Reseller and the Default Customer are configured to ‘Disable Auto Authorization’ of the client - before a clientmachine can backup to the newly installed backup server, the client has to be added under the Default Customer. Whileadding the client under Default Customer in the backup server, you need to specify a password. The StoreGrid client hasto then authenticate itself with the password before it starts backing up to the backup server through. This way you canenforce the clients to sign up with a password to use the online Backup Service and all communication with StoreGridClient and Server is authenticated. For more information on adding a client to the backup server, please check Add Clienthelp.
If you want to allow the client machines to backup without having to add them first in the backup server, then you needto do the following:
a. Enable 'Auto Authorization' for the Default Reseller: Go to the Server Admin->Reseller Management page inthe backup server's web console. In the Default Reseller row, click on the icon under Enable/Disable AutoAuthorization and change it to Enable Auto Authorization. For more information please refer Reseller Managementhelp page.
b. Enable Auto Authorization for the Default Customer: Click on the Default Reseller to list the Default Customerand click on the Enable/Disable Auto Authorization icon against Default Customer and change it to Enable AutoAuthorization. For more information please refer Customer Management help page.
The added client can backup to the backup server without consuming any MCALs (licensing units) for one month. For thisone month, the client will be listed as a Trial Client in the backup server. After one month, the client will automaticallystart using up the MCALs available in the backup server.
You can also refer Client Setup help document to get more details on setting up a client machine.
Organizing the client machines under the respective Reseller and Customer in the backup server
Instead of having clients backing up under Default Reseller and Default Customer, you can organize the client machinesunder respective Reseller (if you offer the backup service to the customer through a reseller) and Customer by creating theReseller and Customer accounts in the backup server and adding the clients under the respective Reseller/Customer.
Adding a new Reseller
To add a Reseller account to your server, you need to do the following:
a. Go to the "Server Admin->Reseller Management" page.
b. Click on the "Add New Reseller" icon on the left.
i. Set the disk space for this reseller.
ii. Enable Web Access with a username and password (if needed) for the Reseller to access the backup serverweb console.
For more details, please refer Add Reseller help page.
Adding a new Customer
To add a customer to the backup server, you need to do the following:
a. Go to the "Server Admin->Reseller Management" page
b. Click on the "Add New Customer" Action icon for the reseller to whom this customer belongs.
i. Set the disk space for this customer.
ii. Enable Web Access for the customer with a username and password (if needed) for the customer to accessthe backup server web console to manage their backups.
For more details, please refer Add Customer help page.
Setting Up StoreGrid Clients For Online Backups
Overview
This document details step by step instructions on setting up a StoreGrid backup client for online backups.
Setting Up StoreGrid Clients for Online Backups
Please refer Windows Follow the below instructions to setup the client for backing up to the online backup server:
Install StoreGrid in your customer's client PCs using the Client-Only installation.
Install the StoreGrid Client build in the client machine. Make sure you assign a unique StoreGrid ID for the StoreGrid Clientinstallation. By default StoreGrid will take the machine name (in which it is installed) as its ID. But we recommend thatyou use a globally unique name, such as email-id or a domain suffix, for all your StoreGrid installations.
If the StoreGrid installation is not associated with any user (e.g. a server at your customer’s office), then using a DNSname (e.g. client1.datamaniacs.com) will make it globally unique.
If the StoreGrid client is associated with a particular user then using the users email ID (e.g. [email protected]) willmake the StoreGrid ID globally unique.
Having globally unique client names will make it easier for you to manage your customers/clients.
Add Server to StoreGrid Peer List
Once StoreGrid is installed in the client machine, go the "Settings->Add Peer / Delete Peer " page in the client StoreGridweb console and add the public lookup name (or public IP address) of the backup server to which the client should connectfor backup.
Connecting to the backup server
If Auto Authorization is enabled for the Default Reseller and for the Default Customer in the StoreGrid backup server, thenthe client can connect to the backup server and start backing up. If, however, Auto Authorization is disabled (it is disabledby default) in the backup server, then the following needs to be done before the client can connect to the backup server:
1. You should first add the client in your backup server under the respective Reseller/Customer account with the sameStoreGrid ID, (say [email protected]) and assign a password to it while adding the client.
2. Make sure the StoreGrid Client is installed in the client machine with the same StoreGrid ID ([email protected]).
3. The StoreGrid client should then be authenticated with the backup server by doing the following:
a. Go to the "Settings-> Authenticate Client" page in the StoreGrid client web console.
b. Select the server.
c. Enter the password that was specified when adding the client ([email protected]) in the backup server.
d. Click on the "Authenticate" button to authenticate this trial client with the server.
e. Once authenticated, the client can start running backups to the server. Note that the manual authenticationstep needs to be done only once. Subsequent authentication (when the client backs up to the server) isdone automatically.
Setting Up StoreGrid Server in a StoreGrid Cluster
Overview
This document details the steps involved in setting up a StoreGrid Server in a StoreGrid Cluster environment. MultipleStoreGrid Servers [Backup or Replication] can be deployed to run as a single entity. These servers store and accessStoreGrid metadata in a centralized StoreGrid Database using ODBC.
Setting Up StoreGrid Server in a StoreGrid Cluster
1. Install StoreGrid in your first cluster node (can also be known as the master node) in Server mode withclustering enabled.
The first step is to assign a StoreGrid ID for the StoreGrid Server installation. StoreGrid Server ID should beunique. This enables the StoreGrid cluster to identify between different StoreGrid nodes in the cluster.
Specify the ODBC parameters to use MySQL system DSN for storing the backend metadata.
In the next screen, enable clustering and provide a cluster name (unique for the cluster) during the installation.
Complete the installation and start StoreGrid. Make sure all configurations done are reflected in the cluster masternode.
2. Install StoreGrid in your next cluster node in Server mode with clustering enabled
The first step is to assign a StoreGrid ID for the StoreGrid Server installation. As earlier, make sure the StoreGridServer ID is unique.
Specify the ODBC parameters to use MySQL system DSN for storing the backend metadata.
In the next screen, enable clustering and provide the same cluster name as provided when installing the firstcluster node.
Complete the installation and start StoreGrid. Make sure the cluster node has been registered successfully.
Install more cluster nodes as needed.
3. Register Resellers/Customers/Clients
Create Reseller accounts from "Server Admin -> Reseller Management -> Add a New Reseller" icon.
Create Customer accounts under Reseller from "Server Admin -> Reseller Management -> Click on Add NewCustomer " Action Icon for the specific Reseller.
Register new Clients for the Customer from "Server Admin -> Reseller Management -> Click on the Reseller Name -> Click on Add New Client " Action Icon for the specific Customer.
4. Configure Node Locking of Reseller/Customer/Client
Access the StoreGrid WebConsole and go to "Server Management -> Cluster Management -> Manage Node LockedServers" tab.
Click on Manage Resellers tab and select the resellers for the particular cluster node.
Click on Manage Customers tab and select the customers for the particular cluster node.
Click on Manage Clients and select the clients for the particular cluster node.
5. Start backing up the Resellers/Customers/Clients to the StoreGrid cluster.
NOTE: For a cluster to be alive, atleast one cluster node should be alive. The first cluster node installation takes care ofcreating and configuring the database with default values, the rest of the installations use the existing configurationalready available from the previous node installation.
Configure Storage LocationThis 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 thislocation 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' backupstorage location.
Reseller Based Storage Location
Each Reseller in StoreGrid can be configured with a different backup location. By default all resellers will use the samelocation as the "Global Backup Data Storage Location". When a new reseller is created in StoreGrid you can provide newstorage location for the reseller. You can edit the existing Storage Location for the reseller by going to the "Edit ResellerConfiguration" UI page. Note that if you modify the reseller storage location, it will not change the existing clients' backupstorage location. It will take effect only for the new clients backing up under the customer.
Customer Based Storage Location
Each Customer in StoreGrid can be configured with a different backup location. By default all customers will use the samelocation as the "Global Backup Data Storage Location". When a new customer is created in StoreGrid you can provide newstorage location for the customer. You can edit the existing Storage Location for the customer by going to the "EditCustomer Configuration" UI page. Note that if you modify the customer storage location, it will not change the existingclients' backup storage location. It will take effect only for the new clients backing up under the customer.
Client Based Storage Location
In StoreGrid, each client under a customer can be configured with a different backup location. By default all clients willuse the same location as the Global Backup Data Storage Location. If a client is created manually, then you can provide adifferent backup location for the client. But you will never have to create a client manually in StoreGrid. Clients are createdunder a customer automatically when the client backs up first time. So the clients will automatically use the Storagelocation 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 backupschedules will continue to backup to the older backup location. While editing backup data storage location in the client,you can choose to move the existing backup data to the newer location. Please note that, copying data in StoreGrid is alittle bit time-consuming and if you have large chunks of data to be moved, we recommend doing the change manually.
StoreGrid Client Registration
Overview
StoreGrid client machines backing up to a StoreGrid backup server are organized under appropriate Reseller (if ResellerManagement is enabled) and Customer accounts in the backup server. When a new client machine backs up to a backupserver, it is by default added under the Default Customer.
The Default Customer account by default is set to 'Enable Auto Authorization' which allows client new machines to beadded under it without having the client machines to first authenticate with the backup server. The other Customeraccounts that are added in the backup server by you are by default set to 'Disable Auto Authorization', for securitypurposes. For a Client machine to be added under such a Customer, you need to first create the Client account in thebackup server. For security purposes, you could create the client with a password and the Client machine has to thenauthenticate with the backup server using that password before it can start backing up under that Customer.
Creating a Client account under the appropriate Customer account in the backup server for each of the client machines andthen assigning a password and authenticating them with it may be cumbersome when the number of client machines islarge. The StoreGrid Client Registration feature provides an easier but a secure way to authenticate and add new clientmachine under the appropriate Reseller/Customer accounts.
How to get here in the StoreGrid Web Console? In the Client web console: In the StoreGrid Client web console login page, click on the "Sign Up" link below the
user name/password fields.
In the Backup Server web console: Go to "Server Admin->Reseller/Customer Management->Add Customer" andenter the details of the Customer account to be created. When you save the information, the backup server will promptyou if you want to send the Customer account details to the Customer. Choose the option to send the email. Thebackup server will send the Passkey to the Customer with which the client machines can be registered under thatCustomer.
StoreGrid Client Registration
The illustration above shows the sequence of steps required by the admin on the backup server and the Customer on theclient side to register a client under a Customer in the backup server.
1. Create the Customer account in the backup server by going to the 'Add Customer' page under CustomerManagement page in the backup server web console. The Customer Management page can be accessed throughServer Admin > Reseller Management > Click on the Reseller' (if Reseller Management is enabled in the backupserver) or through Server Admin > Customer Management (if Reseller Management is disabled). After entering thedetails of the Customer account, click on the Save button. The backup server will prompt you if you want to sendan Email to the Customer with the account details. Choose OK.
2. StoreGrid backup server creates the Customer account and sends an Email to the Customer with the details of theaccount, including the unique Customer Passkey.
3. The Customer will receive the Email with the Passkey. Customer can then access the web console of the clientmachine that needs to be registered. In the login page in the client web console, the Customer should click on thelink Sign Up which takes the Customer to the Client Registration page where a client Password can be chosen andthe Passkey is entered. The StoreGrid ID of the client (user name) and the chosen client password can be used forthe 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 thatparticular Customer.
Troubleshooting
Error occurred while trying to register the client
Cause: Some internal error occurred, either at client or backup server side, when registering this client.
Solution: Check the StoreGrid events for any error message.
The server you are trying to register this client is not a backup server
Cause: StoreGrid is not running in backup server mode in the selected backup server system.
Solution: Check whether StoreGrid is running in backup server. Also make sure the server that you have specified isthe client is a backup server.
The Passkey key specified does not seem to be valid one.
Cause: The entered Customer passkey is not valid.
Solution: Check if the entered Customer passkey is correct by checking it against the passkey in the backup server inthe "Server Admin -> Reseller Management -> Reseller [Reseller Name] -> Edit Customer action" page in the backupserver's web console page.
Client's group is currently deactivated
Cause: In the backup server, the Reseller/Customer is deactivated.
Solution: Check whether the Reseller/Customer account under which the client is been registered is deactivated. If theReseller/Customer is deactivated, then activate the Reseller/Customer and check it again.
Client limit reached for the group corresponding to the specified Passkey.
Cause: The Customer under which you are trying to register the client in the backup server has exceeded themaximum clients limit.
Solution: Check the Customer's client limit value in "Server Admin -> Reseller Management -> Reseller [ResellerName] -> Edit Customer action" page. If the number of clients registered under this Customer has reached this limit,increase the maximum clients limit value for that Customer in the backup server.
No valid backup location was found to be set for the group corresponding to the specifiedPasskey.
Cause: The Customer's backup storage location is not accessible to the backup server.
Solution: Check if the Customer's backup storage location is accessible to the backup server and StoreGrid has enoughpermission to access that location.
Not enough backup space available to add this client.
Cause: There is no sufficient backup space available in the backup server or allotted to the Reseller/Customer toaccommodate this client.
Solution: Increase the allotted backup space for the backup server/Reseller/Customer.
Server Settings
Overview
The Server Settings page helps in getting a overview and also provides an interface to update various configurationavailable for the StoreGrid Server. This page gives details on Server configuration Options, the Server Disk SpaceUtilization, Server MCAL utilization and backup storage location details.
How to get here in the StoreGrid Web Console? In the top menu, select: "Settings->Server Settings"
Server Settings
The page is organized with three parts of information. The first part describes the StoreGrid Server settings and theirvalues and the other two parts summarize the Storage Disk Space Utilization and Backup Storage Location details.
Server Name : Non-editable field displaying the server's StoreGrid ID value. In case, the Server is running in acluster, this shows the cluster name of the cluster.
Backup Location : This is the directory into which all the client backups are stored. Note that if we change thislocation, the new directory will take effect only for the new clients backing up to this server. Backup data of allexisting clients who are already backing up on to this server will still be stored in the same location. You can editthis directory location either manually or by selecting the backup location from the directory tree by clicking thebutton provided at the end of the text box.
Backup Space Allotted : This field specifies the total backup space allotted for the Server. By default, the totalbackup space allotted in the server will be 30% of the free disk space available. You can update this value toincrease or decrease the total backup space in this server allotted for all the StoreGrid clients. Please ensure you'veselected MB/GB option correctly before saving.
SGTrash Settings : SGTrash folder is the location where StoreGrid backup server moves all the backup dataremoved due to retention cleanup, full-backup cleanup and delete-backup cleanup ( by default, the SGTrashlocation is the backup location). Instead of the deleting the excess version files, the server just moves the data tothe SGTrash folder. When it is disabled, the files are deleted permanently from the system.
CPU Utilization Settings : This is used to specify how this server's CPU should be utilized by the StoreGridprocess when clients are backing up on to this server. This is especially useful if this server is a desktop with a useractively using it. Setting it to Low will make the StoreGrid process do the backup slowly without taking much CPUso that it is least intrusive. If this is a dedicated Backup Server, then the CPU Utilization should be set to high sothat backups can happen fast.
Replication Status : This is used to know whether Replication is enabled for the Backup Server.
Replication Server : If Replication is enabled, this field displays the Replication Server Name. You can choose thereplication server from the "Server Management -> Replication Management -> Configure Replication" page. Youcan 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 needto authenticate against before replicating to this replication server.
Active Cluster Nodes (Applicable only when clustering enabled) : This specifies the active cluster nodesavailable in the StoreGrid Server(Backup/Replication) cluster.
Bandwidth Throttling:
In a Backup Server, StoreGrid's Bandwidth Throttling feature enables the user to limit the bandwidth usage for abackup schedule. Bandwidth can be configured at the backup server level, customer and client levels.
In a Replication Server, StoreGrid's Bandwidth Throttling feature enables the user to limit the bandwidth usage forreplication of a backup. Bandwidth can be configured at the backup server level from the 'Settings -> BandwidthThrottling Settings' page.
The user needs to specify the following fields:
Enable bandwidth throttling : Choose to enable or disable bandwidth throttling. If enabled, there areagain two options:
Throttle bandwidth always : Choose to enable bandwidth throttling every time the transfer of datatakes place.
Throttle bandwidth from : Specify the time period when bandwidth throttling is enabled.
Disable Bandwidth Throttling during Weekend - Choose this option to disable bandwidththrottling during weekend (Saturdays and Sundays). However, bandwidth throttling will be active onall the other days.
Throttle each backup to maximum of : Rate to limit bandwidth usage.
Allow clients to reset their web access password:
You can allow end users to reset their client Web Access Password by providing 'Forgot Password' link in the backupserver webconsole login page. You can allow or disable this option in this page.
Save Button : Once all the above options are set, click the "Save" button to save the server settings.
NOTE : The backup location, backup space etc. can be individually configured for each of the StoreGrid clients from theClient 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 upto 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 aboutthese 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.
Server MCAL Utilization
This table shows the MCALs added to the server and MCALs used by the StoreGrid clients.
Total MCALs Added in Server : The total number of MCAL licenses added to the Server.
MCALs utilized to date : The total number of MCALs consumed by the Server till date for the clients backing upto the Server.
Disk Space & Client Management
Overview
The Disk Space & Client Management page represents all the Resellers, Customers, Clients and Backups in an intuitive treeand thus allows the Administrator to manage the storage allocation and usage in a usable interface. It follows a dynamicuser interface using which the storage space allotted could be edited with the least amount of user operations. Thus theadministrator is able to get a bird's eye view of the storage allotted and used by Reseller/Customer/Client. You can alsopush client/backup setting changes from the backup server into the client machines.
How to get here in the StoreGrid Web Console? In the top menu, select: "Settings -> Disk Space & Client Management"
Disk Space & Client Management
This page lists the resellers, customers, clients and their backups in a tree format. It also shows the allotted and used diskspace for the server, resellers, customers and clients.
Clicking on the Resellers root node in the tree will display the List of Resellers.
Clicking on the Reseller node in the tree will display the List of Customers.
Clicking on a Customer node in the tree will display the List of Clients under the customer.
Clicking on a Client node in the tree will display the List of Backup Schedules under the client.
The table for the list of resellers/customers/clients is described below:
Resellers/Customer/Client Name : This is the name of the resellers/customer/client provided when theresellers/customer/client was added to the server.
Backup Location : This is the default location where the backup data will be stored. A new client connecting tothis backup server will by default store its backup data in this location. However, if the client or its parent customeris allocated a different storage location, its backup data will be stored in that location and not in this defaultlocation.
MCALs Allotted : This is the total number of MCALs allotted.
MCALs Used : This is the total number of MCALs used.
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, Reseller, Customer or Client to change the disk space allotted for them.
Click on the Change Client Side Settings icon against the client/backup to make changes to the client or backupsettings and to push those changes changes from the backup server into the client systems through CentralizedClient Management (CCM) feature.
Retention Schedule Configuration
Overview
StoreGrid cleans up the version files as per the retention policy configured for the backup in the client machine. Thesepolicies can be configured to clean up the version files either immediately or on a daily/ weekly/ monthly basis.
How to get here in the StoreGrid Web Console? In the top menu, select "Settings -> Retention Schedule Configuration"
Retention Schedule Configuration
The description of the table columns are given below.
Clean up immediately after completion of each backup schedule: Choose this option to schedule theconfigured retention policy immediately after the completion of each backup schedule.
Run Daily: Select a time of the day when the retention policy should run daily. This will schedule retentioneveryday at the configured time.
Run Weekly: Select a time and day of the week when the retention policy should run. StoreGrid will schedule theretention 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 willschedule 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 ->Reseller Management -> List of Reseller -> [Reseller Name] -> [Customer Name] -> [Client Name] -> Run RetentionCleanup (Action for particular Backup)" page.
Server Side Email Filtering
Overview
When Email Configuration is enabled, by default, reports are sent for all "conditions" that are applicable to the "modules"(backup/restore/delete/replication) selected. The Email Filtering feature allows you specify specific conditions for whichreports need to be emailed for the modules selected in "Email Configuration".
NOTE: "Configure Email Filtering" link is activated only after you've enabled your basic email configuration.
How to get here in the StoreGrid Web Console? In the top menu, select: "Settings->Email Settings->" and click on 'Email Filters' on the left hand side.
Server Side Filter Settings
There are two filters that can be applied here.
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 reportswhen backup/restore process fail or get completed partially. The available options are:
1. When Backup/Restore/Delete/Replication completes successfully (in Server).
2. When Backup/Restore/Delete/Replication fails (in Server).
3. When there are no new or modified files for replication.
4. When Backup is manually suspended (in Client).
5. When Backup/Restore is Partially Completed (in Server).
6. When a Backup schedule is missed.
Filter Email Reports by Customer/Client/Backup names
This filter allows you to email Backup, Restore, Delete & Replication Reports only for specific Backup Schedules, Clients orCustomers.
By default, email reports are sent for all Backups Schedules, Clients & Customers. Manually selecting some backupschedules / clients / customers and "Disabling Email Reports" for them will prevent reports associated with those frombeing emailed.
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 clientsautomatically 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 foravailable updates every one hour (when the client is not backing up/when there is no client activity). If an update isavailable 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 olderthan v2.3, then it should upgraded manually to v2.3 and upgrade to the later versions can then be done through thesoftware update feature.
How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Management -> Software Update -> Add Builds" 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 beprovided in exe/bin & xml file format respectively. These files should be copied to the client update location in the backupserver. 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 isstored and then click on 'List Build File(s)' button. This will list the updates available. You can then select the ones youwant 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 fileslocation. The update's StoreGrid_<NewVersion>.exe file and StoreGrid_<NewVersion>.xml files should be present inthe same location.
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 configuredupdate 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/deleteactivity at the client side.
3. If there exists any application for intrusion detection [such as Zone Alarm], StoreGrid application may not startautomatically after auto upgrading to the latest version. You need to manually start StoreGrid application.
List of added software updates
Overview
This section gives details of all the available updates for the clients. The list is based on the updates added to the server.
How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Management -> Software Update -> List Builds" page.
List of added software updates
StoreGrid will check for the new updates once every hour.
This page lists the available builds in this backup server. It includes the details of the builds like the size, version and buildnumber along with the installation mode details. Unwanted updates can be removed in this page by clicking delete linkagainst them.
Email Alert Settings
Overview
StoreGrid can be configured to send out Email alerts for the following conditions
1. Server, Reseller, Customer or a client is running out of backup space in the backup server2. MCAL shortage in the backup server3. ’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.
How to configure Email alerts by using the StoreGrid Web Console ? On the top menu, select: “Settings > Email Settings > Email Alert Settings”
Server / Reseller / Customer / Client "Used Space Alert"
StoreGrid can be configured to send Email alerts when the disk space available for storing the backup data in the backupserver is low. These alerts will be sent when there is a space shortage at the server, reseller, customer or at the clientlevel till the allotted space is increased or the backup data is deleted. Additionally, you can configure it to send Emailalerts when the backup space used up is nearing a certain percentage of the total space configured for the server,customers and clients. The alert Emails will be sent once every day till more space is allocated for the server, reseller,customer or the client.
Trial Client License Expiry Alert
StoreGrid by default offers a trial period of 30 days to its trial customers. The backup server can be configured to sendEmail alerts when the trial period expires for a customer or when the trial period is about to expire (optional). The alertEmails will be sent once every day till the client is migrated to a paid customer or deactivated.
MCAL License shortage Alert
StoreGrid can send Email alerts when the Server, Reseller or Customer (if certain number of MCALs are assigned to theReseller or Customer) is running out of MCALs. The shortage is calculated based on the number of MCALs that were usedup by the Server, Reseller or Customer during the current month.
Like for example, if the server has 30 MCALs left and if 50 MCALs were used up this month, then an alert will be sent thatis insufficient MCALs for the next month.
The alert Emails will be sent once every day till more MCALs are added to the server or for the Customer.
Limitations
1. If StoreGrid is stopped before the trial period expiry date of a client and restarted again after the expiry date, thentwo Email alerts (one alert that expiry date is nearing and the other that the trial period has expired) will be sent.
2. Emails are sent once every 24 hours and not immediately when the alert condition occurs.
Consolidated Customer Report
Overview
The Consolidated Customer Report is a cumulative report of all backups and restores that have run on the backup serverfor all the clients under the particular customer for the last one day, one week or one month. The report will be sent tothe customer in an Email automatically on a daily, weekly or monthly basis. Click here for sample of the report
The 'Email configuration for Consolidated Customer Report' page, has two options for configuring the the consolidatedreports to be sent.
1. Global Configuration - which configures consolidated report to be sent to a common email id list at the sameschedule for all the Customers.
2. Customer Level Configuration - this option can be used to configure different email IDs and schedules of theconsolidated report for particular Customers.
Global Configuration: This option gets a global recipients email id and a global schedule and configures all the currentavailable Customers with a global email id and schedule for generating the Consolidated Email Report for the customer.
Customer Level Configuration: This option lists all the customers and for each customer the Email IDs to which theconsolidated 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 Email addresses by clicking on the 'Generateand Email Instant Report' link against the particular customer.
The Consolidated Customer Report can also be enabled for a customer while adding a new customer in the 'Server Admin ->Reseller Management -> List of Resellers -> Add New Customer Action' for the particular Reseller page or by editing aparticular customer by going to the 'Server Admin -> Reseller Management -> List of Resellers -> Click on the ResellerName. This will list the customers under the reseller. Now, click on Edit Customer Details (Action for the particularCustomer) page.
How to get here in the StoreGrid Web Console? In the top menu, select: "Settings->Email Settings" and click on the "Consolidated Customer Report " .
The Consolidated Customer Report has the following sections:
1. Consolidated Customer Statistics across all Clients2. Consolidated Client Report3. Individual Client Backup Reports4. Individual Client Restore Reports
Consolidated Customer Statistics across all Clients
The Consolidated Customer statistics has the following details for a particular customer.
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 customer.
Allotted Disk Space : Total space allotted to the customer.
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 customer in thespecified period.
Number of incremental backups done: Total number of incremental backups done during the specified period.
Customer Status: Active/Deactivated state of the Customer.
% of files successfully restored : Success percentage of restore from the particular customer.
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 customer.
MCALs used during the period: Total MCALs consumed during the specified time period.
Consolidated Client Report
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 customer.
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.
MCALs used during the period : MCALs consumed during the period.
Num of new backups configured during the period : Number of new backups configured during the reportingtime.
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 Customer Reports
If a client is migrated from one customer to a new customer, then the client's old reports will also be migrated tothe new customer.
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
Daily report 11:57 PM All days of the week
Weekly report 11:57 PM Every Saturday of the week
Monthly report 11:57 PM Last day of the month
Delete Replication Server DataHow to get here in the StoreGrid Web Console?
In the top menu of Backup Server, select: "Server Management -> Delete Replication Server Data -> DeleteReplication 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 replicationdata from a particular backup server or delete the replication data of specific resellers, customers or specific clients.
This page shows a 'tree' listing of backup servers, customers and clients whose data is present in the Replication Server.Select the backup servers/resellers/customers/clients that need to be deleted.
Limitations
1. Replication data for backup server/reseller/customer/client cannot be deleted if restore, replication or data deletionis in progress for them in the replication server.
2. You cannot delete just a backup schedule under a client.
Replication Server Data Deletion ReportHow to get here in the StoreGrid Web Console?
In the top menu of Backup Server, select: "Reports -> Deleted Reports" page.
Replication Server Data Deletion Report
The report shows the list of backup servers, customers and clients whose data was deleted from the Replication Server.
Server Name - Backup Server of the deleted replication data.
Deleted Reseller/Customer/Client Name - Name of the reseller, customer or the client whose data wasdeleted.
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.
Replication Server Side Bandwidth Throttling
Overview
StoreGrid's Bandwidth Throttling feature enables the user to limit the maximum bandwidth used for replication of abackup. From this page you can configure Bandwidth Throttling for all replication jobs running from the backup serversthat are replicating to this replication server.
How to get here in the StoreGrid Web Console? In the top menu, select: "Settings->Bandwidth Throttling Settings" .
Replication Server Side Bandwidth Throttling
This page lists the backup servers that are replicating to this replication server. You can configure Bandwidth Throttlingspecifically for each backup server.
Backup Server: Name of the backup server replicating to this replication server.
Use Replication server's global configuration:
If the option Yes is selected, then the bandwidth throttling for the backup server will be set as per thereplication server's bandwidth throttling configuration.
If the option No is selected, then you can setup bandwidth throttling specific to the backup server byentering the following details:
Enable bandwidth throttling - 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 thespecified hours of the day.
Throttle each backup to maximum of - The rate to which bandwidth should be throttled.
Integrating StoreGrid with third party applications
Overview
StoreGrid can be configured to send notification to third party applications. Currently, StoreGrid supports integrating thenotifications (such as backup/restore/replication status and alerts) with ConnectWise and AutoTask applications. TheStoreGrid notifications will be created as service tickets in the above third party applications.
StoreGrid can also be integrated with WHMCS to push the invoices created in StoreGrid to the appropriate client account inWHMCS.
How to get here in the StoreGrid Web Console? On the top menu, select: Settings -> Third Party Apps configuration
Selecting Third Party Applications
In this page, you can choose either ConnectWise or AutoTask application to integrate StoreGrid notifications. To get moredetails on configuring StoreGrid with third party applications, refer the following help document pages:
ConnectWise
AutoTask
If you looking to push invoices generated in StoreGrid into WHMCS application, click on the link below:
Invoicing on WHMCS
Remote Server Management
Overview
In this page you can view the MCAL balance, Server health status, client backup status reports, MCAL Utilization Historyand Reseller/Customer invoice reports of other backup servers that you want to monitor. In this page you can also addMCAL for Remote servers. The backup servers have to be first added. For all the added servers you can then view thebackup status and invoice reports from this centralized web console.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Management -> Remote Server Management -> Remote Server Management".
Manage remote servers
This page has two tabs one to list the remote servers and another to add a new remote server.
List remote servers - This lists the remote servers that you want to manage from this backup server. Againsteach server listed here, the following actions are possible by click on the appropriate action icon:
MCAL Balance: It shows the Remote server's total MCAL balance.
Server Status: It shows the Remote server's health status.
Edit Remote Server Details: To edit the server's web console URL and its web console access details.
Client Backup Status Report: Clicking on this icon will show you the client backup status report from thatserver.
MCAL Utilization History: Clicking on this icon will show you the MCAL Utilization History from that server.
Add MCALs : Clicking on this icon you can add MCALs (Monthly Client Access Licenses) to the RemoteBackup Server.
Reseller/Customer Invoice Report: Clicking on this icon will show you the Reseller/Customer invoicereport from that server.
Delete Remote Server: To delete the added backup server.
Add remote server - This allows you to add backup servers that you want to manage. The following fields haveto be given to add a new backup server :
Webconsole URL
Protocol - This can be either http or https [Secured port].Server name - Backup server's FQDN name (if it is a remote server) or the hostname (if it is a localserver) at which the server is reachable.Port number - Web server port [6060] or secure webserver port [6061 - if HTTPS is used foraccessing the server's web console].
User name - Web console user name.
Password - Web console password.
Cluster Settings
Overview
The Cluster Settings page shows the details of the cluster configuration and the status of the nodes (server instances) inthe cluster.
How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Management -> Cluster Management -> Cluster Settings" page.
Cluster Settings
1. Cluster Name: The name of the cluster. The name of the cluster is specified during the installation of StoreGridin the nodes of the cluster and cannot be changed.
2. Nature of the Cluster: Specifies whether it is a Backup Server cluster or a Replication Server cluster.
3. Load Balancing Algorithm: This value specifies the algorithm used by the cluster to load balance the clientsand allocate them to the Server Nodes available in the cluster. Currently only 'Node Locked' load balancingalgorithm is supported.
4. Total Cluster Nodes: This value specifies the total number of server nodes that are added to this cluster.
5. Active Cluster Nodes: This value specifies the server nodes that are active and are addressingBackup/Restore/Replication requests in the cluster.
6. Inactive Cluster Nodes: This value specifies inactive server nodes or the number of server nodes which arecurrently down in the cluster.
7. Unregistered Cluster Nodes: This value specifies the server nodes which are added to the cluster, but arenot yet registered to the cluster.
8. Cluster Health Status: This value specifies the health status of the cluster.
List Cluster Nodes
Overview
This page lists the nodes (server instances) that are registered in the cluster and are currently live.
How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Management -> Cluster Management -> List of Cluster Nodes"
page.
List Cluster Nodes
Node Name: The public lookup name for connecting from the client for online backup.
Node StoreGrid ID: The unique StoreGrid ID of the Cluster Node to identify the StoreGrid Server instance.
External IP Address: The external IP address through which the client connect to the StoreGrid Server instance
Internal IP Address: The internal IP address in the LAN.
Registered On: The time at which the StoreGrid Server instance registered as the node within this cluster.
Health Updated On: The latest time at which the StoreGrid server instance updated the health and load of the ClusterNode.
Health Status: The health status of the Cluster Node.
Add Cluster Node
Overview
Through this feature a record of a new Server instance (Node) can be added to an existing StoreGrid Cluster. The recordincludes the external IP or DNS Lookup name and the backup port numbers at which the Server will be accepting requests.Later when StoreGrid is installed in that Server instance (identified by the StoreGrid ID), the StoreGrid will beautomatically be installed with the backup ports as specified here. If StoreGrid is installed in a Server without first addinga record for it in this page, then the StoreGrid on that server will be installed with the backup ports as specified during theinstallation.
It is recommended that the Server nodes of the cluster be first added here especially when the Server nodes are behind aNAT sharing the same external IP address or DNS lookup name. This is because, when they share the same external IPaddress/DNs lookup name, it is important that the Server nodes run on different backup ports so the NAT can redirect theincoming requests to the right server based on the backup port. This page helps you to make sure you specify unique(external IP+backup port) combination for each server node.
Note: You don't have to add the Server nodes in this page before installing StoreGrid in them if the requests come tothem from the internal network or when each server node is installed on a machine that is available at an unique externalIP.
How to get here in the StoreGrid Web Console? In the top menu, select "Server Management -> Cluster Management -> Add Cluster Node" page.
Add Cluster Node
When a new StoreGrid Server instance is started within a cluster, it registers itself with the StoreGrid Cluster using theCluster Node configuration specified here.
Here are the steps to add a Node to the Cluster
Step 1: Specifies the name of the Cluster. This is non-editable.
Step 2: Specify the StoreGrid ID or the node name of the cluster node.
Step 3: Specify the external IP address or DNS lookup name at which the requests coming to the Node will be sent to.Typically this is the external IP/DNS lookup name of the NAT that forwards the requests to the Node.
Step 4: Specify the non-SSL Backup Port at which StoreGrid installed in the node will be listening on.
Step 5: Specify the SSL Backup port at which StoreGrid installed in the node will be listening on.
Step 6: Save the Cluster Node configuration
Once added, the Cluster Node will be listed in the List Cluster Nodes page.
NOTE: It is recommended to have StoreGrid Servers register automatically to the StoreGrid cluster when runningStoreGrid clients and StoreGrid servers in a LAN environment.
Edit Cluster Node
Overview
Through this feature you can edit the existing cluster node with its basic configurations, the external DNS Lookup name orIP and the ports in which the server is listening for backup/restore/replication requests.
It is recommended that the Server StoreGrid instances are taken down before the Cluster node is edited, as this willenable fresh cluster node configuration when the StoreGrid instance is restarted.
How to get here in the StoreGrid Web Console? In the top menu, select "Server Management -> Cluster Management -> List Cluster Nodes" page, and then select the
‘Edit Cluster Node’ Action.
Edit Cluster Node
When a new StoreGrid Server instance is started within a cluster, it registers itself with the StoreGrid Cluster using thecluster node configuration specified while installing StoreGrid. This occurs when the relevant (with same StoreGrid ID)cluster node configuration is unavailable. Thus some of the cluster node's basic configuration might not be as intended.
This could be corrected by using the ‘Edit Cluster Node’ action.
Here are the steps to edit a Node to the Cluster
Step 1: Specifies the name of the Cluster. This is non-editable.
Step 2: Specifies the StoreGrid ID or the node name of the cluster node. This is non-editable.
Step 3: Specify the external IP address or DNS lookup name at which the requests coming to the Node will be sent to.Typically this is the external IP/DNS lookup name of the NAT that forwards the requests to the Node.
Step 4: Specify the non-SSL Backup Port at which StoreGrid installed in the node will be listening on.
Step 5: Specify the SSL Backup port at which StoreGrid installed in the node will be listening on.
Step 6: Save the Cluster Node configuration
Once edited, when the Cluster Node's StoreGrid instance starts the next time, it will get refreshed with the latest values.
Node Locked Configuration of the StoreGrid Cluster
Overview
When the StoreGrid cluster is configured to use Node Lock algorithm to balance the load of the clients to the Cluster, theReseller/Customer/Client can be configured to be locked to a particular Node ( StoreGrid Server instance) available withinthe StoreGrid cluster. Once locked, all the backups from the locked Reseller/Customer/Client will be sent to the lockedNode. Also, once the Reseller/Customer/Client is locked to a Node, it cannot be edited and locked to a different Node.
Using this page you can lock the Reseller/Customer/Client to a particular Node. This will enable you to scale up theStoreGrid Server deployment as and when more new Resellers/Customers sign up.
How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Management -> Cluster Management -> Manage Node Locked
Servers" page.
Node Locked Configuration
In this page you can configure Reseller/Customer/Client to be node locked to a particular Node. The following tabs areavailable in the Backup Server Cluster:
Node Locked Configuration of Reseller
Node Locked Configuration of Customer
Node Locked Configuration of Client
The Replication Server Cluster has only one tab.
Node Locked Configuration of Backup Server
Node Locked Configuration of Reseller
To node lock all customers/clients to a particular Node do the following :
Step 1: Select 'Manage Resellers' tab
Step 2: Select the Reseller which has to be node locked to the Node from the select box 'Reseller Name' in the left handside.
Step 3: Select the target Node under the select box named Node Name in the right hand side.
Step 4: Save the node locked configuration.
Node Locked Configuration of Customer
To node lock all clients to a particular Node do the following :
Step 1: Select 'Manage Customers' tab
Step 2: Select the Customer which has to be node locked to the Node from the select box 'Customer Name' in the lefthand side.
Step 3: Select the target Node under the select box named Node Name in the right hand side.
Step 4: Save the node locked configuration.
Node Locked Configuration of Client
To node lock particular client to a particular Node do the following :
Step 1: Select 'Manage Clients' tab
Step 2: Select the Client which has to be node locked to the Node from the select box 'Client Name' in the left handside.
Step 3: Select the target Node under the select box named Node Name in the right hand side.
Step 4: Save the node locked configuration.
Node Locked Configuration of Servers
This tab is only applicable when StoreGrid is run in Replication Server mode. To node lock particular Backup Server to aparticular Replication Server Node do the following :
Step 1: Select 'Manage Backup Servers' tab
Step 2: Select the Backup Server which has to be node locked to the Node from the select box 'Backup Server' in theleft hand side.
Step 3: Select the target Node under the select box named Node Name in the right hand side.
Step 4: Save the node locked configuration.
List Node Lock Configuration of Resellers, Customers and Clients
Overview
This page lists the node locked Resellers, Customers and Clients. This will be useful to locate the Node on which therespective Client's backup data is available.
How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Server Management -> Cluster Management -> List Node Locked Servers"
page.
List Node Lock Configuration
Backup Server Cluster
Click on the 'Node Locked Resellers' tab to list the Resellers and their respective Nodes to which they are locked.
Click on the 'Node Locked Customers' tab to list the Customers and their respective Nodes to which they are locked.
Click on the 'Node Locked Clients' tab to list the Clients and the respective Nodes to which they are locked.
The 'Status' column specifies the state of the Node Lock Configuration. If the status is in 'Locked' state, then the backupshave already been stored in the Node and they cannot be 're-locked' to another Node, unless the backups are deleted.
Replication Server Cluster
Click on the 'Node Locked Backup Servers' tab to list the Backup Servers and the respective Nodes to which they arelocked.
The 'Status' column specifies the state of the Node Lock Configuration. If the status is in 'Locked' state, then the data frombackup server nodes have already been replicated in the Node and they cannot be 're-locked' to another Node, unless thebackups are deleted.
Reseller Management in StoreGrid Server
Overview
This page is where reseller administration/management is done in the StoreGrid server. You can easily manage andorganize the various StoreGrid clients backing up to the server under particular customers. The customers can beorganized under the respective resellers and managed.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin-> Reseller Management"
Reseller Management in StoreGrid Server
In the Reseller Management page, the list of resellers is listed in a tree format on the left hand side and in a table formaton the right hand side. The reseller tree will have list of customers under each reseller node and the list of clients undereach customer node. The client node will list backup schedules configured in each StoreGrid client.
Clicking on the reseller's root node (The Server Node) in the tree will display the List Of Resellers in a table format on theright hand side.
Clicking on a Reseller node in the tree will display the List Of Customers under the Reseller in a table format on the righthand side.
Clicking on a Customer node in the tree will display the List Of Clients under the customer in a table format on the righthand side.
Clicking on a Client node in the tree will display the List Of Backup Schedules under the client in a table format on theright 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 resellers table on the right hand side is described below:
Add New Reseller : Clicking on this link will take you to the 'Add New reseller' page. You can add a new resellerin the StoreGrid Server from this page.
Reseller Name : This is the name of the reseller you provided when the reseller was added to the server.
MCALs Allotted - This is the number of MCALs allotted to the reseller.
Total MCALs used till date - This is the total number of MCALs used by the different clients of customers underthe reseller.
Allotted Space : This is the total space allotted to the reseller.
Used Space : The total disk space currently used by the reseller.
Actions : The icons under this column are links to various features to enable you to administer and manage yourresellers.
Enable / Disable Auto Authorization : Clicking on this icon will toggle between enabling and disablingauto authorization for this reseller. The auto authorization feature is described in more detail in the 'Create AReseller' section.
Activate/Deactivate : Clicking on this icon will toggle between activating and deactivating a reseller. If areseller is deactivated then no client from the reseller can backup to the server.
Edit Reseller : Clicking on this icon will take you to the 'Edit Reseller' page. You can edit all configurationsof a reseller from this page.
Add New Customer : Clicking on this icon will take you to the 'Add New Customer page'. You can add a
Customer to the Reseller.
Delete Reseller : Clicking on this icon will take you to the 'Delete Reseller' Page. The 'Default Reseller'available by default with StoreGrid installation cannot be deleted.
Invoice Configuration : Clicking on this icon will take you to the 'Reseller Invoice Configuration' Page.From this page you can enable or disable invoicing for the Reseller.
Invoice Report : Clicking on this icon will take you to the 'Reseller Invoice Report'. >From this page youcan view the generated Reseller invoice reports.
Deleted Customer/Client/Backup Report : Clicking on this icon will take you to the 'DeletedCustomer/Client/Backup Report', which will list in a table format the list of Customers, backup clients andthe data that has been deleted by the server administrator.
Some of the features like Configuring Trial Clients Settings, Seed Backup Migration, etc on the left bottom are describedbelow.
Trial Client Settings : Clicking on this link will take you to the 'Configuration Settings For Trial Clients' page. Youcan change various configurations like backup space to be allotted for the Trial Clients, Trial Period, Delete Periodetc from this page.
Client Migration : Clicking on this icon will take you to the 'Client Migration' page. Using this feature you canmigrate the clients from one reseller to another reseller.
Seed Backup Migration : Clicking on this icon will take you to the 'Seed Backup Migration' page. Using thisfeature you can migrate the backup data from one server to another server and then having the clients do thesubsequent backups (incremental) to the new server.
Replication Server Migration : Clicking on this icon will take you to the 'Replication Server Migration' page. Usingthis feature you can migrate the backup data from backup server to the replication server and thus seeding thereplication server with the initial replicated data. This will enable only incremental replications happening from thebackup server to the replication server.
Add a New Reseller
Overview
To manage the backups in the backup server better, you can group the client machines listed in the backup server undertheir respective customers and the customers can then again be grouped under the respective reseller account. You canenable or disable reseller level management in the backup server during StoreGrid installation.
If reseller management is enabled, then StoreGrid comes preset with a "Default Reseller". You can add additional reselleraccounts from this page. New clients by default get added under the Default Customer under Default Reseller, which canthen be moved to an appropriate Customer account under another Reseller.
A Reseller account can have multiple Customers under it. You need to add the Reseller to the server first before addingthe relevant Customer and their clients under the Reseller. Clients can easily be shifted from one Reseller's Customer toanother.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management" and click on the "Add New Reseller" link.
Reseller Information
At the bare minimum, you need to give the Reseller a name and an Email address. Other Reseller information like Address,City, Phone, Fax and Notes is primarily to help you keep the records organized.
Basic Configuration
Backup Location - Storage location for the backup data for this reseller.
Restrict Usage Space To - Total space allocated for all the customers under this reseller.
Space Utilization Snapshot for server:
Total Backup Space on Server - Disk space configured in the Server for the backup data.
Total Backup Space Allotted to Reseller(s) - The sum of the disk space allotted to the different Resellersin the Server.
Free Backup Space available - Free space available in the server which is not allocated to any Reselleri.e., it is the difference between total backup space in the server and the total backup space allotted toresellers.
The link “Edit Disk Space Allotted for Server/Reseller/Customer/Client” takes the user to Settings -> Disk Space &Client Management. This lists the Resellers, Customers and their clients with their MCAL and Space details. Thespace settings can be edited here.
Automatically add clients when they connect to the server [Enable/Disable] - If you want the clients underthis Reseller to backup without adding the client names ( StoreGrid IDs) manually in the server, then keep the AutoAuthorization enabled for this Reseller. The Clients will be automatically created in the server when the clientsbackup to this server for the first time. Clients will be by default added under Default Customer in Default Reseller.
Email Reports (Enable/Disable) - You can enable Email Reports for particular Reseller to receive email reportsof backup/restore/delete/replication modules of the clients present under this particular Reseller to the emailaddress given in the 'Email' option.
Receive Backup Status Email Reports (Enable/Disable) - You can enable Backup Status Email Reports for theReseller account. When it is enabled, the Reseller will receive a status report of the backups from all the clients
present under the particular Reseller to the email address specified in the Reseller account. The Reseller will receivethis email report only if Client backup status email report is enabled. This email report would be generated based onthe filter options set in the Client backup status email report.
Web Access [Enable/Disable]: You can enable web access to your reseller by which the Reseller can log into theserver web console and manage the backups from their Customers.
User Name: The user name with which the Reseller can log into this server's web console.
Password: The password to be used to login to the server's web console.
Confirm Password: This field is used to confirm that the password is entered correctly in the passwordfield.
Theme Settings:
When this option is enabled, the Reseller and the Reseller's customers logging into the backup server willsee the web console in the Reseller's specific theme as set here. If Theme Settings is not enabled, then theweb console will have the same look and feel for all Resellers and Customers. Obviously this option isavailable only when Web Access is enabled for the Reseller. By default this option is disabled.
Once enabled, click on 'Click here to configure themes' link to configure the Reseller Theme. The following UIelements can be configured:
Product Name: Reseller can choose a different product name that they want to expose to theircustomersCompany Name: Reseller's company name can be mentioned here.Page Title: This is title that will appear on the web console pages. This can be customized as perthe Reseller's choice.Website URL: This URL could be the Reseller's Web Site URL to which the Reseller wants to directhis customers to when they click on the links under the Help menuColors: The Menu background and Font Colors can be changed. As you change the color, the previewon the top will automatically reflect the changes.Images: Reseller can choose their own Product and Company logos that would be displayed whenthey or their customers log into the backup server web console.
Advanced Configuration
Do you wish to restrict this reseller to use fixed number of MCALs ?: By enabling the Automatic allocationoption, StoreGrid server automatically allots MCALs as required for this reseller. This is the recommended option.However, if you wish, you can restrict the number of MCALs to be allotted for the reseller. If/when this limit isreached no more backups will be permitted till you manually increase the MCALs for this reseller.
Activated [Yes/No]: Only active Resellers' clients are allowed to backup to the server. By default a Reseller is'Activated' when created. If you prefer to start this Reseller in a deactivated state, you can do so. You can preventall the clients under the Reseller from backing up to the server by simply deactivating the Reseller at any time.
Set bandwidth throttling specifically for this reseller - StoreGrid's Bandwidth Throttling feature enables theuser to limit the bandwidth usage for a backup schedule. Bandwidth can be configured at the backup server,reseller, customer and client levels.
If the option No [Use server's global bandwidth throttling configuration] is selected, then thebandwidth throttling for the Reseller will be set as per the backup server's configuration.
If the option Yes is selected, then you can setup bandwidth throttling specific to this reseller by entering thefollowing details:
Enable bandwidth throttling for this reseller - 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 thespecified hours of the day.
Disable Bandwidth Throttling during Weekend - Choose this option to disable bandwidth
throttling during weekend (Saturdays and Sundays). However, bandwidth throttling will be active onall the other days.
Throttle each backup to maximum of - The rate to which bandwidth should be throttled.
Save Button - After configuring the options specified above, click on the "Save" button to save the configuration. Oncethe Reseller settings has been saved, a confirm alert message will be displayed to send the account details to the Resellerin an Email. Click "OK" if you would like to view and send the Email. This confirmation alert will be displayed, only if youhave enabled Email feature in the 'Settings->Email Settings'.
Edit Reseller in StoreGrid Server
Overview
From this page, you can edit the reseller information and settings you provided while adding the reseller to your StoreGridserver. You can edit the following information and settings about the reseller. Once you click the Update button the newvalues will override all the old values.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Edit Reseller"
icon in the action column of this reseller row.
Edit Personal Information
Reseller Name - A non-editable field displaying the name of this Reseller.
Email, Address, City - These are all editable fields and you can edit all these details, which you have provided whileadding the reseller.
Phone, Fax and Notes - Phone number, Fax and Notes provided while adding this reseller, can be edited if there is achange.
Basic Configuration
Backup Location - Storage location for the backup data for this reseller.
Used Space - Total space occupied by the backup data in the given location.
Restrict Usage Space To - Total space allocated for all the customers under this reseller.
Space Utilization Snapshot for server:
Total Backup Space on Server - Disk space configured in the Server for the backup data.
Total Backup Space allotted to resellers - The sum of the disk space allotted to the different Resellers inthe Server.
Free Backup Space available - Free space available in the server which is not allocated to any Reselleri.e., it is the difference between total backup space in the server and the total backup space allotted toresellers.
The link “Edit Disk Space Allocated for Server/Reseller/Customer/Client” takes the user to Settings -> Disk Space &Client Management. This lists the resellers, customers, their clients and their backup schedules with their MCAL andSpace details. The space settings can be edited here.
Automatically add clients when they connect to the server [Enable/Disable] - If you want the clients underthis Reseller to backup without adding the client names ( StoreGrid IDs) manually in the server, then keep the AutoAuthorization enabled for this Reseller. The Clients will be automatically created in the server when the clientsbackup to this server for the first time. Clients will be by default added under Default Customer in Default Reseller.
Email Reports (Enable/Disable) - You can enable Email Reports for particular Reseller to receive email reportsof backup/restore/delete/replication modules of the clients present under this particular Reseller to the emailaddress given in the 'Email' option.
Receive Backup Status Email Reports (Enable/Disable) - You can enable Backup Status Email Reports for theReseller account. When it is enabled, the Reseller will receive a status report of the backups from all the clients
present under the particular Reseller to the email address specified in the Reseller account. The Reseller will receivethis email report only if Client backup status email report is enabled. This email report would be generated based onthe filter options set in the Client backup status email report.
Web Access [Enable/Disable] - You can enable web access to your reseller by which the Reseller can log intothe server web console and manage the backups from their Customers.
User Name: The user name with which the Reseller can log into this server's web console.
Password: The password to be used to login to the server's web console.
Confirm Password: This field is used to confirm that the password is entered correctly in the passwordfield.
Theme Settings:
When this option is enabled, the Reseller and the Reseller's customers logging into the backup server willsee the web console in the Reseller's specific theme as set here. If Theme Settings is not enabled, then theweb console will have the same look and feel for all Resellers and Customers. Obviously this option isavailable only when Web Access is enabled for the Reseller. By default this option is disabled.
Once enabled, click on 'Click here to configure themes' link to configure the Reseller Theme. The following UIelements can be configured:
Product Name: Reseller can choose a different product name that they want to expose to theircustomersCompany Name: Reseller's company name can be mentioned here.Page Title: This is title that will appear on the web console pages. This can be customized as perthe Reseller's choice.Website URL: This URL could be the Reseller's Web Site URL to which the Reseller wants to directhis customers to when they click on the links under the Help menuColors: The Menu background and Font Colors can be changed. As you change the color, the previewon the top will automatically reflect the changes.Images: Reseller can choose their own Product and Company logos that would be displayed whenthey or their customers log into the backup server web console.
Advanced Configuration
MCALs Allotted - Auto/Number of MCALs allotted while adding the Reseller. This field can be edited for theresellers other than the 'Default Reseller'.
MCALs Utilization Snapshot for server [ Server(Cluster) ]
Total MCALs added to the Server - This shows the total number of MCALs added to the Server.
Total MCALs already used by or allocated to Resellers - This shows the total number of MCALs alreadyused up in the Server (by all clients).
MCALs available in the Server - This shows the number of MCALs available in Server.
Activated [Yes/No] - Only activated Resellers' clients are allowed to backup to the server. By default all Resellersstart off 'Activated'. If you prefer to start this Reseller in a deactivated state, you can do so. Of course, you canprevent a Reseller (and hence all the clients under the Reseller) from backing up to the server by simplydeactivating the Reseller at any time.
Set bandwidth throttling specifically for this reseller - StoreGrid's Bandwidth Throttling feature enables theuser to limit the bandwidth usage for a backup schedule. Bandwidth can be configured at the backup server,reseller, customer and client levels.
If the option No [Use server's global bandwidth throttling configuration] is selected, then thebandwidth throttling for the Reseller will be set as per the backup server's configuration.
If the option Yes is selected, then you can setup bandwidth throttling specific to this reseller by entering thefollowing details:
Enable bandwidth throttling for this reseller - 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 thespecified hours of the day.
Disable Bandwidth Throttling during Weekend - Choose this option to disable bandwidththrottling during weekend (Saturdays and Sundays). However, bandwidth throttling will be active onall the other days.
Throttle each backup to maximum of - The rate to which bandwidth should be throttled.
Save Button - After configuring the options specified above, click on the "Save" button to save the configuration. Oncethe Reseller settings has been saved, a confirm alert message will be displayed to send the account details to the Resellerin an Email. Click "OK" if you would like to view and send the Email. This confirmation alert will be displayed, only if youhave enabled Email feature in the 'Settings->Email Settings' page.
To assign/modify an invoice to this Reseller please click here - Use this option to configure Invoicesettings for the Reseller. You will be redirected to another page to configure invoice settings. Before clicking this link,ensure that you have saved the changes made in the current page.
Migrating Clients
Overview
StoreGrid by default groups the clients (under auto authorization mode only) when they first backup to the Server underthe Default Reseller's Default Customer. After the initial backup is complete, you can move the client under the specificReseller and its customer.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management" and click on the "Client Migration" icon on the left
hand side.
Migrating Clients
StoreGrid supports seamless migration of a client grouped under one customer to another customer. You can even move aclient from one Reseller's customer to another Reseller's customer. Please note that client migration doesn't move thebackup data from its present backup location.
The steps to follow for moving a client from one customer to another are given below:
Step 1: Select the Reseller name (from which the clients are to be migrated) from the select box named 'Rseller Name'on the left hand side.(i.e Migrate from). When you are logged on as a user with Reseller access, this option is pre-selectedas the Reseller associated with the user.
Step 2: Select the Customer Name from the select box named 'Customer Name' on the left hand side
Step 3: All the Clients under the customer(selected in the previous step) will be listed. Note that by default all theclients' will be checked. (i.e all the clients under this customer will be migrated).
You can also select particularly the clients you wish to migrate. Check the clients, you wish to migrate.
Step 4: Select the reseller name (to which the clients are to be migrated) from the select box named 'Reseller Name' onthe right hand side.(i.e Migrate to). When you are logged on as a user with Reseller access, this option is pre-selected asthe Reseller associated with the user.
Step 5: Select the customer to which the clients to be migrated from the select box named 'Customer Name' on the righthand side.(i.e Migrate to). Incase if you wish to migrate to a new customer, first add the customer by clicking on "ServerAdmin->Reseller Management->Add New Customer" Action icon for the particular Reseller. Then proceed with the abovesteps.
Step 6: Press the migrate button to initiate the migration. The migration should finish in a few seconds. Note if any ofthe clients' are active, (Backup, Restore, Delete, Replication is in progress) that particular client cannot be migrated.
Limitations
1. If Clustering is enabled in the backup server, then you will not be able to migrate a client if it is (or the client'sparent Customer or its parent reseller) node locked to one cluster node and the Customer to which the client is tobe migrated is node locked to a different cluster node.
Configuration Settings for Trial Clients
Overview
A new client machine backing up to a backup server is under 'Trial Mode' by default. You can set the variousconfigurations for Trial Clients from this page.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management" and click on the "Trial Client Settings" Icon on the left
hand side.
Trial Client Settings
Space allocation for trial clientsBy default, the disk space for the trial clients are configured to be AUTO allocated - i.e., the client can continue touse up the disk space in the backup server as long as the space limit for the customer under which it is listeddoesn't exceed. Instead, you can also limit the Trial client's disk space usage by setting a max space limitation inthis page.
Trial PeriodYou can select the trial Period (max up to 30 days) in 'number of days' for the Trial Clients. After this Trial Period,the clients will be deactivated in the Server. The 'Trial Period' is calculated from the time the client first connects tothe StoreGrid Server. By default, the trial period is 30 days.
Automatically delete trial clients at the end of trial periodYou can select the number of days after which 'Trial Clients' and their respective data will be automatically deletedin the Server. Note that the delete period is calculated from the end of the trial period, i.e., after the trial iscompleted. By default, this is 90 days.
Default trial client activation statusBy default, trial clients automatically start in 'activated mode'. By exercising this option, you can choose to starttrial clients in a deactivated state. You will need to manually activate the trial clients before they can start backingup.
Troubleshooting Tips
When the Trial Clients could not backup
Cause 1: Customer /Client Used space exceeds allotted space.
Solution : Check for the space allotted for the Trial Clients or their Customer . Increase/Decrease space as needed forthe Trial Client or their Customer .
Cause 2 : Client is DeActivated.
Solution : Check for the Activate/DeActivate Status in this configuration; ensure trial clients start off 'activated' or thatyou manually activate them as required
Cause 3 : Trial Period expired (for the client)
Solution : Check the Trial Period configured in the above settings. If you wish the client to be active again, increasethe Trial Period. Thereafter, change the 'Deactivated' status of the Client to 'Activate'. Now the client can connect to theBackup Server.
Limitations
1. Change in 'Backup Space' will effect only new clients (i.e. from the time the change is implemented) and will haveno (retrospective) effect on existing clients.
Seed Backup Migration
Overview
Seed Backup 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 theexternal drive can then be physically moved to the remote backup server’s environment to migrate the data into thebackup server. After the data migration and after performing the server side and client side Seed Backup 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->Reseller Management" and click on the "Seed Backup Migration" icon on the
left hand side.
For Client: In the top menu, select: "Backup->Seed Backup Migration".
Seed Backup Migration
1. Configure a backup schedule in the StoreGrid client system. Log into client’s StoreGrid web console page and select'Backup -> Backup Schedule' from the top menu.
2. Select the ‘Backup Type’ as ‘Same Machine’ in Step 3 and enter the external drive location for the ‘Local BackupLocation’. 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 BackupMigration'.
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. (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.0/later backup server using MySQL Server as the backend database, then theStoreGrid database 'sgbackup.db' file will not be available in the backup location since v3.0/later backup server usesMySQL as the backend database. You need to export the metadata from MySQL to SQLite database by followingthe below steps :
Open a command prompt and go the < StoreGrid_HOME> folder.Execute the following command (the below commands are case sensitive): 'bin\StoreGrid.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 youwish to migrate a particular client (or) backup, then you can execute the above command as follows :
bin\StoreGrid.exe ExportToSQLiteDatabase <Client_Name>bin\StoreGrid.exe ExportToSQLiteDatabase <Client_Name> <Backup_Name>
6. Disconnect the external drive from the client machine and connect the external device to the remote backup server.
7. Copy the client's data (Z:\backup\1) from the external device to some temporary location in the drive where youare planning to store the backup data in the remote backup server. Like for example, if your storage device is theE: drive, then copy the data to say “E:\LTOR”. You don’t have to copy the data to the temporary location and youcan migrate the data directly from the external drive itself. However, the migration might take a little longer tocomplete, based on the speed of the external drive.
8. Go to the remote backup server’s web console "Server Admin-> Reseller Management -> Seed Backup Migration(Icon)" page. Enter the location of the client's data followed by the 1/ directory. For example, if you have copiedthe client's data from the external drive to the temporary E:\LTOR location in the backup server, enter location asE:/LTOR/1/ in this page. If you have not copied the data to a temporary location, enter the location of the externaldrive, like for example Z:/backup/1. After entering the path, click on the "Submit Location" button.
9. The client name will be displayed. Select the client. If you are doing the data migration from this client for the firsttime, enter the target customer under which the client is to be migrated and the location where the backup data isto be stored. Click the "Migrate" button.
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.
11. Go to “Backup -> 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 incrementalbackups directly to the remote backup server. Provide the New Backup Server Name and confirm that the backupdata of the selected schedules has already been moved to the new backup server and that you have run the SeedBackup 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 listto 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' tocontinue with the incremental backups directly to the remote backup server and provide the New BackupServer Name.
In the table listing the backup schedules, select the backup schedule(s) whose data has been moved to thenew backup server. You can select all the backup schedules by checking the checkbox against the "AvailableBackups" column name. Confirm that the backup data of the selected schedules has already been moved tothe new backup server and that you have run the Seed Backup Migration module in the remote backupserver (confirm this from the check box).
Choose the option 'Make this client machine backup locally (same machine) from now on' to makethe client machine start backing up locally to itself. You can use this option to do 'Seed Backup Migration ofAdditional Fullbackup data'. After selecting this option, you need to provide the Local Backup Location forthe selected backup schedule(s).
In the table listing the backup schedules, select the backup schedule(s) to start backing up locally to thesame machine. You can select all the backup schedules by checking the checkbox against the "AvailableBackups" column name. Confirm that you have opted to run Additional Full Backup locally in this machine tothe specified backup location. (confirm this from the check box).
Click the Migrate button to complete migration.
12. To confirm that the migration has been successful, try running an incremental backup. If the incremental backupruns fine, the migration is successful and you can delete the backup of the db file that you created in step 10above. If the client starts taking a full backup, then suspend the backup, replace the sgprp.db file with its backupthat you created in step 10 and check the server migration steps again.
Seed Backup 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 customer 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 takenafter the current client migration started and its migration progress.
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 -> ResellerManagement -> Seed Backup Migration(Icon)" page. 'Client_Name' is the client name of the backups which is to bemigrated.
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 2.2.1 or later version of backup server.
Solution : "Seed Backup Migration" can be done only with StoreGrid 2.2.1 or later version of backup server clientsalone.
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 -> Reseller Management -> Seed Backup Migration(Icon)" page.
Solution : Move the data to a location where StoreGrid can access the data without any permission problem or changethe 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 targetlocation for Read/Write access.
Cause 1: StoreGrid does not have the read permission for the location entered in the remote backup server webconsole "Server Admin -> Reseller Management -> Seed Backup Migration(Icon)" page.
Solution : Move the data to a location where StoreGrid can access the data without any permission problem or changethe 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 clientsmigration page that comes after clicking the "Submit Location" button in "Seed Backup Migration" page.
Solution : Provide enough permission for the location you have given for the client or choose any other location whereStoreGrid has the read and write permissions.
Limitations
1. StoreGrid version of the client should be the same as the Backup Server while performing server side Seed BackupMigration.
2. When StoreGrid is stopped during Server side "Seed Backup Migration", it cannot be resumed later from where ithas been left. It has to be run afresh again.
3. Server side "Seed Backup Migration" report cannot be seen once you leave the web console page.4. When there isn’t enough Space in the remote backup server, migration will still proceed to completion by
automatically taking the necessary space.5. File version migration is not supported. Only full backups and incremental backups can be migrated.
Replication Server Migration
Overview
Replication Server Migration is a feature to avoid bandwidth usage and reduce the replication time needed for a full backupover Internet. Using this feature, you can transfer the backup data from the backup server into a local external drive andthen 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->Reseller Management" and click on the "Replication Server Migration" .
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 machinesare not backing up. To make sure the client machines (whose backup data you are trying migrate) don’t during themigration, 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 incrementalbackup data of this full backup.
2. If the local backup server is in v3.0 or above version, the StoreGrid database 'sgbackup.db' file will not be availablein the backup location since v3.0 (and above version) backup server uses MySQL as the backend database. Youneed 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 (below commands for case sensitive): 'bin\StoreGrid.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 youwish to migrate a particular client (or) backup, then you can execute the above command as follows :
bin\StoreGrid.exe ExportToSQLiteDatabase <Client_Name>bin\StoreGrid.exe ExportToSQLiteDatabase <Client_Name> <Backup_Name>
3. Disable replication in the Backup Server from the ‘Server Management > Replication Management > ConfigureReplication’ page.
4. Connect an external device to the local backup server.
5. 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.
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. Youcan leave it in the external drive itself and migrate directly from the external drive but the migration might take alittle longer.
8. In the top menu in the remote replication server StoreGrid web console, go to ‘Server Admin->ResellerManagement’ and click on the ‘Replication Server Migration’.
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.
11. Choose the clients which are to be migrated and select their respective customers. If a client is already replicatingunder a particular customer, then the ‘Migrate to Customer’ and the ‘New Location’ fields will not be selectable forthat client.
12. If the target customer is not listed, choose Default Customer as the target customer and migrate the client to it.Once the replication runs from the backup server (after doing Replication Server Migration) to the replication serverfor the migrated clients, the customer under which the client is listed in the backup server will be automaticallycreated in the Replication Server and the client will be moved from Default Customer to the particular customerunder 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.
15. Enable replication status in the backup server by going to ‘Server Management > 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 oneof the clients by clicking the ‘Replicate Now’ icon in the ‘Server Admin > Reseller Management-> List ofReseller > Reseller > Customer > Client > List of Backup Schedules’ page in the backup server’s web console. Itshould not replicate anything or just replicate the additional backup data that came into the backup server sincereplication migration.
Note: You cannot migrate two clients with the same StoreGrid ID existing in two different backup servers into onereplication 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 ->Reseller Management -> Replication Server Migration" page. 'Client_Name' is the client name of the backups which is tobe 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 webconsole "Server Admin -> Reseller Management -> Replication Server Migration " page.
Solution : Provide enough permission for the location you have given for the client or choose any other location whereStoreGrid 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 cannotbe migrated.
2. You cannot migrate two clients with the same StoreGrid ID existing in two different backup servers into onereplication server. The migration of the second client will fail.
3. If StoreGrid is stopped during the Server side "Replication Server Migration" progress, migration cannot continuefrom the place where it stopped.
4. No Replication Server migration report is available in remote Replication Server.5. 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.6. File version migration is not supported.7. Backup data copied from one Replication Server cannot be migrated to another Replication Server.
Delete Reseller
Overview
This action is used for deleting reseller accounts from the Server which are no longer needed.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers". Click on the "Delete Reseller" icon
in the action column of the Reseller row.
Delete Reseller
This action provides the user with choice to retain the customers, clients and the backup data under the reseller or removeall customers, clients and the backup data under the reseller.
If you click the option 'Delete Reseller but retain customers, clients and data under the reseller', only the reseller will bedeleted and the customers, clients and their data will be moved to 'Default Reseller' in Backup Server.
If you click the option 'Delete Reseller, customers, clients and data under the reseller', then the reseller, the customers,the clients and their backup data will be moved to SGTrash folder in the storage location and will not be permanentlydeleted. If the data is to be removed permanently, the user can manually delete it from the SGTrash folder.
NOTE: Default Reseller cannot be deleted.
Please note that if any one of the reseller's backup is active, then you cannot delete the reseller. When a reseller is notdeleted, you can see the reason why the reseller could not be deleted in Server Server Side Deleted Backup Reportspresent in the reseller row.
Cancel button will take you to the 'Server Admin -> Reseller Management' page.
Customer Management in StoreGrid ServerHow to get here in the StoreGrid Web Console?
In the top menu, select: "Server Admin-> Reseller Management->List of Resellers" and click on the particularReseller.
This page lists the Customers available under a particular reseller in a tree format in the left hand side and in a tableformat in the right hand side. The Customer tree will have list of clients under each Customer node and the list of backupschedules configured under each client node.
Clicking on the Customers root node in the tree will display the List Of Customers in a table format on the right hand side.
Clicking on a Customer node in the tree will display the List Of Clients under the customer in a table format on the righthand side.
Clicking on a Client node in the tree will display the List Of Backup Schedules under the client in a table format on theright 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 customers table on the right hand side is described below:
Add New Customer - Clicking on this link will take you to the 'Add New Customer' page. You can add a newcustomer in the StoreGrid Server from this page.
Customer Name - This is the name of the customer you provided when the customer was added to the server. EachCustomer name has to be unique, even across different Reseller accounts (if Reseller management is enabled)
MCALs Allotted - This is the number of MCALs allotted to the Customer. If the clients under a Customer consume allof the MCALs allotted to the Customer, then none of the Clients can backup even though there may be MCALs available inthe backup server. It is not required to allocate MCALs to the Customer. If MCALs are not allocated to the Customer, thenthe backup server will automatically use the MCALs available in the server pool. You only need to allocate MCALs to aCustomer if you want to restrict only certain number of clients to backup.
Total MCALs used till date - This is the total number of MCALs used by the different client machines under thisCustomer.
Allotted Space - This is the total backup disk space allotted to the customer.
Used Space - The total disk space currently used by the customer.
Actions - The icons under this column are links to various features to enable you to administer and manage yourcustomers.
Enable / Disable Auto Authorization - Clicking on this icon will toggle between enabling and disabling autoauthorization for this customer. The auto authorization feature is described in more detail in the Add New Customersection.
Activate/Deactivate - Clicking on this icon will toggle between activating and deactivating a customer. If acustomer is deactivated then no client from the customer can backup to the server.
Edit Customer - Clicking on this icon will take you to the Edit Customer page. You can edit all configurations of acustomer 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 thecustomer and configure it.
Proceed to Delete Customer - Clicking on this icon will take you to the Delete Customer Page.
Edit Replication - Clicking on this icon will take you to configure Customer Replication Scheduling. Note that youcan configure different scheduling options and replication servers for different customers. By default all customers willbe replicated to the globally configured, replication configuration from the Replication Management page.
Invoice Configuration - Clicking on this icon will take you to the Customer Invoice Configuration Page. From thispage you can enable or disable invoicing for the customer.
Invoice Report - Clicking on this icon will take you to the Customer Invoice Report. From this page you can viewthe generated customer invoice reports.
Deleted Client/Backup Report - Clicking on this icon will take you to the "Deleted Backup Report", which willlist in a table format the list of backup clients and the data that has been deleted by the server administrator.
Some of the features like Configuring Trial Clients Settings, Seed Backup Migration etc on the left bottom are describedbelow.
Trial Client Settings - Clicking on this link will take you to the 'Configuration Settings For Trial Clients' page. You canchange various configurations like backup space to be allotted for the Trial Clients, Trial Period, Delete Period etc from thispage.
Client Migration - Clicking on this icon will take you to the 'Client Migration' page. Using this feature you can migrate thetrial clients to the paid Customer and also the clients from one Customer to another Customer.
Seed Backup Migration - Clicking on this icon will take you to the 'Seed Backup Migration' page. Using this feature youcan migrate the backup data from one server to another server and then having the clients do the subsequent backups(incremental) to the new server.
Cloud Backup Server ( StoreGrid Backup Server deployed in Amazon EC2):
The following fields will not be available in a Cloud Backup server installation:
1. Edit Replication
2. Seed Backup Migration
Add a New Customer
Overview
While you have the option of retaining all your clients under the 'Default Customer', you may find it more manageable tosegregate your customers. - especially since you can allocate storage space and configure other settings on a 'customer-wise' basis. Also, you can allow various Resellers' to create their own Customers and organize the clients.
A customer can have multiple PCs, desktops/laptops/servers (clients) which need to be backed up. You need to add thecustomer to the reseller first before adding the clients under the customer. Clients can easily be shifted from onecustomer to another.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Add New
Customer" Action Icon for the particular Reseller.
Customer Information
At the bare minimum, you need to give the customer a name and an Email address. Other customer information likeAddress, City, Phone, Fax and Notes is primarily to help you keep the records organized.
Basic Configuration
Backup Location : The storage location for the backup data for this customer.
Restrict Usage Space To : Total space allocated for all the clients under this customer.
Space Utilization Snapshot for Reseller:
Disk space allotted for the Reseller - Total disk space allotted for the reseller.
Total Backup Space allotted to customer(s) - The sum of the disk space allotted to different customersunder this reseller.
Free Backup Space available - Free space available in the reseller which is not allocated to any customeri.e., it is the difference between total backup space in the reseller and the total backup space allotted tocustomers.
The link “Edit Disk Space Allocated for Server/Reseller/Customer/Client” takes the user to Settings -> Disk Space &Client Management. This lists the resellers, customers, their clients and their backup schedules with their MCAL andSpace details. The space settings can be edited here.
Automatically add clients when they connect to the server [Enable/Disable] - If you want the clients underthis customer to backup without adding the client names ( StoreGrid IDs) manually in the server, then keep theAuto Authorization enabled for this customer. The Clients will be automatically created in the server when theclients backup to this server for the first time. Clients will be by default added under Default Customer.
Email Reports (Enable/Disable) - You can enable Email Reports for particular Reseller/Customer to receiveemail reports of backup/restore/delete/replication modules of the clients present under this particularReseller/Customer to the email address given in the 'Email' option.
Receive Backup Status Email Reports (Enable/Disable) - You can enable Backup Status Email Reports for theCustomer account. When it is enabled, the Customer will receive a status report of the backups from all the clientspresent under the particular Customer to the email address specified in the Customer account. The Customer willreceive this email report only if Client backup status email report is enabled. This email report would be generatedbased on the filter options set in the Client backup status email report.
Web Access [Enable/Disable] - You can enable web access to your Customer by which the Customer can loginto the server web console and manage the backups from their clients.
User Name: The user name with which the Customer can log into this server's web console.
Password: The password to be used to login to the server's web console.
Confirm Password: This field is used to confirm that the password is entered correctly in the passwordfield.
Advanced Configuration
Do you wish to restrict this customer to use fixed number of MCALs ?: By enabling the Automatic allocationoption, StoreGrid server automatically allots MCALs required for this customer. This is the recommended modusoperandi! However, if you wish, you can restrict the number of MCALs to be allotted for the customer. If/when thislimit is reached no more backups will be permitted till you manually increase the MCALs for this customer.
MCALs Utilization Snapshot for Reseller:
MCALs available in the global pool - This is the total number of available/unutilized MCALs in theStoreGrid backup server's global pool.
Activated [Yes/No]: Only clients from 'active' Customers are allowed to backup to the server. By default allcustomers start off 'Activated'. If you prefer to start this customer in a deactivated state, you can do so. Of course,you can prevent a customer (and hence all the clients under the customer) from backing up to the server by simplydeactivating the customer at any time.
Maximum client limit: Using this option you can limit the number of clients that can be added under thiscustomer.
Set bandwidth throttling specifically for this customer: StoreGrid's Bandwidth Throttling feature provides away to limit the bandwidth usage for a backup schedule. Bandwidth Throttling can be configured at the backupserver, reseller, customer and client levels. Once applied, the settings will be applicable to each backup scheduleunder this Customer.
If the option No [Use Reseller's or Server's global bandwidth throttling configuration] is selected,then the bandwidth throttling for the Customer will be set as per the Reseller's configuration. If there is nospecific setting for the Reseller, then the Customer uses the backup server's configuration.
If the option Yes is selected, then you can setup bandwidth throttling specific to this Customer by enteringthe following details:
Enable bandwidth throttling for this customer - Choose to enable or disable bandwidththrottling.
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 thespecified hours of the day.
Disable Bandwidth Throttling during Weekend - Choose this option to disable bandwidththrottling during weekend (Saturdays and Sundays). However, bandwidth throttling will be active onall the other days.
Throttle each backup to maximum of - The rate to which bandwidth should be throttled.
Send a consolidated report across all clients: You can choose to send a ‘Consolidated Customer Report’ of allclients under this customer. Specify the Email ID of the recipient(s) and the frequency of generation of theconsolidated customer report (Daily/Weekly/Monthly).
Save Button - After configuring the options specified above, click on the "Save" button to save the configuration. Oncethe customer settings has been saved, a confirm alert message will be displayed to send the account details to thecustomer in an Email. Click "OK" if you would like to view and send the Email. This confirmation alert will be displayed,only if you have enabled Email feature in the 'Settings->Email Settings' page.
Edit Customer in StoreGrid Server
Overview
From this page, you can edit the customer information and settings you provided while adding the customer to yourStoreGrid server. You can edit the following information and settings about the customer. Once you click the Updatebutton the new values will override all the old values.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers " and click on the " Reseller
Name". Now you will see the list of customers under the reseller. Click on the "Edit Customer" icon in the action columnof this customer row.
Customer Pass Key - Users can use this Passkey to register their client machines under this Customer account from theclient machine web console before the client machines can start backing up to the backup server.
Edit Personal Information
Customer Name - A non-editable field displaying the name of this Customer.
Email, Address, City - These are all editable fields and you can edit all these details, which you have provided whileadding the customer.
Phone, Fax and Notes - Phone number, Fax and Notes provided while adding this customer, can be edited if there is achange.
Basic Configuration
Backup Location - The storage location for the backup data for this customer.
Used Space - Total space occupied by the backup data in the given location.
Restrict usage space to - Total space allocated for all the clients under this customer.
Space Utilization Snapshot for Reseller:
Disk space allotted for the Reseller - Total disk space allotted for the reseller.
Total Backup Space allotted to customers - The sum of the disk space allotted to the differentCustomers under this reseller.
Free Backup Space available - Free space available in the reseller which is not allocated to any Customeri.e., it is the difference between total backup space in the reseller and the total backup space allotted tocustomers.
The link “Edit Disk Space Allocated for Server/Reseller/Customer/Client” takes the user to Settings -> Disk Space &Client Management. This lists the resellers, customers, their clients and their backup schedules with their MCAL andSpace details. The space settings can be edited here.
Automatically add clients when they connect to the server [Enable/Disable] - If you want the clients underthis customer to backup without adding the client names ( StoreGrid IDs) manually in the server, then keep theAuto Authorization enabled for this customer. Note that if you disable Auto Authorization for a customer (say, ABCInc.) and if ABC Inc. has 5 MCALs allocated to it, then you can allow clients from ABC Inc. to backup until the 5MCALs are used. The Clients will be automatically created in the server when the clients backup to this server forthe first time. Note that only StoreGrid clients tagged with the customer name ABC Inc. (entered duringinstallation) will be allowed to backup to this server under the customer ABC Inc. Clients without a valid customer
name would come under the Default Reseller's Default Customer.
Email Reports (Enable/Disable) - You can enable Email Reports for particular Customer to receive email reportsof backup/restore/delete/replication modules of the clients present under this particular Customer to the emailaddress given in the 'Email' option.
Receive Backup Status Email Reports (Enable/Disable) - You can enable Backup Status Email Reports for theCustomer account. When it is enabled, the Customer will receive a status report of the backups from all the clientspresent under the particular Customer to the email address specified in the Customer account. The Customer willreceive this email report only if Client backup status email report is enabled. This email report would be generatedbased on the filter options set in the Client backup status email report.
Web Portal Access[Enable/Disable] : You can enable web-portal access to your customer by which thecustomer can log into the web console of the backup server and manage the backups of the client machines listedunder that customer. If you would like to enable the web access for the customer, then you need to specify a username and a password which the customer will use to log into the backup server web console.
User Name : The user name that the customer will use to log into the backup server web console tomanage the backups of that customer.
Password : The password that the customer will use to log into the backup server web console to managethe backups of that customer.
Confirm Password : This field is used to confirm that the password is entered correctly in the passwordfield.
Advanced Configuration
MCALs Allotted - Auto/Number of MCALs allotted while adding the Customer. This field can be edited for theCustomers other than the 'Default Customer'.
MCALs Utilization Snapshot for Reseller:
MCALs available in the global pool - This is the total number of available/unutilized MCALs in theStoreGrid backup server's global pool.
Activated [Yes/No] - Only activated Customers' clients are allowed to backup to the server. By default allCustomers start off 'Activated'. If you prefer to start this Customer in a deactivated state, you can do so. Ofcourse, you can prevent a Customer (and hence all the clients under the Customer) from backing up to the serverby simply deactivating the Customer at any time.
Maximum client limit - Using this option you can limit the number of clients that can be added under thiscustomer.
Set bandwidth throttling specifically for this customer - StoreGrid's Bandwidth Throttling feature provides away to limit the bandwidth usage for a backup schedule. Bandwidth Throttling can be configured at the backupserver, reseller, customer and client levels. Once applied, the settings will be applicable to each backup scheduleunder this Customer.
If the option No [Use Reseller's or Server's global bandwidth throttling configuration] is selected,then the bandwidth throttling for the Customer will be set as per the Reseller's configuration. If there is nospecific setting for the Reseller, then the Customer uses the backup server's configuration.
If the option Yes is selected, then you can setup bandwidth throttling specific to this Customer by enteringthe following details:
Enable bandwidth throttling for this customer - Choose to enable or disable bandwidththrottling.
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 thespecified hours of the day.
Disable Bandwidth Throttling during Weekend - Choose this option to disable bandwidth
throttling during weekend (Saturdays and Sundays). However, bandwidth throttling will be active onall the other days.
Throttle each backup to maximum of - The rate to which bandwidth should be throttled.
Send a consolidated report across all clients: You can choose to send a ‘Consolidated Customer Report’ of allclients under this customer. Specify the Email ID of the recipient(s) and the frequency of generation of theconsolidated customer report (Daily/Weekly/Monthly).[Disabled : If Global configuration is enabled in settings->consolidated customer report page].
Save Button - After configuring the options specified above, click on the "Save" button to save the configuration. Oncethe Customer settings has been saved, a confirm alert message will be displayed to send the account details to theCustomer in an Email. Click "OK" if you would like to view and send the Email. This confirmation alert will be displayed,only if you have enabled Email feature in the 'Settings->Email Settings' page.
To assign/modify an invoice to this Customer please click here - Use this option to configure Invoicesettings for the Customer. You will be redirected to another page to configure invoice settings. Before clicking this link,ensure that you have saved the changes made in the current page.
Delete Customer
Overview
From this page, you can either delete a customer alone and retain clients with their data or delete a customerpermanently from the backup server along with the clients and their backup data.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers". Click on the particular reseller.
This will list the customers under this reseller. Click on the "Delete Customer" icon in the action column of the Customerrow.
Delete Customer
If you click the option 'Delete Customer but retain clients and data under the customer', only the customer will be deletedand the clients and their data will be moved to 'Default Customer' in Backup Server.
If you click the option 'Delete customer, clients and data under the customer', then the customer and the clients with theirbackup data will be moved to SGTrash folder in the storage location and will not be permanently deleted. If the data is tobe removed permanently, the user can manually delete it from the SGTrash folder.
NOTE: Default Customer cannot be deleted.
Please note that if any one of the customer's backup is active, then you cannot delete the customer. When a customer isnot deleted, you can see the reason why the customer could not be deleted in Server Server Side Deleted Backup Reportspresent in the customer row.
Cancel button will take you to the 'List of Customers' page.
License Management
Overview
In StoreGrid, all the client licensing are handled in the Backup Server. StoreGrid server uses a unit called MCAL to managethe licensing of clients backing up to the StoreGrid Server.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> License Management"
What is an MCAL ?
MCAL is short form for 'Monthly Client Access License'. MCAL ensures you can purchase as licenses as you need and payas you go for licensing your clients using StoreGrid.
MCALs were introduced to allow easier license management, especially when a client changes his operating system (fromDesktop OS to Server OS or vice versa) or discontinues service for one of his installations. The backup server holds a'bank' of MCALs and as clients connect to the backup server they use up MCALs from the server's bank - on a monthlybasis. MCALs ensure that as long as your server has enough MCALs on it, you needn't spend time and effort worryingabout client licensing.
MCALs Utilization History
From this page you can re-trace the MCALs utilization history for the Clients backing up to the StoreGrid Backup Server.
Add MCALs
From this page you can add/update your MCAL credits to the StoreGrid server.
Added MCALs Details
From this page you can view the list of MCALs added to this Server.
MCAL Utilization History
Overview
This page provides MCAL utilization details of different clients connecting to the backup server. MCAL Utilization History canbe exported into a comma delimited (CSV) file by clicking on the 'CSV' link at the top of the MCAL Utilization History page.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> License Management" and click on the "MCAL Utilization History" icon on
the left side.
MCAL Utilization History
The MCAL Utilization History page provides details about the StoreGrid MCAL usage in the Backup Server and ReplicationServer.
Client MCAL Utilization History
Select the Client tab to get the client MCAL utilization history view. This tab provides MCAL utilization details of differentclients connecting to the backup server. MCAL Utilization History can be exported into a comma delimited (CSV) file byclicking on the 'CSV' link at the top of the MCAL Utilization History page. In a Replication Server, this also shows fromwhich backup server the client is replicated from.
The client MCAL Utilization History has the following details:
Total MCALs Added in Server : Total MCALs added in the server
Total MCALs utilized : Total MCALs utilized in the server.
Date : Date on which the MCAL was utilized by the client.
Client Name : Name of the client.
MCALs Used : MCALs used by the client for its OS type / plugin usage for the particular month.
Server Name : The StoreGrid ID of the backup server which has replicated this client to the Replication Server.This column appears only in StoreGrid running in Replication Server mode.
Server MCAL Balance : MCALs left in the backup server.
Customer Name : Name of the Customer under which the client is grouped.
Customer MCAL Balance : Number of MCALs left in the Customer to which the client belongs to. This is applicableonly for those Customers that have MCALs specifically allocated.
License Type : License type of the client [Desktop/Server OS license].
Plugins Used : Plugins used by the client or No Plugin.
Total MCALs used by the client till date : Total MCALs used by the client till date.
Filter Options
The filter options can be used to filter the view of the MCAL utilization history to view specific entries with respect to:
Client Name : To view the MCAL utilization history of the client alone.
Server Name : To view the MCAL utilization history of this backup server alone. This option is applicable only in
Replication Server.
Add MCALs
Overview
MCALs are monthly client licensing units that are added in the backup server and the client machines consume the MCALson monthly from the backup server as they backup to the server. From this page you can add/update your MCAL credits inthe StoreGrid backup server.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> License Management" and click on the "Add MCALs" icon on the left side.
Add MCALs
For a StoreGrid backup server to accept backup from clients (other than trial clients), the backup server has to be addedwith MCAL credits. You can add as many MCAL key to a server as required. The number of MCAL credits in a server will becumulative of all MCAL added to the server. MCAL keys are based on the following:
User Name: This is the unique name provided while generating the MCAL key. Normally, this name is auto-generated based on the customer/service provider with backup server name added to make the key unique.
MCAL Key: Enter the 16-digit MCAL Key as provided in the Email. It is suggested to copy and paste the MCALdetails from the MCAL license to avoid any typo errors.
Number of MCALs: The number of MCAL licenses supported by the key is embedded in the key itself. This valuehas to be correctly entered while adding the MCAL key to the backup server.
Verification Code: This is a random code used while generating the MCAL key. This random code has to matchwhat is embedded in the MCAL key.
Added MCALs Details
Overview
This page provides the details of the MCALs added to the backup server.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> License Management" and click on the "Added MCALs Details" icon on the
left side.
Added MCALs Details
Added MCALs Details has the following fields:
Date : Date on which the MCAL license key was added in the server.
User Name : This is the user name under which the license key was generated.
MCALs Added : Number of MCALs added in the MCAL license key.
Added In Server : This shows the StoreGrid ID of the server where the MCAL license was added. This will appearonly in StoreGrid running as Replication Server to show the MCALs added in the Backup Servers replicating to theReplication Server.
If a MCAL license key that was added in the two different backup servers replicating to the Replication Server, thefollowing warning message will appear.
Alert: Some MCAL license keys seem to have been added in more than one servers. Please note that a license keyshould be added in only one server. Please contact Support.
NOTE : MCAL license keys are generated for one particular StoreGrid instance and should not be used acrossmultiple StoreGrid instances.
Replication Management
Overview
This where all aspects related to Replication Management are configured. From here, Replication can be scheduled, theBackup Server can be recovered (in case of a disaster).
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Management-> Replication Management"
Replication Management
Configure Replication - Clicking on this icon will take you to the "Replication Configuration" page. You canconfigure 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 canrecover the backup server from the Replication Server in case of any catastrophe affecting the backup serverthereby necessitating a Disaster Recovery operation.
Server Disaster Recovery Reports - This icon will only show up if the server was previously restored from thereplication server. Clicking on this will take you to the "Server Disaster Recovery Reports" page where you can viewreports for all backups that were recovered from the Replication Server.
Authentication with Replication Server - Clicking on this icon will let you authorize your backup server with thereplication server. If the replication server is configured to serve replication requests from authorized backupservers with a password, you can use the password and authorize your backup server for replication.
Test connectivity to Replication Server - With this feature you can check the connectivity from the backupserver to the replication server. It also checks the various settings in the replication server to identify if the backupserver can replicate to the replication server.
Replication Configuration
Overview
StoreGrid supports replicating a backup server to a replication server. Replicating the backup data in the backup server isdone to create redundant copies of the backup data. The replication configuration UI page is used to configure andschedule 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 Management->Replication Management". Click on 'Configure Replication'.
Replication Configuration
Step 1
Enable Replication : By checking or un-checking the checkbox, you can enable or disable replication for the BackupServer.
Replication Server : From the choice box, choose the replication server to which this backup server's data should bereplicated.
If you choose 's3-amazon-webservice' to replicate, the Backup Server data will be replicated to the Amazon S3WebService. Please provide the following additional details to replicate to Amazon S3
1. AWS Access Key: The Amazon WebServices Access key to authorize the Server to replicate to S3.
2. AWS Secret Key: The Amazon WebServices Secret key to authorize the Server to replicate to S3.
3. Bucket Name: The Bucket name under which all the backup data has to be replicated.
4. Enable Reduced Redundancy Storage: Reduced Redundancy Storage (RRS) is Amazon's new 99.99%data durability storage infrastructure in which S3 gives you the option to tradeoff redundancy for cost over a givenyear. For example, if you store 10,000 objects using the RRS option, you can on average expect to incur an annualloss of a single object. By default it is disabled and data is stored in standard S3 which provides higher(99.999999999%) durability. When RRS is enabled, your charges for storage in S3 will be lower but at a lower datareliability.
Step 2
Set CPU Utilization - This is used to specify how this server’s CPU should be utilized by the StoreGrid process when thebackup server replicates the backed up data to the Replication Server. Setting it to low will make the StoreGrid process dothe replication slowly without taking much CPU so that it is least intrusive. But replication will take longer to complete iflow 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 bescheduled every 5 minutes whenever replication is incomplete because of a network error, server crash etc. Note that thisoption is enabled by default.
Step 3
Replicate Immediately After Receiving a Backup: Choosing this option will schedule the replication after the client'sbackup schedule is completed.
1. Changing the schedule type from any other option to 'Replicate Immediately After Receiving a Backup' will causethe immediate scheduling of all the backups.
2. Disabling and then enabling replication with 'Replicate Immediately After Receiving a Backup' will cause theimmediate scheduling of all the backups.
Replicate Every Few Hours: Choose the hours/minutes to schedule replication periodically. If StoreGrid is restarted inthe interim, the replication will be scheduled as soon as StoreGrid starts. Thereafter, StoreGrid will automaticallyreschedule 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 10.30 am, and if you have setreplication to run every 1 hour, StoreGrid will first run the replication schedule at 8 am (i.e as soon as the backup serverstarts receiving the data for the first time) and the next replication will be scheduled at 11.30 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 1hr 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 torun 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 thebackups.
Replicate Daily: Choose the time at which the backup should run daily. All the backup schedules will be replicatedeveryday 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 bereplicated 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 'Settings->Add/Delete Peer' UI page. Then select the ReplicationServer 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 thethread count) number of backup schedules to be replicated at the same time, then the replication schedules will be putin a queue and scheduled for replication one after the other. Hence all the schedules will not be replicatedsimultaneously at the particular time provided.
Solution : Open the SGConfiguration.conf file located in < StoreGrid Home/conf> directory. Edit the Replication Threadcount tag to desired number.
Note: By default Replication Thread count is -1, which will allow infinite number of backups to be replicatedsimultaneously.For fresh installation of StoreGrid (since version 2.2.1) Thread count will be 5 in Linux machines and -1 in Windowsmachines.
Limitations
The global Replication configuration in StoreGrid is applicable to all the resellers, the customers under the reseller,the clients under a customer and the backup schedules under the client. StoreGrid additionally supports configuringreplication at the customer level which is then applicable to the clients under the customer. StoreGrid does notsupport separate replication configuration at the client and the backup schedule level.
Server Disaster Recovery
Overview
This feature helps you recover the Backup Server and its data from the Replication Server. If your Backup Server had beenreplicating to a StoreGrid Replication Server, then, in case of any crash/disaster at your Backup Server, the StoreGrid Backup Servercan be rebuilt from the Replication Server. You can either recover the backup data and the Customers/clients configurations OR youcould recover only the Customer configurations and copy the backup data separately from the Replication Server. After copying thebackup data from the replication server, you would need to do a "Seed Backup Migration".
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Management -> Replication Management -> Server Disaster Recovery"
Server Disaster Recovery
To provide redundancy for the backup data, the StoreGrid backup server can be configured to replicate all its backup data to areplication server. If the backup server crashes, the backup server can be restored back by retrieving the replicated data from thereplication 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 disasterrecovery
2. Install StoreGrid in the backup server with the same StoreGrid ID as before.
3. Go to the Server Management -> Replication Management -> Server Disaster Recovery page. This opens the ServerDisaster Recovery screen which has the following fields:
To perform disaster recovery from the replication server :
a. Select replication server: Select the replication server name from the drop down list.
b. Select data to recover.
i. Customer & Client configurations and Client data:
This recovers the Client and customer configurations along with the clients' backup data.
ii. Customer & Client configurations Only:
This recovers only the backup server configurations like customer details, disk space allotted, MCALs addedetc. The backup data is not recovered. This option is helpful when the amount of data is huge and restoring itfrom 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 andthen shipped to the backup server location. The data from the external drive can then be attached to thebackup server through the server side Seed Backup Migration. This is explained in steps 6, 7 and 8 in theSeed Backup Migration help document.
c. Next specify if you are restoring the data afresh to the backup server or just continuing from the previous interruptionof the recovery process.
d. Parallel Threads: Number of simultaneous backups that should be recovered from the replication server. By default, itis set to 5.
To perform disaster recovery from Amazon S3 :
a. Select replication server: Select the "s3-amazon-webservice" option from the drop down list and enter thefollowing details :
1. AWS Access Key: The Amazon WebServices Access key to authorize the Server to replicate to S3.
2. AWS Secret Key: The Amazon WebServices Secret key to authorize the Server to replicate to S3.
3. Bucket Name: The Bucket name under which all the backup data has to be replicated.
b. Select data to recover.
i. Customer & Client configurations and Client data:
This recovers the Client and customer configurations along with the clients' backup data.
c. Next specify "restore afresh" option to restore the data afresh to the backup server.
d. Parallel Threads: Number of simultaneous backups that should be recovered from the replication server. By default, itis set to 5.
4. Click on the Recover data from the replication server to start the recovery process.
5. If the first option recover Customer & Client configurations and Client data was selected, then the progress chart will beas shown below:
After completion of recovery process, click Server Disaster Recovery Reports through the menu Server Management ->Replication Management.
Clicking the menu gives the details of the data recovered from the Replication server.
If the second option Customer and Client configurations only was selected in step 4b above, then only the backup serverdetails are recovered.
Once the customer & client configurations are recovered from the replication server, you can manually ship the backup datafrom 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 backupsfrom the clients.
6. Enable replication in the restored backup server by going through Server Management -> Replication Management pagein 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.
Server Disaster Recovery Reports
Overview
This report provides information about the number of customers, clients, backups and files recovered from the replicationserver. 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 Management -> Replication Management -> Server Disaster Recovery Reports" (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 filesretrieved, and the number of files skipped (if any). 'Data' represents the actual backed up files and 'Meta-Data' representsthe configuration files.
Success Rate : Measure of the restore operation's success, this is based on the number of total files in thereplication 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 serverdisaster 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 thereplication server and then try restoring the data from the replication server.
Authentication of Backup Server with Replication Server
Overview
You can prevent unauthorized backup server from replicating to your replication server by protecting the replication serverwith a password. Once a password is set in the replication server, backup servers will not be able to replicate to thereplication 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 Management -> 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 froma Replication Server. However, if a password is set in the Replication Server, then the backup server should firstauthenticate with the replication server with that password before it can start replicating its backup data to the replicationserver
You can configure the password in the Replication Server from the "Settings -> Server Settings" page. The Backup Servercan then authenticate with the Replication Server through the "Server Management -> Replication Management ->Authenticate Backup Server for Replication" page with the same password which was configured in the Replication Server
List of Invoicing Plans
Overview
This page lists all invoice Plans that were previously added in the Backup server [from the menu 'Server Admin -> InvoiceManagement -> Add New Invoice Plan']. In StoreGrid, you can create multiple invoice plans and assign any invoice plan toany Reseller/Customer. You can assign an invoice plan to a Reseller from the UI page "Server Admin -> ResellerManagement -> Invoice Configuration (Action)" and for Customer from "Server Admin -> Reseller Management -> List ofResellers -> [Reseller Name] -> Invoice Configuration (Action)".
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> Invoice Management -> List of Invoicing Plans"
List of Invoicing Plans
Plan Name - The Name of the Invoice Plan.
Plan Type - The type of the Invoice Plan (Uniform Discount [depending on volume of data] / Fixed price for eachslab / Sliding scale).
Invoice Calculation Type - Type of Invoice calculation (based on Used Space/Uncompressed Size/ TransferredData Size).
Frequency - The frequency of Invoice Generation [Each Saturday / Last Day of Each Month / Last day of eachquarter].
Used space - Unit for Storage Space Used [MB/GB]
Currency -The currency of the invoice amount.
Minimum Weekly/Monthly/Quarterly charge per client -Minimum [Weekly/Monthly/Quarterly] amount payablefor each of the client machines backing up to the backup server during the invoice period.
Tax - Surcharge is charged on the total sum of the clients' usage charges as per the invoice plan and the additionalper client charges.
Per MCAL usage charge This is the amount payable on the MCAL usage charged as per the invoice plan. This isapplicable only when the invoice is generated on a monthly or quarterly basis.
The slab details are shown with their Minimum Value, Maximum Value, Rate per MB/GB ("For Every" column) value.
The details of the plan can be edited using the 'Edit Plan' action.
The plan can be deleted using the "Delete Plan" action.
Delete Invoice Plan
To delete the invoice Plan, click the 'Delete Plan' icon for the particular plan. Please note that the 'Default Invoice Plan'cannot be deleted (but can be edited). Also, an invoice plan can not be deleted if the plan is currently in use. If acustomer is assigned an invoice plan and if that plan is deleted, then the 'Default Invoice Plan' will be applied for thatcustomer and further invoices for the customer will be generated as per the "'Default Invoice Plan".
Note - An alert message will be displayed while editing/deleting the invoice plan which is assigned to one of theReseller/Customer.
Troubleshooting Tips
There is no Delete Action for a plan which is currently in use.
Cause 1: Some invoice reports may have been generated for customers using the plan. In that case the invoice plancannot be deleted.
Solution : Assign another plan to the customer and then you can delete the plan or edit the Invoice plan as required.
Add/Edit Invoice Plan
Overview
In this page, you can add new Invoice plans or edit an existing one. Once the Invoice plan is added, then the plan can beused for the Resellers/Customers in the server to generate Invoice. If the Customer is configured with the Invoice plan(using the menu 'Server Admin -> Customer Management'), then Invoice Reports for the Customer will be generatedbased on the rules specified in the plan.
How to get here in the StoreGrid Web Console? In the top menu, to create a new Invoice plan, select: "Server Admin -> Invoice Management -> Add New Invoice
Plan. And to edit, select: "Server Admin -> Invoice Management -> List of Invoicing Plans" and click on the edit icon ofthe Invoice plan that you want to edit.
Add/Edit Invoice Plan
Name this Plan - Name of the Invoice plan.
Select Plan Type - Type of the plan. There are three types of plans.
i. Uniform Discount [Depending of Volume of Data] - The storage space utilized by the Reseller/Customerduring the billing period is first calculated. Depending on what slab it falls under, a flat rate per GB or MB isapplied for the total amount of storage consumed. Obviously, this flat rate is lower for larger amounts ofdata backed up.
ii. Fixed Price for each slab - The storage space utilized by the Reseller/Customer during the billing period isfirst calculated. Depending on what slab it falls under, a flat rate is charged for the total amount of storageconsumed. Within a slab, the amount charged is the same. eg. For a slab: 5-10 GB - $20/month, thecustomer will be charged $20 for the month irrespective of whether he uses 6,7 or 9 GB!
iii. Sliding Scale - The storage space utilized by the Reseller/Customer during the billing period is firstcalculated. Slab rates are successively applied (as opposed to the Uniform Discount plan). For example, aCustomer using 12 GB in a month may be charged $ 3/GB for the first 5 GB, $2/GB for the next 4GB, and $1/GB for the last 3 GB.
Generate Invoice Based On - This field is to generate the Invoice based on any of the following factors:
i. Used Space - Invoice is calculated on the disk space used by the backup data on the server.
ii. Uncompressed Size - Invoice is calculated on the compressed size of the data that was backed up. Like forexample, if a file of 1MB in size was compressed to 0.1MB and then backed up, the used space will be0.1MB and the uncompressed size will be 1MB.
iii. Transferred Data Size - Invoice is calculated based on the size of the backup data uploaded/downloadedto/from the server during backup and restore. This will be close to bandwidth used.
Generate Invoice On - This field when to generate the Invoice for the Resellers/Customers.
If it is selected as "Each Saturday", then invoice reports will be generated at each week on Saturday.If it is selected as "Last day of each Month", then invoice reports will be generated at the end of every monthon 30th or the 31st.If it is selected as "Last Day of each Quarter", then invoice reports will be generated at the end of March, June,September and December months.
Measure Data In combo box is used to specify the unit for the disk spaces used in the slab details. You canspecify this to MB (or) GB.
Currency combo box is used to set the currency of amount for the Invoice generated.
Minimum Weekly/Monthly/Quarterly charge per client Minimum [Weekly/Monthly/Quarterly] amount payablefor each of the client machines backing up to the backup server during the invoice period. This is a fixed amountper client that gets added to the invoice on top of the usage charges.
Tax Surcharge payable for the client usage charged as per the invoice plan.
Per MCAL usage charge This is the amount payable on the MCAL usage charged as per the invoice plan. This isapplicable only when the invoice is generated on a monthly or quarterly basis.
The Slab details are used to specify the details about the pricing based on the used spaces. You can specify asmany slabs as required and their corresponding rate (pricing).
The "From" is used to specify the minimum disk space used for the current slab. The "From" value should be zerofor the 1st slab.
The "To" is used to specify the maximum disk space used for the current slab. If the maximum value is specified as"-1", it means there is no maximum value. The slab is applicable for any used disk space above the minimumvalue.
The "Charge" is used to specify the rate (pricing) for the current slab.
The "Per" field is used to specify the unit disk space for which the rate (pricing) is applied. The "Per" field isapplicable for 'Uniform Discount [Depending of Volume of Data]' and 'Sliding Scale' plan types. There is no "Per"fields for 'Sliding Scale' plan type.
For example, if the slabs are configured as follows :
From To Rate Per0 50 6 1
50 500 5 2
500 -1 1 3
and if the weighted average used space for the Customer is 200 MB, then
For 'Uniform Discount' plan type, since 200 MB falls under 2nd slab, rate = (200 / 2) * $5 = $500
For 'Sliding scale' plan type,
For 1st 50 MB, rate = (50 / 1) * 6$ = 300$For next 150 MB, rate = (150 / 2) * 5$ = 375$Total = 675$
For 'Fixed Price for each slab', the "Per" field is zero. Since 200 MB falls under 2nd slab, rate = 5$.
Consider you have 2 clients under a Customer, Minimum Weekly/Monthly/Quarterly charge per client is 10$ and theTax is 2%, then
Minimum Weekly/Monthly/Quarterly charge = 2 * 10 = 20$
For 'Uniform Discount' plan type, Invoice Amount = 500$ + 20$ + 10$(500 * (2 / 100 )) = 530$
For 'Sliding scale' plan type, Invoice Amount = 675$ + 20$ + 13.5$(675 * (2 / 100 )) = 708.5$
For 'Fixed Price for each slab', Invoice Amount = 5$ + 20$ + 0.1$(5*(2/100)) = 25.1$
Note:
Prorating is applied to Resellers/Customers who start backing up in the middle of a month. The MinimumWeekly/Monthly/Quarterly charge calculation is based on the number of days the Client has backed up duringthe partial month. For example, if a client starts backing up from July 20th, then the MinimumWeekly/Monthly/Quarterly per client charge will be prorated for 10 days. The Invoice Amount is calculatedon the basis of the number of days the Reseller/Customer has been backing up during the partial month. Forexample, if a Customer starts backing up from July 20th, then the Invoice Amount will be prorated for 10days.
Prorate is not applicable for invoice generation based on Transferred Data Size.
Troubleshooting Tips
Invoice plan already exists with the same name.
Cause 1: This error occurs if a Invoice plan already exists with the same name.
Solution : Please try adding Invoice plan with a different name.
Limitations
1. For "Fixed Price for each slab", the rate can not be in decreasing order.2. The invoice details based on transferred data size are not available after recovering the backup server using
Server Disaster Recovery feature.3. Invoice report may show incorrect per client charge value for the clients which are migrated to another
customer.4. Invoice amount may be little high, when creating invoice report for customer for their deleted period.5. The client details will not be available in the invoice reports for the deleted clients after migrating it from
v2.5.5 to v3.2.6. If a client is migrated from one customer to another customer, the bandwidth usage for the source customer
may become incorrect.
Reseller/Customer Invoice Reports
Overview
This page is used to view Invoice reports of all Resellers/Customers - at one place. You can, of course, view Invoices forindividual Resellers from the 'Server Admin -> Reseller Management -> List of Resellers -> View Invoices (Action for theparticular Reseller)' menu and for Customer from the 'Server Admin -> Reseller Management -> List of Resellers ->[Reseller Name] -> View Invoices (Action for the particular Customer)' menu.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> Invoice Management -> View Reseller/Customer Invoice Reports".
Invoice Report Summary
The Reseller/Customer Invoice reports list is listed in reverse chronological order, i.e., last invoice first. The following fieldsare listed:
Invoice Report Icons - The icons in this column represent the basis for Invoice report.
Used Space - Pie chartUncompressed Size - Bar chart with arrowTransferred Data Size - Up and down arrows
Reseller/Customer Name - For whom the Invoice was generated. The icon before the Reseller / Customer nameindicates the Invoice calculation type.
Billing Date - The date on which Invoice was generated.
Plan Name - Plan used for invoice generation.
Billing Period - The days (period) for which the invoice is calculated.
Invoice Amount - The Invoice Amount for the generated Invoice.
Currency - The currency of the Invoice amount.
View - This action (click on icon) is to view the detailed Invoice Report.
Fields in the Invoice Report
Reseller/Customer Name - The name of the Reseller/Customer for whom the Invoice was generated.
Billing Date - The date on which the Invoice Report was generated.
Billing Period - The days (period) on which the Invoice is based.
Email - Email address of the Reseller/Customer.
Reseller/Customer Utilization Details
Used Space - This is the disk space occupied by the client's backup data in the backup server's storage location.
Uncompressed Size - This is the original size of the client's data before it was compressed and encrypted for backup.
Transferred Data Size - This is the actual amount of data transferred from/to the client machine to/from the backup
server during backups and restores.
For example,
Size of the file when first backed up = 1.0 MBSize of the file after modification = 1.2 MBModified data size = 0.2 MBCompression ratio for backing up the file = 50%Space used for Meta data in the backup server = 10 KBClient restored the original file (version 0) once.
For this example, StoreGrid's calculation is given below:
Used Space = 1.0 MB * 0.5 (initial full file backup) + 0.2 MB * 0.5 (for version file) + 10 kB (for meta data) = 0.601 MB.
Uncompressed Size = 1.0 MB (for initial full file backup) + 0.2 MB (for version file) = 1.2 MB
Transferred Size = 1.0 MB * 0.5 (initial full file backup) + 0.2 MB * 0.5 (version file) + 1.0 MB * 0.5 (for restored file)= 1.1 MB
The following fields are shown in the Reseller/Customer Utilization Details:
Average Used Space/Uncompressed Size[During billing period] - This is the Reseller's/Customer's averageused space/uncompressed size which is calculated for the purpose of Invoice generation. StoreGrid stores the usedspace/uncompressed size of the Reseller/Customer each day. During the Invoice generation, average usedspace/uncompressed size for the Reseller/Customer is calculated based on the Invoice frequency. For example, ifthe frequency is 'Monthly', average used space for the Customer is calculated for the 30/31 days and the InvoiceAmount is calculated for this based on the slab details specified in the plan.
Total Transferred Data Size [During billing period] - This is the amount of bandwidth used for the data tranferduring the invoice period. It includes the bandwidth used for backups and for restores as well.
Current Used Space/Uncompressed Size[as of billing date] - The total disk space used/uncompressed size byall the customers and clients under this Reseller or clients under this Customer.
Total No. of Customers/Clients - This is the number of customers under the Reseller or clients under theCustomer for which Invoices are calculated. The customer/client name and their used space/uncompressedsize/transferred data size are shown.
Currency - The currency on which the Invoice is based.
Usage Charges as per the Invoice plan - Total amount payable for disk space usage/uncompressedsize/transferred data size of all client machines backing up to the backup server during the Invoice period.
Per client machine charges - Minimum amount payable for each of the client machines backing up to the backupserver during the Invoice period.
Surcharge - Surcharge is charged on the total sum of the clients' usage charges as per the invoice plan and theadditional per client charges.
MCALs Used - Total MCALs used by Reseller/Customer during the Invoice period.
Per MCAL charges - MCAL Charges payable for the Reseller/Customer as per the Invoice plan. This is calculatedby multiplying Total MCALs used by the Reseller/Customer during the Invoice period with "per MCAL value".
Total Charges - The total Invoice Amount calculated for the Reseller/Customer. The total Invoice amount is sumof Usage Charges as per the Invoice plan, Per client machine charges and Surcharge.
Customer / Client Utilization Details
Customer Name/Client Name - Customer name/ StoreGrid ID of the client. If a client is deleted during theInvoice period, then the client name is displayed in the Invoice report with a deleted time stamp.
Current Used Space/Uncompressed Size[as of billing date] - The disk space used/uncompressed size by thatcustomer/client
Limitations
1. The Invoice details based on transferred data size are not available after recovering the backup server using ServerDisaster Recovery feature.
2. Invoice report may show incorrect 'per client charge' value for the clients which are migrated to another customer.3. Invoice amount may be little high, when creating Invoice report for customer for their deleted period.4. The client details will not be available in the invoice reports for the deleted clients after migrating it from v2.5.5 to
v3.2.
Integrating StoreGrid with WHMCompleteSolutionRelated Links
WHMCS Integration using Provisioning
module
or Action Hook
Overview
StoreGrid Server can integrate with WHMCS (WHMCompleteSolution) for generating invoice under the appropriate clientaccount in WHMCS to manage StoreGrid invoices. You will be able to associate the StoreGrid Customer accounts to theappropriate client account in WHMCS so that StoreGrid invoices for that Customer are created under the appropriateaccount in WHMCS.
Setting up WHMCS for StoreGrid integration
The first step for integrating StoreGrid with WHMCS is to set up the permissions in WHMCS to allow StoreGrid to accessthe WHMCS APIs to post the data. Please follow the steps mentioned below in WHMCS to setup the permissions:
1. Log into WHMCS admin account.
2. Click on 'Setup' menu and goto 'Administrator Roles' page.
3. Edit your administrator role configuration and make sure whether 'API Access' is enabled. If API is disabled thenenable it and save changes.
4. Now, you need to allow your Backup Server IP to connect WHMCS API. You can allow the connection by StoreGridBackup Server IP address or WHMCS API access key.
Here are the steps to integrate StoreGrid Backup Server with WHMCS:
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Invoice Management->WHMCS Integration"
Step 1:
Log into the backup server web console. Click on the 'WHMCS Integration’ menu which is available in the Server Adminmain menu.
Step 2:
Choose the application status and save the changes.
Step 3:
Enter the WHMCS authentication credential details. Once you have entered the details, click on the Save button.
Note: Please make sure you enter the URL of application upto whmcs folder in Application Site URL field. Like for example'http://mydomain/whmcs'
It will authenticate with WHMCS and save the details if and only if the authentication details are correct.
Step 4:
Next, the wizard will take you a page where you need to map the StoreGrid Customers to a WHMCS Client Account. All theinvoice reports which are generated under a customer will be pushed to WHMCS under the corresponding Client Account.
Click on the Fetch client details from WHMCS for the backup server to first fetch all the Client Accounts from WHMCS.Those will then be listed in the dropdown. Then for each of the StoreGrid Customer, select a WHMCS Client Account. Youcan also select a Default WHMCS Client Name under which invoice reports will be created if there is no mapped ClientName for a Customer.
That's it! StoreGrid backup server is now configured to connect the WHMCS site to create Invoice Reports as and when theinvoices are generated by StoreGrid.
Invoice Report in WHMCS
Here is how the StoreGrid Invoice Reports will look in WHMCS application:
View List Of Backup Clients
Overview
This page lists the StoreGrid clients under the selected customer that are backing up on to this server and provides thefollowing information about each client.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name"
link. This will take you to the List of Customers Page. Now click on the "Customer Name" link. This will list the clientsbacking up under this customer.
View List Of Backup Clients
This list displays following details about the clients backing up to the selected customer:
Client Name : This is the StoreGrid ID of the client backing up to the server. Clicking on the link here will open thelist of backup schedules page.
Needed MCALs : The total MCALs needed by the client for the current month.
Total MCALs used till date : The total MCALs used by the client from the beginning till now.
Next MCALs Usage Date : The date at which the client will use MCALs for the next month. If the client is still intrial, this mentions the date at which the trial period will expire.
Allotted Space : The disk space allotted for this client in the server. The disk space allotted is shown as AUTO, ifthe client is configured to automatically allot disk space as per customer's disk space limitation.
Used Space : The disk space used by the backup data from this client.
Total Backups : Number of backup schedules the client has configured for backup to the server.
Actions : The icons under this column are links to various features to enable you to administer and manage thebackup clients.
Enable / Disable Auto Authorization : If a client is set to 'Enable Auto Authorization', then the client canbackup to the backup server without having to authenticate with the backup server. If the client is set to'Disable Auto Authorization', then the client has to be first added in the backup server and then the clientshould 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 todecide 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 isrejected 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 youcan specify specific configuration options (backup location, disk space, client password etc.) for this client inthe server.
Reset Password : Clicking on this icon will reset the password for this client in this server. Once thepassword is reset, the client, if it uses the old password, will not be allowed to backup. If auto authorizationis 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 theclients and all its backup data.
Deleted Report : Clicking on this icon will take you to the "Deleted Backup Report", which will list in atable format the list of backup schedules and data that has been deleted under this client.
Change Trial To Paid : Clicking on this action converts the trial client to paid client.
NOTE: After you convert a trial client to paid client, you cannot revert back.
Change Client Side Settings : The backup settings on the client such as Backup Window, BandwidthThrottling, Automatic Software Update options can be changed from the backup server. Also Adding aBackup Schedule is also possible. These changes made in the backup server will be picked up by the clientand the client will automatically apply them. The settings that are shown in this page may not be the samepresent in the client currently.
Export backup : The backup data can be exported to any destination location by clicking on this icon. Thisfeature allows the user to export the backup data and the backup database to the user given destinationlocation as a "Local" backup type which is then used to restore by attaching the data to the Client (usingLocal backup "Disaster Recovery "). Instead of restoring the backup data from the client by connecting thebackup server, using this feature, the data can be restored quickly from the client machine itself therebysaving time and bandwidth usage. The backup is exported as a "Local " backup for this purpose.
The export of backup data can be executed with two options namely
With a prefix name (Alias name) - If the user wishes to attach the exported backup data and restore itin the case where the backup already exists in the Client,then this option should be used.Otherwise thebackup cannot be attached to the Client using "Disaster recovery " (as the backup names arealways unique for a client) . Here, the backups are exported by using a user given prefix name and thebackup is exported in the format "Prefix_Backup_Name ".
Important Note:: The backup(s) exported with this option can be attached to the Client and can only beused to restore the backup data.The backup options like "Schedule ", "Suspend/Resume ", "Edit " is notavailable for such backups.
Without prefix name - If the user wishes to attach the exported backup data in the client and restore it inthe case where the client is freshly installed with the same " StoreGrid ID ", then this option can be used.For such backups, all the backup options like "Schedule ", "Suspend/Resume ", "Edit ", "Restore " areavailable.
Troubleshooting Tips
Limitations
Limitations for Export backup feature:
1. "Abort/Suspend" of Export of backup data is currently not available.
2. For "Cluster enabled" backup servers, the backup data can be exported only in the backup servers wherethe client is "Node locked". It cannot be exported from the other backup servers available in that Cluster.
3. Export of backup data is not available for servers installed as an "Amazon machine instance(AMI)"
Add a New Client For a Customer (in the StoreGrid Server)
Overview
From this page, you can add a new client under a customer and configure backup space, backup location and an optionalpassword for the client (backing up to this server).
If you have enabled Auto Authorization for the customer, then you don't really need to add clients manually. Yourcustomer 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 the customer or if you'd prefer to set disk space & passwordindividually for each client of your customer(s), you can add the client from this page.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the Reseller Name.
This will list the page with the list of customers under the reseller. Now click on the "Add Client" icon (in the actioncolumn) in the row corresponding to the customer under which you wish to add the client.
Client Information
Client Name : You should input the StoreGrid ID of the client that will backup to the server. Note that thisStoreGrid ID should exactly match the ID the client will use to identify itself. So make sure, the client uses thecorrect StoreGrid ID when he/she installs the StoreGrid client.
Server(Cluster) Name : A non-editable field displaying the name of this StoreGrid server.
Customer Name : A non-editable field displaying the name of the customer.
Basic Configuration
Backup Storage Location: This field is used to set the backup location where the selected client's backup dataneeds to be stored. You can edit this directory location either manually or by selecting the backup location from thedirectory tree by clicking the button provided at the end of the text box. [This field will not be available in CloudBackup Server as the storage backend used is Amazon S3.]
Cloud Backup Server ( StoreGrid Backup Server deployed in Amazon EC2): The following field will beavailable only in a Cloud Backup server installation:
Temporary backup data cache location: Location on the local drive in the Cloud Backup Server instancewhere data is temporarily stored before being uploaded to Amazon S3 Storage. Once successfully uploadedto Amazon S3, the data is deleted from the cache location.
Space Allocation: Using this field you can select to allot storage for the client manually or in auto mode. In automode, the client will be able to store backup data limited only by the storage used by all the clients under thecustomer with the maximum limit set for the customer. If you would like to allot a limited space for the client, thenthe space can be allotted by providing the disk space value in MB, GB or TB by selecting the appropriate option.
Space Utilization Snapshot for customer:
Disk space allotted for the customer - Total disk space allotted for the customer.
Disk Space used by the customer - The sum of the disk space allotted to different clients under thiscustomer.
Free Backup Space available - Free space available in the customer which is not allocated to any clienti.e., it is the difference between total backup space in the customer and the total backup space allotted toclients.
The link “Edit Disk Space Allocated for Server/Reseller/Customer/Client” takes the user to Settings -> Settings ->Disk Space & Client Management. This lists the resellers, customers, their clients and their backup schedules withtheir MCAL and Space details. The space settings can be edited here.
Web Access [Enable/Disable]: You can enable web access to this client by which the client can log into theserver web console and access its backup data in the backup server from anywhere by using the StoreGrid ID ofthe client as the user name and the password specified in the 'Type Password' field.
Type Password: If you are manually adding the client to the server and Auto Authorization is disabled for thiscustomer, then you need to provide a password for authorizing the client with this server. The client should begiven 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.
This password is also used for the user to access the client machine's backups in the backup server from anywhere(when Web Access is enabled) - by logging into the backup server web console using the StoreGrid ID of the clientas the user name and this password.
Confirm Password: This field is used to confirm that the password is entered correctly in the password field.
Advanced Configuration
Evaluation Status [Client Type] : Using this option you can add the client for a maximum of 30 day trial. Afterthe trial the client can be converted into a paid client or de-activated and removed. To automatically de-activateand remove the trial client and to configure the number of days for the trial to last, please update the Trial ClientSettings.
Set bandwidth throttling specifically for this client - StoreGrid's Bandwidth Throttling feature enables the userto limit the bandwidth usage for a backup schedule. Bandwidth can be configured at the backup server levelreseller, customer and client levels.
If the option No [Use Reseller's or Customer's or Server's global bandwidth throttlingconfiguration] is selected, then the bandwidth throttling for the client will be set as per the Customer'sconfiguration. If there is no specific setting for the Customer, then the client uses the Reseller'sconfiguration. If there is no specific setting for the Reseller, then the client uses the backup server'sconfiguration.
If the option Yes is selected, then you can setup bandwidth throttling specific to this client by entering thefollowing details:
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 thespecified hours of the day.
Throttle each backup to maximum of - The rate to which bandwidth should be throttled.
Add Client Button: After configuring the options specified above, click on the 'Add Client' button to add a new client.Once the Client settings has been saved, a confirm alert message will be displayed to send the account details to theClient in an Email. Click 'OK' if you would like to view and send the Email. This confirmation alert will be displayed, only ifyou have enabled Email feature in the "Settings->Email Settings" page.
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 proceedonly after the client is allotted more space on the server.
Edit Client Backup Configuration
Overview
This page is used to configure backup space and backup locations for StoreGrid clients backing up on to this server.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management (or Customer Management if Reseller Management is
disabled)->List of Resellers". If Reseller Management is enabled, click on the name of the particular reseller and this willlist the customers under the reseller. Now click on the name of the particular customer. This will list all the clients underthe customer. Click on the "Edit Configuration" icon in the action column of this client row.
Client Information
Client Name : A non-editable field displaying the StoreGrid ID of this Client.
Server(Cluster) Name : A non-editable field displaying the name of this StoreGrid server.
Customer Name : A non-editable field displaying the name of the Customer.
Basic Configuration
Backup Storage Location : This is the location where backups from the client will be stored. If the client hasalready backed up to the server and if the backup location is changed, then there is an option to move the existingbackups to the new location. [This field will not be available in Cloud Backup Server as the storage backend used isAmazon S3.]
Cloud Backup Server ( StoreGrid Backup Server deployed in Amazon EC2): The following field will beavailable only in a Cloud Backup server installation:
Temporary backup data cache location: Location on the local drive in the Cloud Backup Server instancewhere data is temporarily stored before being uploaded to Amazon S3 Storage. Once successfully uploadedto Amazon S3, the data is deleted from the cache location.
Move available backups for this client to new backup location: The user has the following three options:
If the user opts for Move backup data and update the databases option, then all the existing backupdata will be moved to the new backup location. Data from all backup schedules from the client will hereafterbe stored in new backup location.
Please note: If the new location is in another partition (or drive), then the backup data in the earlierlocation will be copied (not moved) into the new location. Once the data is copied and the backups arerunning to the new location, you can then delete the backup data present in the earlier location.
If the user opts for I have manually moved the backup data to the new location. Just update thedatabases option, then only the database entries are updated for the already moved backup schedules. Ifthe data is moved manually only for some backup schedules, then the database in the new location isupdated 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 Old Backup Location/1/<Client Name>/ location tothe 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 OldBackup Location/1/<Client Name> folder. Please note that folder names are casesensitive.
iii. In this sub-folder, copy the Backup Name folder (backup data) and the sgclient.txt fileavailable under Old Backup Location/1/<Client Name>/ folder.
If the user opts for Leave the backup data in the old location option, then data from new backupschedules in the client will be stored in the new location. The existing backup data will remain in the oldlocation and data from the existing backup schedules (full or incremental) will continue to be stored in theold location.
Disk space used by this client: Total space used by this client on the server.
Space Allocation: Using this field you can select to allot storage for the client manually or set it in auto mode. Inauto mode, the client can continue using up the backup space till the allocated space for the Customer doesn'texceed.
Space Utilization Snapshot for Customer:
Disk space allotted for the Customer - the total space that all the clients under this Customer can use.
Disk Space used by the customer - The sum of the disk space allotted to different clients under thiscustomer.
Free Backup Space available - Free space available in the Customer which is not allocated to any clienti.e., it is the difference between backup space allotted to Customer and the total backup space allotted toclients.
The link “Edit Disk Space Allocated for Server/Reseller/Customer/Client” takes the user to Settings -> Disk Space &Client Management. This lists the Resellers, Customers, their clients and their backup schedules with their MCALand Space details. The space settings can be edited here.
Web Access [Enable/Disable]: You can enable web access to this client by which the client can log into theserver web console and access its backup data in the backup server from anywhere by using the StoreGrid ID ofthe client as the user name and the password specified in the 'Type Password' field.
Type Password: Password for this client can be edited here.
Confirm Password: This field is used to confirm that the password is entered correctly in the password field.
Advanced Configuration
Evaluation Status[Client Type]: Using this option you can upgrade a client that is in Trial to a paid client.
Set bandwidth throttling specifically for this client - StoreGrid's Bandwidth Throttling feature enables the userto limit the bandwidth usage for a backup schedule. Bandwidth can be configured at the Backup server, Reseller,Customer and Client levels.
If the option No [Use Reseller's or Customer's or Server's global bandwidth throttlingconfiguration] is selected, then the bandwidth throttling for the client will be set as per the Customer'sconfiguration. If there is no specific setting for the Customer, then the client uses the Reseller's configuration(if Reseller Management is enabled in the backup server). If there is no specific setting for the Reseller, thenthe client uses the backup server's configuration.
If the option Yes is selected, then you can setup bandwidth throttling specific to this client by entering thefollowing details:
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 thespecified hours of the day.
Disable Bandwidth Throttling during Weekend - Choose this option to disable bandwidththrottling during weekend (Saturdays and Sundays). However, bandwidth throttling will be active onall the other days.
Throttle each backup to maximum of - The rate to which bandwidth should be throttled.
Update Button : After configuring the options specified above, click on the Update button to save the configuration forthe selected client. Once the Client settings has been saved, a confirm alert message will be displayed to send the accountdetails to the Client in an Email. Click 'OK' if you would like to view and send the Email. This confirmation alert will bedisplayed, only if you have enabled Email feature in the "Settings->Email Settings" page.
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 proceedonly 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 completedbefore you try moving the data'.
Exporting Client Backup Data
Overview
Export client backup feature in the backup server can be used to export a particular backup or all the backups under aclient from the backup server to a specified location in a locally attached drive. The exported data will be in the sameformat as the backup data; i.e., if the backup was encrypted, the exported data will also be encrypted. The exported datacan then be shipped to the client side and the data can be attached into the client machine as a "Local" backup andrestored.
This is different from Server-Side Restore feature in the following ways:
1. The data remains compressed and encrypted when it is been shipped to the client side2. It is not required to know the encryption password for exporting a backup.
How to get here in the StoreGrid Web Console?Client Level
In the top menu select: "Server Admin -> Reseller Management -> List of Resellers -> Reseller [reseller name] ->Customer [customer name]. This will list the Clients. Now click on "Export backup data" icon.
Backup Level In the top menu select: "Server Admin -> Reseller Management -> List of Resellers -> Reseller [reseller name] ->
Customer [customer name] -> Client [client name]. This lists the backup schedules for this client. Now click on "Exportbackup data" icon.
Export Client Backup(s) (Both Client and Backup level)
Client Level
If all or select few backup(s) under a client need to be exported, then the export option can be chosen at the clientlevel. On clicking the "Export backup data" icon, a "pop-up" with the client name, "list of backup(s)" , an option to exportwith "actual" (or) "alias" backup name (Explained below) and an option to enter the destination location are displayed. Theuser can select the required backup(s) and export to a destination location.
Backup Level
If only a specific backup under a client needs to be exported, then the export option can be chosen at the individualbackup level. On clicking the "Export backup data" icon, a "pop-up" with the client name, backup name, an option toexport with "actual" (or) "alias" backup name (Explained below) and an option to enter the destination location aredisplayed. The user can select the backup and export to a destination location.
Export backup options
Export of backup data can be done with two options that are provided in the "Export backup" pop-up itself:
1. With a prefix (Alias name) - If the user would like to attach the exported backup data in the client and restore itwhile the backup job already exists in the Client, then this option should be used. Otherwise the exported datacannot be attached to the client machine as the backup with the same name already exists. The backups areexported as Prefix_BackupName.
Note:: The backup(s) exported with this option can be attached to the Client and can only be used to restorethe backup data. The backup options like "Schedule ", "Suspend/Resume ", "Edit " will not available for suchattached backups.
2. Without prefix name - Can be attached back in the client and can be restored in the case where the client doesn'thave a backup schedule with that name already (like in a freshly installed client). For such attached backups, all thebackup options like "Schedule ", "Suspend/Resume ", "Edit ", "Restore " will be available.
Limitations
1. "Abort/Suspend" of Export of backup data is currently not available.
2. For "Cluster enabled" backup servers, the backup data can be exported only in the backup servers where theclient is "Node locked". It cannot be exported from the other backup servers available in that Cluster.
3. Export of backup data is not available for servers installed as an "Amazon machine instance(AMI)"
Delete a Client
Overview
A client under a customer can be permanently deleted from this page.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the reseller name of
the particular reseller. This will list the customers under the reseller. Now click on the customer name of the particularcustomer. This will list all the clients under the customer. Now, click on the "Delete Client" icon in the action column ofthe client row.
Delete a Client
If you want to delete a client from a customer, then you can do that from this page. All the backup data from the clientwill be moved to SGTrash folder in the storage location and will not be permanently deleted. If the data is to be removedpermanently, the user can manually delete it from the SGTrash folder.
If the Client still has the license key and you have enabled Auto Authorization for this customer, then the Client will be re-created under this customer if the Client tries a backup again. But if you have disabled Auto Authorization for thiscustomer 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 customer" page.
You can see the status of the deletion operation from the Server Side Deleted Backup Reports.
Change Client Side Settings
Overview
In this page, backup settings on the client such as Backup Window, Bandwidth Throttling, Automatic Software Updateoptions can be changed from the backup server. Also Adding a Backup Schedule is also possible. These changes made inthe backup server will be picked up by the client and the client will automatically apply them. The settings that are shownin this page may not be the same present in the client currently.
How to get here in the StoreGrid Web Console?
Method 1: In the top menu, "Settings -> Disk Space & Client Management" and click on the "Change Client SideSettings" icon against the client.
Method 2: In the top menu, select: "Server Admin -> List of Resellers -> Reseller [Reseller Name] -> Customer[Customer Name]". Click on the "Change Client Side Settings" icon against the client.
Method 3: In the top menu, enter the client name in the search text box and click search icon. In the result page,click on the "Change Client Side Settings" icon against the client.
Change Client Side Settings
You can manage the following settings for the selected client.
Adding a new backup schedule - A new backup schedule for backing up files/folders can be added. While addinga new backup schedule, make sure a backup with the same name doesn't already exist in that client. Also ake surethat the OS dependent features such as VSS option, Automatic Directory Monitoring, NTFS backup options areapplicable for the selected client.
Backup Window Settings - You can enable, disable or edit existing Backup Window settings for the client in thissection. Please note that the client's actual existing backup window settings may be different from what is currentlyshown in this page (client's settings are not propagted to the backup server).
Configure Automatic Software Updates - You can enable, disable or edit the client's software update settings inthis section. Make sure that the location that you specify here to store downloaded updates in the client machineactually exists in the client and is accessible to the backup application.
Client Side Bandwidth Throttling - You can enable,disable or edit the client's bandwidth throttling option in thissection. Since the clients actual bandwidth throttling setting is not sent to the backup server, the current status ofthese settings that you see in this page may not be what actually currently exists in the client.
More number of client settings manageability options from the backup server like Adding Plugin Based Backups, RestoringBackups on the Client from the Backup Server etc. will be supported in the next versions.
Limitations
1. Plugin backups cannot be edited from the server.
View List Of Client Backup Schedules
Overview
This page lists the backup schedules from the client.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management>List of Reseller" and click on the "Reseller Name".
This will list the Customers under the reseller. Now click on the "Customer Name". This will list the clients under thisReseller's Customer. Now click on the client name to view the list of backups for that client.
View List Of Client Backup Schedules
The following information is shown for each backup schedule:
Backup Name : The name of the backup schedule as configured by the client. Clicking on the link here opens theServer Side Backup Schedule Report page which gives the detailed Backup, Restore, Delete, Retention andReplication Reports for the backup schedule.
And the icon in this column can be in different states. The following describes the different states the backupschedule 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 : Angular green pointer with a red spark.
Export Backup : Dotted green arrow icon.
Backup Location : The directory in which the backup data from this backup schedule is stored. The details areavailable 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 inprogress or replication is in progress or delete is in progress or move backup is in progress or retention cleanup is inprogress 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. Thisincludes 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 thebackup schedule of clients.
1. Abort Backup (Applicable only to Backup server) : Clicking on this icon aborts the backup immediatelyand no further data will be transferred to the backup server. However the backup will resume at the nextscheduled time.
2. Suspend Client Side Restore (Applicable only to Backup server) : Clicking on this icon suspends theClient Side Restore (Restore initiated from the client), but can be resumed only from the client side. Thesuspended restore process will remain suspended till it is resumed from the client again.
3. Abort Restore : Clicking on this icon aborts the Client Side/Server Side Restore.
4. Suspend Server Side Restore : Clicking on this icon suspends the Server Side Restore (Restore initiatedfrom the server). The suspended restore process will remain suspended till it is resumed from the serveragain.
5. Resume Server Side Restore : Clicking on this icon resumes the Server Side Restore (Restore initiatedfrom the server).
6. Activate/Deactivate Backup : This Activate/Deactivate action can help the Backup Server administrator todecide 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 StoreGridclient for that backup will be rejected by the backup server.
StoreGrid Backup Server Administrator can Activate the client backup again by clicking the same action.
7. Replicate Now : This "Replicate Now" action will immediately schedule Replication for a particular backup ifthe replication for the backup is in idle status.
8. Resume/Suspend Replication : This "Resume/Suspend Replication" action is used to resume a suspendedbackup (for replication) or to suspend a backup (for replication) when it is either idle or in replicationprogress.
9. Proceed to Restore Backup : Clicking on this icon takes you to the server side restore page where youcan restore the backed up data.
10. Proceed to Delete Backup : Clicking on this icon takes you to the delete backup page from where you candelete the backup data associated with the schedule.
11. Run Retention Cleanup : You can run the retention cleanup process by clicking on this action. Theretention cleanup process will delete any excess version files present in the server. Like for example, if theretention version count or retention period configuration is reduced in the client machine, then the backupserver can be forced to clean up these excess versions of the files by running the Run RetentionCleanup(the client should have connected at least once after the retention was changed for the backupschedule in the client).
12. Change Client Side Settings : The backup settings on the client such as Backup Window, BandwidthThrottling, Automatic Software Update options can be changed from the backup server. Also Adding aBackup Schedule is also possible. These changes made in the backup server will be picked up by the clientand the client will automatically apply them. The settings that are shown in this page may not be the samepresent in the client currently.
13. Export backup : The backup data can be exported to any destination location by clicking on this icon. Thisfeature allows the user to export the backup data and the backup database to the user given destinationlocation as a "Local" backup type which is then used to restore by attaching the data to the Client (usingLocal backup "Disaster Recovery "). Instead of restoring the backup data from the client by connecting thebackup server, using this feature, the data can be restored quickly from the client machine itself therebysaving time and bandwidth usage. The backup is exported as a "Local " backup for this purpose.
The export of backup data can be executed with two options namely
With a prefix name (Alias name) - If the user wishes to attach the exported backup data andrestore it in the case where the backup already exists in the Client,then this option should beused.Otherwise the backup cannot be attached to the Client using "Disaster recovery " (asthe backup names are always unique for a client) . Here, the backups are exported by using auser given prefix name and the backup is exported in the format "Prefix_Backup_Name ".
Important Note:: The backup(s) exported with this option can be attached to the Client and canonly be used to restore the backup data.The backup options like "Schedule ", "Suspend/Resume", "Edit " is not available for such backups.
Without prefix name - If the user wishes to attach the exported backup data in the client andrestore it in the case where the client is freshly installed with the same " StoreGrid ID ", then thisoption can be used. For such backups, all the backup options like "Schedule ", "Suspend/Resume ","Edit ", "Restore " are available.
Limitations
Limitations for Export backup feature:
1. "Abort/Suspend" of Export of backup data is currently not available.
2. For "Cluster enabled" backup servers, the backup data can be exported only in the backup servers wherethe client is "Node locked". It cannot be exported from the other backup servers available in that Cluster.
3. Export of backup data is not available for servers installed as an "Amazon machine instance(AMI)"
Server Side Backup Reports
Overview
This page gives a historical report of backups done by the client to the server as part of this backup schedule.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name" in
this reseller row. This lists the customers under this reseller. Now click on the customer name in the customer row. Thislists the clients under this customer. Click on the "Client Name" in this client row. This lists the backup schedules for thisclient. Click on the "Backup Schedule Name" to fetch this backup schedule reports. Now click on the "Backup Report"tab.
Server Side Backup Report
The report is shown in a table format with each row representing a backup done by the client. If there are multiple fullbackups done, then the top row will appear with a plus (+) sign. Clicking on the plus sign will show the incrementalbackups done between two successive full backups.
The description of the columns in the report table is 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 filesbacked 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 forincremental 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. Onlyfor 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 backupduring this schedule. Clicking on the 'View' link will take you to a page which lists the files that were skipped andthe 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 notbe 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 notavailable 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 StoreGridskipped the folders.
Used Space Added : The amount of disk space that was used up in the server by the new files and by the newversions 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 duringthis backup schedule. For example, if the backup schedule was configured to retain 5 versions and if the 6thversion of a file was added during this backup schedule, then the first version of the file will be deleted. If the firstversion was of say 30KB, then that 30KB will be included in the Used Space Removed.
Change in Used Space : This is the difference between the Used Space Added and Used Space Removed. Apositive value indicates that additional disk space was used up in this backup schedule. If the Change in UsedSpace 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 fileversions 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 an older full backup data. If you have more than onefull 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 "DeleteButton".
Server Side Backup/Restore Progress
Overview
Server Side Backup Progress is a popup showing the progress of a currently active backup schedule. This progress is basedon the total allotted disk space and the disk space used by the currently active backup schedule.
Server Side Restore Progress is a popup showing the progress of a currently active restore operation. The percentageprogress shown is based on the number of files to be restored and the number of files already restored.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name" in
this reseller row. This lists the customers under the reseller. Now click on the customer name. This lists the clients underthis customer. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Now click onthe "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 thebackup is active. The percentage progress is based on the disk space allotted vs. disk space used and not based on thetotal 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 couldbe 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 clientmachine.
8. Transfer Rate : The average rate at which backup data is been transferred - calculated as size of total backupdata 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 beenbacked up in the current backup schedule.
11. Deleted Files : Displays the number of files which were deleted since the last backup schedule and the deletenotifications 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 notbe 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 laternot 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 runduring 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 isactive. The percentage progress is shown based on the number of files to be restored and the number of files alreadyrestored. 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 aswell 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.
8. Abort Restore : Clicking on this icon will abort the restore process.
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 thereplication is active. The progress is based on the number of files already replicated vs. total number of files to bereplicated as part of the current schedule.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name" in
this Reseller row. This lists the Customers under the Reseller. Now click on the Customer name. This lists the clientsunder this customer. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Nowclick 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 filesgathered.
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 thedirectory.
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 thecurrent 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.
The backup server replication progress window polls the StoreGrid Backup Server every single second to get the progressof replication. This process can slow down the actual backup operation by between 50% to 75% ! So, for large backupschedules it is better to keep the backup server replication progress window closed and open it only occasionally to checkthe replication progress.
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 thereplication is active. The percentage progress is based on the disk space used vs. disk space allotted and not based on thetotal data already replicated vs. total data 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->Reseller Management->List of Reseller" and click on the "Reseller Name" in
this reseller row. This lists the customers under the reseller. Now click on the customer name. This lists the clients underthis customer. Click on the "Client Name" in this client row. This lists the backup schedules for this client. Now click onthe "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 filesgathered.
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 theStoreGrid 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
1. The replication server replication progress window polls the StoreGrid Replication Server every single second to getthe 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 onlyoccasionally to check the replication server replication progress.
Run Retention Cleanup
Overview
Older versions of a file are automatically cleaned up from the StoreGrid server when the later versions of the file arebacked up in the subsequent incremental backups. In addition to the retention schedule configured in the server, you canmanually run the retention cleanup process using 'Run Retention Cleanup' feature to delete the older version of the filesfrom the server.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name" in
this Reseller row. This lists the Customers under the Reseller. Now click on the Customer name. This lists the clientsunder this customer. Now, click on a client name. This will open a page which lists the backup schedules backing up tothis server (from the selected client). Now click on the "Run Retention Cleanup" action icon.
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 abackup 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 thecleanup 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 thecleanup process.
Abort Cleanup: You can manually abort the retention cleanup process by clicking on the abort icon in the retentionprogress 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 backupversion 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.
Server Side Restore Report
Overview
This page provides details on all the restore operations done for this backup schedule. This page lists both the restoreoperations performed from clients as well as from the server itself.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name" in
this reseller row. This lists the customers under the reseller. Now click on the customer name. This lists the clients underthis customer. 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.
Server side Restore Report
The report is generated in a table format with each row representing a restore operation. The description of the tablecolumns are given below.
Restored to : In a client initiated restore this represents the StoreGrid ID of the client which this backup scheduledata was restored to. In a server initiated restore this represents the StoreGrid ID of the server.
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 : In a client initiated restore, this is the total size of data transferred to the client system. In a server initiatedrestore, this represents the data processed to complete the restore.
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.
Compressed Restore Files : In a server initiated restore if the restored data is configured to be compressed forlater download, this header will provide the download URL of the compressed restore files.
Compressed File Size : If the restore data is configured for compression for later download, this value willrepresent the file size of the downloadable zip file.
Server Side Delete Report
Overview
This page provides backup deletion history for the selected backup schedule. It gives details on all the delete operationsdone for this backup schedule.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name" in
this reseller row. This lists the customers under the reseller. Now click on the customer name. This lists the clients underthis customer. 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.
Server Side Delete Report
The delete report is generated in a table format with each row representing a delete operation performed on the backupschedule. 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.
Reseller / Customer / Client Name : The StoreGrid reseller / customer / client for which the delete operation isperformed.
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.
Server Side Replication Report
Overview
This page provides a historical report on replication of the primary server to the replication server. The report is generatedin a table format with each row representing a replication schedule. A replication report is generated for each backupschedule from each client backing up to the server.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name" in
this reseller row. This lists the customers under the reseller. Now click on the customer name. This lists the clients underthis customer. 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.
Content 1
The description of the various information in the report is 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.
Replication Server : 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 replicationevery minute.
Remarks : Messages about the replication schedule.
Warning : Error messages during the replication.
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 -> Reseller Management" and click on the "Reseller Name" in the "Reseller"
Row. This lists the customers under the Reseller. Now, click on the "Customer Name" in the customer row. This will listthe clients under the particular customer. Click on the "Client Name" in the client row. This lists the backup schedules forthe 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
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.
Cleanup Version Files
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.
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->Reseller Management->List of Reseller" and click on the "Reseller Name" in
this reseller row. This lists the customers under the reseller. Now click on the customer name. row. This lists the clientsunder the customer. Go to "Client Report" action corresponding to the client name and click on the "Move Clientbackup(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 isavailable, StoreGrid will move the backup data for that backup. If sufficient space is not available for aparticular 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. Pleasecheck 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 thebackup 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 thefolder [New Storage Location]/1/[client name]/[backup name]
Skipped File Report in Backup Server
Overview
This page gives a tabular summary of the files which StoreGrid could not backup during a backup schedule.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name" in
this reseller row. This lists the customers under the reseller. Now click on the customer name. This lists the clients underthis customer. 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.
Skipped File Report in Backup Server
This page shows the list of files that StoreGrid could not backup during the backup schedule. The page lists the files ingroups of 100.
This tabular summary of each schedule's backup skipped file report 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 addedfile that StoreGrid is trying to backup for the first time.
Remarks : The reason why the file was skipped.
Skipped Folder Report in Backup Server
Overview
This page gives a tabular summary of the folders which StoreGrid could not backup during a backup schedule.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name" in
this reseller row. This lists the customers under the reseller. Now click on the customer name. This lists the clients underthis customer. 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 foldercount.
Skipped folder report in Backup Server
This page shows the list of folders that StoreGrid could not backup during the backup schedule. The page lists the foldersin groups of 100.
This tabular summary of each schedule's backup skipped folder report includes the following:
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.
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 backupserver 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->Reseller Management->List of Resellers". From the list of resellers displayed
in the table, click on the Reseller Name. This lists the customers under this Reseller. Now click on the Customer Name.This lists the clients under this Customer. Now, click on a client name. This will open a page which lists the backupschedules backing up to this server (from the selected client). Now click on the "Restore" action icon. If you hadpassword 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 backupthat has been done with the time stamp of the last incremental backup performed for this full backup. If the backupschedule was not configured with multiple full backups, then this list will have only one parent node- that of the first fullbackup. Under each parent node, a leaf node with timestamp represents an incremental backup that has been done. Theleaf-node with the earliest timestamp represents the time when the full backup was done and all other time stampsrepresent 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 defaultthe 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 thefile/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 thatthe tree will also list the number of versions of each file as of the timestamp chosen in Step 1. You can eitherchoose a specific version of a file to restore or choose the root node to restore the latest version (as of thetimestamp 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/foldernames instead of selecting them from the tree view link in step 2. Enter the complete path of the file/folder torestore 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 wasavailable at the backup time that you selected in Step 1. If you are trying to restore a delete file, then you shouldenter 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 willbe saved in this location, but with their full original path – that way you know exactly where these files were in the firstplace !
Compress Restore Files - It is an optional step to compress the restored data.
Enable Restored files for download - If enabled, the data is stored in a zip file format.
Encrypt Zip File - If required, the restored zip files can be encrypted while archiving the data and protected with apassword.
[For Exchange Server Backups only] Restore Exchange server database backup data inuncompressed state - Normally for Exchange Server backups, the backed up data is substantially large. By default,the backup data is restored in compressed state as this requires less disk space in the client's restored location and therestore process is faster. However, you can restore Exchange backup data in an uncompressed state if you wish to importit to the Exchange server manually later. To do this, select this check box and proceed with the restore.
Restore and Cancel Button - Once all the options are set and the files and folders to be restored are selected, clickon the Restore button to restore the files and folders. The status of the restore operation will be displayed on a pop-upbrowser window.
Limitations
1. Files/Folders entered manually for restore are case sensitive. Also, ensure that the complete path of the files/foldersto 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 3.
3. No error message will be displayed in the webconsole, if the files/folders entered manually for restore do not existin the backup server or is not a part of the configured backup schedule. However, the error message will bereported 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 completefile/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.
Restore Bare Metal Backup Data from Server
Overview
The image of a disk or a drive that StoreGrid backs up can be restored either as a file or during the restore the image canbe applied directly into a disk. When the disk or drive that is to be restored is accessible from the StoreGrid machinerunning the image restore, the image can be directly applied into the disk. The steps for this are in the later half of thisdocument.
However, often the disk may not be accessible or may be in a remote location. In such cases, the image can be restoredas a file first, shipped to the client location and then applied into the disk through StoreGrid's Recovery CD. For moredetails on this, refer this document.
StoreGird can also convert the restored disk image to a virtual image in the following formats:
1. VMDK - VMWare's virtual machine image format. Image converted into VMDK format can be launched as a virtualmachine on a VMWare Server.
2. VHD - Microsoft Hyper-V virtual machine format. Image converted into VHD format can be launched as a virtualmachine in a Hyper-V environment.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers". From the list of resellers displayed
in the table, click on the Reseller Name. This lists the customers under this Reseller. Now click on the Customer Name.This lists the clients under this Customer. Now, click on a client name. This will open a page which lists the backupschedules backing up to this server (from the selected client). Now click on the "Restore" action icon against theAdvanced disk image backup. If you had password protected the backup schedule, StoreGrid will ask the password forthat backup schedule.
Supported OSes
Windows XP
Windows Server 2003
Windows SBS 2003, 2008 & 2011
Windows Vista
Windows 7
Windows Server 2008 & R2
Both 32 and 64 bit OSes are supported.
Restore Bare Metal Backup Data
Step 0: Backup Details
Backup Name - The backup name is a non-editable field.
Step 1: Select version to restore
Here you can choose to restore either the entire disk(s) or restore specific drive(s).
Selecting version for restore: Based on your backup schedule, you can select to restore any version of the backupimage of a particular schedule. You can choose the version by scolling down the select version option list in which the
latest version of backup image with the time stamp will be on the top and the oldest backup image at the bottom of thelist. select the desired version and click Load button to load the particular image for restore to continue. By default, thelatest version of the backup image is loaded.
Selecting entire disk for restore: If you select to restore the entire disk, then in step 3 you can either restore the diskimage to the hard disk or convert the disk image into a VMDK / VHD format.
Selecting drive(s) for restore: Here you have the option to restore drive(s) alone to another drive(s).
Step 2: Confirm Restore Settings
Restore Location - Specify the location for restore. The restored files will be saved in this location but with theirfull original path - that way you know exactly where these files were in the first place!. Make sure the directory youprovide for restore has enough disk space and has valid read and write permissions. It is recommended to providean empty directory or a new directory path for the local restore location.
Step 3: Confirm Bare Metal Restore Settings
Download Disk Image files
This option " Download the image file from backup server." is used to restore the backup as an image (.vhd) file. Thisoption is useful when the disk that needs to be restored is in a remote location or is not accessible from the machinewhere StoreGrid is running. After restoring the files, you can take it to the client local and using the StoreGrid RecoveryCD, you can restore the disk image file (present in external device) into the new hard disk. For more details on how torestore a disk using StoreGrid's Recovery CD, please refer to this help document. If Compression and encryption is notenabled for the backup schedule, this downloaded Vhd file can be directly connected to any supporting virtualizationenvironment like Microsoft Hyper-v and can be booted as ready to use VM
VMDK or VHD Conversion
Option 'Convert the restored disk image into VMDK/VHD format' is used to convert the disk image file into virtual fileseither VMDK - VMWare's virtual machine image format or VHD-Microsoft Hyper-V virtual machine format. The convertedvirtual image can be used to boot it up as a virtual machine in a VMWare or Hyper-V environment.
Note: While launching the VMDK/VHD file on a virtual machine environment, you have to inject the drivers through theRecovery CD
Hard disk or Partition restore
This steps restores the backed up disk image data to disk/drive. By default, the option 'Perform disk or parition restore...'is selected. This will restore the data to the hard disk/drive.
Note: In Windows Vista, Windows 7, Windwos 2008 OSes, you have to set the BCD configuration through the Recovery CDif any problem occurred while booting the OS from the recovered hard disk data.
Step 4: Compress Restore Files
It is an optional step to compress the restored data if the option "Download the image file from backup server." is chosenin step 3.
Enable Restored files for download - If enabled, the data is stored in a zip file format.
Encrypt Zip File - If required, the restored zip files can be encrypted while archiving the data and protected with a
password.
Restore and Cancel Button - Once all the options are set, click on the Restore button to restore the backup. Thestatus of the restore operation will be displayed in a pop-up browser window.
Virtual Recovery as Hyper-v VM
Overview
The image of a disk or drive backup can be converted as ready to use VM. StoreGrid supports the following virtualizationenvironment Microsoft Hyper-v, Virtual PC, Virtual Server, Oracle Virtual Box, VmWare. If the backup source harddisk hasoperating system, the converted image can be directly booted in the above mentioned virtualization platforms. The stepsfor booting in HyperV Manager is explained in detail here.
How to boot as Hyper-v VM ?
NOTE : It is assumed the backup image has been converted to VHD with help of this document. The same conversionoperation can be performed using StoreGrid Recovery CD as explained here. If the backup is configured without enablingencryption and compression, the Backup VHD can be directly booted using Hyper-v.
Step 0: Launch Hyper-v :
Launch Hyper-v Manager from Start->All Programs->Administrative Tools->Hyper-V Manager. Note: Hyper-V Manager willbe available in Windows 2008 R2 Operating System if the Hyper-v role is enabled in the server.
Step 1: Create New Virtual Machine :
Create New Virtual Machine by Right click -> New -> Virtual Machine or In Menu, Action -> New -> Virtual Machine
Step 2: Enter Name of Virtual Machine :
Enter the desired name for the new virtual machine.
Step 3: Select Memory :
Select virtual RAM Memory in this page.
Step 4: Select Virtual Network :
Select the Virtual Network of choice from the drop down option, for the newly created VM.
Step 5: Select Hard Disk :
Choose to select Use Existing Hard disk. Click the browse icon and navigate to the location where the converted VHDexist and select the desired VHD.
Step 6: Finish Page :
Now the process of creating Virtual Machine using Converted VHD is complete , click Finish to Exit.
Step 7: Connect to Created Virtual Machine:
To connect the created VM, Right Click and select connect option.
Step 8: Start Created Virtual Machine:
To start the created VM, Click the start button or you may choose Action->Start from the Menu Bar.
Step 9: Booting Screen :
VM gets started and you will get to see the booting screen.
Troubleshooting Tips
Resource Allocation Error
Check whether you have allocated Virtual RAM memory that is more than 50% of the Host Operating Sytem. It isrecommended that you choose RAM memory less than 50% of the Host Operating Sytem.
Delete A Backup From The Server
Overview
This page lists the backup schedules from the selected client backing up to the backup server. Clicking on the 'DeleteBackup' action icon corresponding to the backup name will delete the data permanently from the backup server.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin->Reseller Management->List of Resellers" and click on the "Reseller Name" in
this Reseller row. This lists the Customers under the Reseller. Now click on the Customer name. This lists the clientsunder this customer. Now, click on a client name. This will open a page which lists the backup schedules backing up tothis server (from the selected client). Now click on the "Delete Backup" action icon.
Deleting a backup from the Server
If you want to delete a client's backup data associated with this backup schedule, then you can do that from this page. Allthe backup data associated with this backup schedule will be moved to SGTrash folder in the storage location and will notbe permanently deleted. If the data is to be removed permanently, the user can manually delete it from the SGTrashfolder. If your server can directly reach the client, then the client will also be notified about this deletion. Whether theclient gets notified or not about the deletion, the client will take a new full backup to the server, if the same backupscheduled is scheduled again in the client.
You can see the status of the deletion operation from the Server Side Deleted Backup Reports.
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 nextschedule.
How to get here in the StoreGrid Web Console? In the top menu select: "Server Admin -> Reseller Management ->List of Resellers -> Reseller [reseller name] >
Customer [customer name] -> Client [client name] -> List of Backup Schedules from client" in the backup server's webconsole.
Aborting Backup from backup server
To abort a backup from the backup server, go to the 'Server Admin -> Reseller Management ->List of Resellers ->Reseller [reseller name] -> Customer [customer 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 backupwill 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.
Suspending Server Side Restore (Restore initiated from the backupserver)
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 -> Reseller Management -> List of Resellers -> Reseller [reseller name] ->
Customer [customer name] -> Client [client name] -> List of Backup Schedules" page.
Suspending Server Side Restore (Restore initiated from the backup server)
To suspend Server Side Restore, go to the 'Server Admin -> Reseller Management > List of Resellers > Reseller [resellername] -> Customer [customer name] -> Client [client name] -> List of Backup Schedules' page in the backup server'sweb console. When restore is in progress, 'Suspend Server Side Restore' icon will be displayed under 'Actions' against thatbackup schedule. Click on the 'Suspend Server Side Restore' icon to suspend the Server side Restore.
Exported Client Backup Report
Overview
The Export report is generated every time when the backup(s) under the Client are exported to the specified destination.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Admin -> Reseller Management (List of Resellers) -> Customer (List of customers) -
> Client (List of Clients)". This lists the clients under the customer. Go to "Client Report" action corresponding to theclient name and click on the "Exported Client Backup" tab.
Exported Client Backup Report
The following is the description of the report columns:
Client Name - StoreGrid ID of the client whose backup data was exported.
Backup Name - The backup schedule name whose data was exported.
Backup exported as - The alias name of the actual backup name whose data was exported with "Prefix" option.
Status - The status of the export operation.
Start Time - The start time of the backup export operation for each individual backup.
End Time - The end time of the backup export operation for each individual backup.
Total Time Taken -The total time taken to export the backup data for each individual backup.
Change Client Side Backup Configurations
Overview
In this page, you can edit existing backup schedule in the client, run the backup, suspend a runing backup, resume asuspended backup and delete a backup in the client from the backup server. These changes made in the backup server willbe picked up by the client and the client will automatically apply them.
How to get here in the StoreGrid Web Console?
Method 1: In the top menu, select: "Settings -> Disk Space & Client Management". Click on the "Change Client SideBackup Configurations" icon against the backup.
Method 2: In the top menu, select: "Server Admin -> List of Resellers -> Reseller [Reseller Name] -> Customer[Customer Name] -> Client [Client Name]". Click on the "Change Client Side Backup Configurations" icon against thebackup.
Method 3: In the top menu, enter the backup name in the search text box and click search icon. In the result page,click on the "Change Client Side Backup Configurations" icon against the backup.
Change Client Side Backup Configurations
You can manage following settings for the selected backup schedule:
Edit Backup Schedule - Allows you to edit the backup configuration in the client side.
Run the Backup - Allows you to Run the backup in the client.
Suspend Backup - Allows you to suspend the backup in the client if the backup is running.
Resume Backup - Allows you to resume the backup in the client if the backup is suspended.
Delete Backup Data/Schedule - Allows you to delete the backup schedule and/or the data from the client.
Limitations
1. Plugin backups cannot be edited from the server.
StoreGrid Server Dashboard
Overview
The Server dashboard has four 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 and MCAL 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:
Reseller Name - The Reseller from which this backup schedule's client's customer is backing up.
Customer Name - The customer 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 upare:
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 notbe 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 notavailable 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 StoreGridskipped the folders.
No. Of Full backups - This total number of full backup that has been taken.
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 offull backups, Skipped files, Skipped folders and any remarks from the backup report. Also, there is an option toview 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 :
Reseller Name - The Reseller from which this backup schedule's client's customer is backing up.
Customer Name - The customer 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 ofbackup, restore, delete, replication operations and moving backup data from one location to other location for thisbackup schedule. The following describes the different icons:
Backup : Triangle iconRestore : Inverted triangle iconDelete : Cross iconReplication : Play Triangle iconMove Backup : Double Triangle iconRunning Retention Cleanup : Rotating arrows iconServer Disaster Recovery : Angular green pointer with a red sparkExport Backup : Dotted green arrow 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. Thischart 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. Bydefault it will be set to 75%, so that an alert message will be displayed if the usage goes over 75% of allocatedstorage in server. You can set this to your desired level. To change this, enter the numeric value inside the textbox and click "Ok" to save the settings.
Licensing
These fields are applicable to Backup Server only:
MCALs needed for existing clients - This shows the number of MCALs needed by the existing clients in theserver for the current month. This value is only applicable in StoreGrid running in Backup Server mode
MCALs Available in Global Pool - This is the total number of available/unutilized MCAL licenses in the StoreGridbackup server's global pool.
MCAL status message - MCAL status message is displayed at the bottom of the MCAL table. This is to notifywhether the MCAL balance in the server is healthy enough or there is shortage of MCALs. The status can be one ofthe following:
Healthy - If enough MCALs are available in the backup server for the next 2 months for the existing clients, it isconsidered a Healthy Balance.Low - If enough MCALs are available in the backup server for the next 1 month for the existing clients, it isconsidered a Low balance.Very Low - If there aren't enough MCALs in the backup server for the next 1 month for the existing clients, it isconsidered a VERY LOW balance
View MCAL Details link - Using this link you can go to the MCAL Utilization History page under the Licensemanagement.
Generate MCAL License link - This link redirects you to the StoreGrid Partner Zone page from where you cangenerate MCAL License.
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 customers. Also this report canbe scheduled to be sent in an Email 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,customer and date. By default, the reports will be show the status of all backup schedules of all customers for the last 24hours. 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 thefilter as the default by clicking on the 'Change settings for default view' icon in the top right corner of the report.
Filter : There are two types of Client backup status reports generated using StoreGrid:
Running Log of backup status
Displays status of all the backup schedules. If a backup schedule has multiple skipped schedules, this log will list all ofthem. Using this option, the backup reports can be filtered by backup status, customer 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 willopen the Filter Settings windows where you can enter the following details:
Running Log of backup status:This section has the following options:
All: Will include report of all backup schedulesFailed: Will include the report of only those backup schedules that failed, were manually suspended from theclient or were aborted in the backup server.Missed: Will list backup schedules that didn't run at the scheduled time, and even in 1 hour after thescheduled time.Partially Completed: Will list backups that completed partially i.e. some files or folders were skipped.Successfully Completed: This includes backups which completed successfully, including those backups wherethere were no new or modified files to backup.
Filter by customer: Backup reports can be generated either for all the customers or for a particular customer.Select the customer [all customers/trial/default/....] for which the report is to be generated.
Filter by duration Backup reports can be filtered by duration of the backup schedule. A data range can be also bespecified 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 endtime. The reports can not be sorted by the 'Total Time Taken'.
Show: The number of reports to be listed per page, default been 25.
The following fields are displayed in the report type Running Log of backup status
i. 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.
ii. Reseller Name: Name of the reseller.
iii. Customer Name: Name of the customer.
iv. Clients: StoreGrid ID of the client machine.
v. Backup: Name of the backup schedule.
vi. Schedule Type: Full backup/Incremental Backup.
vii. Backup Start Time: Time when the backup was scheduled.
viii. Backup End time: Time when the backup ended.
ix. Total Time Taken: Time taken for the backup schedule to complete.
x. Next Schedule Time: Time when the backup is scheduled next.
xi. No of Attempts: Number of attempts StoreGrid made to run the backup schedule. In case of failure, StoreGrid willtry to run the backup again after 5 minutes and the number of such attempts is captured here.
xii. Total Files Listed : Total number of files available for backup.
xiii. Protected Files: Number of files that were successfully backed up to the backup server.
xiv. Skipped Files: Number of files skipped in a particular backup schedule.
xv. Skipped Folders: Number of folders skipped in a particular backup schedule.
xvi. Remarks: Warning message.
Latest status of a backup
Displays the latest status of each backup schedule. In this report, only the latest status of the backup schedule will belisted. If a backup schedule has several missed schedules, this report will show only the latest one. The backups can befurther filtered based on their backup status and customer.
Filter by Backup Status:The backup reports can be sorted in the following ways:
Show backups that have not backed up successfully for the last 1 day: If selected, the user can viewbackups that have not completed successfully in the last 1/2/7/15/30 days, with the default setting as 1 day.Show backups that have backed up successfully in the last 7 days: If selected, the user can view backupsthat have completed successfully in the last 1/2/7/15/30 days, with the default setting as 7 days.Latest status of backups for the last 7 days: If selected, the user can get the latest status of all the backupsscheduled for all customers in the last 1/2/7/15/30 days, with the default setting as 7 days.
Filter by customer: Backup reports can be generated either for all the customers or for a particular customer.Select the customer [all customers/trial/default/....] for which the report is to be generated.
The following fields are displayed in the report type Latest status of a backup
i. Last Backup Status: Indicates backup status of the last schedule;Success/ Failure/ Partial/ Missed.
ii. Reseller Name: Name of the reseller.
iii. Customer Name: Name of the customer.
iv. Clients: StoreGrid ID of the client machine.
v. Backup: Name of the backup schedule.
vi. Last Successful Backup End Time: Time when the last successful backup ended.
vii. Last Backup End Time: Time when the last backup ended.
viii. Last Backup Remarks: Warning message.
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.
Email: The status report that is current listed in the 'View Report' page can be sent as an Email. Click on the 'Email' link atthe top right corner above the status report and enter the Email addresses to which this report should be sent. Whenentering more than one Email addresses, the Email 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 backupschedules from all customers for the last one day. You can configure it to show a different status report when the pageloads by setting the appropriate filter in default settings page which can be accessed by clicking on the 'Change settings fordefault view' (icon) at the top right corner above the status report in the View Report page.
Schedule Email Report
StoreGrid can be scheduled to send Email report of the status of the backups on a daily or weekly basis. To schedule theEmail reports, click on the 'Schedule Email Report' tab and enter the following details:
To Email ID: Recipient Email IDs, multiple addresses should be separated by comma.
Apply This Filter: Reports can be filtered using selected filters.
Schedule: The reports can be emailed 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, customer/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 abackup is interrupted in client side and is rescheduled after 5 minutes, the backup server may still show the nextschedule time based on the backup schedule configuration.
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: "Reports -> Client Information Report"
Client Information Report
The Client Information Report has the following details:
Client Name - Name of the client.
Customer Name - Name of the customer to which the client belongs to.
Reseller Name - Name of the reseller to which the client belongs to.
OS - Type of operating system running in the client machine [ Windows/ Linux/ FreeBSD/ Mac ].
Client Type - Provides information whether the client is under evaluation (Trial) or has been converted to a PaidClient.
Version - Version of StoreGrid running in the client machine.
Build No. - The build number of StoreGrid running in the client machine.
Next MCALs Usage Date - Indicates the date on which the paid client is next scheduled for MCAL consumption.For the trial client, this indicates the trial expiry date.
Allotted Space - Total space allotted to the client in the backup server.
Used Space - This is the total disk space occupied by the client's backup data in the backup server's storagelocation.
License Type - License type of the client [Desktop/Server OS license] with plugin details.
Plugins Used - This column lists the plugins used by the Client, such as, MS Exchange, MS SQL Server, MSExchange Mailbox Plugin, etc.,
NAT IP - This column provides the public static IP address through which the client connects to the StoreGridServer.
Local IP - This column provides the local network IP address of the system through which the client ( StoreGridID) connects to the StoreGrid Server.
Backup Location - This column provides the backup storage location of the client machine.
Limitations
1. This report will contain the details of a client only when the client is running 2.3.5 or a higher version.2. If a client is added in the backup server manually or by using ‘Seed Backup Migration’ feature; client name,
customer 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.
Client Management Report
Overview
This report shows the list of Client Settings Changes added in the backup server. Clients automatically pull these settingchanges and apply them. This report also shows, whether these settings have already been applied in the clients or not.The client settings can be disabled, enabled or deleted, if they are not yet sent to the clients.
How to get here in the StoreGrid Web Console? In the top menu, select: "Reports -> Client Management Report" page.
Client Management Report
The report has the following details:
Client Name - Client to which the Client Setting Change has to be sent.
Reseller Name - Reseller under which the client exists in the backup server.
Customer Name - Customer under which the client exists in the backup server.
Description - Type of Client Setting Change.
Add Backup ScheduleEdit Backup ScheduleDelete Backup ScheduleSchedule BackupSuspend BackupResume BackupClient Backup Window Setting ChangeAutomatic Software Update Setting ChangeBandwidth Throttling Setting Change
Created Time - The time when the Client Setting Change was created in the backup server.
Actions
Enable/disable client setting (only if the setting change not yet retrieved by the client)Delete client setting change (only if the setting change not yet retrieved by the client)View detailed report - Status of client setting change in the client, after it is sent to the client.
Software Updates Downloaded
Overview
This section gives details of the latest client updates and their installation.
How to get here in the StoreGrid Web Console? In the top menu, select: "Reports -> Updates Downloaded" page.
StoreGrid client checks the backup server for the new builds every one hour. If a new update is available, the StoreGridclient will automatically download and install it in the client system. If there is a backup/restore/delete operation inprogress, the client waits for it to finish and then downloads and installs the new updates.
Software Updates Downloaded
This page contains the client's software update report. The report includes details of the available builds in the configuredbackup server, when they were identified, downloaded and installed.
The version and build details can be obtained from the About Us link on the right top corner of the page.
Software Updates Sent
Overview
This section gives details of the updates downloaded and upgraded by different clients
How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Reports -> Updates Sent" page.
Software Updates Sent
This page shows the report for the clients who have downloaded and updated with the builds from this server.
User Activity Log
Overview
This report shows the activities of users who have signed into the web console of this StoreGrid server. This activity log iscreated for the user login, logout actions, MCAL management, server and customer management activity in the server. Youcan sort this log by activity time, user name, Entity, activity and status columns. This report is available only for adminlevel web console access.
How to get here in the StoreGrid Web Console? In the top menu, select: "Reports->User Activity Log"
User Activity Log
To enable or disable the User Activity Log, click on the Gear Icon on the top right hand corner of the page. The report hasfollowing details:
Activity Time - The time at which the activity was executed.
User Name - The webconsole login user name.
User IP - The local IP address of the machine where the user logged in from.
Entity - The Server/Customer/Client account on which the activity was performed.
Activity - The activity that was performed.
Description - Description of the activity.
Status - Whether the activity was completed successfully or not. Like for example, if a user tried to apply an MCALlicense and if it could not be applied, the status would be reported as Failure.
Limitations
Currently this report only captures the logs of the following activities - user login, logout, MCAL management, Server andCustomer management.
Raised Alarms
Overview
In this page, you can view the alarms which were recently raised due to the events in the StoreGrid. Events that arecritical and are raised repeatedly are raised as alarms.
How to get here in the StoreGrid Web Console? In the top menu, select: "Alarms & Events -> Alarms" page.
Raised Alarms
The alarms are raised by events which are caused when an error occurs during backup/restore or any other process in theStoreGrid instance. The events which occur during an error are raised as alarms based on the criticality of the events.
The list of alarms indicate the client that was performing the backup/restore process for which the alarm was raised, thebackup schedule that the client was processing.
The list of raised alarms shows the following details:
Severity: The severity of the alarm.
Reseller Name: The reseller name with which the alarm is linked. [shown only if available]
Customer Name: The Customer name with which the alarm is linked. [shown only if available]
Raised By: This value specifies the StoreGrid instance which raised this alarm.
Raised For: This value specifies for whom the StoreGrid instance raised this alarm.
While processing: This value specifies what was processed when this alarm was raised.
Caused by Events: This value specifies the number of events responsible for raising this alarm and updating the alarmwith the latest values.
Module: The module in which the latest event updated this alarm.
Last Updated Time: The time in which the alarm was last updated.
Last Updated Message: The message updated from the last event which updated this alarm.
Actions
Acknowledge Alarm - Using this action a user can acknowledge an alarm and add relevant comments to it.You would typically acknowledging an alarm if you know what the alarm is for and you are in the process of fixingit.
Add Comment - To add a comment to the alarm.
View Comments - View the list of comments added for this alarm by various users.
Clear Alarm - After the issue related to the alarm is resolved, the alarm can be cleared using this action.
View Cleared Alarms
Overview
In this page, you can view the alarms which are recently cleared from the raised alarms. Normally, the alarms are clearedafter the real cause of the alarm is resolved by the Administrator.
How to get here in the StoreGrid Web Console? In the top menu, select: "Alarms & Events -> Alarms -> Cleared Alarms" page.
View Cleared Alarms
The cleared alarms are the list of alarms which are cleared by the administrator after the real cause of the alarm areresolved. This view can be used to review the recently cleared alarms and check out if any alarm is getting repeated afterits been cleared. The view can also be used to review how the alarm was cleared and the procedure can be used to clearsimilar alarms across other clients' backup/restore processes.
The cleared alarms list shows the following details:
Severity: The severity of the alarm.
Reseller Name: The reseller name with which the alarm is linked. [shown only if available]
Customer Name: The Customer name with which the alarm is linked. [shown only if available]
Raised By: This value specifies the StoreGrid instance which raised this alarm.
For: This value specifies for whom the StoreGrid instance raised this alarm.
While processing: This value specifies what was processed when this alarm was raised.
Caused by Events: This value specifies the number of events responsible for raising this alarm and updating the alarmwith the latest values.
Module: The module in which the latest event updated this alarm.
Last Updated Time: The time in which the alarm was last updated.
Last Updated Message: The message updated from the last event which updated this alarm.
Actions
View Comments - View the list of comments added for this alarm by various users. Also the comment addedwhen the alarm was cleared.
The cleared alarms and the relevant events will be cleaned up under the Event/Alarm cleanup schedule.
View Events which Raised the Alarm
Overview
In this page, you can view the list of events which raised the particular alarm and have updated the alarm.
How to get here in the StoreGrid Web Console? In the top menu, select: "Alarms & Events -> Alarms -> Click on the number under 'Caused by Events' column for the
particular Alarm row" page.
View Events which Raised the Alarm
The events which occur during error are managed as alarms based on the effect they cause on the routine process ofStoreGrid. In this page the list of events which raised a particular alarm is shown. This shows in detail the actual errorswhich have caused the alarm to be raised. Using these error messages the relevant resolution can be identified andperformed. After the issue is resolved the alarm raised by these events can be cleared.
The events list shows the following details:
Severity: The severity of the event.
Reseller Name: The reseller name with which the event is linked. [shown only if available]
Customer Name: The customer name with which the event is linked. [shown only if available]
Raised By: This value specifies the StoreGrid instance which raised this event.
For: This value specifies for whom the StoreGrid instance raised this event.
While processing: This value specifies what was processed when this event was raised.
Module: The module in which the event occurred.
Last Updated Time: The time in which the event was last updated.
No. of Occurrences: The number of occurrences of the same event to cause this alarm.
Last Updated Message: The message updated from the last event which updated this alarm.
View Events
Overview
In this page, you can view the list of events which have occurred.
How to get here in the StoreGrid Web Console? In the top menu, select: "Alarms & Events -> Events" page.
View Events which Raised the Alarm
Events are messages which give details about a problem that needs to be addressed by an administrator. There could be anumber 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.
The events list shows the following details:
Severity: The severity of the event.
Reseller Name: The reseller name with which the event is linked [shown only if available]
Customer Name: The Customer name with which the event is linked [shown only if available]
Caused By: This value specifies the StoreGrid instance which raised this event.
For: This value specifies for whom the StoreGrid instance raised this event.
While processing: This value specifies what was processed when this event was raised.
No: of Occurrences: The number of occurrences of the same event to cause this alarm.
Module: The module in which the event occurred.
Last Updated Time: The time in which the event was last updated.
Last Updated Message: The message updated from the last event which updated this alarm.
StoreGrid Alarms and Events Configuration
Overview
StoreGrid generates events to alert the user about potential problems that may require attention. The events in turn raiseor update the necessary alarms using which the problem is analyzed and resolved. The events configuration UI is meant toconfigure parameters on how StoreGrid should handle its events and the resultant alarms.
How to get here in the StoreGrid Web Console? In the top menu, select: "Alarms & Events -> Configuration"
StoreGrid Alarms and Events Configuration
StoreGrid generates events to alert the user about potential problems that may require attention. The events in turn raiseor update the necessary alarms using which the problem is analyzed and resolved. The events configuration UI is meant toconfigure parameters on how StoreGrid should handle its events and the resultant alarms. The following describes theconfiguration options:
Events & Alarms Configuration - Events that are generated locally by the StoreGrid installation. Each eventgenerated raises or updates an alarm which can be used to analyze and resolve the issue which causes the event. Hereyou can configure the following:
a. Clean Up Frequency - This field is used to specify how often should StoreGrid check and cleanup the clearedalarms. StoreGrid automatically cleans up the cleared alarms, the associated events as well as the Informationevents which never raise an alarm. It is not advisable to check and cleanup alarms & events frequently as thismight cause performance issues. Hence, the maximum frequency you can specify is a "Day".
b. Generate Windows Event - You can use this option to have StoreGrid also generate a Windows event whenit is generates a StoreGrid event.
You can select the type of StoreGrid events for which the Windows events should be generated. You can select oneor more of the following event types:
1. Critical and Major2. Warning3. Information
StoreGrid Administration
Overview
The StoreGrid Administration features (available under the Settings menu), are related broadly to administering andconfiguring a StoreGrid installation which is operating as a Client.
How to get here in the StoreGrid Web Console? In the top menu, go to "Settings" and select the feature listed under it.
StoreGrid Administration
Please go to the section StoreGrid Client User Guide -> Administration to learn about administration and configurationoptions of StoreGrid Clients. If you want to learn about StoreGrid Server Administration go to the section StoreGrid ServerUser Guide -> Server Administration
The following administration features are available in StoreGrid Server:
Add/Delete Peer ( StoreGrid Clients, Servers or Replication Servers)
Test connectivity to Replication Server
Email Settings
User Management
Mysql Settings [ For Windows ]
Mapped Drive Settings
Configure Automatic Software Updates
NOTE: All administration and configuration related specifically to a StoreGrid Server are available under the "ServerAdmin" menu.
Add / Delete StoreGrid Peer(s)
Overview
In this page, you can add the details of the other machines (peers) that are running StoreGrid. Once added, you can usethe 'Switch Peer' feature (available at the top right hand corner of the web console pages) to access the web console ofthe added peers from this web console.
How to get here in the StoreGrid Web Console? In the top menu, select: "Settings-> Add/Delete Peer" and select the "Add Peer(s)" table.
Add/Delete StoreGrid Peer(s)
In a client machine, you may need to add the backup server machine as a peer here (Machine Type as 'Server') to be ableto configure backups to the backup server in the 'Add Backup Schedule' page.
In a backup server machine, if you want to replicate it to a Replication Server, then you need to add the ReplicationServer as a peer here to be able to configure replication against it in 'Replication Management' page.
NOTE: When you add a peer with its IP address, then this StoreGrid machine will access it only through the IP address.Therefore, if the peer is in a DHCP network, then make sure you add the peer with its DNS name and not its IP address.
Machine Name - This is the name of the peer (if known) which needs to be added. You can either give the IP or theDNS name.
StoreGrid ID - This is an optional field to enter the StoreGrid ID of the peer (if known) which needs to be added. Ifyou do not give a StoreGrid ID, StoreGrid will automatically get it from the peer if it is able to connect to it.
Machine Type - Select the ‘type’ of the peer (server/client/replication server).
Add Peer Button - Once the machine name and the machine type are specified as described above, click on the AddPeer Button to add the peer.
Delete Peer - To delete a StoreGrid peer, simply click on the delete icon in the row corresponding to the peer.
Once added, the machines are listed in the table available below the Add Peer button with their corresponding details. Theavailability (if this machine is able to connect to the peer) of the added machine can be interpreted from the imagedisplayed before the StoreGrid ID; a blue icon indicates that the machine is available, and a black icon denotes that thismachine was not able to connect to that peer.
Test connectivity to Replication Server
Overview
With this feature you can check the connectivity from the backup server to the replication server. It also checks thevarious settings in the replication server to identify if the backup server can replicate to the replication server.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Management -> Replication Management -> Test connectivity to Replication Server".
This is also available in step 1 of 'Server Management -> Replication Management -> Configure Replication' page and'Server Management -> Replication Management -> Server Disaster Recovery' page.
Test connectivity to Replication Server
This feature checks for the following:
DNS lookup - It checks if the backup server can resolve the replication server's hostname (FQDN). If this checkfails, then check the DNS server in the backup server's network and make sure there is an entry for replicationserver's hostname. If the replication server has a static IP then try using that IP instead of the hostname.
Telnet & Ping - It checks if the backup server is able to reach the replication server. If this check fails, make surethe replication server is online and StoreGrid is running on it. Also make sure that the firewall on both the backupserver and the replication server side allows TCP/IP traffic from backup server to the replication server.
Server Type - This checks if the server connected to is a backup server or a replication server.
StoreGrid Edition and Version - It checks the compatibility of StoreGrid editions/versions running in the backupserver and the replication server. Backup server running SP edition cannot replicate to a Replication Server runningPro Edition and vice versa. Backup server running a higher version of StoreGrid cannot replicate to a replicationserver running a lower version of StoreGrid. For example, v3.1 backup server cannot replicate to a replicationserver running StoreGrid v3.0.
Authentication - This checks if the backup server is authenticated with the replication server. If a password isconfigured in the replication server, then you need to authenticate the backup server with the replication serverfrom the 'Server Admin -> Replication Management -> Authenticate Backup Server for Replication' page.
Email Settings
Overview
StoreGrid has the capability to email all the client-side and server-side reports to interested recipients.
How to get here in the StoreGrid Web Console? In the top menu, select: "Settings -> Email Settings".
Email Settings
The following describes the configuration options:
Enable - First you need to check this checkbox to enable email feature in StoreGrid and then provide inputs to the restof the fields.
Outgoing (SMTP) Server - This is the SMTP server StoreGrid should use to send the email. This will most probablybe the same server as the one you use in your email client (Outlook, Eudora etc.). If you are not sure, check with yourSystems Administrator.
More Options Link - If you click on the "More Options" link you will be shown couple of more advanced options:
a. Outgoing (SMTP) Server Port Number - By default SMTP servers use port number 25. If by any chanceit is different in your case, you can provide the port number here.
b. This SMTP Server Requires Authentication - If your outgoing server (SMTP server) requiresauthentication before it can accept an email for sending out, you need to check this checkbox. You will get thefollowing 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 emailclient 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 notsure leave it with the default value "AUTO".
iv. Use SSL - Select this checkbox if you want emails to be communicated through SSL port. You need toenter email server's SSL port in the port number text box.
Sender Email ID - Provide the email ID of the sender from which the reports should be emailed. The email will bedelivered to the recipients as if coming from the Sender Email ID you provide here.
Test Mail Server - Once you have entered the SMTP server details, click on the link "Test Mail Server" and check ifit works by entering an Email ID in the 'To Email ID' field and then clicking on "Send Test Email". A test email will be sentto the 'To Email ID'. If you don't receive the test email, check the SMTP server settings again.
Email Reports - You can enable StoreGrid to set Email reports on completion of various jobs like Backup, Restore,Deleting a Backup or a Replication job. You can enter separate recipient Email IDs based of the status of the job - youcould have the Emails sent to one Email address when the job completes successfully and another when the job fails. Also,you could have same Email address for all reports or different ones for each of the reports. If you would like to send theEmails to the same Email address for Backup, Restore, Replication and for Delete Backup, select the check box: Use thesame Email IDs for all the reports. If you would like to specify different Email addresses for each report, you can selectthe check box Use different Email IDs for each report. When you select one of the two chck boxes, the fields to enter therecipient Email IDs will appear. In case you want to Email the reports to multiple recipients, specify the Emails IDsseparated by commas. (for example: [email protected], [email protected]).
Edit Email Subject - You can customize the subject of the Emails by clicking on the Edit Subject link. It will
take you to a separate pop up where you can specify the subject. For constructing the Email subject, you can useplace holders that will be substituted when the Email is constructed. Like for example, if you want the subject tobe: StoreGrid Backup Report from the server: backupserver1.datamaniacs.com where StoreGrid is the product nameand backupserver1.datamaniacs.com is the backup server name, you can specify the Email subject as:'PRODUCT_NAME Backup Report from the server: SERVER_NAME' - PRODUCT_NAME and SERVER_NAME are theplace holders.
Edit Email Header/Footer - You can edit the Email header and footer for success and failure reports byusing this link. The specified header and footer content will be added at the top and at the bottom of the Emailcontent. You could specify the header and footer in HTML as well.
You can also configure the conditions in which the reports should be sent by accessing the 'Email Filters' page through themenu "Settings->Email Filters".
Send File list with the Backup Report - This is the option to send the protected, skipped and deleted files list asattachment with the client backup email reports. The files list will be compressed as a zip archive file and then attachedwith the email report.
Protected Files - If this option is selected, the protected files list will be attached with the client's backup emailreport.
Skipped Files - If this option is selected, the skipped files list will be attached with the client's backup emailreports.
Deleted Files - If this option is selected, the deleted files list will be attached with the client's backup emailreports.
User Management
Overview
This page lists all the users, checks privileges and create new users for accessing the StoreGrid WebConsole.
How to get here in the StoreGrid Web Console? In the top menu, select: "Settings ->User Management".
User Management
Create User - This section is to create a new user for accessing the StoreGrid Web Console. Provide the followingdetails and click the Create User button.
Role : By default, set to 'Admin', as only Admin users are created from this page. Users forReseller/Customer/Client are created when Add Reseller/Customer/Client operation is performed. You can also Edita Reseller/Customer/Client to enable Web Portal access.
User Name : Logon name of the new user.
Access Privilege : To select the access privilege of the new user, Full access or Read-Only access. This field isapplicable on the Client-Only installation, as the Read-Only access user is available only in client.
Password : Password for the new user.
Confirm Password : This field is used to confirm that the password for the new user is entered correctly.
List of Users- This section lists all the users and their access privileges.
User Name : Name of the user.
Role : Role of the user [Admin/Reseller/Customer/Client].
Accessed By : The Admin/Reseller/Customer/Client name who uses this logon to the Web Portal.
Access Privilege : Access Privilege provided for the logon user. For example, Web Portal/Web Service and allFull Access, Web Portal only Access, Web Service only Access, only access to Server Lookup Web Service, Read-Only Access to Web Portal or Denied Access to any Service etc.,)
Actions : The following actions are available for each User.
Change Password : This action can be used to change the password for the currently logged in andother login users. The current user should know the old password in order to update. For other users, theold password is not required. Also, the current user should have enough permission to change the otheruser's password.
Delete User : This action will remove the User Access credentials for the logon user.
NOTE : For the Client users, this action simply updates the User Privileges to ServerLookup WebServiceonly. This is to facilitate the client's to connect for ServerLookup WebService to identify the Server ClusterNode to backup to.
Limitations
You cannot delete the logon user using which you are currently logged in.
MySQL Settings[For Windows]
Overview
StoreGrid can be configured to backup the MySQL Database(s) available in the local machine. StoreGrid uses the internalMySQLDump utility (mysqldump.exe) to backup MySQL Database(s) and it uses the MySQL Exe (mysql.exe) to list thedatabase names in "Backup -> Plugin Backups -> MySQL" page.
In Windows, before a MySQL backup can be configured in StoreGrid, you should configure the MySQL settings. Withoutcorrect values for these settings, StoreGrid will not be able to list the databases to be configured for backups.
This section explains how to configure the MySQL settings so that StoreGrid can list the MySQL database(s) in "Backup ->Plugin Backups -> MySQL" page(For Windows).
How to get here in the StoreGrid Web Console? In the top menu, select: "Settings->MySQL Settings".
MySQL Settings
In Windows, before a MySQL backup can be configured in StoreGrid, you should configure the MySQL settings from"Settings->MySQL Settings" menu. With the values entered in the MySQL settings, StoreGrid will create a backup dump ofthe MySQL database.
MySQL Server NameThis is a non-editable field. "localhost" will be used as the value.
MySQL Server Instance PortBy default MySQL server uses port 3306. But MySQL supports running multiple instances and in that case eachinstance will be using its own port. If you have just one instance of MySQL running, simply enter the port numberhere or leave the default as it is and save it. But if you have multiple MySQL instances running, then you canprovide the ports for all the instances in the following manner:
Once you have configured one port for one of the instances and saved it, this field will have two options "1.Choose a port from the list" and "2. Add an additional port".
By selecting "Add an additional port" you can add additional ports for other MySQL instances running.
By selecting "Choose from the list", you can select any one of the ports already configured. This step is requiredbefore you configure MySQL backup from the "Backup -> Plugin Backups -> MySQL" page. Depending upon theMySQL instance for which you want to configure the backup, you should first select the appropriate port, save itand then go backup to "Backup -> Plugin Backups -> MySQL" page to configure MySQL backup for that instance.The MySQL databases listed in the "Backup->Create MySQL Database Backup" page (For Windows) will be for theMySQL Server instance whose port was last selected and saved from this MySQL settings page.
MySQL EXE PathEnter the location of the mysql.exe file for the mysql server instance in the local machine. For example, ifmysql.exe file is present in the "C:/Program Files/MySQL/MySQL Server5.0/bin/" folder, then enter "C:/ProgramFiles/MySQL/MySQL Server5.0/bin/" as this field value. Please note that exe file name "mysql.exe" should not beappended to the path value.
MySQL Dump EXE PathEnter the location of the mysqldump.exe file for the mysql server instance in the local machine. For Example, ifmysql.exe file is present in the "C:/Program Files/MySQL/MySQL Server5.0/bin/" folder, then enter "C:/ProgramFiles/MySQL/MySQL Server5.0/bin/" as this field value. Please note that exe file name "mysqldump.exe" should notbe appended to the path value.
MySQL User NameProvide the MySQL server instance authentication user name here. Note that each instance can have its ownauthentication user name and password. Make sure you give the correct user name matching the MySQL serverinstance you have chosen in the "MySQL Server Instance Port" field.
MySQL PasswordProvide the MySQL server instance authentication password here. Note that each instance can have its ownauthentication user name and password. Make sure you give the correct user name matching the MySQL serverinstance you have chosen in the "MySQL Server Instance Port" field.
The option "Continue with previous authentication for this MySQL Server Instance" is provided if a username and password have already been configured for the MySQL server instance. By default "Yes" option isselected and the "No" option could be used to change the previously saved "User Name" and "Password" values.
Temporary location to store the backup dumpsEnter the location/directory path to which the mysql database dumps has to be stored temporarily before uploadingto the backup server. Please ensure that you have enough disk space in the configured temporary location (wherethe backup dump has to be saved). Please note that, backup dumps stored in the temporary location will bedeleted once backup dumps are transferred successfully to the remote backup server.
Once these MySQL settings are correctly configured and saved, the tree in the "Backup -> Plugin Backups -> MySQL" pagewill display the option to configure a mysql database backup.
Troubleshooting Tips
Database names is not listed in "Backup -> Plugin Backups -> MySQL" page(for windows).
Cause 1: If MySQL Settings for StoreGrid is not configured.
Solution : Configure MySQL settings from "Settings" menu "MySQL Settings" icon in the left hand side and then checkif MySQL database(s) are listed in the "Backup -> Plugin Backups -> MySQL" 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 -> Plugin Backups -> MySQL" page (for windows).
Cause 3 : When the last time MySQL Settings was saved for mysql server instance port, MySQL Exe path field valuewas 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 "<INSTALLATION_HOME>/plugins/MySQLServer/" folder does not havethe database list.
Solution : Check the MySQL version running in the machine (4.x or 5.x). StoreGrid only supports listing MySQL 4.xand 5.x database(s) for backup.
Database names are listed in "Backup -> Plugin Backups -> MySQL" page(for windows), butdump is not created.
Cause : Entered 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 abackup dump of the database(s).
Limitations
1. Databases listed in the "Backup -> Plugin Backups -> MySQL" page(For Windows) will be for the the last savedMySQL Server instance port in the MySQL Settings.
2. MySQL Settings edited/modified will not affect the mysql database backup schedules configured previously andchanges 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.
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 byStoreGrid and therefore that may not be listed. To resolve this, you can map the drives in this page and then used themapped drives to configure backups from them.
How to get here in the StoreGrid Web Console? In the top menu of Backup Server, select: "Settings -> Mapped Drive Settings".
Mapped Drive Settings
1. Install StoreGrid as a Service with the administrative privileges.
2. Go to the 'Settings -> 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 toinclude files and folders in them. The mapped drives will be listed in other pages as well, e.g. 'Server Settings'page, 'Seed Backup 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. Forexample, 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 ofthat 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.
Configure Automatic Software Updates for Backup Server(fromReplication Server)
Overview
From StoreGrid v2.4, backup server can automatically download updates from the replication server and upgradethemselves. The updates have to be first uploaded in the replication server and then the uploaded files have to be selectedfrom the replication server web console. The backup server machine will check the replication server for available updatesevery one hour (when there is no activity in the backup server). If an update is available in the replication server, it willautomatically download and install it, when there is no client or server activity in the backup server. The backup server willdownload and update only the compatible updates from the replication server.
How to get here in the StoreGrid Web Console? In the top menu, select: "Server Management -> Software Update -> Configuration" page.
Configure Automatic Software Updates
Software update from replication server is enabled by default from StoreGrid v2.4. But to do automatic software updatefrom replication server to backup server, the replication server is to be chosen manually.
If the user has manually disabled software update in the backup server, then it is not enabled by default when the serveris upgraded to a higher version. The user will have to manually enable it to make it functional again.
Turn on Automatic Software Update: Select this option to enable Automatic Software Update. Once enabled,backup server will check with the replication server every one hour for the availability of new updates. If updatesare available in the replication server (selected below), it will automatically download it to the location (specifiedbelow) and then install the updates and restart StoreGrid automatically.
Select the server to download update(s) from: In this page, both the backup server and replicationserver will be listed. You can select the replication server from which the backup server will download theupdates.
Specify the location to store downloaded update(s): The location in the backup server system wherethe downloaded updates will be stored. Make sure StoreGrid can write to that location. By default, StoreGridwill store the downloaded updates in the "<SG Home>/downloadedUpdates/" folder.
Turn off Automatic Updates: This option is to disable the automatic software update feature.
Troubleshooting Tips
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.
StoreGrid Configuration
You can change some of the basic configuration of StoreGrid by editing theSGConfiguration.conf file located under the conf/ directory.
If the entries in SGConfiguration.conf file is changed, you should restart StoreGrid.
A sample SGConfiguration.conf file is as follows
< StoreGrid ID="lewis" IPAddress="">
<Configuration><Module StartModule="601" ThreadCount="1" KeepAliveEnabled="1" KeepAliveTime="60"EncodeOption="1" ReconnectionEnabled="1" ReconnectionAttemptCount="-1"ReconnectFileUploadAttemptCount="5" FlushSend="1" IdleSocketTimeOutInterval="1800"ClientReconnectTimeOut="120" ServerReconnectTimeOut="180" SGTempLocation=""/><Restore KeepAliveEnabled="1" KeepAliveTime="60" ThreadCount="1"RestoreLocation="restoreData" CompressLocation="restoreData" DocumentRootEnabled="0"DocumentRootPath="" /><BackupDBStorageLocation Option="0" Path=""/><DBStorageLocation Path="C:\Program Files\ Vembu\StoreGrid"/><Process Priority="32"/><Debug DebugPrint="0"/><DiskUtil ProcessBytesFactor="1" DisableDiskUtil="0" ReadBuffer="10000"WriteBuffer="10000"/><Ports Server="32004" GUI="32005" SSLServer="32007" MAPI32Bit="32008" /><Replication Enabled="1" ThreadCount="-1" KeepAliveEnabled="1" KeepAliveTime="60"/><RepPRPDBStorageLocation Option="0" Path=""/><BackupMetaData Enabled="0" TimePeriod="0"/><ListFile ElementCount="500" FilesPerPRPCheckSleep="20"/><MMAPRead Enable="0" MaxFileSize="524288"/><MMAPWrite Enable="0" MaxFileSize="524288"/><DeleteSchedule Count="5"/><Retention ThreadCount="2"/><SSL Enabled="0" SSLCertFile="conf/ssl.crt.pem" SSLKeyFile="conf/ssl.key.pem"/><SGEmailLogo Enabled="1"/> <MissedScheduleConfig GraceTime="3600"UpdateNextScheduleTime="1"/><SGTimeOutConfig BackupAck="120" Authorization="120" FileAck="120" ResetPrevBackup="30"/><Database UseODBC="1" DSName=" StoreGridDB" UserName="storegrid" Password="storegrid"ConnectionPooling="1" DatabaseName=" StoreGridDB" HostName="localhost" SplitDatabase="1"SplitLevel="2" /><S3Backup Enabled="1" AccessKey="" SecretKey="" BucketName="backup-server-bucket" UseSSL="1"UploadCache="D:\ StoreGridCache" DownloadCache="" DebugTrace="0" UploadThreadCount="5"MaxFileSize="524288000" StorageClass="1" /><Migration ThreadCount="5" /><Cluster ClusterName="[email protected]" NodeLookupNameIP="" Enabled="1" AlgorithmType="1"NodeAllocatin="1" NodeHealthStatusTimeout="600" /><ServerLookup Enabled="1" SSLEnabled="1" HTTPPort="6060" HTTPSPort="6061" /><BackupServerMetaData Enabled="1" Path="C:\Program Files\ Vembu\StoreGrid"BackupDBEnabled="1" >
<Schedule Type="Daily" Day="0" Hour="0" Mins="0" />
</BackupServerMetaData> <SGTrash Enabled="1" /> <ConsolidatedReport Hours="" Mins="" />
</Configuration>
</ StoreGrid>
Changes made in 4.2.0
1. Added 'StorageClass' attribute in the 'S3Backup' tag for storing S3 Storage Class infrastructure where the attributevalue set to 1 means STANDARD and the value set into 2 stands for REDUCED_REDUNDANCY S3 Storage class.Currently this attribute will be populated at the time of Replication UI configuration.
Changes made in 4.0
1. Added 'ConsolidatedReport' tag with an attribute 'Hours' and 'Mins' to configure required time to send ConsolidatedCustomer report. By default the Consolodated Customer report will be sent at 11:57 pm daily/weekly/monthly.
Changes made in 3.2
1. Added 'SGTrash' tag with an attribute 'Enabled' to enable or disable the StoreGrid trash. When it is enabled, thebackedup files removed due to retention cleanup, full-backup cleanup and delete-backup cleanup are moved to theSGTrash ( by default, the SGTrash location is the backup location). When it is disabled, the files are deletedpermanently from the system. By default, the SGTrash is enabled.
Changes made in 3.1
1. Added 'TimeDelay' attribute in 'Module' tag to start StoreGrid process after a delay when the machine is rebooted (ifStoreGrid is run as a service) or when the user has logged in (if StoreGrid is run as an application under that user).The value of 'TimeDelay' attribute is in seconds and StoreGrid will wait for that many seconds before starting.
Changes made in 3.0
Changes done in StoreGrid Backup/Replication Server
1. Database tag introduced to configure ODBC datasources for storing StoreGrid's metadata. This tag is an alternativeto the embedded RBDMS engine (SQLite, www.sqlite.org) used by StoreGrid. StoreGrid only supports mysqldatabases as ODBC datasources initially. This will be expanded to other databases (PostGRESQL, Oracle, MS SQL,etc.) in future.
2. Cluster tag added for configuring Cluster of StoreGrid Server and Replication Server.
3. ServerLookup tag added for configuring servers to lookup for the relevant StoreGrid Replication Server in thecluster.
4. BackupServerMetaData tag introduced to dump backup server database data as sql files for redundant backup.
5. Restore tag is added with two attributes, "RestoreLocation" & "CompressLocation" where
"RestoreLocation" mentions the Path where server side restore from various web-access roles(Reseller/Customer/Client) are performed.
"CompressLocation" mentions the Path where server side restored zip files are stored.
Changes done in StoreGrid Clients
1. ServerLookup tag added for configuring clients to lookup for the relevant StoreGrid Backup Server in the cluster.
2. ProcessBytesFactor attribute added in the DiskUtil tag to increase the total number of bytes processed in one-passin the client.
Changes made in 2.5.5
StoreGrid MySQL sharding related changes under <Database> tag.
Changes done in StoreGrid Backup/Replication Server.
a. 'SplitDatabase' attribute is to specify enabling/disabling sharding in MySQL database (Sharding is nothing butsplitting up of large numer of database entries/rows in to multiple database(s) based on the 'SplitLevel'). It takesvalue of 0/1. By default, it is 1.
b. 'SplitLevel' attribute is to specify the level of sharding to be used in MySQL Server ie., Server/Client/Backup level.It takes value of 0/1/2.
If SplitLevel=0 (Server level sharding), single MySQL database is used for the whole backup/replicationserver.If SplitLevel=1 (Client level sharding), separate MySQL database for each clients in the backup/replicationserver.If SplitLevel=2 (Backup level sharding), separate MySQL database for each backups in the backup/replication
server.
By default, it takes value '2' ie., backup level.
Added number of simultaneous migration thread counts under <Migration> tag.
a. 'ThreadCount' is the number of simultaneous backups to be migrated during v2.5.5 migration. By default, it is 5.
Changes made in 2.5
Changes done in StoreGrid Backup/Replication Server.
StoreGrid ODBC related configurations to connect to MySQL Server under <Database> tag.
a. 'UseODBC' attribute to enable/disable external database support. By default it is set to 1. In StoreGrid v2.5, onlyMySQL is supported as the external database.
b. 'DSName' attribute is the system DSN Name to connect to the MySQL Server.c. 'DatabaseName' attribute is database name in the MySQL Server which StoreGrid uses to store its metadata.d. 'UserName' is the MySQL user name which StoreGrid uses to connect MySQL Server.e. 'Password' is the MySQL password which StoreGrid uses to connect MySQL Server.f. 'ConnectionPooling' is to enable/disable pooling of connection to MySQL Server. By default, it is set to 1. It is
recommended to be set as 1 for smooth functioning of StoreGrid with ODBC.
StoreGrid Amazon S3 related attributes are added under <S3Backup> tag.
a. 'Enabled' attribute to enable/disable storing the backup files to Amazon S3 using the local hard drive as atemporary local cache. It takes the value of 0/1.
b. 'AccessKey' attribute is the access key of your AWS (Amazon Web Services) account which StoreGrid uses toupload/download the files from Amazon S3.
c. 'SecretKey' attribute is the secret key of your AWS account which StoreGrid uses to upload/download the files fromAmazon S3.
d. 'BucketName' attribute is the name of the Amazon S3 bucket where the backup data are stored.e. 'UseSSL' attribute is the option to enable/disable SSL tranfer for communication with Amazon. By default, this is
set to 1.f. 'UploadCache' attribute is the temporary local location in your hard disk (or) external drive where the backup data
are temporarily stored before uploading the files to Amazon S3.g. 'DownloadCache' attribute is not currently used. The upload cache location itself is used as the download cache.h. 'DebugTrace' attribute is to enable/disable debug prints for Amazon S3 upload progress.i. 'UploadThreadCount' attribute is the number of threads StoreGrid should use to progress the backup files in the
local cache location to upload to Amazon S3. By default, it is set to 5.j. 'MaxFileSize' is the maximum file size (in bytes) that StoreGrid should not exceed while storing the files in Amazon
S3. By default, it is set to 500 MB.
Changes made in 2.4
1. Added 'SGTempLocation' attribute to specify the location for creating StoreGrid temporary files. The default value of'SGTempLocation' attribute is < StoreGrid Home> path.
2. Added 'MAPI32Bit' attribute in the Ports tag.
3. Added 'Retention' tag to control the number of simultaneous retention threads to cleanup the old files in the backupserver.
Changes made in 2.3.5
1. ServerReconnectTimeOut changed from 1500 to 180 seconds
2. ReadBuffer changed from 100000 to 10000
3. WriteBuffer changed from 100000 to 10000
4. StoreGrid Timeout Settings <SGTimeOutConfig> tag added. It has the following attributes
a. BackupAck : Timeout period in seconds for which StoreGrid client will wait to receive the backup initializationacknowledgments from the backup server. By default this value is 120 seconds
b. Authorization: Timeout period in seconds for which StoreGrid client will wait for backup serveracknowledgments during the authorization process. The default value is 120 seconds.
c. FileAck: Timeout period in secs for which client will wait for acknowledgments sent from the backup serverafter completing backup of a file. The default value is 120 seconds.
d. ResetPrevBackup: If the previous backup schedule of a particular backup job is in active state in the backupserver when the next incremental backup is scheduled, StoreGrid will try to reset the previous backupschedule and continue the current backup schedule. By default, StoreGrid will take 30 secs to reset theprevious backup schedule. If it fails, then the current backup schedule will be aborted with the error "Backupin progress".
5. Missed Schedule Configurations <MissedScheduleConfig> tag added. It has the following attribute:
GraceTime: From the 2.3.5, backup server will monitor all the clients’ backup schedule and alert the user ifany of the backup job misses the backup schedule. The backup server will report the backup schedule asmissed only if the client doesn't connect to the backup server within the Grace Time. By default, the Gracetime value is 3600 secs (1 hr).
StoreGrid ID
While installing StoreGrid, you can specify the StoreGrid ID. By default, it takes your machine name as the StoreGrid ID.You can change the StoreGrid ID by editing the attribute " StoreGrid ID=".( StoreGrid ID="<New StoreGrid ID>").
IP Address
By default "IPAddress" tag is "0"and StoreGrid uses the primary IP of the machine in which StoreGrid is installed.
In case of using virtual IP Address, you can change the IP Address in which StoreGrid should run. This can be done byEditing the attribute "IPAddress=". (IPAddress="<New IPAddress>").
Start Module
The StoreGrid mode (i.e. Client-Server,Client,Server,Replication Server) specified during installation can be changed byediting the attribute"<Module StartModule= >". (StartModule="<New Mode>") Various modes are:
Client = 602Server = 601Replication Server = 609
Multi-threaded backup scheduling:
From StoreGrid 2.1.1 version, StoreGrid supports multi threaded backups. i.e., if there are more than one backup to bescheduled at the same time, then all these backup schedules can be scheduled simultaneously from multiple threads.
You can control the maximum number of backup schedules that can run at the same time by modify the maximumnumber of backup threads. Follow the steps below to change this settings:
1. Stop the StoreGrid application.2. Open the "[ StoreGrid Home]/conf/SGConfiguration.conf" xml file in a text editor.3. Edit the "<StoreGrid< StoreGrid>gt;<Configuration><Module>" tag "ThreadCount" attribute value to maximum
ThreadCount value.4. Save and close the configuration file.5. Restart the StoreGrid application.
ThreadCount
It is related to running multiple backup schedules at the same time. By default StoreGrid will run only one backupschedule at a time. You can edit the attribute "<Module ThreadCount="(ThreadCount="<New ThreadCount>").
For example if the "ThreadCount" is 3, StoreGrid will have the capability to run three backup schedules simultaneously. Ifyou want StoreGrid to run infinite number of backup schedules at the same time, give the ThreadCount as -1.
Priority
StoreGrid tries to use the available system resources to run the backups.
You can configure the StoreGrid Process Priority as required. By default priority is set to normal.(<ProcessPriority="32">)
Priority = 64 ; LowPriority = 32 ; NormalPriority = 128 ; High
Debug Print
It is used to print the debug prints. Set it to 1 if you want StoreGrid to print the debug messages in the console.
Disk Util
This tag configures the StoreGrid interactions with Disk I/O and also helps in listing out disks available for StoreGrid.
The <DisableDiskUtil> attribute helps configuring the OS based Disk Util which lists out the mount points availablein the StoreGrid Server. The various values available for DisableDiskUtil attribute are:
0 - The Disk Util follows Operating System based APIs to list the mount points
1 - The Disk Util uses the configuration file "< StoreGrid_Home>/conf/diskinfo/<host name>/diskinfo.sdif" toparse the available mount points. This file has to be populated manually.
2 - The Disk Util follows Linux/MAC based command-line tools to list down the available mount points. Thisvalue should only be used on Linux/MAC operating systems.
The <ProcessBytesFactor> attribute sets the number of blocks to be processed at the same time for backup inclient.
The <ReadBuffer> attribute provide the number of bytes to be cached before processing the backups in client. The<WriteBuffer> specifies the number of bytes to be cached before a Disk I/O operation to be performed per backupfile entering the StoreGrid server.
Ports
By default StoreGrid uses 32004 port for backup and TCP Discovery. If you want to change this port edit the attribute"Ports Server=". (Ports Server="<New Port Number>").
Similarly StoreGrid uses 32005 port for UI and you can change this by editing the attribute "Ports GUI=". (PortsGUI="<New GUI port Number>").
The default SSL port on which client will communicate with the backup server is 32007. You can change the SSL portnumber by editing the attribute SSLServer="<New SSL Port Number>". Please note that SSL is by default disabled. Toenable it, set the 'Enabled' attribute in the SSL tag to 1 in this configuration file.
In Windows 64 bit operating systems, StoreGrid uses it's 32 bit executable for backing up Exchange Server 2007 MailBoxdata. StoreGrid communicates it's 32 bit executable through the MAPI32BIT TCP port. The default MAPI32BIT port value is32008. In Windows 64 bit OS installed with Exchange Server 2007, you need to enable this MAPI32BIT port to backup theExchange Server MailBox data backup in the local firewall settings.
Replication
By default Replication feature is enabled "<Replication Enabled=1>"in the StoreGrid server. If the attribute "<ReplicationEnabled=0>" is changed to zero, the Replication feature will be disabled. After disabling the Replication feature in theSGConfiguration.conf file, Replication does not take place even when replication is enabled either in "Server Admin->Server Settings" or in "Server Admin -> Reseller Management -> Reseller [reseller name] -> List Of Customers" UIpage.
ThreadCount is related to running multiple replication schedules at the same time. By default StoreGrid can run infinitereplication schedules(ThreadCount="-1") simultaneously. You can edit the attribute "<ReplicationThreadCount="(ThreadCount="<New ThreadCount>") to limit the number of replication schedules StoreGrid can runsimultaneously.
For example if the "ThreadCount" is 3, StoreGrid can run three replication schedules simultaneously.For fresh installation of StoreGrid (since version 2.2.1) Thread count will be 5 in Linux machines and -1 in Windowsmachines.
ODBC Datasource Configuration
This option enables you to store the client's backup metadata to an ODBC Datasource. This can be configured using thenew <Database> tag available in StoreGrid. This tag has the following attributes :
1. UseODBC: This attribute is used to enable the ODBC storage of StoreGrid metadata
2. DSName: This attribute specifies the datasource name as configured in the ODBC Data Sources configuration in thesystem
3. UserName: This attribute specifies the username for authenticating the ODBC database connection for thisdatasource.
4. Password: This attribute specifies the password of the user for authenticating the ODBC database connection forthis datasource.
5. ConnectionPooling: This attribute specifies the configuration to use connection pooling in the ODBC. Thisconfiguration should always be enabled as '1' for optimal performance of the StoreGrid Server
6. DatabaseName: The database name of the datasource is specified in this attribute.
7. SplitDatabase: This attribute is to specify enabling/disabling sharding in MySQL database (Sharding is nothing butsplitting up of large numer of database entries/rows in to multiple database(s) based on the 'SplitLevel'). It takesvalue of 0/1. By default, it is 1.
8. SplitLevel: This attribute is to specify the level of sharding to be used in MySQL Server ie., Server/Client/Backuplevel. It takes value of 0/1/2.
a. If SplitLevel=0 (Server level sharding), single MySQL database is used for the whole backup/replicationserver.
b. If SplitLevel=1 (Client level sharding), separate MySQL database for each clients in the backup/replicationserver.
c. If SplitLevel=2 (Backup level sharding), separate MySQL database for each backups in the backup/replicationserver.
Backup Meta Data
If BackupMetaData is enabled(i.e. Enabled="1") all the metadata of the StoreGrid client will be backed up to the server. Bydefault StoreGrid client will backup the metadata once in a day( < TimePeriod="86400"). You can configure the timeinterval (days/hours/minutes/seconds) for the metadata backup as required. Note that the interval should be given inseconds.
Backup Server Meta Data
If BackupServerMetaData is enabled(i.e. Enabled="1") all the metadata of the StoreGrid Server will be redundantly dumpedin the StoreGrid Server. The <Schedule> tag specifies the schedule at which the metadata is dumped in StoreGrid Server.The <Type> attribute specifies the type of schedule, Daily/Weekly/Monthly. By default the Server metadata dump isenabled and configured for Daily dump. The <Day>, <Hour> & <Mins> attribute specifies the day, hour and minute whenthe dump should be initiated
In the <BackupServerMetaData> tag, the <BackupDBEnabled> attribute specifies the dump status for the sharded backupdatabases. These databases are dumped as soon as a backup process completes.
Retention
StoreGrid supports time based retention feature to cleanup the old files in the backup server. In the backup server, youcan control the number of simultaneous retention threads to cleanup the old files by setting the "ThreadCount" attributevalue. The default ThreadCount attribute value is 2.
List File Element Count
The List file element count value (ElementCount="500") configures the Backup Server to prepare the list file upto a filecount of 500 before creating the relevant work files for the same. This groups the list files into separate file groups andlets the backup- database-update thread process a work file of a limited size and file count for each database transaction.
Application Level Keep Alive Time
If you are getting "SG0083: Unable to send backup details to server <Server Name>......" error message in client BackupReport, then you can solve this problem by configuring the application level keep alive time in the 'SGConfiguration.conf'file (instead of changing the registry keep alive time). Please note that this error message will occurs when the connectionbetween client and server is closed prematurely by an external force, while StoreGrid Client is actively sending backup data
to the Backup Server. The external forces may be Anti virus software, Intrusion detection software, NAT/Firewall timeoutsettings, Internet link Error.
You can configure the application level keep alive time in StoreGrid by changing the following attributes value in the '<StoreGrid_HOME>\conf\SGConfiguration.conf' file.
1. By default, application level Keep alive will be disabled. If you want to enable application level keep alive to preventconnection closure between StoreGrid Client and Backup Server, then you need to set the 'KeepAliveEnabled'attribute value under the <Module> tag to '1'.
In short manner,
If 'KeepAliveEnabled' = 0, then application level keep alive is disabled.If 'KeepAliveEnabled' = 1, then it is enabled.
2. After enabling the application level keep alive, You need to set 'KeepAliveTime' attribute value under the <Module>tag.
The 'KeepAliveTime' is the time interval at which the StoreGrid will send the keep alive protocol, if no data istransferred to the Backup Server within the interval. The 'KeepAliveTime' value is based on seconds. We suggestyou to edit the 'KeepAliveTime' value as less than 180 seconds(ie 3 minutes).
Similarly, if the socket problem occurs for restore/replication, you can configure the keep alive time forrestore/replication by changing the 'KeepAliveEnabled' & 'KeepAliveTime' attribute under the respective <Restore> ,<Replication> tag in the '< StoreGrid_HOME>\conf\SGConfiguration.conf' file.
Communication over SSL between Client, Backup Server and ReplicationServer
From v2.3, StoreGrid supports SSL communication between Client, Backup Server and Replication server. SSL providesadditional data security on top of data encryption when the data is in transition between one machine to another. Bydefault SSL is disabled. You can enable it my editing the Enabled attribute in the SSL tag as <SSL Enabled="1"SSLCertFile="conf/ssl.crt.pem" SSLKeyFile="conf/ssl.key.pem"/>.
Reestablishing the connectivity after interruption
From v2.3, StoreGrid can reestablish the connection once it has been interrupted due to a network error. The StoreGridclient will try to reestablish the connect by creating another socket connection while maintaining the same session with thebackup server. The client will try to reconnect for the time as defined by the 'ClientReconnectTimeOut' attribute in the'Module' tag, after which the client will abort the connection. The number of times the client should retry to establish theconnection is defined by the 'ReconnectionAttemptCount' attribute, default been -1 (no limit). The number of seconds thatthe Backup Server will wait for the client to reestablish the connection is defined by the 'ServerReconnectTimeOut'attribute, default been 180 seconds. This feature can be disabled by setting the 'ReconnectionEnabled' attribute in the'Module' tag to 0. By default it is enabled.
Idle session cleanup in the Backup Server
From v2.3, StoreGrid Backup Server can cleanup the client connections if the connections are idle for a certain amount oftime. This timeout period is by default 1800 seconds (30 minutes) and is defined by the 'IdleSocketTimeOutInterval'attribute in the 'Module' tag. When the client is not sending any data (like for example, when it is checking the changedbytes of a modified file), it will send the KeepAlive messages (if enabled) to keep the connection active. When aninterruption in the connection occurs, the Backup Server will wait for the timeout period to check if it receives anymessages, after which it will cleanup the session. Till the time the Backup Server cleans up the session, the backupschedule from the client will show up as 'Active' in the backup server.
Embedding a logo in the Email Reports
From v2.3, the logo that is sent in the Email Reports can be disabled by changing the 'Enabled' attribute in the'SGEmailLogo' tag to 0. By default it is enabled.
Configuring Server to run in Cluster
From v3.0, you can configure the Server to run in a cluster by enabling Cluster using the 'Enabled' attribute in the 'Cluster'tag to 1. During installation the Cluster configuration option automatically configures this attribute. You have to mentionthe Cluster Name with attribute 'ClusterName' to enable registering this Server instance to the StoreGrid Server Cluster.The detailed list of the attributes and their purpose are:
1. ClusterName: This attribute specifies the name of the cluster to register the cluster nodes to.
2. Enabled: This enables the clustering of the StoreGrid Server deployment
3. ClusterAlgorithm: The algorithm to be used to assign clients for the specific Server in the cluster. StoreGrid nowsupports only the Node Locked algorithm, for which the value is 1.
4. NodeAllocation: This attribute determines whether to hold a specific domain for a particular StoreGrid Server. Ifthe attribute is configured as '0' then, the StoreGrid cluster holds the domain for the particular Server in the cluster.Hence, if the Server goes down and comes back up, the domain remains intact for the server. If the configuration isdynamic, i.e., '1', then the domain allocation is removed when the server goes down.
5. NodeHealthStatusTimeout: This is the timeout value after which the other Cluster Nodes will reset the healthstatus of the affected Cluster Node as 'Down'. Normally, the Cluster Node will update the Health status with theuptime and general health parameters within this timeout period.
Configuring Client/Backup Server to Lookup Backup/Replication Server in aBackup/Replication Server Cluster
From v3.0, you can configure the Client/Backup Server to lookup a particular StoreGrid Backup/Replication Server instanceto connect for Backup/Restore/Replication. Using the new tag named 'ServerLookup', you can enable the lookup for theexact server instance to whom StoreGrid should connect for Backup/Restore/Replication.
The Server returns the DNS Lookup name of the Server, ip address of the Server as well as the port to connect forBackup/Restore/Replication. The Server Lookup is a webservice on the Backup/Replication Server cluster, hence you haveto configure whether to use HTTP/HTTPS with the attribute SSLEnabled (0 - HTTP, 1 - HTTPS) and the WebServer's portsto connect for the WebService with the attributes HTTPPort and HTTPSPort.
SGTrash Recovery
Deleted clients and deleted backups can be recovered from SGTrash location using command line options. Below are thedetails about SGTrash recovery command line parameters and examples.
Windowsbin\ StoreGrid.exe RecoverTrashedData <SGTrashLoc> <RecoveryLevel> <RecoveryGroupName><ParentName>
Linux./bin/ StoreGrid RecoverTrashedData <SGTrashLoc> <RecoveryLevel> <RecoveryGroupName><ParentName>
* SGTrashLoc - <SGTrash_location>/1 * RecoveryLevel - 3 (Client Level)/4 (Backup Level) * RecoveryGroupName - Clientname/Backupname * ParentName - Clientname(Mandatory parameter for backup recovery)
NOTE : Recovered backups will be in "Deactivated State".
Recover a Client
To recover a client from SGTrash run the below command from StoreGrid installation location.
Windowsbin\ StoreGrid.exe RecoverTrashedData <SGTrashLoc> 3 Client_Name
Linux./bin/ StoreGrid RecoverTrashedData <SGTrashLoc> 3 Client_Name
Eg:-
* SGTrashLoc - C:\SGTrah\1(for windows) and /home/SGTrash/1(for linux) * RecoveryLevel - 3 (Client Level) * RecoveryGroupName - testclient(Client Name)
Windowsbin\ StoreGrid.exe RecoverTrashedData C:\SGTrah\1 3 testclient
Linux./bin/ StoreGrid RecoverTrashedData /home/SGTrash/1 3 testclient
By executing the above commands you can recover the testclient from the SGTrash.
Recover a backup
To recover a particular backup from SGTrash run the below command from StoreGrid installation location
Windowsbin\ StoreGrid.exe RecoverTrashedData <SGTrashLoc> 4 Backup_Name Client_Name
Linux./bin/ StoreGrid RecoverTrashedData <SGTrashLoc> 4 Backup_Name Client_Name
Eg:-
* SGTrashLoc - C:\SGTrah\1(for windows) and /home/SGTrash/1(for linux) * RecoveryLevel - 4 (Backup Level) * RecoveryGroupName - testbackup(Backup Name)
* ParentName - testclient(Client name - Mandatory parameter for backup recovery)
Windowsbin\ StoreGrid.exe RecoverTrashedData C:\SGTrah\1 4 testbackup testclient
Linux./bin/ StoreGrid RecoverTrashedData /home/SGTrash/1 4 testbackup testclient
By executing the above commands you can recover the testbackup from the SGTrash under testclient.
Please note that recovered data from the SGTrash location are only for restore purpose. After successful restore you candelete those recovered data from the StoreGrid backup server using server side client delete or backup delete.
Frequently Asked Questions
1. StoreGrid reports an error "Unable to list the Exchange mailbox users. Make sure sufficient permissions areavailable for the user account under which StoreGrid service is running. Exchange Mail Level Backup requires theuser account to have 'Full Control' access to the Exchange Server to list the mailbox users." while trying toconfigure mailbox level backup.
2. StoreGrid reports an error "Unable to list the Exchange mailbox users..." when trying to configure mailbox levelbackup in 2007 Exchange server (64 bit) machines.
3. How is StoreGrid different from other desktop backup and laptop backup products?
4. Can StoreGrid be used to backup desktops and laptops to a dedicated backup server inside the intranet?
5. Can StoreGrid be used for Remote Backups?
6. I have given a daily backup schedule to run at 5.00 PM. But at times, StoreGrid seems to be running this backupschedule at other times as well. Why?
7. Why does my StoreGrid peer not discover other StoreGrid peers in my network automatically?
8. How does StoreGrid do Open File Backups?
9. Can the StoreGrid Client be installed on a NAS file server to back it up to user desktop machines or other dedicatedbackup servers?
10. What type of encryption does StoreGrid use to secure the data being backed up? How secure is my data?
11. What happens if I forget my backup encryption password?
12. Why does StoreGrid restart automatically even after I shut it down?
13. Does StoreGrid support backing up to peers over the internet?
14. When I click on StoreGrid Web Console, I am redirected to a search/directory page. Why does this happen and howdo I get around it?
15. If I shut down and restart StoreGrid after a period of time, will StoreGrid automatically detect modified files andnewly created files and back them up?
16. I need to backup a large amount of data over the internet and its taking too much time. Is there a better way?
17. I had backed up my data from my laptop to a server. But now I don't have my laptop (original machine) anymore.How do I restore my old data to my new machine?
18. My server was set up to backup data to a certain location. I now wish to change that location. How do I do this?
19. I'm currently using the Free Edition. I wish to move to StoreGrid Professional. How do I do this?
20. Sometimes when I try deleting an existing backup schedule, it takes a lot of time. Why is this?
21. I have backups scheduled in my laptop for a certain day and time. If the backup server is not powered on at thescheduled backup time, how do I ensure that StoreGrid in my laptop runs the backup as soon as the backup servercomes on?
22. What are 'additional full backups' and why do I need them?
23. How do I delete files & folders that I've backed up but no longer need. I've deleted them on my machine - butthey're still taking up space on my StoreGrid server?
24. I tried the Internet Explorer Settings preconfigured backup. While I expected it to just backup my bookmarks, itseems to be backing up a whole lot more?
25. Can StoreGrid work in any Linux distribution?
26. I know StoreGrid works across Windows, Linux, Mac, FreeBSD operating Systems. Does that mean the backups andrestore can also be done across different operating systems?
27. I see that StoreGrid uses the MySQL database. Can I replace the MySQL database in my backup server withPostgreSQL or MS-SQL Server etc?
28. When I try to login to the StoreGrid Web Console, I receive the following error message "The requested address isnot valid in its context"?
29. The menu bar is missing from the StoreGrid Web Console?
30. I am getting "Unable to send backup details to server <server name>. An operation was attempted on somethingthat is not a socket." error when running large number of files/Exchange Server/MS SQL Server/other plugin backupjobs. What to do now?
31. StoreGrid doesn't seem to run properly after upgrading Windows to Vista.
32. Error while dumping the Exchange Mail Boxes. Unable to create the PST file [or] "No new/modified files for backup"
33. Dump location does not have enough space to export the PST file
34. Error while creating the dump location <Dump_Location>
35. Users Mailbox/folder are not listed in the "Add Exchange Mailbox Backup" page.
36. I get the error "Windows Server Backup is not installed in your System. Please install and try again." When tryingto backup system state in Windows 2008.
1. StoreGrid reports an error "Unable to list the Exchange mailbox users. Make sure sufficient permissionsare available for the user account under which StoreGrid service is running. Exchange Mail LevelBackup requires the user account to have 'Full Control' access to the Exchange Server to list themailbox users." while trying to configure mailbox level backup.
If you encounter an error while accessing "Add Exchange Mailbox Backup" page in the StoreGrid webconsole, thenfollow 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 "<INSTALLATION_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 "Add Exchange MailboxBackup" page. However 'MSPST MS' service should be added in the MAPISVC.INF file to successfullybackup the Exchange users mailbox).
Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to accessthe mailboxes.
2. StoreGrid reports an error "Unable to list the Exchange mailbox users..." when trying to configuremailbox level backup in 2007 Exchange server (64 bit) machines.
StoreGrid uses Microsoft's MAPI client component installed in the Exchange Server to backup the ExchangeMailboxes. 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 accomplishthis, StoreGrid 32-bit exe requires Microsoft's 32-bit MAPI client component.
Please refer Granting Mailbox Rights document to get more details.
Top
3. How is StoreGrid different from other desktop backup and laptop backup products?
StoreGrid is a flexible backup solution that works with your existing hardware. This flexibility allows it to bedeployed in multiple modes - Service Provider Hosted Online Backup, Trusted Peer To Peer Backup and TypicalClient-Server deployments.
Service Provider Hosted Online Backup - Online Backup service providers including MSPs, VARs, SIs etc. can usethis deployment to offer an online backup service to their customers.
Trusted Peer To Peer Backup - StoreGrid provides an easy and intuitive mechanism to use the free space in userdesktops in a network for backup purposes. StoreGrid’s P2P deployment capability is based on the concept oftrusted peers in an intranet whose desktop space can be utilized in a peer-to-peer fashion.
Typical Client-Server deployments - This is a more traditional deployment - ideal for leveraging existing backupinfrastructure by allowing customers to include desktop and laptop data. All the desktops and laptops run theStoreGrid in Client mode only, and they all back up their data to a central backup storage server.
Another important feature of StoreGrid is the ease with which end users can configure backups and restore them,when required, without the help of system administrators. StoreGrid also allows centralized administration from aWeb Console (Browser based), to make it easy for system administrators to manage and monitor StoreGriddeployments.
Top
4. Can StoreGrid be used to backup desktops and laptops to a dedicated backup serverinside the intranet?
Yes, StoreGrid can be used to backup desktops and laptops to a dedicated backup server inside the intranet. Inthis deployment, the dedicated backup server(s) should run StoreGrid in server mode and desktops and laptopsshould run StoreGrid in client mode.
Top
5. Can StoreGrid be used for Remote Backups?
Yes, StoreGrid can be used to backup a computer to a Remote location provided the computer has directconnectivity to the Remote Backup server running StoreGrid. This facility is however not available in the FreeEdition!
Top
6. I have given a daily backup schedule to run at 5.00 PM. But at times, StoreGrid seems tobe running this backup schedule at other times as well. Why?
There are two reasons why StoreGrid will run a backup schedule at a time different from the configured scheduletime.
i. When StoreGrid is shutdown and restarted, it will run all backup schedules once before scheduling them atthe configured time. This is to ensure that any files created/modified when StoreGrid was shutdown arebacked up as soon as possible.
ii. If you selected "Attempt to run this backup every five minutes..." in Advanced options, and a backupschedule is incomplete because of various reasons (like network connection problem etc.), StoreGrid willschedule the backup every 5 minutes to ensure the backup schedule is completed as soon as possible. Inthis case, only after the backup schedule is completed will StoreGrid schedule it at the configured time.
Top
7. Why does my StoreGrid peer not discover other StoreGrid peers in my networkautomatically?
StoreGrid relies on multi-casting, UDP and TCP port scan to discover at least one StoreGrid Client/Server(peer)inthe network. But if multi-casting is disabled in the network, then discovery may be delayed because UDP or TCPport scans can be time consuming. Also, StoreGrid is configured to discover StoreGrid peers only in a subnet. Youcan manually discover a StoreGrid peer (both within and outside the subnet) using the "Add Peer" feature from theStoreGrid Web Console.If you are using Windows XP with Service Pack 2 installed, please click here.
Top
8. How does StoreGrid do Open File Backups?
StoreGrid can comfortably backup up files that are exclusively locked up or are being used by other applications atthe time of backup in Microsoft Windows OSes. StoreGrid supports Volume Shadow Service to backup the openfiles. If the operating system in use is supported by VSS (e.g., Windows XP and above OS versions), then simplyenable the VSS option when configuring a backup schedule. And if your operating system does not support VSS(e.g., Windows 2000), then you can backup Open Files with the help of StoreGrid’s Open File Backup Plugin. Thisplugin is pre-configured to allow StoreGrid process to access the open files.
Top
9. Can the StoreGrid Client be installed on a NAS file server to back it up to user desktopmachines or other dedicated backup servers?
StoreGrid can be installed on Linux or Windows based NAS servers. It is possible to backup a NAS file server overthe network to other user desktops or a dedicated backup server. If StoreGrid cannot be installed on a NAS filer, itwill be possible to install StoreGrid on a PC, mount the NAS server and then back it up. In the case of NAS fileservers, open file backup may not happen if a file is being continuously modified by an application. In WindowsStorage Server, it is possible to use the Volume Shadow Copy feature to support Open File backups. In NAS filerswhere files are not modified continuously StoreGrid's open file backup should suffice.
Top
10. What type of encryption does StoreGrid use to secure the data being backed up? Howsecure is my data?
StoreGrid uses the Blowfish encryption algorithm. You can get more information about blowfish algorithm athttp://www.schneier.com/blowfish.html
Excerpts from the blowfish website:"Blowfish was designed in 1993 by Bruce Schneier as a fast, free alternative to existing encryption algorithms. Sincethen it has been analyzed considerably, and it is slowly gaining acceptance as a strong encryption algorithm".StoreGrid will support other encryption algorithms as options in the future. As such your data is very secure asblowfish based encryption has never been broken before.
Top
11. What happens if I forget my backup encryption password?
Whoops! If you forget the backup encryption password, then there is no known way to decrypt your backed updata. So it is recommended that you write down the backup encryption password in a safe and secure place.
Top
12. Why does StoreGrid restart automatically even after I shut it down?
During installation, StoreGrid also installs a separate application called StoreGrid Tray. This application appears asan icon in your Windows Tray. If you want to stop the StoreGrid application, you need to stop it through the menuthat pops up while right clicking the StoreGrid Tray. If you stop the StoreGrid application in any other way,StoreGrid Tray will automatically restart the StoreGrid application. This feature is to ensure that StoreGridapplication is always running to protect your data even if it exits unexpectedly because of any bugs or otherreasons.
Top
13. Does StoreGrid support backing up to peers over the internet?
StoreGrid (Professional Edition) peers can communicate with each other and backup data over the internet if thereis direct connectivity between the peers. If the two peers are behind NAT, then you need to configure portforwarding in your NAT device to enable StoreGrid peers to connect to each other. If the two peers are just backingup to each other then you need to configure TCP port 32004 for port forwarding in your NAT device. Please checkthe "NAT/Firewall" configuration in the StoreGrid help documentation for more details.
Top
14. When I click on StoreGrid Web Console, I am redirected to a search/directory page. Whydoes this happen and how do I get around it?
Some toolbars and related software can take over your browser window even if you don't want them to!Uninstalling them usually solves the problem. Alternatively, you could manually type in the URL in your browser'saddress bar: http://machine-name:6060 where "machine-name" is the name of your machine, eg. http://joe:6060
Top
15. If I shut down and restart StoreGrid after a period of time, will StoreGrid automaticallydetect modified files and newly created files and back them up?
It depends on the settings you've selected when creating the backup schedule. StoreGrid will automatically detectall the modified and newly created files and back them up after a restart if:
i. You selected the continuous backup option
ii. You selected the ‘run every __ hours __minutes” option. In this case, StoreGrid will run this schedulewhenever it restarts, and thereafter schedule the next backup after the period you’ve selected.
iii. You’ve selected the “Run this Backup each time StoreGrid restarts” option in Advanced Options
Top
16. I need to backup a large amount of data over the internet and its taking too much time.Is there a better way?
Yes there is! Typically, your first backup takes the longest time/bandwidth. Thereafter, if you've enabledincremental backups (which you should be doing if you're backing up online), only changes in files/folders arebacked up. These incremental backups consume lot less time & bandwidth! StoreGrid has a feature that allows youto take the first 'heavy' backup locally to say, a USB Disk, physically move the data to a remote server, andthereafter seamlessly continue with incremental backups directly to the remote server. Details on using this featureare covered under the section 'Seed Backup Migration' in the Help Documentation. Please refer the following URL:PageHelp/server-side-seed-backup-migration.html
Top
17. I had backed up my data from my laptop to a server. But now I don't have my laptop(original machine) anymore. How do I restore my old data to my new machine?
If you want to restore your data from a new machine (new laptop), you can install StoreGrid on the new machinewith the same StoreGrid ID you used before. And you will first need to restore your Client configurations fromthe backup server before you restore your data from them (the backup servers). You can do this from the Restore-> Disaster Recovery page in the StoreGrid client webconsole. Once your configurations are restored, you canrestore your data from the Restore menu. Note that you will have to authenticate your new StoreGrid with theserver before the server will allow you to connect.
Top
18. My server was set up to backup data to a certain location. I now wish to change thatlocation. How do I do this?
By default, StoreGrid server uses the installation location or Server Backup Storage Location value configuredduring installation as the backup location to store the client's backup data. You can change the backup location ofthe server from the "Server Admin->Server Management-> Server Settings" page in the backup server's StoreGridwebconsole. But if you already have clients backing up to the server, then those existing clients will not use thenew backup location for further backups. The new location will only take effect for the new clients backing up tothe server.
You can also change the backup storage location for individual clients. The client's backup storage location can bechanged by going to ‘Server Admin -> Reseller Management -> <Reseller Name> -> <Customer Name> -> EditClient Configuration (action for the particular client)’ page in the backup server webconsole. For more details, pleaserefer the URL: PageHelp/client-backup-configuration.html
Top
19. I'm currently using the Free Edition. I wish to move to StoreGrid Professional. How do Ido this?
From StoreGrid v2.4 onwards, upgrading from Free edition to Professional edition is not directly supported. Forupgrading StoreGrid free edition to professional edition, you can save the Free edition backup data andconfigurations to another location. Then, uninstall free edition installation and install the professional edition buildafresh. After that, you can migrate free edition backup data to professional edition by using Seed Backup Migrationfeature.
Top
20. Sometimes when I try deleting an existing backup schedule, it takes a lot of time. Why isthis?
While deleting a backup, StoreGrid tries to connect to the server machine to delete the backed up data. So, pleaseverify that the server machine is accessible from the client machine and that StoreGrid is running on the Servermachine in "Server/ Server-Client" mode. The delete operation will be scheduled every 5 minutes. If a backup couldnot be deleted because of some reason (the backup server being down permanently, etc.) then the delete operationwill be rescheduled every5 minutes. There is no way to cancel the delete operation. It will be scheduled again evenwhen StoreGrid is stopped and restarted. Hence, ideally, StoreGrid must be running on the server machine forcompleting the backup delete schedule. In a 'not so ideal' situation, you could use the "Delete Backup Scheduleeven if the server is down" option from the "Delete Backup Data/Schedule" page. The backup configuration will bedeleted from the client side in the next delete schedule, ie about 5 minutes. Please note that the backed up data inserver might not be deleted by selecting this option.
Top
21. I have backups scheduled in my laptop for a certain day and time. If the backup server isnot powered on at the scheduled backup time, how do I ensure that StoreGrid in mylaptop runs the backup as soon as the backup server comes on?
Simply ensure that the " Attempt to run this backup every 5 minutes in case of non completion because of aproblem (Network error etc.) " box is ticked when you configure the backup schedule. This option is part of the'Advanced Options' that can be configured by clicking the 'Advanced Options' button under Step 5 (Scheduling) inthe 'Backup-->Add Backup Schedule' menu.
Top
22. What are 'additional full backups' and why do I need them?
Typically, you would take a first full backup and incremental backups thereafter. This way, only changes infiles/folders are backed up during future backups. However, in some cases, you may prefer to take a full backupevery once in a while for various reasons. StoreGrid supports this as well. Once you've decided your incremental
backup schedule, select the"Configure additional full backups" option and configure your full backups as required.This option is a part of the 'Advanced Options' that can be configured by clicking the 'Advanced Options' buttonunder Step 5 (Scheduling) in the 'Backup-->Backup Schedule' menu.
Top
23. How do I delete files & folders that I've backed up but no longer need. I've deleted themon my machine - but they're still taking up space on my StoreGrid server?
StoreGrid does not delete backed up files automatically when they are deleted in the client machine. InsteadStoreGrid will backup the fact that the files are deleted and the backup server will tag the files with thatinformation. But StoreGrid WebConsole UI provides a way to delete files permanently from the server. Please checkthe "Backup->Permanently Delete Files From Server" section in the StoreGrid help documentation to learn moreabout how to delete backed up files permanently from the server. Future releases of StoreGrid will have a featureto automatically delete files permanently from the server after a configurable time period.
Top
24. I tried the Internet Explorer Settings preconfigured backup. While I expected it to justbackup my bookmarks, it seems to be backing up a whole lot more?
The IE Settings backup is configured to backup all related to IE - history, temp files, security settings, etc - so ifyou need to restore, you get your IE exactly as it was earlier. If you wish to only backup the bookmarks file, yousimply need to configure this as any other file backup after manually selecting the file.
Top
25. Can StoreGrid work in any Linux distribution?
StoreGrid is well tested on Redhat 8.0, Redhat 9.0, Fedora Core 3, Fedora Core 4, Mandrake 10.x, SuSE 9.x, Debian4.x, Ubuntu 7.x. We expect StoreGrid to work in most flavors of Linux if the installation of StoreGrid goes throughfine. During installation StoreGrid compiles its own bundled Apache and PHP. So StoreGrid installation will requirethe following packages to be installed in the Linux system: make, gcc, g++, libc6-dev, libxml2, libxml2-dev andlibstdc++5, bison, flex. If you want to try a linux distribution, we suggest that you try the StoreGrid build (Redhat,Debain etc.) which is closer to your target system. If your installation is not successful, please contact us [email protected] for help.
Top
26. I know StoreGrid works across Windows, Linux, Mac, FreeBSD operating Systems. Doesthat mean the backups and restore can also be done across different operating systems?
Yes, StoreGrid not only works across different operating systems, it is also interoperable across the supportedoperating systems. That is, you can backup your Mac OS X to a Windows or Linux OR backup your Windows to aLinux or Mac OS X and so on. The only limitation is that when you restore your data to any client machine (otherthan the originator machine), the new client machine has to support the same matching endian byte order. Forexample, a Mac OS X can backup to a Windows. But the backed up data has to be restored by only another MacOS X system. This is because the blowfish encryption algorithm StoreGrid uses is based on the endianess of themachine. If all the different machines are based on Intel processor, then there should not be any problems with therestore across operating systems.
Top
27. I see that StoreGrid uses the MySQL database. Can I replace the MySQL database in mybackup server with PostgreSQL or MS-SQL Server etc?
Technically it is possible to replace the MySQL database with any other SQL-92 compliant database. We arecurrently working on supporting other databases (such as, PostgreSQL, Microsoft SQL Server) for StoreGrid internaldatabases and will be available in future versions of StoreGrid.
Top
28. When I try to login to the StoreGrid Web Console, I receive the following error message"The requested address is not valid in its context"?
Usually the error "The requested address ..." occurs when the StoreGrid webconsole fails to communicate theStoreGrid application.
1. If your system is configured with any firewall settings, please add the following to your firewall exceptionlist.
a. < StoreGrid_Home>\apache\Apache.exeb. < StoreGrid_Home>\bin\SGTray.exec. < StoreGrid_Home>\bin\StoreGrid.exed. TCP Port 32005
2. If the previous step did not help, disable your firewall and try logging in to StoreGrid webconsole.3. Also try logging in to StoreGrid webconsole with some other browsers.4. In IE browser this error also occurs due to the following reasons.
a. When "Include all local(intranet) sites not listed in other zones" option in "Tools -> Internet Options -> Security -> Local intranet -> Sites" is disabled.
b. And if the privacy settings is set to "High" in "Tools -> Internet Options -> Privacy" tab.
Top
29. The menu bar is missing from the StoreGrid Web Console?
This problem comes when javascript is disabled in the browser. To solve this enable javascript in your browser andtry using the StoreGrid webconsole.
Top
30. I am getting "Unable to send backup details to server <server name>. An operation wasattempted on something that is not a socket." error when running large number offiles/Exchange Server/MS SQL Server/other plugin backup jobs. What to do now?
This problem occurs when the socket connection to the backup server from the client is disconnected for reason.When the connection between the client and the backup server is lost, the StoreGrid client will automatically try toreestablish the connection and proceed with the backup from where it left off. However, if the client is not able toreestablish the connection after several attempts, then this error message is thrown In such a scenario, check theelements (NAT/firewall/Router) in the network and see if they are closing the connection for some reason.
Top
31. StoreGrid doesn't seem to run properly after upgrading Windows to Vista.
If StoreGrid was installed in an older version of Windows and then if the OS was upgraded to Vista, StoreGrid mayfail to run. If this is the case, then install the same version of StoreGrid again on top of the existing installation.
Another reason for this could be that if StoreGrid is installed under C:/Program Files in Vista, then make sure yourun 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 forthe < 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 youdon't want to run StoreGrid under the administrator account, make sure you install StoreGrid under your useraccount folder or other than the 'Program Files' folder.
Top
32. Error while dumping the Exchange Mail Boxes. Unable to create the PST file [or] "No new/modified filesfor backup"
This error might show up when 'MSPST MS' service is not configured in the Exchange Server.
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 doesnot have this information, then the Exchange Mailbox dump will fail with an error indicating that it was "Unable tocreate 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\ orC:\Windows\System32\).
Verify the file has an entry for the Microsoft Personal Folder store service. You can determine this by looking for thefollowing 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 MSPPR_SERVICE_DLL_NAME=mspst.dllPR_SERVICE_INSTALL_ID={6485D262-C2AC-11D1-AD3E-10A0C911C9C0}PR_SERVICE_SUPPORT_FILES=mspst.dllPR_SERVICE_ENTRY_NAME=PSTServiceEntryPR_RESOURCE_FLAGS=SERVICE_NO_PRIMARY_IDENTITY
[MSPST MSP]34140102=4e495441f9bfb80100aa0037d96e0000PR_PROVIDER_DLL_NAME=mspst.dllPR_SERVICE_INSTALL_ID={6485D262-C2AC-11D1-AD3E-10A0C911C9C0}PR_RESOURCE_TYPE=MAPI_STORE_PROVIDERPR_RESOURCE_FLAGS=STATUS_DEFAULT_STOREPR_DISPLAY_NAME=Personal FoldersPR_PROVIDER_DISPLAY=Personal Folders File (.pst)
For more information about the format of the MAPISVC.INF file see the following Microsoft article:http://support.microsoft.com/kb/294470
Top
33. Dump location does not have enough space to export the PST file
This error will occur when the dump location configured for this backup schedule doesn't have enough free space tostore the *.PST files. To resolve this, increase the free space or cleanup the used space for the drive which isconfigured as dump location for this backup schedule. Location configured for dump process can be viewed from'view backup configuration' of that backup schedule in the Backup->List Backup Schedule page in the client webconsole.
Top
34. Error while creating the dump location <Dump_Location>
When the configured dump location for that particular backup schedule is not accessible or StoreGrid does not haveenough permission to access the directory, then this error might occur. Make sure that the dump location driveexist in your StoreGrid client. If that drive exist, provide enough permissions to the user under which StoreGrid isinstalled to be able to write to the location.
Top
35. Users Mailbox/folder are not listed in the "Add Exchange Mailbox Backup" page.
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 tolist the users Mailbox.
2. Insufficient rights on the Exchange user mailbox.
Exchange Mail Level Backup requires "Full Control" access on the Exchange Server for the user account underwhich StoreGrid service is running. Please refer Granting Mailbox Rights document on creating a new user andgranting the sufficient rights to access the mailboxes.
Top
36. I get the error "Windows Server Backup is not installed in your System. Please install and try again."When trying to backup system state in Windows 2008.
StoreGrid uses Windows server backup utility to backup the system state in Windows 2008. If this utility is notinstalled then you will get this error. Please refer the System State backup trouble shooting page to get moredetails.
Limitations
Limitations in StoreGrid
1. In advanced disk image plugin backup schedule, additional disk drives cannot be added or removed from theschedule, once configured.
2. Keep the advanced disk image plugin backup data to local location (along with to remote backup server) option isnot supported.
3. Backing up dynamic disk drives using advanced disk image plugin is not supported.
4. Only NTFS formatted disk drives are supported by advanced disk image backup plugin.
5. Restore advanced disk image backup data to physical disk/drive is not supported in Linux OS.
6. Aborting/suspending the active export backup data process is not supported.
7. Export backup data feature is not supported in Amazon machine instances.
8. In clustered backup server environment, export backup data feature is supported only at client's 'node locked'backup server.
9. The backup schedules recovered from exported backup data cannot be edited or scheduled to continue the backup.The imported backups are for restore purposes only. After restoring the backup data, the imported backupschedules can be deleted.
10. Bandwidth throttling is not supported for the local backups (backup to another location in the same machine).
11. Bandwidth throttling is applicable only for backup processes from clients to the backup server and replicationprocess from the backup server to the replication server. Bandwidth throttling is not supported for restoreprocesses.
12. If an Exchange Mailbox name(user name) contains forward slash(/) or reverse slash(\), that mailbox might not bebacked up. You will need to change the full name of that mailbox without the slash characters to get them backedup.
13. If any special character is present in any folder name (present under a user), that character will be replaced withother set of valid characters while creating the dump file.
14. The feature to resume a restore from where it left off is not supported for restoring backups to a different clientother than the client from which backup was done.
15. The feature to resume a restore from where it left off is supported only at a file level and not at a block level. Thatis, if a restore failed/aborted while transferring a large file, the restore job, when it resumes, will restore that fileagain from the beginning.
16. In MCAL usage history page, the MCAL balance value for the Backup Server and the Customers may not beavailable after migrating StoreGrid from a older version. These details will be available only after the clients connectto the backup server.
17. After doing server side disaster recovery, the MCAL usage history page will not contain all the MCAL usage details.
18. StoreGrid sends Email alerts for low available disk space and shortage of MCALs once every 24 hours and notimmediately when the alert condition occurs.
19. If the user forgets the encryption key/password, then there is no way to restore the data. The data cannot bedecrypted and hence the backup is as good as lost.
20. Encryption key for a backup cannot and should not be changed across backup schedules.
21. StoreGrid does not support automatic directory and file monitoring in Mac OS X, FreeBSD, Solaris and Linuxmachines. So, when a continuous backup is configured, the backup will check for modified files continuously bylisting all the files and checking with StoreGrid backup meta data. This process will affect the performance of otherapplications. Hence configuring a continuous backup is not recommended in Mac OS X, FreeBSD, Solaris and LinuxOS machines.
22. The tree display in the StoreGrid Web Console will take a long time to load if a directory contains 1000s offiles/directories under it.
23. Cross platform restore is not possible for encrypted Mac OS X backups. But cross-platform encrypted backups arepossible. The reason is that the encryption algorithm StoreGrid uses is dependent on the processor architecture.This limitation is only applicable for Power PC Macs.
24. If a backup schedule is configured to two backup servers ( StoreGrid peers), then the backup data in both theservers need not be the same. As the backup is done to the servers one by one, the data, files etc. can differbetween the backups.
25. Aborting a continuous backup from the server side will only make the client begin the next schedule, making thebackup start again.
26. When a client's backup fails due to insufficient MCALs in the backup server, reports or events are not shown for theerror in the backup server.
27. StoreGrid does not allow restoring the selected mailbox to an alternate Exchange Server. If needed, .PST files canbe restored to alternate Exchange Server manually after restoring the files to local disk from backup server.
28. While restoring the complete contents of the selected folder to the original mailbox folder, the existing foldercontents will not be deleted prior to performing the restore and restore process will append all emails to the folders.It may result in duplicate email items within the original folder.
29. Search and restoring individual mails is not supported, however restoring up to mailbox folders is supported usingStoreGrid Exchange Mailbox plugin.
30. When sharding is enabled, before shipping data from backup server to another backup server, you need tomanually export the StoreGrid meta-data. After exporting, data can be shipped to destination backup/replicationserver. To export meta-data, execute the following commands from < StoreGrid_HOME> directory,
bin\StoreGrid.exe ExportToSQLiteDatabase
bin\StoreGrid.exe ExportToSQLiteDatabase <Client_Name>
bin\StoreGrid.exe ExportToSQLiteDatabase <Client_Name> <Backup_Name>
These steps need to performed before migrating data to replication server.
31. In 'Add backup schedule' page, files/folders with Unicode name will not be listed.
32. Advanced filter option will not work for Unicode name files/folders and the normal files inside folders with Unicodenames.
33. Include/exclude file/folders with search pattern for restore/delete will not work for Unicode files/folders.
34. Delete notification will not be processed for Unicode files/folders and also for the normal files/folders inside theUnicode folders.
35. Storage Location configured in Server Settings or Reseller or Customer should be available & accessible in allcluster nodes. If not, the backups might fail when client chose to backup to the specific cluster node where theStorage Location is inaccessible.
36. For basic disk image plugin backup and system state backups in Windows Vista & above operating systems,StoreGrid uses Windows operating system's built-in "wbadmin" utility. Hence, all the following limitations of"wbadmin" utility is applicable to StoreGrid basic disk image plugin & system state backup in Windows Vista &above operating systems.
The FAT32 file system drives will not be listed in the drives list.You cannot dump Disk Image data to Critical volume (system drive).You cannot dump Disk Image data to the drive where StoreGrid is installed.You cannot configure the dump location as a network shared folder or mapped drive or a tape drive.If the given dump location is CD/DVD, confirm that there is a media which is writable during backup.VSS services should be enabled for image backups.
37. For WSS2.0/SPS2003, only the sites added from 'SharePoint Settings' page will be listed in 'Add SharePoint SiteBackup' page.
38. Though the whole SharePoint Server or a whole portal site is selected for backup, only a site-collection level ofbackup will be done. Hence, to restore all the site-collections under a portal site, you need to restore the site-
collections under that portal site one by one using STSADM.EXE.
39. A site-collection whose total size exceeds 15 GB cannot be backed up as this is being a limitation with STSADM.EXE[which StoreGrid uses] itself. However, in such cases, you can use StoreGrid's SQL Server backup feature forbacking up the SQL databases being used by the SharePoint Server.
40. StoreGrid should be run with Administrator privileges to list and backup SharePoint sites as STSADM.EXE can berun only with Administrator permissions.
41. If the dump path of the SharePoint backup exceeds 255 characters, dump process will fail. Hence, make sure, youhave entered a shorter dump path to enable the dump to complete successfully.
42. The invoice details based on transferred data size are not available after recovering the backup server using ServerDisaster Recovery feature.
43. In StoreGrid cluster setup, all the cluster nodes should be installed with same type of reseller management option.
44. If clustering is enabled in the backup server, then you will not be able to migrate a client if it is (or the client'sparent customer or its parent reseller) node locked to one cluster node and the customer to which the client is tobe migrated is node locked to a different cluster node.
45. If you have configured Clustered Exchange Server backups, then Exchange Server name cannot be edited from theExchange Server configuration page. If you would like to backup a different Exchange Server, then you need todelete the Exchange Server backups that have already been created.
46. Invoice plan cannot be created with name that was already deleted/in use.
47. In cluster enabled replication server, restored data/compressed restored data file is available only in the cluster notit is backing up. i.e., if the client is backing up to backup_node2, then the client's restored data will be availableonly in the backup_node2 system. But the restore report will be available in all the backup server cluster nodes.
Issues
Known Issues in StoreGrid
1. In "Cluster Enabled" backup server setup, the backup data can be exported only in the backup server where theclient is "Node locked". It cannot be exported from the other backup servers available in that Cluster.
2. Export of backup data is not available for servers installed as an "Amazon machine instance(AMI)"
3. In sending backed up, skipped, deleted files list as attachment with email backup report feature, if the compressedlist file size exceeds maximum allowed attachment size limit of the email server, the backup report may not be sentto the recipients and it is not notified to the user.
4. The client's, who are migrated from another customer, may show wrong bandwidth usage value for the immediatemonth's invoice calculation.
5. In the 'Backup Location Details' feature in 'Settings > Server Settings' page, if the client's backup location wasconfigured with different cases [example, E:\backupdata\, E:\BackupData\], then they will be shown as separateentries in the list of backup locations.
6. While restoring the deleted MS SQL Server database(s), the same cannot be restored directly to the MS SQL Serverusing StoreGrid's complete restore feature. You should first restore the deleted database(s) locally in the clientmachine using StoreGrid. And then you should use StoreGrid's 'Plugin local restore' feature to restore the deletedMS SQL Server database(s).
7. When a backup schedule is configured with very low bandwidth throttling rate and the actual theoretical transferrate of the network is very high, then the backup progress would appear to be frozen periodically as if the backup isnot happening. But the backup would be running without any issue.
8. Changing replication server's backup storage location will be applicable only for the new resellers/customersreplicating to that replication server. The existing resellers/customers & their clients would still replicate to the oldbackup storage location. Also, the feature to edit a reseller's/customer's backup location in the replication server isnot yet supported. If you wish to change the reseller's/customer's backup storage location in the replication servercontact our technical support team.
9. Sometimes while doing restore, the skipped files from backups are also listed for restore. The restore reports maytherefore show that the restore was partially completed as it could not find the skipped files in the backup server.
10. Skipped folders may sometimes be listed in the skipped file list in the backup reports.
11. Replication progress window may not sometimes show the exact count of the total number of files to be replicated.
12. When Directory Monitoring is enabled, sometimes the Directory Monitoring service may give the short names of thefiles/folders backed up, in which case StoreGrid will assume them to be new files/folders and will backup themafresh.
13. StoreGrid will report error when trying to edit backups in Linux client machines where file/folder having " (doublequotes) in their names are selected for backup.
14. If the global (server) level replication settings are changed in the backup server, the new global settings may not beapplied to the individual customers.
15. Delete notification may not be sent from the backup server to the replication server when a customer to which aclient was migrated to (from another customer), is deleted in the backup server.
16. Cross platform restore is not possible for encrypted Mac OS X backups. But cross-platform encrypted backups arepossible. The reason is that the encryption algorithm StoreGrid uses is dependent on the processor architecture.This limitation is only applicable for Power PC Macs.
17. Events mechanism may not report all the important error conditions. Duplicate events may be generated for thesame problem.
18. Default backup space allocated by StoreGrid can be greater than the free space available in the partition of thebackup location because StoreGrid uses the total free space in all the partitions while computing the default backupspace.
19. In SQL Server database backup schedule, multiple databases can be configured for backup. But during restore, onlya single database can be restored at a time.
20. In MySQL backups, databases listed in the "Backup -> Plugin Backups -> MySQL" page (For Windows) will only befor the the last saved MySQL Server instance port in the MySQL Settings.
21. Local temporary dump location configured for a plugin(MySQL Server/System State) backup schedule cannot bechanged to another location for the same backup schedule.
22. If a plugin(SQL Server/Exchange Server/MySQL Server/System State/Image Backup) backup schedule is suspendedwhile local dump is in progress, then StoreGrid will not be able to suspend the creation of local backup dump.Instead, the dump will proceed to completion and after that the backup scheduled will be marked as suspended. Onresuming the same backup schedule, a new dump process will not occur, instead, the previously dumped files willbe transferred to the server and an error message will be reported in the backup report.
23. In server side restore report page, the restored compressed file's download link will be displayed, even if that zipfile is not present in the backup server (if for example the admin deletes the file) for download.
24. StoreGrid web console menu might flicker while navigating to the sub-menus in Internet Explorer 6.
25. If some files are deleted from the replication server using filter delete option, then some files will be skipped forreplication in the next replication schedule.
26. In a backup server, client's seed backup may get successfully migrated, even when no MCALs are available for thatclient.
27. Backup server may show some bytes as bandwidth usage for clients' backup schedules, even when no files/foldersare backed up to it.
28. Invoice amount may be little high, when creating invoice report for customer for their deleted period.
29. Invoice report may show incorrect per client charge value for the clients which are migrated to another customer.
30. In StoreGrid cluster setup, the PHPMailer email configuration is applicable to the local cluster node only. It will notbe shared to other cluster nodes.
Release Notes for StoreGrid 4.2 [Incremental VHD based Disk ImageBackup]Build Number: 4202012013120Date: 06 February 2012
What's new in StoreGrid v4.2
1. Incremental VHD based Disk Image Backup: StoreGrid`s Block Tracker continuously keeps track of all theblock level changes that are taking place in the disks that are configured for image backup. Each StoreGridRecovery point-in-time incremental backup is a fraction of the original volume size, because it only keeps track ofthe changes that are made to a volume. Also the image full or incremental backups are saved as VHD files whichcan be individually directly booted up as a virtual instance of the machine, very quickly. In earlier versions ofStoreGrid, the disk image backup has to be restored and converted to a VHD format before booting up as a virtualmachine.
2. Oracle Backup: StoreGrid v4.2 supports backing up of Oracle Server. StoreGrid uses RMAN (Oracle RecoveryManager), a command-line and Oracle Enterprise Manager-based tool to perform hot backup of the Oracledatabases. RMAN is the Oracle-preferred method for efficiently backing up and recovering an Oracle database.Oracle database has to be in "Archive Log" mode for performing hot backup using StoreGrid.
3. Outlook Backup using MAPI: StoreGrid v4.2 supports the option to incrementally backup Outlook. Only theemails, Outlook items changed since last backup is backed up during the incremental backup. Each incrementalbackup of Outlook is backed up as a separate PST giving complete control during restore. In the earlier versions ofStoreGrid, the entire Outlook data is dumped and the difference between the earlier full backup is sent during theincremental backup.
4. cPanel Server Backup : StoreGrid v4.2 supports backing up of accounts and domains in a cPanel Server.StoreGrid can backup the entire home directory, MySQL databases, Email Forwarder settings and Email Filtersettings . Entire cPanel Server, specific accounts or specific data within an account can be restored. It also offersan interface in the cPanel Management Console for domain users to self manage their restores.
5. PostgreSQL Backup : StoreGrid v4.2 supports backup of PostgreSQL database(s). StoreGrid supports Full andIncremental PostgreSQL database backups even when the database server is online and accessible.
6. CRC Integrity check for backup data : StoreGrid v4.2 supports data integrity check where the data sent fromthe client machine is verified for integrity at the backup server. When a file's integrity check fails, StoreGrid flagsthat file as skipped and the file is backed up again during the next backup schedule.
Enhancements in StoreGrid v4.2
1. Support for Reduced Redundancy Storage for S3 replication.2. Option to enable or disable SGTrash from the web console.3. Option to enable client backup status e-mail report for individual resellers and customers.4. Sending just one backup failure email report from the backup server when the client runs several reattempts to
resume an interrupted or failed backup. The email will be sent only after the client has exhausted all its reattempts.Similarly only one failure service ticket will be created in Connectwise/Autotask. Before v4.2, every attempt fromthe client will create an error report in the backup server.
5. Email reports made compatible for iOS devices.6. Notes can be added about the client during the client's registration with the backup server.7. API enhancements:
1. Export Backup API is added2. Allowed to add maximum client limit for customer when add/edit using 'SignupCustomer' and
'UpdateCustomerConfiguration' API3. Client Backup Status Report can be enabled/disabled for reseller/customer using 'SignupReseller',
'SignupCustomer', 'UpdateResellerConfiguration' and 'UpdateCustomerConfiguration' API.
Minor Enhancements and Bug Fixes in StoreGrid v4.2
1. MySQL Pconnect issue fixed in MySQL online installer in Linux2. Ability to add/edit/delete client/customer/ceseller through server side search page.
3. Disabled recipient e-mail in add/edit customer page, if Global Configuration is selected in Consolidated CustomerReport page.
4. Total disk utilization details removed from reseller/customer access of the web console.5. Summary Report link added in list of backup schedules page.6. Fixed an issue where files/folders are not deleted from s3 even though it is deleted in backup server.7. NTFS folder permissions restore for Windows 2003 and 2008 servers fixed.8. Fixed the issue generating On-Demand invoice using Web Services API.9. Online client registration fixed for failure cases when the customer name contains the symbol "&"(ampersand).
10. Fixed an issue in authenticating backup server after performing the seed backup migration in client side when thebackup server name is specifid in upper case.
Release Notes for StoreGrid 4.1 [Hyper-V Backup]Build Number: 4102011110720Date: 9 November 2011
New Features in StoreGrid v4.1
1. Support for backing up Hyper-V Virtual Machines - Hyper-V Virtual Machines can now be backed up using StoreGrid.StoreGrid needs to be installed in the Hyper-V Server and it can then centrally backup all the VMs running in thatHyper-V server.
2. WHMCS Provisioning Integration With StoreGrid - With the integration of WHMCS provisioning APIs with StoreGrid,an action in WHMCS (like subscribing a customer for a service) in WHMCS can trigger an event in the StoreGridbackup server (like creating that customer account in the backup server).
Enhancements in StoreGrid v4.1
1. Bandwidth Throttling can now be disabled during weekends2. For Exchange Mailbox backup, backup can be configured to upload the previous Mailbox and delete its dump while
the next Mailbox is being dumped in the Exchange Server. This will save dump space required for Exhange Mailboxbackup. Currently all the Mailboxes have to be first dumped before upload to the backup server can start.
3. SGTrash Management enabled for Amazon AMI builds - StoreGrid will move version files that have exceededretention policy to a SGTrash folder in the storage location in the backup server.
4. Server side MySQL DB and query optimizations to improve performance and resource utilization.5. Added skipped file report during server side restore.6. Option to include MCAL usage cost into customer invoicing7. Group notes can be added/edited via API for Reseller/Customer/Client.8. Mutliple Email addresses can be added for Consolidated Email report via API.9. Option to not ask encryption password when deleting a backup job in the client machine through StoreGrid's
Centralized Client Management feature in the backup server.10. Recovering data from SGTrash through StoreGrid utility.11. Sending Email reports from backup server (on backup/restore success/failure etc.) to Customer and Reseller as
well. Currently only the Server Admin gets the emails.12. Uncompressed size of files included in Backup Reports13. Adding MCALs to remote backup server and backup server health through remote server management.14. Excluding reports of deleted client from backup status report15. Filter delete performance improvement and removing empty directories after filter delete
Minor Enhancements and Bug Fixes in StoreGrid v4.1
1. Adding an event when MCAL balance is low for the Server and Customer.2. Issue in updation of backup used space after filter delete operation is fixed.3. Reseller level branding themes for the backup server web console cannot be now enabled by a reseller when its
disabled by the server admin.4. Issue where reports of two day prior backups sent in daily consolidated customer report has been fixed.5. The backup will be reported as 'Failed' when the root folder configured for backup is missing from the client
machine.6. Fixed the issue where continuous backup causes high CPU usage in backup server during retention cleanup.7. Hiding Export data option at reseller/customer/client level login.8. Fixed an issue where unicode files where getting skipped when the files were open even with VSS enabled9. Fixed the issue where StoreGrid client would abort backup if another application had run Copy Only Full Backup on
the SQL Server that is been backed up by StoreGrid.10. Fixed the issue where the file/folder tree listing hangs when the number of files is several millions
11. Fixed the issue where backups run outside the backup window when two backups are configured in a client machinewith the same start time.
12. Fixed issue in generating On-Demand invoicing when the time zone specified in the web console is different fromthat of the backup server machine OS
13. Issue in SharePoint backup where dumping site-collections with "https" extension fails if already an identical site-collection with "http" enabled is fixed
Release Notes for StoreGrid 4.0 [BMR, P2V, P2P supported]Build Number: 4002011071521Date: 18 July 2011
New Features in StoreGrid v4.0
1. Support for Disk Image Backup and Bare Metal Restore (BMR) on all versions of Windows. The image backup canbe restored even to a machine with a dissimilar hardware (P2P).
2. Support for conversion of Physical Disk Image to Hyper-V or VMWare Virtual Machine image (P2V).3. Reseller Level Branding of backup server for rebranded server installations - customers accessing the backup server
can now see the reseller specific branded user interface4. Integration of StoreGrid Invoicing with WHMCS5. Backup data can now be exported from the backup server in encrypted format itself and imported into the client for
restore.6. Centralized Management Console to monitor multiple backup servers - can centrally view the backup reports and
invoices from the different backup servers.7. User activity log report to log user activities in the backup servers.
Enhancements in StoreGrid v4.0
1. List of files backed up in a backup job can now be optionally included in the backup completion notification email.2. Ability to abort a restore job from both client and backup server3. Newly designed menu for easier navigation in web console UI.4. Add Backup from backup server with a System Generated Password is now supported through CCM.5. The time at which the automated consolidated customer email report is sent can now be configured in
SGConfiguration.conf file.6. StoreGrid client now checks if other third party backup software is also running in the client machine for SQL and
Exchange Server Backups. Backups will be aborted if both applications run backups out of sequence.
Minor Enhancements and Bug Fixes in StoreGrid v4.0
1. Fixed the issue where invoice was getting calculated on average usage instead of total bandwidth usage.2. Issue where custom SSL certificates would get over written during upgrade with default certificates is now fixed.3. Fixed the issue where backup status would be wrongly reported as failed when deleted DBs where present in the
SQL Backup. Now the deleted backups would be skipped and the backup would be reported as success with themessage that deleted DBs were skipped.
4. Fixed the issue where usage would be wrongly updated in MCAL utilization history report for new clients with one ormore plugin based backups.
5. Restore failure due to 0 KB ori file is now handled. If the ori file is a 0 KB file, a full backup of the file will be run.6. Fixed the issue where multiple emails were mistakenly sent from the backup server for missed backups.7. Fixed the issue in authenticating backup server with replication server.
Release Notes for StoreGrid 3.5 SP3 [with Centralized ClientManagement feature]Build Number: 3502011041520Date: 15 April 2011
New Features in StoreGrid 3.5 SP3
1. Supports Centralized Client Management feature to manage client settings and backup schedules from the backupserver.
2. Support for maintaining a local copy of the backup for plugin based backups.
Enhancements in StoreGrid 3.5 SP3
1. Ability to do Client Disaster Recover directly from local drive backups (without the backup server).2. Option for the clients to reset their backup server web access password.3. Support for configuring the Email SSL settings from the web console itself.4. Support for backing up Microsoft SQL Server databases with Unicode names.5. Performance improvement in filter based deletion of backed up files.6. Performance improvements in backup, restore and replication processes.
Minor Enhancements and Bug Fixes in StoreGrid 3.5 SP3
1. Incorrect MCALs count issue in server dashboard page is fixed.2. Backup failure issue under certain cases while backing up over SSL is fixed.3. Listing Exchange Server log files in Exchange Server restore tree is made optional.4. The *.edb files dumped for Exchange Server Information Stores with same names in Exchange 2000/2003/2007 are
not uploaded to the backup server issue is fixed.5. Dump process failure issue for Exchange 2010 databases if the DB name contains more than one continuous white
spaces is fixed.6. StoreGrid will be by default installed as a Windows service on local system account in Microsoft Windows Vista and
above OSes.7. While restoring the whole Mailbox store data, public folder will also be restored now.8. Memory leak issue under certain failures is fixed.9. Issue of scrambled content in Email reports is fixed.
10. Issue where old events and alarms are sometimes not properly cleaned up is fixed.11. Issue when sometimes processing deleted files in replication server is fixed.
Release Notes for StoreGrid 3.5 SP2 [with VMWare Guest OSes backupfeature]Build Number: 3502010122919Date: 07 January 2011
Applicable to: Windows & Linux OS, Client and Server installations
New Features in StoreGrid 3.5 SP2
1. Supports backup of VMWare Guest OSes.
Enhancements in StoreGrid 3.5 SP2
1. For backup server, following report pages are directly retrieved from MySQL database to reduce load on StoreGridprocess and faster report rendering.
i. Client backup status report.ii. Consolidated client backup status report.iii. Client information report.iv. Server dashboard.v. MCAL utilization history report.vi. Added MCAL details report.
2. Supports adding and removing databases by editing that backup schedule for MySQL Server database backup.3. Allowing to provide for minimum fixed price slab in sliding scale invoice plan.4. Events and alarms web console page is modified for faster rendering.
Bug Fixes in StoreGrid 3.5 SP2
1. Issue where Synthetic Backup is not scheduled if the backup schedule is aborted is fixed.2. The issue where other re-seller's alarm and event details are listed for a re-seller's login session is fixed.3. Issue where Exchange Server Mailboxes are not listed in Exchange 2010 DAG member Exchange Servers issue is
fixed.4. Fixed the issue where mails are not restored if the folder name contains Unicode characters.5. Fixed the issue where StoreGrid crashes when backing up an empty mailbox folder.6. Issue where Client backups sometime hang when backing up through SSL based socket.
Release Notes for StoreGrid 3.5 SP1 [with Exchange Mail Level Restorefeature]Build Number: 3502010111115Date: 15 November 2010
Applicable to: Windows Client only installations
New Features in StoreGrid 3.5 SP1
1. Supports Mail Level Restore from restored Exchange Server mailbox (.pst files) data.
Enhancements in StoreGrid 3.5 SP1
1. Client Disaster Recovery page is re-designed to support recovering backup configurations for both authenticated aswell as auto-authetnicated clients.
Bug Fixes in StoreGrid 3.5 SP1
1. Fixed Exchange Server restore issue when locally restored Exchange Server backup data is separately loaded andrestored to the Exchange Server.
2. Fixed MSSQL Server restore issue due to incorrect order of restoring log files, in some cases.3. Fixed issue in editing and continuing plugin backup schedules after recovering plugin backup schedules through
Client Disaster Recovery.
Release Notes for StoreGrid 3.5Build Number: 3502010102621
New Features in StoreGrid 3.5
1. Synthetic Full Backup of Files: During incremental backup schedules, StoreGrid client automatically runs aSynthetic Full Backup of a file if its backed up version file is larger than a certain percentage of its initial fullbackup. During Synthetic Full Backup, changed data with respect to the earlier Full Backup or Synthetic Full Backupalone is uploaded. Version files uploaded after a Synthetic Full Backup contain modified data with respect to thelast Synthetic Full Backup and are therefore much smaller.
2. Synthetic Full Backup of Exchange Server: Instead of running Additional Full Backup of the Exchange Server tolimit the number of incremental backups in the backup server, StoreGrid can now optionally run Synthetic FullBackups. During Synthetic Full Backups, only the data that is changed after the previous Full Backup or SyntheticFull Backup alone is uploaded and not the entire the Exchange Server data.
Enhancements in StoreGrid 3.5:
1. Further performance enhancements for backing up Unicode files.
2. Support for cleaning up multiple alarms at a time.
3. Ability to choose the parent folder and exclude sub folders or files while configuring file backups.
4. Adding client name and backup name in Windows Events.
5. Improved the performance in files tree listing during client side restore when large number of files exist in a folder.
6. StoreGrid client can now backup the site collections of Microsoft SharePoint Server 2010.
Bug Fixes in StoreGrid 3.5:
1. Issue when backing up large files in Nexenta Open Solaris OS fixed.
2. Made changes to automatically include the missed libraries while installing StoreGrid in Linux.
3. Fixed the issue where sometimes tickets were not created in ConnectWise PSA when Email reports were also
enabled in the backup server.
Release Notes for StoreGrid 3.2Build Number: 3202010041915
New Features in StoreGrid 3.2
1. Migration of v2.5.5 Server and 2.5.1 Client installations to v3.2: StoreGrid v3.2 supports all the featuresincluded in v3.0 and v3.1 (listed below) along with migration of v2.5.5 Server and v2.5.1 client installations tov3.2. StoreGrid backup server and replication server running v2.5.5 can now be upgraded to v3.2 and clientsrunning v2.5.1 to StoreGrid v3.2.
Release notes for StoreGrid v3.1 SP2 release:Build Number: 3102010083121Date: 04 September 2010
New Features in StoreGrid 3.1 SP2:
Supporting integration with ConnectWise and Autotask: StoreGrid can integrate with ConnectWise and Autotask PSA(Professional Services Automation) applications. Currently StoreGrid can push major events like backup/restore/replicationprocess status and alerts (such as disk space shortage, trial client expiry) to the PSA services. More features integrationwith PSA is coming. To get more details StoreGrid's integration with these PSA , refer the following online documentation:
ConnectWise
Autotask
Enhancements in StoreGrid 3.1 SP2:
1. Supporting backup of My Pictures, My Music and My Videos folders as one-click backup schedule in Windows Vistaand above OSes. In prior StoreGrid versions, these folders will be backed up along with My Documents folderbackup schedule.
2. Fixed database connection related issues in StoreGrid backup server.(MySQL Server gone away, crash issues)
3. Enhanced the built-in CheckAndUpdate utility for recovering StoreGrid Backup Server's MySQL database frombackup data alone. This utility now recovers Reseller and Customer account details as well automatically.
Minor enhancements and bug fixes in StoreGrid 3.1 SP2:
1. The issue where StoreGrid backup server crashes when the internal client configuration file (sgclient.txt) iscorrupted is now fixed.
2. Fixed the issue where StoreGrid crashes sometimes when trial client cleanup process runs.
3. Outlook archive folders not backing up if configured to non-default location is fixed.
4. Fixed issues with backing up files with Unicode file name.
5. The issue in running retention cleanup of replicated deleted files is fixed.
6. Fixed the issue where Microsoft Exchange Server 2010 mailboxes were not listed when the Exchange server wasmigrated from lower version.
7. Issue in backing up Microsoft Exchange Server 2010 data if the Exchange server is upgraded from MicrosoftExchange Server 2007 is fixed.
8. Restored "All Public Folders" items was not accessible to all users in the Exchange Server, instead it was accessibleonly to profile user and this issue was fixed.
9. Issue in listing & backing up Microsoft Exchange Server mailboxes if Microsoft Exchange Server contains more thanone default store, is fixed.
10. Showing different email report time due to DST changes issue is fixed.
11. Issue in restoring all Microsoft Exchange Server databases from locally restored data to Exchange Server is fixed.
12. Consolidated customer report shows 100% success rate for failed backups issue is fixed.
13. Several other minor fixes
Enhancements in StoreGrid 3.1 SP1:
1. Support for Exchange Server 2010 database level backup and restore.
2. Option for Enabling/Disabling SGTrash Management through StoreGrid configuration file – by default StoreGridmoves version files that have exceeded retention policy to a SGTrash folder in the storage location in the backupserver. This can now be disabled (so that the files are just deleted and not moved to SGTrash) in the backup serverby changing the appropriate tag in the SGConfiguration.conf file of StoreGrid.
3. Configure email Settings with NTLM SMTP authentication supported email servers - StoreGrid can now be configuredto send email reports via Exchange Server 2003 and above versions, which support only NTLM authentication typeby default.
4. Uniform Discount Invoice Plan can now be created with a fixed rate for the initial x GB for the first slab and thenthe regular per GB slabs. Fixed rate can be specified by entering 0 in the per GB field for that slab.
5. In the backup server web console, added links for Reseller, Customer, Client and Backup names under "ClientActivity [Current]" section in Server Dashboard page.
Bug Fixes in StoreGrid 3.1 SP1:
1. Exchange Server 2010 mailboxes not listed in some cases.
2. After Client Disaster Recovery, Exchange Server backup schedule shows "No new or modified files found forbackup" message.
3. Large latency between the completion of Exchange Server backup data dump and uploading of the dumped files tothe backup server when large number of files are dumped in Exchange Server.
4. Outlook Express is not backed up in Windows XP SP3 when StoreGrid is installed as a service.
5. Outlook (pst) files in non-default location doesn’t get backed up.
6. Issues in backing up Unicode file/folders.
7. The number of established socket connections on SSL backup port 32007 increases in the backup server over aperiod of time.
8. Hidden files and folders are not displayed in the "Add Backup Schedule" page tree list in linux clients.
9. Reports of all the clients available in the 'Consolidated client backup status' report for customer level login in thebackup server, instead of for just that customer.
10. Replication to S3 storage failed with errors "The specified bucket is not empty, hence cannot be removed."
11. Replication Server sometimes crashes when time based retention cleanup process runs.
12. Backup performance affected when processing deleted files/folders notification.
Release Notes for StoreGrid 3.1Build Number: 3102010021517
New Features in StoreGrid 3.1
1. Bare Metal Restore of Windows 2008, Windows 7 and Windows Vista: StoreGrid can backup the entireimage of the client machines running Windows 7, Windows 2008 & Windows Vista Business, Enterprise, andUltimate editions. The backed up image can be restored to the same machine or to a machine with very similarhardware as the original client machine.
2. Backup and Restore from local drives: StoreGrid client can now backup to a local drive and also restore from it,without having to connect to a backup server.
3. SharePoint Server Backup: StoreGrid client can now backup the site collections of SharePoint Portal Server 2003and Microsoft Office SharePoint Server 2007.
4. Publishing StoreGrid Events as Windows Events: You can now configure StoreGrid to also generate WindowsEvents when StoreGrid Events are created. This will help Service Providers to monitor StoreGrid events throughthird party applications that can monitor Windows Events.
5. Customization of StoreGrid's Email notifications: The Emails generated by StoreGrid can be now customized.Service Providers can now send their own customized messages embedded in StoreGrid's Email notifications to theircustomers.
6. Reseller Level Invoicing: Invoicing is now possible at Reseller level also.
7. Customer Invoicing based on Uncompressed File Size and Transferred Data Size - The backup server cannow be configured to invoice customers based on the uncompressed size of the data and the size of the datatransferred (uploaded during backup and downloaded during restore). Prior to v3.1, customer invoicing was basedonly on the size of the backup data used in the backup server.
8. Bandwidth Throttling during Replication: The maximum bandwidth that a backup server can use whilereplicating to a replication server can now be throttled. The bandwidth throttling settings can be set at thereplication server.
9. Enabling/Disabling Reseller Management: Reseller Management in Backup and Replication servers can now beenabled or disabled during StoreGrid fresh installation in the server. For existing StoreGrid v3.0 server installations,Reseller Management can be disabled by changing the StoreGrid configuration file after migrating to v3.1.
10. Client Registration from Client Web Console: Users/Customers can now register their client machines under theappropriate customer account in the backup server from the client web console itself. The StoreGrid backup servernow sends a unique Customer 'Passkey' to the Customer through email when the customer's account is created inthe backup server. Using this unique passkey, users (customer) can register the client machines under thatCustomer account in the backup.
Enhancements in StoreGrid 3.1
1. Support for backing up Exchange Server cluster.
2. New mailboxes can now be added to an existing Exchange Server Mailbox Backup through client web console.
3. Connectivity check can now be run from the backup server to replication server in the backup server web console.
4. Additional full seed backups can now be run from the client to a locally attached drive before importing them intothe backup server.
5. Ability to abort a live backup from the client web console.
6. Ability to limit the number of clients backing up under a customer account in the backup server.
7. Added a search capability in the backup server to search by backup/client/customer/reseller name.
8. Monthly Charges and Taxes can now be added to the invoice plans.
9. Exchange Server Backup data can now be optionally restored in the uncompressed state on the server side. Thisdata can then be applied into the Exchange Server manually through third party application. Prior to v3.1, therestored data will be in compressed state and therefore required StoreGrid Client to apply it into the ExchangeServer.
10. Ability to suspend, abort MSSQL Server and Exchange Mailbox backups while its dump is in progress.
11. The speed of the replication process performance is improved in the backup server.
Minor enhancements and bug fixes in StoreGrid 3.1
1. No MCALs will be used for the clients' automatic software update connection to the backup server.
2. Adding Microsoft SQL Server instance name from client's web console, if StoreGrid couldn't detect the MSDE/SQLServer Express Instances.
3. Displaying client's NAT & local IP address details in the backup server's client information web console page.
4. Ability to edit the invoice plans currently in use.
5. Issue in backing up Outlook Express filter settings issue is fixed.
6. Additional full backup data with file versions is supported for seed backup at backup server.
7. StoreGrid client exits, if the restore data location doesn't have space for restore data issue is fixed.
Release Notes for StoreGrid 3.0Build Number: 3002009102219
New Features In StoreGrid 3.0
StoreGrid Server
1. Comprehensive Reseller based management in StoreGrid server - Master Service Providers (MSPs) who taketheir backup service to the customers through resellers can group the client machines and the customers undertheir respective Reseller accounts in the backup server. Just like a Customer account, a Reseller account can beconfigured and managed for backup location and space, client license units, bandwidth throttling, authenticationetc.
2. Clustering and Load Balancing of StoreGrid Servers - StoreGrid Backup Server installations can now beconfigured into a cluster. New client machines connecting to the cluster will be automatically assigned a backupserver instance to which the client will then run its backups to. As the clients machines grow, new backup serverinstances can be dynamically added to the cluster to handle the increased load without any changes on the clientside.
3. Reseller/Customer/Client access to backup server - Resellers, Customers and Clients present in the backupserver can now be provided access to the backup server. A Reseller logging into the backup server's web consolecan access all Reseller related details and all the Customers and Clients under that Reseller. Similarly a Customercan access the details of that Customer and all the Clients listed under that Customer. End user (Client) can accesstheir backups, run restore and download the restored files, if needed through their web access to the backupserver.
4. Replication of StoreGrid Backup Server to Amazon S3 - StoreGrid backup server can now be replicated toAmazon's S3 Cloud storage for backup data redundancy.
5. Alarm based Management of StoreGrid Events - StoreGrid can now generate Alarms based on the Events itgenerates, for better monitoring.
6. Automatic Disk Allocation for Clients - Clients under a Customer can now share the disk space allocated to theCustomer in the backup server; each client doesn't need to be allocated disk space individually.
7. StoreGrid Server Side Restore & Download for Clients - Users with Reseller, Customer or Client access to thebackup server can now log into the backup server web console from any machine, run a server side restore anddownload the restored files from backup server.
8. WebServices APIs to access StoreGrid modules - StoreGrid's internal data and functionalities can now beaccessed via Web Service based APIs. These APIs can be used to integrate third party applications, like billingsoftware or monitoring systems with StoreGrid.
9. Database Sharding to enhance scalability of backup server - With the v3.0, each backup is stored in aseparate database in the external database of the backup server, providing higher scalability and performance ofthe backup server.
StoreGrid Client
1. Support for 3DES Encryption - Users can now choose between BlowFish and 3DES encryption algorithms whilecreating a backup schedule.
2. ‘Read-Only’ user accounts supported - Read-Only user accounts can now be created to access the client webconsole. ‘Read Only’ users logging into the client machine can force an existing backup schedule to run or dorestores. They will not be able to add new backup schedules or change existing schedules.
3. System Generated Password for backups - Users can now optionally choose StoreGrid to generate its ownencryption password while creating a backup schedule instead of the user specifying an encryption password. Abackup created with System Generated password for encryption will not require the user to enter the password forrestore or for deleting the backup schedule.
Release Notes for StoreGrid 2.5.5Build Number: 2552009080521
New Features In StoreGrid 2.5.5
1. Support for MySQL database (instead of SQLite) for Backup Server and Replication Server backend.
Enhancements in StoreGrid 2.5.5
1. Restore process optimized for bulk restore with large number of directories and files.
2. StoreGrid monitor script added for Linux installations to monitor the StoreGrid process.
Release Notes for StoreGrid 2.5.1 SP2Enhancements In StoreGrid 2.5.1 SP2
1. Supporting incremental backups for system state backup in Windows 2008.
2. Added an option where the client backup status report in the backup server will show only the latest status of eachbackup.
3. Added the feature where Exchange Server user details can be specified through the client web console for Mailboxbackup.
4. Added the feature where Microsoft SQL Server instance name can be specified through the client web console whenStoreGrid is unable to automatically detect the Microsoft SQL Server instance.
5. Resume from where it left off after an interruption during the replication is now made more efficient.
6. Performance improvements when backing up files in large number for folders.
Major Bug Fixes In StoreGrid 2.5.1 SP2
1. High CPU utilization issue fix during retention cleanup process.
2. Fixed the issue where client sometimes runs a full backup to the backup server after local to remote servermigration.
3. Fixed the issue where sometimes StoreGrid crashes when restoring files with Unicode names.
4. Fixed the issue in backing up Exchange Mailbox folders with display name ending with a dot(.).
5. Fixed the issue in displaying erroneous restore status and restore report for Exchange Server, Exchange Mailboxand SQL Server backups.
6. StoreGrid reports success message when it is unable to start the Exchange Server 2007 Mailbox dump process issueis fixed.
7. In incremental Exchange Server Mailbox backup schedules, the issue of dumping large amount of data for aselected folder, if the folder contains large number of sub-folders, is fixed.
8. Fixed issue in backing up a sub-folder under Exchange Server public folders when a sub-folder is chosen individuallyfor that backup.
Minor Bug Fixes In StoreGrid 2.5.1 SP2
1. Invalid backup space usage issue fixed in the replication server.
2. Sometimes older versions not cleaned up for system state backup issue is fixed.
3. Directory monitoring and retention of deleted files option is now disabled for run once backup types.
4. Fixed issue in displaying the exact mount status [Mounted/Dismounted status] of the exchange database(s) inrestore report after the completion of the exchange restore process.
Release Notes for StoreGrid 2.5.1 SP1Enhancements In StoreGrid 2.5.1 SP1
1. Performance improvement in the retention cleanup process in the backup server.
2. Performance improvement in incremental backup schedule when the backup set contains very large number of files.
3. Performance improvement in backing up empty folders during incremental backup schedules.
Major Bug Fixes In StoreGrid 2.5.1 SP1
1. Backup server fails to replicate backup data to the replication server due to the socket connection timed out issuefixed.
2. StoreGrid client takes full backup, if the client's day light saving time (DST) changes issue is fixed.
3. StoreGrid client crashes when backing up Exchange Server Mailbox public sub-folders.
4. StoreGrid gives error message when listing Exchange Server Mailbox folders, if Exchange Server runs with IPv6option.
5. Re-attaching archived backup data back to the backup server through service side Local to Remote ServerMigration issue is fixed.
6. Exchange Mailbox sub-folder items getting dumped again in incremental backup issue is fixed.
7. Restoring Exchange Server backup schedule from where it left off issue is fixed.
8. Problem in listing MySQL databases in Linux, FreeBSD OSes, if database files stored in non-default location, issue isfixed.
9. In the client side consolidated backup report dashboard page, success rate for latest schedule will be shown.
10. The alert settings web console page hanging in StoreGrid Professional Edition issue is fixed.
11. Fixed the issue in updating the SQL Server backup schedule status from active to idle state, if the backup serverconnection was timed out.
Minor Bug Fixes In StoreGrid 2.5.1 SP1
1. The client's backup schedule with VSS option fails as the StoreGrid VSS writer is not listed when taking backup.This issue is fixed.
2. StoreGrid backup server skips files during replication process issue is fixed.
3. Showing higher transfer rate for file transfer with bandwidth throttling option is enabled issue is fixed.
4. Listing Exchange Server MailBox folders fails with MAPI_E_INVALID_PARAMETER error in some Exchange Serversystem issue is fixed.
5. Plugin backup schedule success email report's subject line is incorrect, in some cases, issue is fixed.
6. In some cases, not inserting the renamed/deleted files details in the backup server database issue is fixed.
7. StoreGrid intermediate files not cleaned up for backup schedules configured with Directory Monitoring optionenabled, issue is fixed.
8. StoreGrid Windows installation hangs in Windows 2008 OS, if system contains more number of disk drives issue isfixed.
9. Software update issue fix for 2.3.5 clients for non-English builds.
10. Opening web console with systems default web browser application in StoreGrid system tray.
Release Notes for StoreGrid 2.5.1Build Number: 2512009032420
New Features In StoreGrid 2.5.1
1. Backing up and restoring files or folders with Unicode names is now supported.
Enhancements in StoreGrid 2.5.1
1. Backing up multiple mailboxes with the same (display) name is now supported.
2. High CPU utilization and occasional internal sgserver.db database file corruption issue in backup server is fixed.
Minor changes and bug fixes in StoreGrid 2.5.1
1. Issue in restoring files with filenames containing specific set of characters when backup is encrypted is fixed.
2. Fixed the issue where sometimes replication seems to be in progress in the backup server but actually gets stuckwithout replicating the files.
3. If additional full backup is configured with monthly schedule option, the backup may be additionally scheduled onthat day of the week in the next month, for example, schedule configured to run additional full backup on 4thSunday may be scheduled on 3rd Sunday of the next month. Also, if the additional full backup was configured toschedule on particular days, around end of the month, the full backup mistakenly occurs on that day of the week inthe next month's first week. Both of these issues were fixed in this build.
4. Client side filter delete of files doesn't work for the backups stored in client's old backup storage location [and theclient's backup storage location is changed] issue is fixed.
5. Issue where files were not listed for restore when additional full backup is migrated into backup server throughLocal to Remote Migration is fixed.
6. Issue in showing the schedule details in client side backup schedule view page & edit backup schedule page, ifmonthly full backup is configured, is fixed.
7. Advanced filter options configuration in Internet Explorer web browser issue is fixed.
Release Notes for StoreGrid 2.5New Features In StoreGrid 2.5
1. Using MySQL RDBMS backend as StoreGrid backend database (replacing the current embedded RDBMS engineSQLite).
2. Backend data storage on Amazon Simple Storage Service (S3).
3. Out-of-the-box support for StoreGrid in Amazon Elastic Compute Cloud (EC2).
Bug fixes in StoreGrid 2.5
1. Resuming Restore from where it left off when the restore process is suspended/killed during Restore of anencrypted backup is fixed.
2. No response from server while doing Client Disaster Recovery fixed.
3. Disk space usage updation while doing retention cleanup fixed.
Release Notes for StoreGrid 2.4New Features In StoreGrid 2.4
1. Bandwidth Throttling Limiting the maximum bandwidth a StoreGrid client can use.
2. Advanced Retention Retention based on age of the version files and retention of deleted files both based on theversion count as well as age of the deleted files.
3. Exchange Server 2007 Mailbox backup Backing up Exchange mailbox in 64 bit Exchange server.
4. Windows 2008 System State Backup Support for backing up System State in Windows 2008 machines.
Enhancements in StoreGrid 2.4
1. Resume Restore from where it left off Resume restore from where it left off after an interruption.
2. Automatic software update of backup server from replication server.
3. Backup location settings at Customer level currently the backup location can be specified at server and client levelsonly.
4. Email notifications for missed backup.
5. Restore performance improvements.
6. MCALs added and usage history in backup server.
7. Option to edit local dump location for the plugin based backups (MS SQL Server/ Exchange Server/ ExchangeMailbox).
8. Support for manually moving of backup data location in the backup server; user can then update the settingsthrough the web console.
9. Consolidated list of all backup locations with the used space has been added in the Server Settings page in thebackup server web console.
10. Added new email filter option to not send Emails when there is no files to replicate.
11. Option to allow unlimited number of attempts when a backup fails due to space, license etc for non-plugin basedbackups.
12. Option to configure time interval to reschedule a backup every 5/10/15/20/25/30 minutes, whenever an attemptedbackup is incomplete because of a network error, server crash etc.
Minor changes and bug fixes in StoreGrid 2.4
1. Keep all previous installation settings during upgrade installation.
2. Enhanced Advanced port configuration in a Windows installation setup to display separate dialog window.
3. The local dump location can now be configured while creating system state backup schedule in the client webconsole.
4. Moved MySQL Server database(s) backup configuration to separate screen "Backup -> Create MySQL DatabaseBackup".
5. Fixed the issue in taking incremental backup of Exchange Mailbox user subfolders.
6. Removed backup space validation when editing client settings in replication server.
7. Filter delete of folder should also delete the references to the folder from the DB so that the empty folder doesn'tget listed in restore tree.
8. Option to select the months of the year when you configure the full backup of plugin backups(MS SQLServer/Exchange Server/Exchange Mailbox).
9. Option to select days of the week when you configure the additional full backup for file and folders backup.
10. Upgraded Apache to v2.0.63 in the Windows Installation setup. This has fixed ' StoreGrid webserver start issue innon English OS' issue.
11. Upgraded PHP to 5.2.6 in the Windows, Linux and FreeBSD installation setup.
12. Skipped file count displayed in the server side backup progress window.
13. Fixed in the issue in sending the false Email report while successfully deleting the backup data using 'Backup Dataonly' option.
14. Fixed the issue in displaying the backed up files with double quotes in the 'List of backed up files' in the client sidebackup report.
15. Fixed the issue in navigating the files/folders with double quotes in the restore tree.
16. Enabled auto refresh of 'List Backups for Restore' page.
17. Fixed the logic issue in displaying the pie chart of used/available space on the Server Dashboard page.
18. Fixed the issue in editing the File/Folders Filter settings, if the number of filters configured for backup is large.
19. Fixed the issue in backing up Exchange Mailbox user folder/subfolder name with special characters like doublequote("), forward slash(/), backward slash(\), question(?), colon(:), asterisk(*), lesser than(<), greater than(>),pipe(|) and empty space( ) at the end of the folder name.
20. Supporting Microsoft SQL Server 2008 database backup.
21. StoreGrid can now run with backup operator privilege to avoid access denied issue while reading files for backup.
22. In Windows, default filters have been added to remove System Volume Information, Windows, RECYCLER foldersand pagefile.sys file for the full drive backup schedules.
Release Notes for StoreGrid 2.3.5
New Features In StoreGrid 2.3.5
1. Single page all backup status report: Status report of all backup schedules will now be available in a single page inthe backup server web console. The report indicates backups that have completed successfully, failed, partiallycompleted and missed. The report can be customized through user defined filters and can be scheduled to be sentin an Email on a daily or weekly basis.
2. Backup Window: StoreGrid client can now be configured not to backup during certain hours of the day.
3. Consolidated Customer Report: A consolidated report of all backup schedules of all clients under a customer alongwith disk space usage details can now be automatically generated on a daily, weekly or monthly basis and sent tothe customer’s Email ID.
4. On Demand Invoicing: Invoices can now be generated on demand for a specified billing period.
5. Email alerts for license expiry and disk space shortage: StoreGrid backup server can now be configured to sendEmail alerts for license expiry and disk space shortage. Replication server can be configured to send Email alertsfor license expiry.
6. Windows Mail backup.
Enhancements in StoreGrid 2.3.5
1. The number of versions to be kept for a file can now be set to zero when Intelli-Delta backup option is disabled.The backup server will then just store the latest version of the full file. When the file changes, StoreGrid will backupthe entire file and replace the existing file with this latest version.
2. Added a filter option to include or exclude files/folders by providing the complete name or by giving the completepath in Advanced file/folder backup filters.
3. Email notifications can now be sent to different Email addresses based on the status. For example, backupnotification Emails can be configured to be sent to one Email address when the backups fails and to another whenthe backup completes successfully..
4. Reports of the delete notifications (when backups, clients or customers are deleted) sent from the backup server tothe replication server will now be available in the backup server.
5. Specific calendar months can be selected while configuring additional monthly full backups.
6. Included details of skipped folders in the backup reports in the client as well as in the backup server.
7. Restoring folders/files by specifying the complete path instead of selecting from file/folder tree listing.
8. Displaying all client details (like client’s OS type, client’s plug-in type, client build/version number, license type etc.)
in the backup server.
9. Incremental backup is now supported for MySQL backup in Linux. In earlier StoreGrid versions, it was supportedonly in Windows.
10. New options added in Silent Installation for:
i. Whether given Windows login credentials (for running StoreGrid as a service) should be verified or notii. Enabling/disabling SSL portiii. Specifying the SSL backup port
Minor changes and bug fixes in StoreGrid 2.3.5
1. Replication progress window will now show activity as the backup server is gathering files for replication or when itis replication directories. As the backup server is gathering the files, the total file/folder count will increases. As thedirectories are replicated, the number of directories replicated so far will be displayed in the progress window.
2. Updated the restore progress window to show the number of files listed for restore when StoreGrid is initiating therestore process.
3. Fixed the issue where editing a backup with files/folders containing special characters (like &, ‘, “ etc) failed.
4. Fixed the issue where the backup report would show status as partially completed but 100% backed up when a fewfiles were skipped in a large backup set.
5. Software update will now be enabled by default. In 2.3, it was disabled by default and have to enabled manuallyafter installation.
6. Fixed client side software update reports.
7. If a peer is added using the IP address in the Add/Delete peer page, the IP will be added as entered. In earlierversions, StoreGrid does a DNS lookup on the IP and adds the peer with the lookup name and not the IP address.
8. StoreGrid sometimes exiting or hanging when mailbox is corrupted are fixed.
9. Cleaning up the dump location when StoreGrid is aborted during mailbox backup.
10. Limiting the number of attempts to reschedule the backup when mailbox backup fails.
11. Fixed the backup progress window to correctly update the status during mailbox backup.
12. Fixed the issues with installing StoreGrid builds in 64 bit Ubuntu machines.
13. Removed the MCALs shortage alert from the server dashboard in the replication server since MCALs are not relevantto replication server.
14. Enabled auto refresh of ‘List of Backup Schedules’ page.
15. Fixed the issue where ‘Keep Alive’ packets were not sent over SSL connection.
16. Enabled auto refresh in server dash board page.
17. Fixed automatic reconnection failure issue when the client is sending keep-alive messages to the backup server.
18. Fixed the issue where the data location path goes in a loop when configuring backup of ‘Document settings’ inWindows Vista.
19. Fixed the issue where replication sometimes doesn’t start.
20. StoreGrid will now automatically recover the backup configuration (.sbc) file in the backup server if the file iscorrupted.
21. Listing files and folders in ascending order in Restore Page.
Release Notes for StoreGrid 2.3
Issues fixed in StoreGrid v2.3 SP1 (Build No. - 2302008040515)
1. Backup server license gets disabled when StoreGrid gets bound under multiple IP addresses when the backup
server has multiple NIC cards.
2. StoreGrid skipping open files even when Volume Shadow Copy is enabled.
3. StoreGrid skips Outlook .pst files even when VSS is enabled.
4. StoreGrid stopping while backing up NTFS permissions of folders/files for which StoreGrid doesn't have readpermission.
5. StoreGrid skipping files with long file names.
6. High CPU usage in the backup server while starting a replication schedule.
7. Files shown as skipped in the replication reports while replicating "Deleted File" notifications, though the notificationsare actually replicated.
8. Backup server not showing the added MCALs though it reports that the license was applied successfully for partnerswho had their backup server migrated from 2.1 to 2.2
9. Server side backup email report shows "Failure" in subject while the email content shows "Success".
10. Error while creating a new Fixed Slab invoice plan.
11. Web console not displaying the build details in "About Us" link in server-only installations.
New Features In StoreGrid 2.3
1. Mailbox/Folder Level Exchange Backup and Restore in 32 bit environment.
PLEASE NOTE: StoreGrid can backup only up to Group level in 2007 Exchange Server (64 bit) machines. StoreGriddoesn't support backing up Mailboxes in 2007 Exchange Server (64 bit). Click here for more details
2. All Databases Backup of MS SQL Server.
3. Automatic StoreGrid update from backup server.
4. SSL connectivity between client, backup server and replication server.
5. NTFS File Permissions Backup.
6. Importing backup data from backup server to replication server.
7. Authentication of Backup Server with Replication Server.
8. Customer level disk space allocation in the backup server.
9. Advanced filters for selecting files/folders to backup.
10. Same Machine Backup: Backing up to local/external drives in Client Only installation. This feature is only for Localto Remote Server Migration purposes. You cannot restore from Same Machine Backup data.
11. Testing SMTP server settings and connectivity.
12. Testing backup server connectivity from client.
13. Deletion of Primary Server data in replication server.
14. Moving backup data when changing the client backup location in the backup server.
15. Skipped file(s) report in backup server.
Enhancements in StoreGrid 2.3
1. Significant backup performance enhancement especially for large number of small files.
2. Significant Replication performance optimizations.
3. Reestablishing client connection automatically after network interruption.
4. Optimized Event Sharing protocol.
5. Upgraded the SQLite version to 3.5.4 to reduce chances of database corruption.
6. Web console user interface enhancements.
7. Prorating invoices for partial billing periods.
8. In-built Mapped Network Drive Support for client backups.
9. Aborting backup and restore processes from client and backup server.
10. Versioning of backup data with Intelli-Delta disabled.
11. Limiting the number of client rescheduling attempts to connect to backup server in case of backup failure.
12. Multiple simultaneous restores at the client.
13. Limiting the number of client attempts to delete backup data in backup server.
14. Propagating backup delete operations from backup server to replication server.
15. Cleaning up idle sessions in the backup server.
16. Precompiled installation binaries for Linux and Mac.
17. Resuming replication from where it left off, even within a file.
18. Rebuilding sgbackup.db file from backup data.
Release Notes for StoreGrid 2.2.5
Bugs Fixed In StoreGrid 2.2.5
1. Have made enhancements to significantly improve the performance of the backup process. Performanceimprovement could be up to 60%, especially when backing up large number of small files.
2. Made enhancements to reduce backup server CPU usage during simultaneous replication of multiple backups.
3. Added a Vembu logo in the email reports. For branded builds, the partner logo will appear.
4. Application level Keep Alive is now enabled by default to prevent early closure of the network connection betweenthe StoreGrid client and the backup server.
5. Fixed the client authorization issues in the client and the server. If the client is not present in the backup server and'Auto Authorization' is not enabled, then the Authorization page will now show the right error messages. Also, onceauthorized, the user will be automatically redirected to the login page.
6. Fixed an issue related to not sending email reports when a few files are skipped during backup.
7. In the SP edition, the feature that automatically applies the StoreGrid server licenses to other StoreGrid servers inthe same network has been disabled.
8. Fixed the issue where a client connecting with a new IP address would get rejected if its previous connection from adifferent IP could not be cleaned up in the backup server. With this release, the previous connection will be cleanupforcefully and the new connection would be established.
9. Now you can update the encryption key to the old value after Client Disaster Recovery
10. Fixed the issue with updating the used space in the client side backup report when there are large number ofbackups scheduled. Also fixed an issue in updating the disk space usage in the server side reports after deletion ofa full backup.
11. Improved error recovery in Volume Shadow Copy enabled backups
12. Disabled the harmless 'Error:0' message from the tray.
13. Added an alert in the Edit Backup Server List of Edit Backup Schedule page to indicate that changing the backupserver will create fresh backups on the new server and that user should rather do a Local to Remote migration.
14. Fixed the reports for backup schedules in partially completed status.
15. Added an UI alert indicating that changing backup location on the server will change only for subsequent backups.
16. Added an UI alert indicating that space allocation may have to be done both at the server and the client levels.
17. Added an alert message for Suspend/Resume backup action.
18. Fixed the issue in the UI related to editing a customer with 'Auto MCAL' allocation setting.
Release Notes for StoreGrid 2.2.1
Bugs Fixed In StoreGrid 2.2.1
1. Fixed the issue of StoreGrid client exiting while listing files with wide characters.
2. Fixed the issue of StoreGrid displaying invalid file size while backing up files greater than 4 GB when VolumeShadow Copy is enabled.
3. Fixed the bug in StoreGrid client reset password when the backup server system name and the backup server namein the client are different.
4. Fixed the issue of Replication failure if the Trial Customer's auto-authorization is configured as "Denied".
5. Email SMTP server configurations related to SMTP authorization are now properly rendered in the StoreGrid WebConsole. The user name and password fields are still not rendered for security purposes.
6. Fixed the issue in receiving email reports when SMTP server adds more headers to the email sent by StoreGrid.
7. Fixed the security issue with the way StoreGrid was handling the backup encryption password.
8. New configuration option to allow backup database in the StoreGrid server to be stored in a separate hard diskother than the client backup location. This is useful to improve StoreGrid server performance including theStoreGrid server web console performance.
9. More customization of server dashboard features and dashboard refresh times added.
Release Notes for StoreGrid 2.2
New Features In StoreGrid 2.2
StoreGrid Server
1. Improved organization of the clients backing up to the server.
2. Server Side management of all licenses (MCAL based licensing).
3. Revamped 'Local To Remote Server Migration'; now additional full backups can also be done locally and migrated tothe remote backup server.
4. Revamped replication management, flexible replication scheduling, CPU usage control and lots more.
5. Replication progress support in both the Backup Server and the Replication Server
6. Primary Server Disaster Recovery from Replication Server using StoreGrid web console.
7. Invoice Generation based on Invoice Plans. You can assign the same plan across Customers.
8. Server Activities Dashboard (Current Active Clients Monitoring, Last 5 Successful/Failed Backups, Disk SpaceMonitoring, License Monitoring, etc.,)
9. Trial Client Settings (Evaluation Period/De-Activation Period/Automatic Cleanup of De-Activated Client, etc.,).
10. Individual Client/Backup De-activation.
StoreGrid Client
1. Advanced Plugins for Exchange using ESE APIs.
2. Advanced Plugins for MS SQL Server using VDI APIs.
3. Volume Shadow Copy support for Windows XP, Windows 2003 Servers systems.
4. In StoreGrid Service Provider Edition, there is no need to apply license keys in the client.
5. MySQL Plugin for windows
6. Restore progress window enhanced to show file based restore progress
7. Revamped Client Dashboard.
General
1. Secure(https) Web Console.
2. Support for 64-bit Windows Operating Systems.
Bugs Fixed In StoreGrid 2.2
1. Unicode File listing and backup (supporting long file path > 256 characters) in windows.
2. Local Dump location for Exchange/SQL plugins can be specified from the backup configuration page itself.
3. Application level Keep Alive protocol supported for working around the 'Unable to send backup details ...' issue.
4. Outlook Mail box PST File is backed up even if it is specified in a location other than the default location.
5. Fixed the error 'File Modified during backup' when Open File Plugin is installed and available.
6. "Replication In Progress" issue in the Replication Server fixed.
7. Disk Space Allocation issue in replication server fixed.
8. Client Backup Location can now be modified even if a client is already backing up to the server. Note that, only thenew backup schedules will be backed up to the new location and the older backup schedules will continue backingup to the older backup location
9. Service Installation of Apache in Vista is now supported
10. Duplicate peers issue in the discovered peer list fixed.
11. Fixed the bug on Skipped file count when a file is listed for backup and is unavailable during the backup process.
12. Fixed restore tree listing issue when one of the drive is available in the backup database but no files are availablefor the drive in the current full backup.
Release Notes for StoreGrid 2.1.1
New Features In StoreGrid 2.1.1
StoreGrid Server
1. Server Side Restore --> Restoring client's backed up files from Server Web Console itself.
2. Server Side Email Reporting - Backup/Restore/Delete/Replication
3. Performance Improvements in Replication
4. Email Filtering based on Backup Status and Customer/Client/Backup Jobs.
5. Customer Invoice Configuration from the StoreGrid Web Console.
StoreGrid Client
1. Run a list of commands before & after a Backup Schedule.
2. MSSQL - Maximum number of DIFFERENTIAL backups to be had in server.
3. MSSQL - Support for multiple databases in single backup job.
4. Suspend & Resume on Large file backups. Start from where it left.
5. Client side Historical Backup Report.
6. Client Backup Progress updated with a particular File's backup progress.
7. Multi-threaded backup scheduling.
8. Skipped files list on Restore Report.
9. Email Filtering based on Backup Status and Backup Names.
General
1. Performance improvements for backups.
2. Internationalization related enhancements.
3. Configurable StoreGrid Ports [GUI/SERVER].
4. Configurable IP Address to which the sockets are bound.
Bugs Fixed In StoreGrid 2.1.1
1. Immediate Scheduling/Suspension of Replication Schedules after Replication Configuration.
2. Multiple Replication Report entries for the same error fixed
3. Suspend/Resume/ScheduleNow of SQL Server backup jobs
4. Password is not mandatory in Add Client, when auto authorization is enabled
5. Listing Empty folders in Restore Tree
6. When Invoice generation frequency updated, Next Invoice Update time is also updated
7. Unique invoice recipients for different customers
8. Updation of Used space in Replication server's Backup report
9. Exchange Server 2000 supported.
10. Error message reporting on Exchange Server & SQL Server backup failure
11. MSSQL Server & Exchange Server backup failure when installed under directory with special characters
12. Client License is not updated in server when the new license is applied
13. Added backup progress message for all plugins.
Release Notes for StoreGrid 2.1
New Features In StoreGrid 2.1
StoreGrid Server
1. Support for generating rules based Customer Invoice.
2. Support for Replication of data in StoreGrid Server.
3. All server databases moved to Server Backup location to support easily creating redundancy for a StoreGridServer's data.
4. Support for monitoring Backup activity from the server side.
5. Local to Remote Migration now supports migrating clients to Trial Customer too.
StoreGrid Client
1. Support for automatic MS Exchange Server backups.
2. Support for automatic MS SQL Server backups.
3. Support for automatic Active Directory/System State backups.
4. Support for editing files and folders of a backup schedule.
5. On Demand scheduling of backup schedules using a "Schedule Now" feature.
6. Option to disable Automatic Directory Monitoring in Windows to support backing up mapped drives and applicationgenerated files, which could delete and create the same files, create lots of temp files which need not be backed up.
7. Support for backing up empty folders.
8. Supporting of listing Mapped Drives in the backup schedule configuration tree.
9. Added keep alive feature in connections to server to fix NAT timeout issues.
Bugs Fixed In StoreGrid 2.1
1. Fixed bugs in calculation of used and free disk space for customers and clients.
2. Fixed bugs and usability issues in Auto Authorization between StoreGrid client and server.
3. Fixed the limitation while deleting a file and creating a new file with the same name.
4. Fixed RSync bug while restoring versioned large files greater than 4 GB.
5. Fixed the bug related to not emailing backup reports when there is a connection failure with the StoreGrid serverfixed.
6. Fixed a few memory leak issues.
7. Fixed bugs in updating reports and disk space usage during Local to Remote Migration.
8. Fixed the bug related to server showing "backup in Progress" after the client has completed the backup.
9. Fixed the bug related to server not sending a negative file acknowledgement when the server could not rename thetemp file name to the original file name for a successfully backed up file.
10. Fixed the bug related to client getting added to the server even if authorization fails.
11. Updated MySQL backup in Linux to use mysqldump utility to support InnoDB tables.
12. Fixed issue related to Trial Customer Migration overwriting an existing client data if the same client is migrated fromtrial to a customer. Only fresh clients can be migrated from trial to a customer.
Release Notes for StoreGrid 2.0
New Features In StoreGrid 2.0
Infrastructure
1. Major Design and Architecture changes for better scalability and performance.
2. All modules in both server and client use embedded RDBMS.
3. All metadata of a client and client book keeping for management use the RDBMS. Provides better capability forreporting, easier management functionality and better scalability.
4. Designed to easily support other RDBMSs like MySQL, PostgreSQL, MS-SQLServer, Oracle etc. for enterprisescalability, in future releases of StoreGrid.
StoreGrid Server
General
1. Configure authentication requirements for a client.
2. Server side drill down reports for each backup schedule of a client.
3. Reporting on disk space based on both original size of files and the disk space used in the server after compression.
4. Server side historical reports for each backup schedule for each client.
5. Ability to consolidate client events in the server and filtering based on client name and other event parameters.
Service Provider Edition
1. Comprehensive Customer based management in StoreGrid server.
2. Ability to add customers.
3. Apply license for a customer with restrictions on number of clients.
4. Disk quota management at the customer level and client level.
5. Ability to activate/deactivate a customer or a specific client within a customer.
6. Local to Remote Server Migration of Backups.
7. Trial Customer to New Customer migration of backups.
StoreGrid Client
1. Support for multiple full backups and incremental backups in between.
2. Support for the first full backup to a local server and then incremental backup to a remote server.
3. Configurable encryption key length (from 64 to 448 bits).
4. Support for time based restores.
5. Files and Folders filtering support in restore UI.
6. Permanent deletion of backed up Files and Folders with filtering support.
7. Support for sharing client events to StoreGrid servers.
8. Support for event filtering based on various event parameters.
9. Support for configuring clients with password protected access to the server.
10. Support for emailing backup and restore reports to the user.
11. Local to Remote Server Migration of Backups.
Bugs Fixed In StoreGrid 2.0
1. The 256 character problem in Windows backups & restore is resolved.
2. StoreGrid 2.0 can now accept varying length password for encryption. In StoreGrid 1.6, the encryption passwordhad to be exactly 8 characters.
3. For Outlook and Outlook Express, StoreGrid 2.0 has the option of closing it automatically and backing it up or youcan install the StoreGrid Open File Backup Plugin to backup Outlook and Outlook Express without closing theapplications during backup.
4. In StoreGrid 1.6, a full backup of StoreGrid Metadata database was done for every schedule. This was taking timeeven when the incremental backup schedules were very small. In StoreGrid 2.0, you can configure the metadatabackups to run infrequently or even disable it.
5. Suppose a backup is scheduled to run daily at 8:00AM. However, if the StoreGrid machine is started only at 9:00AM then this backup schedule will be rescheduled for next day 8:00AM without actually running the backup. Thisissue is fixed in StoreGrid 2.0 Release.
6. FQDN (Fully Qualified Domain Name) problem fixed in Discovery Module.
7. In StoreGrid 1.6, special characters was not allowed in License User name. This is fixed in StoreGrid 2.0 Release.
8. When a backup is restored to another machine instead of the original client, then its restore report cannot beviewed. This issue is fixed in StoreGrid 2.0. And now restore report can be viewed(Reports->Restore Reports) in themachine in which the restore was done.
9. Directory Statistics are now correctly backed up and restored.
Click here for a list of Known Issues In StoreGrid
Click here for a list of Limitations In StoreGrid
SupportVembu's support plans include:
1. For StoreGrid Free Edition, support is provided through the StoreGrid User Forum
2. For StoreGrid Professional and Service Provider Edition users, free email support is provided during the 30-dayevaluation period. StoreGrid support is offered through email, forum and the StoreGrid KnowledgeBase.
a. StoreGrid Technical Support Request Form : http://storegrid.vembu.com/technical-support.php
b. StoreGrid Discussion Forum : http://storegrid.vembu.com/forum/viewforum.php?f=1
c. StoreGrid KnowledgeBase : https://support.vembu.com/index.php?_m=knowledgebase&_a=view
Premium Support Plans:
1. For StoreGrid Professional and Service Provider Editions, we offer three Premium Support Plans (Bronze, Silver andGold) that include instant messenger, phone support and other support options tailormade to suit the technicalsupport requirements of StoreGrid partners.
2. You can learn more about StoreGrid support plans at http://storegrid.vembu.com/online-backup/support-plans-sp.php
Support Email Id
Please send all your support questions to [email protected]
Vembu Software License Agreement (Service Provider Edition)If you want to obtain a license to use our StoreGrid Service Provider Edition software and/or subscribe to ourservices, read the terms of this agreement ("Agreement") carefully. Indicate your acceptance of these terms byselecting the "Agree" button at the end of this Agreement and if you do not agree to all of the terms of thisAgreement, select the "Decline" button at the end of this Agreement and do not download, access or use theSoftware.
If you have separately agreed (in writing) to license terms for your license to this Software, then the terms ofsuch written agreement shall override this Agreement and the said written agreement shall govern your use of theSoftware.
1. Scope of the Agreement
1.1. This Agreement sets forth the terms upon which you may (i) license the Evaluation Version of theSoftware in order to evaluate it and/or (ii) license the Software to provide data backup Services to yourCustomers.
2. Definitions
2.1. In this Agreement, "you" means the legal entity (more particularly identified in the partner applicationform) that has entered into this Agreement with Vembu Private Limited by accepting the terms hereof and"Licensor" means Vembu Private Limited, a company incorporated in India and having it's registered officeat Office A, II floor, 209, Velachery Main Road, Velachery, Chennai - 600042, India. You and the Licensormay each be referred to individually as a "party" or collectively as "the parties" in this Agreement.
2.2. "Backup Server" means your server where the Software is installed in Server mode and onto whichCustomer Data is backed up as part of your Data Backup Services.
2.3. "Client Software" means the component of the Software in binary object code form which is to beinstalled in the Customer's server / computer devices as permitted by your Package to enable the Customerto access and use the functionality of the Software.
2.4. "Customer" means an individual or legal entity that obtains Data Backup Services from you.
2.5. "Customer Agreement" means the contract between you and a Customer under which you provide DataBackup Services to such Customer.
2.6. "Data Backup Services" means the data backup services that you provide to your Customers bymaking the Software functionally available to your Customers.
2.7. "Evaluation Version" is the version of the Software that is provided to you without charge inaccordance with the terms hereof.
2.8. "MCAL" is the unit by which the Licensor measures your use of the Software. For details of the numberof MCALs you will use when you install or use the Software in the production environment, please refer tothe pricing and licensing section in your Partner Zone account.
2.9. "Node" shall mean a device with an operating system where the Software, or any part of the Software,is installed.
2.10. "Partner Zone" is an online resource provided to you by the Licensor on its Website to enable you tomanage your license requirements.
2.11. "Permitted Purposes" means the purposes for which you are permitted to use the Software as detailedin your Package.
2.12. "Package" means the package of services you have subscribed to under this Agreement. The Packagewill include the details of the Software licensed to you, your systems requirements, your PermittedPurposes, the fees payable by you, the MCALs credited to your account, the branding services madeavailable to you and the terms of the support services you are eligible for. The terms of your Package asavailable at the Partner Zone shall be deemed to be part and parcel of this Agreement.
2.13. "Replication Server" means your server where the Vembu Replication Server Software is installed andonto which you may back up your Backup Server.
2.14. "Server Software" shall include the following software components:
2.14.1. The " Vembu Backup Server Software" in binary object code form which is to be installed inbackup server mode to enable the provision of Date Backup Services, and
2.14.2. The " Vembu Replication Server Software" in binary object code form which is to be installedin replication server mode to enable replication of the data on a Backup Server.
2.15. "Software" means the Licensor's StoreGrid Service Provider Edition together with its documentationidentified in your Package that you may license under this Agreement to provide Data Backup Services toyour Customers. The Software includes Server Software and Client Software. The term Software alsoincludes any evaluation version of the Software and any updates, bug fixes or patches to the originalSoftware provided to you under this Agreement at no additional cost.
2.16. "Website" shall mean the Licensor's website at vembu.com, storegrid.com and storegrid.net.
3. Grant of License for Evaluation
3.1. Subject to the terms and conditions of this Agreement, the Licensor grants to you a non-exclusive,non-transferable and limited right to use the Evaluation Version of the Software in binary object code form,for trial and evaluation of the performance of the Software. This license is valid for a period of thirty (30)days from the date of your download or installation of the Evaluation Version, whichever is earlier("Evaluation Period"). If you want to use the Evaluation Version beyond the Evaluation Period or if you wantto use Software to provide Data Backup Services to your Customers, you have to purchase licenses for thesame in accordance with the terms of this Agreement. If you do not purchase licenses to use the Software(any version) beyond the Evaluation Period, you should stop using the Software (all versions) and / or itsfunctionality and delete all the copies of the Evaluation Version installed in your computer/s forthwith on theexpiry of the Evaluation Period. Subsequent downloads of the Evaluation Version by or for you does notextend, renew or otherwise restart the term of the license for the Evaluation Version granted herein.
4. Grant of License to Provide Services
4.1. Subject to the terms and conditions of this Agreement and your Package, the Licensor grants you anon-exclusive, terminable, non-transferable, worldwide and limited right to use the Software for thePermitted Purposes in order to provide Data Backup Services.
4.2. Your right to use the Software in accordance with the rights granted to you under this Agreement islimited by the number of MCALs you have purchased and the number of MCALs remaining unutilized in youraccount at the Partner Zone and your Backup Server.
4.3. The license and rights granted to you under this Agreement will automatically terminate uponexpiration or termination of this Agreement.
5. Permitted Use and Restrictions
5.1. The Permitted Purposes for which you may use the Software will be as selected by you and mentionedin your Package. You may use and permit the use of the Software only as expressly permitted in yourPackage and not in any other manner.
5.2. Activation of the Software will require MCAL license keys. MCAL licenses will be credited to your PartnerZone account after your purchase of the licenses. The MCAL license keys generated are for use only on asingle Backup Server identified at the time of your generating the MCAL license keys from the Partner Zone.
5.3. An MCAL license key is for one-time use and should not be reused once a key is applied and utilized.You will not in any way attempt to circumvent any mechanism as may be used by the Licensor from time totime to prevent reuse of MCAL keys.
5.4. You acknowledge and agree that to ensure that use of the MCAL license keys is as described above inclause 5.1, 5.2 or 5.3, each time you use the Software, the Licensor may track the number of Customersbacking up to the Backup Server, the MCAL units consumed by the Backup Server and other relevantdetails for tracking your use of the Software. If the Licensor finds that you have violated the terms of use ofthe Software as permitted herein, the Licensor reserves the right to forthwith terminate this Agreement andyour use of the Licensor's services.
5.5. You may copy or install the Software or any part thereof only on such Nodes as specifically permittedin your Package.
5.6. The copy of the Software provided to you under this Agreement is licensed to you and nothingcontained in this Agreement transfers any ownership rights in the Software or any part thereof to you. The
Licensor reserves all rights not expressly granted to you including all rights in the source code for theSoftware.
5.7. You may not rent, lease, sell, transfer, publish, make available or distribute the Software or itsfunctionality to any third party except as expressly permitted by this Agreement.
5.8. You may not export the Software or any part thereof or allow its use in any country that does not haveintellectual property laws that will protect the rights of the Licensor in the Software.
5.9. You may not disassemble, decompile, unlock, decode, reverse-engineer or reverse translate theSoftware or otherwise take any action to recreate or discover the equivalent of the Software.
5.10. You may not alter, adapt, translate, enhance, customize or otherwise modify the Software.
5.11. You may not combine the Software or any portion thereof with any other software, source codes,data, databases or technologies save as may be expressly provided for by this Agreement.
5.12. You may not make copies of the Software or allow copies of the same to be made by others except asspecifically permitted by this Agreement.
5.13. You may not attempt to bypass or circumvent the security procedures applicable to the Software orprevent or restrict in any manner any automated software updating services installed in the Software.
5.14. You may not remove, modify or obscure any copyright, trademark or other proprietary rights noticesthat appear on / during the use of the Software. This Agreement does not grant you any rights to anytrademarks, logos or service marks of the Licensor.
5.15. The Software contains programs that collect data about use of the Software on all Nodes. You agreethat the Licensor may collect such data about use of the Software and that the data collected through suchprograms may be used by the Licensor to monitor your compliance with the terms of this Agreement, toprovide you with support services and/or to improve the Software. You agree that you will not prevent or inany manner restrict the right to the Licensor to collect such data about use of the Software.
5.16. Portions of the Software include software with open source licenses from third parties that govern theuse of those portions. Nothing contained herein limits the rights and obligations you may have under suchopen source licenses. However, the disclaimer of warranty and limitation of liability provisions in thisAgreement will apply to the Software as a whole. For details of the open source software included in theSoftware and the terms of the license for the same, please refer http://storegrid.vembu.com/online-backup/open-source-license-agreement.php.
6. Your Account at the Partner Zone
6.1. On your acceptance of this Agreement, the Licensor will create an account for you at the Partner Zone.As and when you purchase licenses for the Software, the Licensor will credit the MCALs purchased by youinto your account.
6.2. To access your account at the Partner Zone, the Licensor will provide you with a password. When youaccess your account for the first time, you will be prompted to change the default password provided to youby the Licensor. You shall be solely responsible for safeguarding the security and confidentiality of the username and password for your account. If you lose your password, you will not be able to access youraccount or use the Software. You shall be solely responsible for all actions initiated using your user nameand password. If you become aware of any unauthorized use of your user name or password, you maynotify the Licensor of the same by e-mail addressed to [email protected] with the title"Unauthorised Use of User Name / Password". The Licensor will not be liable for any loss or damage arisingfrom your failure to maintain the security and confidentiality of your user name and / or password.
7. Support Services
7.1. If your Package does not entitle you to the premium paid support services provided by us, you will beentitled to receive our standard support services.
7.2. You will be eligible to receive our standard support services for as long as you have unutilized MCALSto your credit in your Partner Zone account or on your identified Backup Server.
7.3. Our standard support services entitle you to receive bug fixes and updates that are provided to all ourpartners generally, free of charge. We will provide you with support services by e-mail. We will respond toany request for support from you within one (1) business day from receipt of your request for standardsupport services. The response time guaranteed only applies for the initial response where best effort willbe made to provide the solution to the issue. There is no guarantee that the issue reported would be
Change Trial To Paid : Clicking on this action converts the trial client to paid client.
NOTE: After you convert a trial client to paid client, you cannot revert back.
Change Client Side Settings : The backup settings on the client such as Backup Window, BandwidthThrottling, Automatic Software Update options can be changed from the backup server. Also Adding aBackup Schedule is also possible. These changes made in the backup server will be picked up by the clientand the client will automatically apply them. The settings that are shown in this page may not be the samepresent in the client currently.
Export backup : The backup data can be exported to any destination location by clicking on this icon. Thisfeature allows the user to export the backup data and the backup database to the user given destinationlocation as a "Local" backup type which is then used to restore by attaching the data to the Client (usingLocal backup "Disaster Recovery "). Instead of restoring the backup data from the client by connecting thebackup server, using this feature, the data can be restored quickly from the client machine itself therebysaving time and bandwidth usage. The backup is exported as a "Local " backup for this purpose.
The export of backup data can be executed with two options namely
With a prefix name (Alias name) - If the user wishes to attach the exported backup data and restore itin the case where the backup already exists in the Client,then this option should be used.Otherwise thebackup cannot be attached to the Client using "Disaster recovery " (as the backup names arealways unique for a client) . Here, the backups are exported by using a user given prefix name and thebackup is exported in the format "Prefix_Backup_Name ".
Important Note:: The backup(s) exported with this option can be attached to the Client and can only beused to restore the backup data.The backup options like "Schedule ", "Suspend/Resume ", "Edit " is notavailable for such backups.
Without prefix name - If the user wishes to attach the exported backup data in the client and restore it inthe case where the client is freshly installed with the same " StoreGrid ID ", then this option can be used.For such backups, all the backup options like "Schedule ", "Suspend/Resume ", "Edit ", "Restore " areavailable.
Limitations
Limitations for Export backup feature:
1. "Abort/Suspend" of Export of backup data is currently not available.
2. For "Cluster enabled" backup servers, the backup data can be exported only in the backup servers wherethe client is "Node locked". It cannot be exported from the other backup servers available in that Cluster.
3. Export of backup data is not available for servers installed as an "Amazon machine instance(AMI)"
11.2. If on inspection you are found to have violated the terms of this Agreement, you shall forthwithpromptly order sufficient MCALs to cover any shortfall. You shall also bear the cost of the audit and inaddition, you shall also be liable to pay the Licensor liquidated damages at the rate of USD 500 per Nodewhere the Software or any part of it has been used in violation of this Agreement. This amount of liquidateddamages represents a genuine pre-estimate of the loss, which it is anticipated that the Licensor wouldsuffer as a result of your failure to comply with the terms of this Agreement. This payment does not limitother possible rights of the Licensor including right to terminate this Agreement.
12. Confidentiality
12.1. All information and data disclosed by one party to the other party pursuant to this Agreementincluding but not limited to the Software, trade secrets, the terms of this Agreement and the Package isand shall remain the proprietary and confidential information of the disclosing party ("ConfidentialInformation").
12.2. Each party agrees to maintain the Confidential Information of the other in confidence and to use ordisclose such Confidential Information only as permitted by this Agreement unless otherwise permitted inwriting by the disclosing party.
12.3. Each party will take all reasonable precautions to maintain the confidentiality of the ConfidentialInformation of the other, including without limitation, requiring employees and others with access to theConfidential Information to sign confidentiality agreements and limiting access to the ConfidentialInformation to employees on a "need to know" basis.
12.4. A party will immediately notify the other upon discovery of any unauthorized use or disclosure ofConfidential Information and will cooperate in any reasonable way to help the other party regain possessionof the Confidential Information and prevent further unauthorized use.
12.5. Confidential Information shall not include:
12.5.1. information which at the time of disclosure is in the public domain;
12.5.2. information which after disclosure is published or otherwise becomes part of the publicdomain through no fault of the receiving party or its employees or agents;
12.5.3. information which the receiving party can document through written records, dated prior tothe time of disclosure, as having been in the receiving party's possession and belonging to it at thetime of disclosure;
12.5.4. information which the receiving party can document was developed independent of andwithout any reliance / access to the Confidential Information of the disclosing party; or
12.5.5. information which the receiving party can show as having been received after the time ofdisclosure by the receiving party from a third party without any obligations of confidentiality.
12.6. The obligation of confidentiality shall survive termination or expiry of this Agreement and shall bebinding on the parties for a period of five (5) years from such termination / expiry.
13. Warranty
13.1. The Licensor warrants that it holds all right, title and interest in and to the Software or that it isotherwise entitled to provide the Software to you on the terms contained herein.
13.2. The Licensor warrants that the Software, when it is delivered to you, is free of viruses, Trojanhorses, worms, and other similar destructive or disabling code.
13.3. THE ABOVE IS A LIMITED WARRANTY AND IS THE ONLY WARRANTY MADE BY LICENSOR. THESOFTWARE IS PROVIDED ON AN "AS IS" BASIS AND YOUR USE OF THE SOFTWARE IS AT YOUR SOLERISK.
13.4. THE LICENSOR EXPRESSLY DISCLAIMS AND YOU HEREBY EXPRESSLY WAIVE ALL OTHERCONDITIONS, WARRANTIES AND REPRESENTATIONS, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. LICENSOR DOES NOT WARRANT THATTHE SOFTWARE WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION OF THE SOFTWARE WILL BEUNINTERRUPTED OR ERROR-FREE OR THAT ERRORS IN THE SOFTWARE, IF ANY, WILL BE CORRECTED.
13.5. THE LICENSOR'S ABOVE LIMITED WARRANTY IS IN LIEU OF ALL LIABILITIES OR OBLIGATIONS OFLICENSOR FOR DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE INSTALLATION, USE ORPERFORMANCE OF THE SOFTWARE. THE SOFTWARE'S FAILURE TO PERFORM IN ACCORDANCE WITH THE
SPECIFICATIONS SHALL NOT BE CONSIDERED A FAILURE OF THE ESSENTIAL PURPOSE OF THEWARRANTIES CONTAINED HEREIN.
14. Indemnity
14.1. Subject to the terms of this Agreement, you agree to indemnify and hold harmless the Licensor, itsemployees, directors and agents for any damages, legal fees and costs arising from or as a result of theviolation of any of the terms of this Agreement.
14.2. Licensor will, at its expense, defend any claim brought against you or your officers, directors,employees or agents and indemnify all of them against any liability for damages awarded in any suchaction, insofar as the same is based on a claim that the Software infringes any copyright or otherintellectual property of a third party. If the Software is found to infringe any copyright of a third party,Licensor shall:
14.2.1. secure a license from such third party to allow your continued use of the Software,
14.2.2. cure the Software of any infringing elements, or
14.2.3. provide you with substitute, non-infringing software.
This section lays down your sole remedy against the Licensor for any claim that your use of the Software inaccordance with the terms of this Agreement violates any third party's rights.
14.3. The obligations under the foregoing indemnity by the Licensor are subject to the condition that:
14.3.1. you have not used the Software contrary to the terms of this Agreement;
14.3.2. you give the Licensor prompt written notice of any claim or action for which indemnity issought;
14.3.3. you allow the Licensor complete control of the defense or settlement of the claim; and
14.3.4. you co-operate with the Licensor in the defense of the claim as may reasonably be requiredby the Licensor.
15. Limitation of Liability
15.1. NOTWITHSTANDING ANYTHING CONTAINED IN THIS AGREEMENT, UNDER NO CIRCUMSTANCESSHALL THE LICENSOR BE LIABLE TO YOU OR ANY OF YOUR CUSTOMERS FOR ANY SPECIAL, INDIRECT,PUNITIVE, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING BUT NOT LIMITED TO DAMAGES FORLOSS OF PROFITS OR SAVINGS, BUSINESS INTERRUPTION, LOSS OF INFORMATION OR DATA, INCLUDINGCUSTOMER DATA) WHETHER IN CONTRACT, NEGLIGENCE, TORT OR OTHERWISE ARISING OUT OF YOURUSE OR INABILITY TO USE THE SOFTWARE OR THE BREACH OF THIS AGREEMENT, EVEN IF ADVISED OFTHE POSSIBILITY OF SUCH DAMAGES.
15.2. A PARTY'S AGGREGATE LIABILITY FOR DAMAGES UNDER THIS AGREEMENT SHALL NOT EXCEED THEAMOUNTS RECEIVED BY THE LICENSOR FROM YOU DURING THE PERIOD OF ONE (1) YEAR IMMEDIATELYPRIOR TO THE DATE OF THE OCCURRENCE OF THE EVENT THAT GAVE RISE TO THE CLAIM. IN NO EVENTSHALL THIS LIMITATION LIMIT EITHER PARTY'S LIABILITY:-
15.2.1. FOR ANY WILLFUL BREACH OF THE TERMS OF THIS AGREEMENT; OR
15.2.2. FOR INFRINGEMENT OF THE OTHER PARTY'S OR ANY THIRD PARTY'S INTELLECTUALPROPERTY RIGHTS.
15.3. THE LIMITATIONS SPECIFIED IN THIS SECTION WILL SURVIVE AND APPLY EVEN IF ANY REMEDYSPECIFIED IN THIS AGREEMENT IS FOUND TO HAVE FAILED IN ITS ESSENTIAL PURPOSE.
16. Term and Termination
16.1. This Agreement shall commence on the date on which you agree to the same by selecting the"Agree" button at the end of this Agreement and shall continue in force till the occurrence of the earlier ofthe following events:
16.1.1. the termination of this Agreement by either the Licensor or by you in accordance with theterms of this Agreement; or
16.1.2. on the date of expiry of a continuous period of 3 months from the date on which the MCALS
in your account at the Partner Zone or your Backup Server is zero (0).
16.2. Either party may terminate this Agreement without cause by giving the other sixty (60) days priorwritten notice of its intention to do so.
16.3. Either party may terminate this Agreement for cause by giving the other party thirty (30) dayswritten if the other party breaches any term or condition of this Agreement. This Agreement will not beterminated if the breaching party cures the breach within thirty (30) days of receipt of notice.
16.4. Notwithstanding anything contained herein, the Licensor may terminate this Agreement forthwith if:
16.4.1. You use the Software in breach of clause 3 : Grant of License or Clause 5 : Permitted Useand Restrictions;
16.4.2. You make any assignment for the benefit of creditors, file a petition for bankruptcy or areadjudged bankrupt or become insolvent or are placed in the hands of a receiver; or
16.4.3. You terminate or suspend your business operations.
16.5. Notwithstanding anything contained herein, you may terminate this Agreement forthwith if:
16.5.1. If you are unable to use the Software for a continuous period of one hundred (100) businessdays in accordance with the rights granted to under this Agreement and your Package;
16.5.2. If the Licensor fails to perform its support or other obligations hereunder, and such failure isnot cured within thirty (30) days after receipt by Licensor of written notice in this regard; or
16.5.3. If the Licensor ceases its operations.
16.6. The termination or expiration of this Agreement will automatically terminate all licenses and rightsgranted to you under this Agreement. Therefore, on such termination or expiry you and your Customers willcease using the Software and permanently delete all copies of the Software and all parts thereof from allNodes and return all other Confidential Information of the Licensor in your possession or control. Within ten(10) days from the effective date of the termination, you shall certify in writing that all copies of theSoftware have been have been returned, permanently deleted and destroyed.
16.7. On your compliance with obligations under clause 16.6, the Licensor shall refund to you thesubscription fee for the unused MCALS in your Backup Server and Partner Zone account if the terminationof this Agreement was as follows:
16.7.1. By the Licensor without cause pursuant to clause 16.2 or
16.7.2. By you, further to clause 16.3 on account of a breach of this Agreement by the Licensor orfurther to clause 16.5.
16.8. The expiry or termination of this Agreement will not affect any rights of the parties accrued to themup to the date of termination or that by their terms are to continue in effect after a termination orexpiration hereof.
16.9. Neither party will be liable to the other for exercising its right to terminate this Agreement inaccordance with the terms hereof.
17. Intellectual Property Rights
17.1. All rights, title and interests including intellectual property rights in and to the Software and theWebsite and any derivatives, suggestions, ideas, enhancement requests, feedback, recommendations orother information provided by you or any other party relating to the Software or the Website are owned /licensed by the Licensor and you have no right, title or interest therein except for the limited license as setforth in the Agreement.
17.2. You confirm that you have read and understood the trademark and copyright notices on the Websiteand agree that this Agreement does not grant you any right, title or interest in any of the said marks orcopyrighted material available on the Website.
18. Governing Law and Jurisdiction
18.1. This Agreement, its existence, validity, its interpretation, performance and all matters related to orarising from this Agreement shall be governed by the laws of India without regard of any conflict of lawprinciple or rules.
18.2. You agree that any dispute between the parties arising out of or in connection with this Agreement(including any question regarding its existence, validity or termination) shall be submitted exclusively tothe competent courts located at Chennai, India to the exclusion of any other court that may havejurisdiction in the matter.
19. General
19.1. Relationship of the Parties
The relationship between the Licensor and you is on a principal to principal basis and nothing expressed orimplied in this Agreement shall be deemed to constitute either party as the partner or agent of the other.
19.2. Assignment
Except as may be otherwise expressly provided in this Agreement, you may not assign, sub-contract ortransfer in any manner whatsoever this Agreement or your rights and obligations under this Agreementwithout first obtaining the Licensor's written consent. The Licensor may freely assign this Agreement or anyof its rights or obligations to any third party.
19.3. Notices
Any notice or other communication required to be given under this Agreement will be deemed to be validlygiven if in writing and delivered by mail or e-mail to the other at their respective address as notified below.
To the Licensor:
Address: Vembu Pvt. Ltd.II A, Kaashyap Enclave209, Velachery Main RoadVelacheryChennai - 600042IndiaE-mail: [email protected]
To you:
Address and e-mail: as available in your account with the Partner Zone
A notice is deemed to be received if:
- Delivered by registered mail, on receipt; and- Sent by email, the earlier of the sender's receipt of confirmation of successful delivery or two days afterdispatch (being when the relevant email first leaves the sender's network for delivery to the recipient'saddress) provided the sender does not receive any indication of the failure of, or delay in, delivery within24 hours after dispatch.
19.4. Severability
If any term or provision of this Agreement is held to be illegal, invalid or unenforceable that particularprovision will be deemed modified to the extent necessary to make the provision valid and enforceable andthe remaining provisions will remain in full force and effect.
19.5. Waiver
Neither party shall be deemed to have waived any right under this Agreement unless the waiver is inwriting and signed by the party waiving its right. Any failure or delay by a party to exercise any right orremedy under this Agreement shall not operate as a waiver of that right or remedy. Any waiver by a partyof any breach, or failure to exercise any right or remedy, under this Agreement shall not constitute awaiver of any subsequent breach or continuing right.
19.6. Remedies cumulative
Except as is expressly stated otherwise in this Agreement, the rights and remedies available to either partyin this Agreement are cumulative and are not exclusive of any rights or remedies provided by law or underthis Agreement; and the exercise of any of the rights and remedies provided in this Agreement by eitherparty shall not prejudice the exercise of any other right or remedy under this Agreement or existing at law.
19.7. Entire agreement
This Agreement constitutes the entire agreement of the parties with respect to its subject matter andsupersedes all previous agreements, arrangements, understandings or representations relating to that
subject matter.
19.8. Amendment
The Licensor may modify this Agreement at any time without notice to you by posting a revised Agreementon the Website or the Partner Zone. You are responsible for regularly reviewing this Agreement. Yourcontinued use of the Website or the Partner Zone constitutes your binding acceptance of this Agreement,including any modifications that Licensor makes.
19.9. Precedence
In the event and to the extent of any inconsistency between this Agreement, the details of your Package inthe Partner Zone or any other part of the Website, these documents shall, unless expressly statedotherwise, be interpreted in the following descending order of precedence (from high priority to lowpriority):
- this Agreement;- your Package; and- the rest of the Website.
© Vembu Technologies Pvt. Ltd. All rights reserved.
Vembu Technologies Pvt. Ltd.Office-A, II Floor, "Kaashyap Enclave"13-A/209, Velachery Main Road, VelacheryChennai - 600 042IndiaPhone : +91-44-4202 2671.Website: www.vembu.comWebsite: www.vembu.com