Introduction
What is StoreGrid?
Very simply, Vembu StoreGrid is an extremely versatile Backup Software that works with your Existing Hardware ! StoreGrid literally creates a storage grid from free space on your network. For example, if you have a few PCs connected through a LAN but no backup server, StoreGrid can create a trusted intranet peer-to-peer backup solution to backup desktop and laptop data -it simply taps into surplus hard disk capacity on PCs in a network and uses this to back up user data.
But say, you did have a backup server (or servers) - StoreGrid could then be deployed in a conventional client-server mode. StoreGrid also handles remote online backups easily – ideal if you prefer backing up to a server outside your network.
Like we said, StoreGrid works with your existing hardware !
But there’s more – StoreGrid is more than plain vanilla backup. Features include robust data encryption, compression & versioning – and all of these are user configurable. Backup schedules can be continuous, at fixed intervals, or at a particular time and day. When you do need to restore your data, you could drill down as deep as you’d like. Restore everything, just a few folders, or just a few files – its your call! With all this and a detailed reporting engine, you can control your backups the way you want. And yes, all of this at a great price!
How is StoreGrid different from other backup software?
The difference lies in its flexibility!•
StoreGrid allows the flexibility of multiple deployment modes – use it in Intranet P2P Backup Mode, Client-Server backup mode, or for Remote/Online Backups (or any other configuration we don’t know of).•
Since it can be deployed in multiple ways, StoreGrid can be used by a variety of users.•
It works across various operating systems: Windows® XP, Windows 2000, Windows ME, Windows 2000/2003 Server, Linux RedHat 8.0 & above, Debian 3.0, Mandrake 10.0 & above, SuSE 9.x & above, Mac OS X 10.x and FreeBSD 5.4 & above.•
StoreGrid allows users the flexibility to configure their backups the way they want. Every network is different. You are different. Your data is different. You need different backups for different data/users/networks – StoreGrid recognizes this and except for the source code, allows you to configure almost everything else – the way you want!StoreGrid is different because it offers all this flexibility without compromising on the basics – your data is well encrypted and password protected, compressed, and best of all – StoreGrid quietly works without eating into your CPU, thanks to the incremental backup feature.
StoreGrid Features
1. Automatically detects changes in files and/or directories and backs up accordingly
2. Mobile (laptop) users' data can be backed up immediately as they connect to the LAN
3. Hot links provided for windows registry backup and windows system files backup, among others
4. Versioning support for backing up multiple versions of the same file 5. Incremental backups supported: backs up only changes in files and not the
entire file every time. This saves bandwidth and time
6. Supports multiple periodical full backups and incremental backups in between two full backups
7. Supports MySQL Backup in Linux
8. Quick restore capability: end users can easily restore their data up to the file level
9. Optional compression of backed up data possible: saves disk space and network bandwidth
10. Support for auditing User Operations 11. Support for non-English PCs
2. Data Security
1. Encryption support provided to protect users' personal data 2. Robust encryption based on the blowfish algorithm
3. Authentication support between StoreGrid client and server
3. Deployment Flexibility
1. Trusted intranet P2P backup deployment 2. Typical client-server backup deployment
3. Remote backup with StoreGrid server residing outside the intranet 4. Permutations & combinations of 1,2 and 3
4. Supported Platforms -
StoreGrid is platform independent and supports the following operating systems 1. Windows® Vista, Windows XP, Windows 2000, Windows 2000/2003 SBS/2003Server
2. Debian Linux 3.0
3. Mandrake Linux 10.0 and above 4. RedHat Linux 8.x and above 5. SuSE Linux 9.x and above 6. Mac OS X 10.x
7. FreeBSD 5.4 and above
5. Supported Browsers -
StoreGrid requires one of the following browsers to be installed in the system 1. Internet Explorer 5.5 and above2. Firefox 1.0 and above 3. Netscape 7.0 and above 4. Opera 7.01 and above 5. Mozilla 1.5 and above 6. Safari 1.2.4 and above
StoreGrid Editions
Editions:
Usage:
Ideal for SoHos,
Home Networks
and single
computers
Perfect for
SMBs and
Remote &
Branch Offices
of larger
companies
Especially created
for XSPs, VARs,
SIs offering Online
Backup Services to
SMBs
Features
Download
Download
Partners Only
Operating Systems supported
Windows
Desktop OS
only
Windows
Desktop &
Server OS,
Linux, Mac OS
X, FreeBSD
Windows Desktop
& Server OS,
Linux, Mac OS X,
FreeBSD
Number of installations
Maximum of 3
As purchased (free trial supports 5
installations)
As purchased (free
trial as required)
Create any number of backup schedules Intelli-Delta technology for Incremental backups Hot links for commonly used files & folders Multiple versions of backed up files Deleted file support Robust Encryption with configurable (up to 448 bit) key length
Configurable CPU / bandwidth utilization Backup Data Compression Various scheduling options including continuous backup Multi-threaded backup schedules
Large File Backup support (including 'continue where you left off' feature)
‘Email my reports’ feature
Detailed reporting
(includes
enhanced group
management)
(includes enhanced
customer
management)
Backup only duringcertain hours of the day Support for Volume Shadow Copy Service (VSS) in Windows Secure (HTTPS) WebConsole option MySQL Server backup (Windows) SSL Connectivity NTFS File Permissions Backup Multiple simultaneous restores
Map Drive Support Mailbox/Folder Level Exchange Backup MySQL Server backup (Linux) Client Authentication MS SQL Server Backups MS Exchange Server Backups Remote Backup to server outside the subnet
Backup Server Replication
Local to Remote Server Data Migration (First backup taken locally, thereafter incremental backups done online) Customer/Group centric reporting Automatic Software Update Customer Invoice Generation Module Option to co-brand StoreGrid
Technical Support
Forums only
Forums & email
support
Forums & email
support
Product/featuremessages in User Interface
Terminology
These are some terms we use quite liberally – both in this document, and in our user interface. So here’s a short description of what each of them means.
StoreGrid General Terminology:
StoreGrid Server:
A StoreGrid Server receives (and stores) backup data from StoreGrid Clients.
The backed up data is stored in the machine which runs the StoreGrid Server – a PC can run StoreGrid server if you plan to store data on that PC.
If you wish, the same machine can run StoreGrid Server and StoreGrid Client. This would be the case in a true P2P deployment, or if you have a backup server that will in turn be backed up, as well.
StoreGrid Client:
A machine that has data it wants to back up has to run StoreGrid Client.
The StoreGrid Client backs up its data on to a machine running StoreGrid Server.
If you wish, the same machine can run StoreGrid Server and StoreGrid Client. This would be the case in a true P2P deployment, or if you have a backup server that will in turn be backed up, as well
StoreGrid ID:
This is the unique ID each installation of StoreGrid is identified with. StoreGrid will prompt you to give an ID during the installation. It will automatically take the machine name as the StoreGrid ID by default.
(anyone who purchases a paid license of Vembu StoreGrid is also a StoreGrid client )
Client-Server:
A Client-Server architecture is a concept in which many clients are served by a single or multiple servers. In the context of Vembu StoreGrid, multiple clients (Desktops) can backup to a single Backup Server or multiple Backup Servers.
The Backup Servers are generally dedicated to a particular purpose, in this case, to store the backed up data.
Replication:
Term used for the process where a backup server sends its backup data to a replication server to create a redundant copy of the backup data.
StoreGrid Replication Server:
A machine that receives replication data from a backup server. In case the backup server crashes, it can be restored from the replicated data in the replication server. A backup server can replicate to only one replication server. A replication server can accept replication from more than one backup servers.
StoreGrid Web Console:
This is the browser based StoreGrid user interface from which the backup, restore and administration of StoreGrid servers and clients are done.
Since the user interface is browser based, any StoreGrid Client or Server can be configured and administered from any location.
Peer-to-Peer (P2P):
In P2P, individual entities like Desktops (Peers) exchange information with each other without the help of a central server. In a true P2P architecture, all peers are equal and participate in some form of network activity. In the case of Vembu StoreGrid, which can be deployed in a P2P fashion, the Peers (Desktops) use each others free disk space to backup data between each other. In the case of a true P2P deployment both the StoreGrid Server and the StoreGrid Client will run in the same machine as a single process.
Remote / Online Backups :
Deployment Scenarios
One of the unique features of Vembu StoreGrid is the deployment flexibility it offers. This flexibility makes it suitable for a broad spectrum of users.
Depending upon their existing/planned Backup & Storage infrastructure, users can choose a suitable type of deployment (or do a mix and match type of deployment)
1. Service Provider Hosted Remote Online Backup Deployment 2. Peer-to-Peer(P2P) or Grid deployment
3. Dedicated Backup Server deployment (Client-Server)
Service Provider Hosted Remote Online Backup Deployment
Online Backup service provider including MSPs, VARs, SIs etc. can use this deployment to offer an online backup service to their customers. This deployment mode is supported in the StoreGrid Service Provider Edition. Typically, the service provider will install StoreGrid in server mode in the data center and install StoreGrid from a custom Client Only installation (provided by Vembu) in the customer PCs. The Service Provider Edition supports comprehensive customer based
management of backup clients, storage, reports etc.
Peer-to-Peer or Grid Deployment (P2P Backup)
In a true P2P deployment StoreGrid can be configured to run both the server and the client in all the desktops or laptops that need to be backed up, thus forming a StoreGrid P2P network. Each individual Peer can then be configured to backup to one (or more) other peers. This deployment is the most cost-effective solution as it does not require a dedicated backup storage server (and the associated expenses). This is perfect for Home, SoHo, & Small businesses where it is easy to set up a trusted peer-to-peer StoreGrid Backup network. In general, laptops are not suitable for storing other peers' backup since the laptop may not be on the network when needed! So, it is advisable not to configure a laptop as a StoreGrid Server, but run it only in Client mode. In such cases where all peers do not store backup data, the deployment is still a ‘Peer-to-Peer deployment’- but one where all peers are not ‘equal’.
This is a more traditional deployment - ideal for leveraging existing backup infrastructure by allowing customers to include desktop and laptop data.
All the desktops and laptops run the StoreGrid in Client mode only, and they all back up their data to a central backup storage server. The backup storage server alone runs the StoreGrid in Server mode. It is also possible to have more than one backup server for additional data protection. The backup storage server can also be deployed in a remote location to support remote/online backup and disaster recovery.
NAT/Firewall Configuration
This page provides information about the ports used by StoreGrid, and details on what ports need to be opened to enable StoreGrid to work across different networks behind a NAT/Firewall.
TCP Port 32004
StoreGrid Server opens this port. All Client-Server communication including backups, restore etc. (except TCP discovery) is done through this port. If a StoreGrid Server is behind a NAT/Firewall then this port needs to be opened to enable StoreGrid clients to backup to this server. Opening up this port is mandatory for the core functionality of backup and restore to work in StoreGrid. 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 port is disabled in the backup server and the client by default. SSL port can be enabled by changing the Enabled attribute to 1 in the SSL tag in the SGConfiguration.conf file. When enabled in the backup server, the StoreGrid backup server can accept backup requests on both port 32004 and the SSL port 32007. When enabled in the client, the client will start sending the backup data on the SSL port.
If SSL port is enabled in the backup server and in the client, all Client-Server communication including backups, restore etc. (except TCP discovery) from that client will be done through the SSL port 32007 and therefore if a StoreGrid Server is behind a NAT/Firewall then this port needs to be opened to enable the StoreGrid client to backup to this server.
By default the port used by StoreGrid for SSL is 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 32008(Windows 64-bit OS)
From StoreGrid v2.4 Exchange Mailbox backup and restore is supported for Exchange Server 2007. StoreGrid 64-bit client exe can send the backup request to the 32-bit client exe on port 32008 running in the same machine. If a StoreGrid Client is behind a NAT/Firewall then this port needs to be opened to enable Exchange 2007 Mailbox backup and restore to be
performed. Opening up this port is mandatory for the core Exchange 2007 Mailbox functionality of backup and restore to work in StoreGrid. By default the port used by StoreGrid for Exchange 2007 Mailbox backup is 32008. But it can be modified by changing the "MAPI32Bit" attribute in the "e;Ports"e; tag in the SGConfiguration.conf file located in
<SG_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 the StoreGrid C++ modules. In StoreGrid, all UI requests from the browser are served by PHP pages, which in turn connect to this port to get the required data. By default the port used by StoreGrid is 32005, if you have modified the 'UI Communication Port' during installation, then you have to open the corresponding port in your NAT/Firewall. 2. StoreGrid peers also use this port to do a more complete discovery of each other sharing details about other peers
etc. This TCP discovery is always enabled in StoreGrid.
This port need not be configured in the NAT/Firewall. If so, the only feature that would not work is: Switching to a StoreGrid peer behind the NAT/Firewall through the WebConsole of another StoreGrid peer outside the NAT/Firewall.
These ports are used by the StoreGrid Web Server (Apache) to serve requests from StoreGrid WebConsole (User Interface). These ports are configurable. When you first install StoreGrid you would have been given an option to change these ports. The NAT/Firewall should also 'allow' these ports if you need the ability to connect/administer a StoreGrid peer behind the
NAT/Firewall.
Multicast Ports (UDP) 6363, 6364
These two multicast ports are used by StoreGrid Clients and Servers for discovering peers within a subnet. In most networks, multicasting will work only within a subnet. There is no need to open these ports in firewall or NAT devices as multicast packets may not be sent across networks, anyway. Multicast discovery is enabled by default in StoreGrid.
UDP Port 32006
This UDP port is used in discovery of StoreGrid peers in a network. StoreGrid does a UDP scanning on port 32006 of all possible IP Addresses in a network to detect the presence of other StoreGrid peers. There is no need to open this port in the NAT/firewall as StoreGrid does the UDP scanning only within its subnet. By default, UDP network scanning is disabled in StoreGrid.
Vembu StoreGrid Troubleshooting Guide
1. Description of the Error CodesCommon StoreGrid Error Codes and their corresponding description are listed below. If you require further clarification on these or if you encounter a different error code from those listed below, contact us at [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 Detection software, Antivirus software or
NAT/Firewall Idle socket configuration.
Click here for the
resolution
ii.
Exceeding allotted backup space in the server.
Click here for the
resolution
SG0198
This error occurs when the socket connection between the Client and the
Server gets disconnected due to any external force such as a. Internet
Link error, b. Intrusion Detection software, c. Antivirus software, d.
NAT/Firewall Idle socket configuration.
Click here for the resolution
SG0145/SG0134
Problem in resolving Backup Server Name and IP Address, DNS
Lookup for Backup Server Name or IP Address failed.
Click here for the
resolution
SG0147/SG0136
Problem in connecting to Backup Server, Backup Port (32004) not
opened up in NAT/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
the backup and schedule delete
SG0291
Backup schedule Restore is active during delete schedule configuration,
suspend the 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 data from 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
2. StoreGrid reports an error "Unable to list the Exchange mailbox users. Make sure sufficient
permissions are available for the user account under which StoreGrid service is running. Exchange Mail Level Backup requires the user account to have 'Full Control' access to the Exchange Server to list the mailbox users." while trying to configure mailbox level backup.
Resolution :
If you encounter an error while accessing "Create Exchange Mailbox Backup" page in the StoreGrid webconsole, then follow the steps given below to resolve the issue:
1. Create a new user with sufficient rights through Active Directory Users and Computers. 2. Assign "Full Mailbox Access" permission to that new user.
3. Add that new user in the 'PluginConfiguration.conf' file located in "<SG_Home>/plugins" folder. 4. Add the 'MSPST MS' service by modifying the MAPISVC.INF file.
(NOTE: above 3 steps should resolve the issue in listing the Mailbox users in the "Create Exchange Mailbox Backup" page. However 'MSPST MS' service should be added in the MAPISVC.INF file to successfully backup the Exchange users mailbox).
Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access the mailboxes.
3. StoreGrid doesn’t start after upgrading an old version of StoreGrid to the latest version. Cause :
StoreGrid databases not upgraded properly. Resolution :
Please refer this online detailed help document on upgrading StoreGrid and on how to recover from a bad upgrade http://www.storegrid.net/docs/storegrid/recovering-bad-multi-version-upgrade.pdf
4. StoreGrid reports an error "Unable to list the Exchange mailbox users..." when trying to configure Exchange Mailbox level backup in 2007 Exchange server (64 bit) machines.
StoreGrid uses Microsoft's MAPI client component installed in the Exchange Server to backup the Exchange Mailboxes. For 64-bit environment the MAPI client component is yet to be released by Microsoft. Currently, StoreGrid uses its 32-bit exe to list, backup and restore the Exchange Mailboxes in 64-bit machines. To accomplish this, StoreGrid 32-bit exe requires Microsoft's 32-bit MAPI client component.
Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access the Exchange 2007 mailboxes.
5. SG0147/SG0136: Unable to connect to the Backup Server Cause:
This error occurs when
a. Client is not able to connect to the Backup Server's Backup Port (default 32004).
b. StoreGrid is not started in the server machine, therefore Backup Port (default 32004) is not occupied by StoreGrid.
Resolution:
• Confirm if the client is able to connect the Backup Server's Backup Port (default 32004) by executing telnet <Server Name/IP Address> <Backup Port> command in the StoreGrid Client system through the command prompt.
• If the telnet command doesn't work, then check the firewall configuration of the StoreGrid Server and make sure the Backup Port (default 32004) is open for the incoming traffic.
• Check that the StoreGrid server is running in your StoreGrid Server machine and the Backup Port is in LISTEN state by executing netstat -an | find <Backup Port> [in Windows OS] or netstat -an | grep <Backup Port> [in Linux OS] in StoreGrid Backup Server system.
• If Backup Port is not in LISTEN state, start the StoreGrid in the Backup Server. Also make sure StoreGrid is running in either Server Only or in Client-Server mode in the StoreGrid Server.
• If the Backup Port is in LISTEN state and telnet command fails, make sure the Backup Port is open in the Backup Server network's NAT/Firewall settings.
• Also confirm that both the backup server and the client are configured with the same Backup Port (by default, the port should be 32004). Verify this by checking the <StoreGrid
Home>/conf/SGConfiguration.conf file.
• Refer the following URL to know more about NAT/Firewall configurations. http://www.vembu.com/storegrid/help/nat-firewall-configuration.html
6. SG0198: Connection failure error / SG0083: Unable to send backup details to server Cause:
These errors occur when the connection between a client and the Backup Server is closed prematurely by an external force, while the StoreGrid is actively processing the backup data to the Backup Server. The external forces may be:
. NAT/Firewall configurations. a. Low end routers/switches.
b. Intrusion detection software. c. Internet-link error.
Resolution:
• Most routers, NATs and firewalls keep a track of all connections made through them. They will assume a connection to be dead if no data is transferred in either direction for a certain time interval and they may then close the network connection. Hence, check the “Idle Socket Timeout” configuration in the
NAT/Firewall settings.
• The premature closure of the connection can be prevented by configuring either the Keep Alive Time in the Windows Registry or by configuring the Application Level Keep Alive Time (available since StoreGrid 2.2 Release) For details, refer to the FAQ section at http://www.vembu.com/storegrid/network-backup-faq.html #Network-Backup-Faq34.
7. SG0132: Invalid remote socket Cause:
This error message occurs when StoreGrid client exits or its connection is closed when the backup is in progress. Check the Client side historical backup report from the Backup -> List Backup Schedules -> Backup Summary Report(action) -> Click to view historical backup report (link). The historical backup report page will show one of the following errors:
• 'StoreGrid stopped during backup' – This error indicates that either the StoreGrid process was stopped during backup or the StoreGrid Client machine was shutdown/restarted while the backup was in progress. • 'Unable to send backup details...' - This error indicates that the socket connection was closed
prematurely. Check the timeout settings in the server side NAT/Firewall settings. Sometimes an existing socket connection is closed when the socket remains idle for a specified time period.
Resolution:
Check the StoreGrid FAQ on the same error at http://www.vembu.com/storegrid/network-backup-faq.html #Network-Backup-Faq34
8. SG0145/SG0134: Unable to get target machine Cause:
This error occurs when there is a problem in resolving the Backup Server's name at the client side. This can be verified by running the following commands in the client machine's command prompt:
. ping <Backup Server Name> command. a. nslookup <Backup Server Name> command.
If the above commands work, then the StoreGrid should be able to resolve the Backup Server's hostname. If the above commands fail, then check the DNS configurations on the client side and make sure that the client is able to lookup Backup Server's hostname. Also, try running the telnet <Backup Server Name> <Backup Port> (by default the Backup Port is 32004) command in the client machine. If the telnet command works (shows a blank console screen), then backup should work.
If the client is not able to resolve the Backup Server's hostname, try configuring the backup with the Backup Server's IP address as the server name by following the steps given below:
• Go to the Administration -> Add/Delete peer page in the StoreGrid Client web console. • Delete the Backup Server name from the list of StoreGrid running machines.
• Add the IP address of the Backup Server in the Add Peer. Now the IP address of the Backup Server will be listed in the list of backup servers in the Backup -> Add Backup schedule page.
• Configure a backup using the Backup Server's IP from menu Backup -> Add Backup Schedules page. 9. SGRP0001: No Server available for Replication
Cause:
This error will occur if the Backup Server is unable to connect to the Replication Server during the replication process due to one of the following reasons:
. Replication Server is not running in the system.
a. Backup Server is not able to resolve the Replication Server's hostname due to DNS lookup issue. b. Replication Port (default: 32004) is not open in the Replication Server side NAT/Firewall/Router settings.
Resolution:
Use the following commands to check the connectivity from Backup Server to Replication Server: iii. ping <Replication Server Name>
iv. nslookup <Replication Server Name>
v. telnet <Replication Server Name> <Replication port>
If the above commands work, then replication should also work. If the ping and nslookup commands fail, then it is a DNS lookup issue for the Replication Server hostname from the Backup Server. If the telnet command fails, then check if the Replication Port is open in the firewall at the Replication Server and make sure StoreGrid Replication Server is running in that port.
10. SG0083: Exceeding allotted backup space in the server Cause:
This error occurs if the client is trying to use more backup space than the allotted space. Resolution:
• Check the allotted space for the particular client in the Backup Server.
• To increase the space for the client in Backup Server, go to Server Admin -> Group Management -> [Group_Name] ->Edit Configuration (Action for the particular Client) page and enter the required space in Space Allotted field. Refer to the URL http://www.vembu.com/storegrid/sp-help/PageHelp/client-backup-configuration.html for more details.
11. 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 which though the backup was suspended in the client, the server thinks that the backup is still in progress. In the next incremental backup schedule from the client, StoreGrid will reset the status of the backup schedule in the Backup Server. If the reset of active status completes successfully, then the StoreGrid client will continue the backup. However, if for some reason the reset of active status fails, then backup will fail with the 'Backup in progress' error message in the client's backup report.
Resolution:
• This error should be cleared during the next backup schedule. If it doesn't, then try restarting the Backup Server once to see if this error goes off in the subsequent schedule.
• This issue is fixed in v2.3 by updating the status based on the Keep Alive messages (for each backup schedule) received from the clients.
12. Problem in accessing the snapshot device while opening file Cause:
This error appears when the StoreGrid is unable to open the configured files for backup from the snapshot device, when the 'Volume Shadow Copy' option is enabled for the backup schedule. This happens if the file to be backed up doesn't exist when the snapshot is performed, but exists while StoreGrid is listing the files for backup. Resolution:
StoreGrid will backup these skipped file(s) in the subsequent backup schedules
• Check the skipped files count in the next schedule.
• If the problem persists, try disabling the 'Volume Shadow Copy' option for that backup schedule through the Backup -> List Backup Schedules -> Edit(Action for the particular backup) -> Advanced Options page.
13. “Error Code 21 Cannot Start Storegrid” message from the tray / “Error in Starting StoreGrid" message from StoreGrid Tray
Cause:
These errors occur when the StoreGrid tray is unable to start the StoreGrid Application or the Service. The reason could be one of the following:
• The StoreGrid Tray application doesn't have permissions to start the StoreGrid Service.
• The StoreGrid Application file is not available at the StoreGrid Tray Applications path, i.e <StoreGrid Home>\bin location.
• Another instance of StoreGrid is already running in the machine. Resolution:
• Check if the StoreGrid Tray Application is running in an user account who has privileges to start the StoreGrid Service.
• Check if the StoreGrid service's logon user has enough privileges to start Windows services.
"StoreGrid.exe" process in the 'Task Manager' tool. If there is already another instance running, try stopping that process and then starting it again.
14. Your StoreGrid license has expired. Number of StoreGrid Installations exceeded 1. Backups disabled. Cause 1:
System name/IP addresses are duplicated in the Administration -> Add/Delete Peer page Resolution:
. Stop StoreGrid application.
i. Rename the "<DB Storage Location>/data/sgdisc.db" to "sgdisc.db.org" file. ii. Start the StoreGrid application.
Cause 2:
More than one StoreGrid instance is trying to use the same license key. The applied StoreGrid license is shared by other StoreGrid instances running in the same network. If there is a StoreGrid instance running in trial-user mode or with expired license period, then the license key from a Server running on a valid license will be propagated to that StoreGrid instance.
Resolution:
Apply valid server licenses on the servers through Administration -> Apple License Key to Server page. Applying a valid license on the server will fix this issue.
Cause 3:
This error could occur if the Backup Server has multiple network cards and the localhost entry is duplicated in the Administration -> Add/Delete Peer page.
Resolution:
If this is the case, bind the StoreGrid application to a particular IP address/subnet only by following the steps below.
iii. Stop the StoreGrid.
iv. Open <StoreGrid Home>\conf\SGConfiguration.conf file in a text editor.
v. Provide the private IP address value in the IPAddress attribute of the <StoreGrid> tag and save the file. vi. Restart the StoreGrid application.
The StoreGrid application will be bound to the specified IP Address now. If peer system name/IP addresses are duplicated in the Administration -> Add/Delete Peer page, then the peer should be deleted from the Add/Delete Peer page. The following steps will rediscover the StoreGrid peers again and update itself correctly after restart. vii. Stop StoreGrid application.
viii. Rename the "<DB Storage Location>/data/sgdisc.db" to "sgdisc.db.org" file. ix. Start the StoreGrid application.
15. Your StoreGrid license has expired. License period elapsed, Backups disabled Cause:
Resolution:
If the StoreGrid is running as a Client-Server, then a valid server license is needed in that machine. Therefore, it is recommended that all the clients are installed in Client Only mode.
• If the client is a Windows OS machine, then right click the StoreGrid Tray icon, go to Change StoreGrid Mode menu and select the Client option mode.
If the client is running in a non-Windows machine, then the StoreGrid mode can be changed manually by following the steps given below:
• Stop StoreGrid.
• Edit the <STOREGRID_HOME>/conf/SGConfiguration.conf file and change the value of StartModule in Module tag. The possible values of StartModule attribute and the corresponding modes of StoreGrid installation are listed below.
601 - Server only 602 - Client only 603 - Client-Server 609 - Replication Server
Change the StartModule attribute value to 602 for Client and save the file.
• Start StoreGrid.
16. Failed to authenticate this client with the Backup Server Cause 1:
If Deny Auto Authorization is enabled in the Backup Server. Resolution:
Enable Allow Auto Authorization option for the particular group and check. Cause 2:
If there is a password mismatch between the Backup Server and the Client. Resolution:
If this is the case,
• Reset the client's password in the StoreGrid Backup Server. Go to Server Admin > Group Management -> [Group Name] --> Reset Password (Action for the particular client) page in the backup server's web console.
• Reset the server password for the client through Administration -> Advanced option -> Reset Password (Action for the Backup Server) page in StoreGrid client's web console.
• Authorize a new password (for both client and server) by editing the password in the Backup Server in Server Admin -> Group Management -> [Group Name] -> Edit Client Configuration page in the server
web console and then authorizing the client with the same password from the Administration -> Advanced Options -> Authorize Client page in the client web console.
• Resume the backup schedule and check if it works.
17. Backup request failed for backup [Backup Name] To Server [Server Name] with Error : Unable to take backup to Replication Server
Cause:
This error will occur if the Backup is configured directly from the StoreGrid client to the StoreGrid Replication Server.
• The StoreGrid Replication Server will not accept the backup request from StoreGrid Clients.
• StoreGrid Replication Server is designed only for receiving replication requests and replication data from the Backup Server and to handle restore requests from the client.
• Similarly, the StoreGrid Backup Server is designed for receiving Backup/Restore Requests from the client. • Hence, Replication Server will not process the backup request from the StoreGrid client.
Resolution:
• Configure backup from StoreGrid client to StoreGrid Backup Server.
• Enable replication in the StoreGrid Backup Server for the corresponding group.
• The client will backup to their server and the backup data on the server will be replicated to Replication Server.
18. On backup completion, a message "there were no modified files" is shown though several files were actually modified
Cause:
This error might occur if files to be backed up are from a mapped drive and Automatic Directory Monitoring is enabled for the backup.
• StoreGrid client running on Windows OS can use the Windows Directory Monitoring to get a notification when a file configured for backup is added/deleted/modified.
• These notifications are saved in the database to create the list of files that need to be backed up during the next backup schedule.
• However, notifications are not sent by the Directory Monitoring when the files modified/deleted/updated are in a mapped drive.
• Therefore, StoreGrid will not be able to identify the changed files when Automatic Directory Monitoring is enabled for backup of files from a mapped drive.
• Disabling Automatic Directory Monitoring should resolve this issue.
• Uncheck Automatic Directory Monitoring in the Backup -> List Backup Schedules -> Edit Backup Configuration (Action for particular backup) -> Advanced Options page.
• If the backup is already in progress, then suspending and resuming it manually will make the StoreGrid list all files/folders for backup again and therefore the files will get picked up.
19. SG: Unable to allot backup space Cause:
This error will occur if the sum of the allotted space for all the clients is larger than the total allotted space for the Backup Server.
Resolution:
• Before increasing the space for a client, confirm if the server has enough allotted space. • Then increase the allotted space for the client.
• If the server does not have the necessary space, increase the allotted space for the Backup Server by going to Server Admin -> Server Settings page and then increase the allotted space for the client. • After increasing the allotted space for the client in the Backup Server, schedule the backup from the client
and check if the backup is successful.
20. StoreGrid not able to backup over the internet Cause:
StoreGrid is not able to connect to the server on the Backup Port (default 32004). Resolution:
• Check the Backup Server side NAT/firewall settings. Make sure the incoming traffic on the Backup Port (default 32004) to the Backup Server is not blocked.
• Run a quick check for the connectivity from the client with the command telnet <server name/server IP Address> <Backup port>.
• If this command works, then the client should be able to backup to the server over the internet. If it fails, then make sure that Backup Port (32004) is open in the Firewall/NAT configuration in the network where the server is installed.
21. StoreGrid doesn't seem to work in XP SP2/SP3 Cause:
In Windows XP SP2/SP3, the firewall is enabled by default. StoreGrid can neither discover other StoreGrid peers nor it can backup data to other machines.
Resolution:
To disable the firewall, follow the steps below:
o
Open START->CONTROL PANEL->WINDOWS FIREWALLo
Select Exceptions tabo
Under 'Programs and Services', click on Add Programs buttono
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).
o
Select OK to save the configuration and exit. StoreGrid can now use any TCP/UDP ports as the firewall settings have been disabled for the StoreGrid and Apache applications.Enable to the following ports:
TCP Ports: 32004, 32005, 32007, 32008, 6060, 6061 UDP Ports: 32006, 6363, 6364
o
Open START->CONTROL PANEL->WINDOWS FIREWALLo
Select Exceptions tabo
Under Programs and Services, click Add Port buttono
Add 4 TCP Ports with unique names, allowing TCP Port numbers 32004,32005, 32007, 32008, 6060 and 6061.o
Add 3 UDP Ports with unique names, allowing UDP Port numbers 32006,6363 and 6364.o
Select OK to save the configuration and exit.22. StoreGrid Server is not listed in the "Backup Servers" list Cause:
StoreGrid automatically discovers other StoreGrid peers in a network using various means (multicast, UDP port scan, TCP port scan etc). If for some reason a StoreGrid server or client is not discovered automatically, it will not be listed in the 'Backup Servers' list.
Resolution:
Manually add the StoreGrid peer to the list from the menu item Administration->Add Peer. In the "Add Peer" page, enter the StoreGrid peer’s name or IP address. This is especially relevant if some peers are outside the network (as in the case of remote online backups).
23. StoreGrid has exited, do you want to restart it Cause:
This error appears when StoreGrid application is shutdown and Windows does not clean up the TCP network connections.
Resolution:
Run the command netstat -a from a command window (Start > All Programs > Accessories > Command Prompt) and check if the TCP ports 32004 or 32005 are in listening mode. If the ports are in listening mode, then the system has to be restarted.
24. "Apache.exe could not be replaced" message during installation Cause:
This happens when the StoreGrid web server service (which uses Apache) did not exit properly when the previous installation of StoreGrid service was deleted.
Resolution:
Open the windows task manager and kill any instances of php and apache that is running. If this does not help, open the Control Panel->Administrator Tool->Services and stop the StoreGrid Web server service and then proceed with the install.
25. Linux installation fails while installing GD/PHP (applicable only to versions older than 2.3) Cause:
StoreGrid uses Apache, GD and PHP for its browser based user interface. StoreGrid is bundled with Apache, GD and PHP source files and these files get compiled during installation. StoreGrid installs Apache, GD and PHP in "/Vembu/StoreGrid" directory. And it is packaged with the modules that are required for StoreGrid user interface. If the required packages or third party libraries are not present, then the compilation will fail.
Resolution:
Before installing StoreGrid in linux machines, please check that the following packages are installed.
• make, available from http://ftp.gnu.org/pub/gnu/make/ • gcc, available from http://gcc.gnu.org/
• g++, available from http://gcc.gnu.org/
• 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 install even without these, it is recommended that at least zlib, libpng, freetype and jpeg are installed as well:
• Data compression library: zlib, available from http://www.gzip.org/zlib/
• Portable Network Graphics library; requires libpng, available from http://http://www.libpng.org/pub/png/ • Free, high-quality, and portable font engine: FreeType 2.x, available from http://www.freetype.org/ • Portable JPEG compression/decompression library: JPEG library, available from http://www.ijg.org/
To install PHP following 3rd-party libraries are required :
• Flex, available from http://lex.sourceforge.net/
Flex is a tool for generating programs that perform pattern-matching on text. • 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.
• libxml2, available from http://www.xmlsoft.org/
26. Unable to log you in. Make sure StoreGrid is running / No connection could be made because the target machine actively refused it
StoreGrid application is not running in the system. Resolution:
In Windows OS.
• Confirm that the StoreGrid application [StoreGrid.exe] is running in the system by using "Task Manager". • If the application is not running, start StoreGrid through the StoreGrid system tray application.
In Linux OS
• Verify if the StoreGrid application is running in the system by executing the command 'ps -e |grep StoreGrid'.
• If the application is not running, start it with the command "sh startStoreGrid.sh" in <STOREGRID_HOME> directory.
• If you see the following error message: "error while loading shared libraries: libstdc++.so.5..." while trying to start StoreGrid, check whether the libstdc++.so.5 and other compatible libraries are installed in that system. You can check this by listing the libraries by "ls -l /usr/lib/libstdc++.so.5*" command. • If it is a 64 bit system, make sure 32 bit compatible libraries are present in your 64 bit Linux OS as
StoreGrid runs as a 32 bit application in a 64 bit Linux machine. If the libraries are missing, please install 32 bit compatible libraries in your system and then try to start StoreGrid.
For example, if your Linux flavor is Debian or Ubuntu or Gentoo, then install the 32 bit libraries with the following command:
$ apt-get install ia32-libs
For RedHat machine, you can search the dependency packages and install it by the following commands:-
$yum search <Package Name> - To check the package is in the machine or not. $yum install <Package Name> - To install the package.
Note: The above command should be executed with the root user privileges. Cause 2:
The StoreGrid web console is unable to connect the StoreGrid applications UI communication port [by default, 32005].
Resolution:
Confirm if the StoreGrid is in the listening mode at the UI communication port.
• Verify this by running the command 'netstat -an | find "32005"' in the command prompt to check if the port 32005 is in LISTEN state.
• Run the "telnet <machine name> 32005" command in command prompt to confirm if the web console can access the StoreGrid application UI communication port.
• If any personnel firewall/intrusion detection tools are installed in the system, try adding the StoreGrid.exe, SGTray.exe applications and 32005 default port in the NAT/Firewall configuration's exception list and then try logging into the StoreGrid’s web console.
27. Cannot export .\registry\regbackup.reg:Error opening the file. There may be a disk or file system error." error in Vista.
Cause:
This error message shows up in Windows Vista when the user does not have full administrator privileges. In Vista, an application can be run as a service only by the Administrator account. A user account cannot run it as a service even if it has all the administrative privileges.
Resolution:
. Select StoreGrid build exe.
i. Right click the exe and "run as an administrator".
28. StoreGrid doesn't seem to run properly after upgrading Windows to Vista. Cause 1:
If StoreGrid was installed in an older version of Windows and then if the OS was upgraded to Vista, StoreGrid may fail to run.
Resolution 1:
Install (upgrade) the same version of StoreGrid again on top of the existing install. Cause 2:
StoreGrid is installed under C:/Program Files in Vista. Resolution 2:
Make sure you run StoreGrid with the option "Run as Administrator". The reason been, Vista allows an application to access the 'Program Files' folder only when run as an administrator user. You can enable the 'Run as
Administrator' option for the <StoreGrid Home>\bin\StoreGrid.exe application from it's file properties dialog through 'Compatibility' tab -> 'Privilege Level' -> 'Run this application as administrator' option.
If you don't have administrator access or if you don't want to run StoreGrid under the administrator account, make sure you install StoreGrid under your user account folder or install it in a folder which is not under 'Program Files'.
29. Error while dumping the Exchange Mail Boxes. Unable to create the PST file [or] "No new/modified files for backup"
Cause :
'MSPST MS' is not configured in the Exchange Server. Solution :
Add the 'MSPST MS' service by modifying the MAPISVC.INF file.
The MAPISVC.INF file should have the information of the Microsoft Personal Folder store service. If this file does not have this information, then the Exchange Mailbox dump will fail with an error indicating that it was "Unable to
create the PST file" [or] "No new/modified files for backup".
The MAPISVC.INF file is usually located in the Windows system directory (e.g.C:\Winnt\System32\ or C:\Windows\System32\).
Verify the file has an entry for the Microsoft Personal Folder store service. You can determine this by looking for the following information. If this information is not in the file then you need to add it in the proper sections:
[Services]
MSPST MS=Personal Folders File (.pst) [MSPST MS] Providers=MSPST MSP PR_SERVICE_DLL_NAME=mspst.dll PR_SERVICE_INSTALL_ID={6485D262-C2AC-11D1-AD3E-10A0C911C9C0} PR_SERVICE_SUPPORT_FILES=mspst.dll PR_SERVICE_ENTRY_NAME=PSTServiceEntry PR_RESOURCE_FLAGS=SERVICE_NO_PRIMARY_IDENTITY [MSPST MSP] 34140102=4e495441f9bfb80100aa0037d96e0000 PR_PROVIDER_DLL_NAME=mspst.dll PR_SERVICE_INSTALL_ID={6485D262-C2AC-11D1-AD3E-10A0C911C9C0} PR_RESOURCE_TYPE=MAPI_STORE_PROVIDER PR_RESOURCE_FLAGS=STATUS_DEFAULT_STORE PR_DISPLAY_NAME=Personal Folders
PR_PROVIDER_DISPLAY=Personal Folders File (.pst)
For more information about the format of the MAPISVC.INF file see the following Microsoft article: http://support.microsoft.com/kb/294470
30. Dump location does not have enough space to export the PST file Cause :
The dump location configured for this backup schedule doesn't have enough free space to store the *.PST files. Resolution :
Increase the free space or cleanup the used space for the drive which is configured as dump location for this backup schedule. Location configured for dump process can be viewed from the view backup configuration of that backup schedule.
31. Error while creating the dump location <Dump_Location> Cause :
The configured dump location for that particular backup schedule is not accessible or StoreGrid does not have enough permission to access the directory.
Make sure that the dump location drive exist in your StoreGrid client. If that drive exist, provide enough write permission to the user under which StoreGrid is installed.
32. Users Mailbox/folder are not listed in the "Create Exchange Mailbox Backup" page. Cause :
StoreGrid would fail to list the Exchange Users Mailbox folders for the following reasons.
• Mailbox which was accessed does not exist in the Exchange Server or invalid logon information being used to list the users Mailbox.
• Insufficient rights on the Exchange user mailbox. Resolution :
Exchange Mail Level Backup requires "Full Control" access on the Exchange Server for the user account under which StoreGrid service is running. Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access the mailboxes.
33. StoreGrid fails to list some files/folders during a backup schedule. StoreGrid fails to list the files/folders due to the following reasons: Cause 1:
In Windows, StoreGrid logon user is not in the Backup Operators group. Resolution 1:
Check if the StoreGrid logon user is added in the Backup Operators group. If the StoreGrid logon user is a member of Backup Operators group, StoreGrid should able to list and read the files & folders for backup irrespective of the security settings configured for the files/folders.
Cause 2:
If the file/folder doesn't have enough permission for the StoreGrid user. Resolution 2:
• Check if StoreGrid logon user has ‘Read’ and 'List Folder Contents' access permissions for the skipped folder by going to 'Folder Properties -> Security' dialog.
• If StoreGrid logon user doesn't have permission, enable the required permissions. • Reschedule the backup and check.
Cause 3:
File/folder name contains Unicode characters. Resolution 3:
34. I had changed the dump location and now I am not able to restore the previous
backups.[Applicable for Advanced Exchange Server, Exchange Mailbox and
Advanced SQL Server backups.]
Resolution :
Please follow the steps below to restore the files from backup server to client and then to the Exchange Server/SQL Server.
• Restore the files in the backup server side which were backed up before changing the dump location (i.e. backup files pertaining to the old dump location).
• Transfer the restored files from the backup server to the client machine, say by using an external USB drive.
• Edit the 'restore.conf' available in "<Restored_location>/plugin/" folder in client machine.
• Change the 'DumpLocation' attribute value to old dump location in <StoreGrid><Restore><Plugin> tag. • Save the 'restore.conf' configuration file.
• In the client machine, choose the second option - "I have previously restored data from my backup server to a local folder. I now want to use this data to restore the Exchange Mailbox." in 'Step 0' in the Restore Backup Data page and restore the files restored in step 2 by specifying the location of the files in 'Restore Location' field.
Migrating from version 2.3.5 to 2.4
You can install StoreGrid v2.4 on top of the existing version 2.3.5 and StoreGrid will automatically migrate to v2.4 release. Before migrating to v2.4, please make a note of the following instructions:
• To upgrade to v2.4 SP edition, you should be currently running the v2.3.5 SP edition.
• To upgrade to v2.4, just install v2.4 on top of the v2.3.5 installation. DO NOT UNINSTALL v2.3.5.
• If you are currently running a previous version, make sure you first upgrade to v2.3.5 and start StoreGrid to complete the migration process before installing v2.4.
Also ensure that your backup server is running the same (or higher) version than the clients backing up to it. For example: before upgrading clients to v2.4, you must ensure that your backup server has been upgraded to v2.4; we typically ensure backward compatibility for clients, for example, a v2.3.5 client can still backup to a v2.4 server (this way, you can upgrade your clients in a phased manner). In short, ALWAYS UPGRADE THE BACKUP (& REPLICATION) SERVERS FIRST. Versions previous to v2.3.5 cannot be migrated directly to v2.4. You will have to first migrate them to v2.3.5 and install v2.4 on top of it. For versions previous to v2.2.1, first migrate them to v2.2.1 and to v2.3 and then to v2.3.5. You can download the v2.2.1 from http://www.vembu.com/storegrid/storegrid-pro-221-downloads.php, version v2.3 from http://www.vembu.com/storegrid/storegrid-23-downloads.php?edt=pro and version v2.3.5 from
http://www.vembu.com/storegrid/storegrid-235-downloads.php?edt=pro
Migrating from version lower than 2.3.5
If you are currently running a version previous to 2.3.5, then you need to first upgrade to v2.3.5 before installing v2.4.
It is very important that after every version upgrade, you need to start the StoreGrid application and login into the web console and confirm the upgrade has happened successfully before upgrading it to the next version. !!!!
As an example, if you are currently running StoreGrid v2.2, then you need to follow the steps given below to upgrade to v2.4
• Install StoreGrid v2.2.1 build on top of the existing v2.2 installation.
• Choose 'Start StoreGrid' option after completing the installation and wait for some time to let the StoreGrid application to complete the migration. If you log into the web console while the migration is in progress, you will be redirected to page that indicates the migration is in progress.
• Once the migration process is completed, login to the web console and verify all the configurations and backups are intact - VERY IMPORTANT
• Install StoreGrid v2.2.5 build on top of the existing v2.2.1 installation.
• Choose 'Start StoreGrid' option after completing the installation and wait for some time to let the StoreGrid application to complete the migration.
• Once the migration process completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT
• Install StoreGrid v2.3 build on top of the existing v2.2.5 installation.
application to complete the migration.
• Once the migration process completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT
• Install StoreGrid v2.3.5 build on top of the existing v2.3 installation.
• Choose start StoreGrid option after completing the installation and wait for some time to let the StoreGrid application to complete the migration.
• Once the migration process is completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT
• Install StoreGrid v2.4 build on top of the existing v2.3.5 installation.
• Choose start StoreGrid option after completing the installation and wait for some time to let the StoreGrid application to complete the migration.
• Once the migration process is completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT
Migrating from version 2.3 to 2.3.5
You can install StoreGrid v2.3.5 on top of the existing version 2.3 and StoreGrid will automatically migrate to 2.3.5 release. Versions older than v2.3 cannot be migrated directly to v2.3.5. You will have to first migrate them to v2.3 and install v2.3.5 on top of it. For versions older than v2.2.1, first migrate them to v2.2.1 and then to v2.3. You can download the v2.2.1 from http://www.vembu.com/storegrid/storegrid-pro-221-downloads.php and version v2.3 from
http://www.vembu.com/storegrid/storegrid-23-downloads.php?edt=pro
If you login into the web console when the migration process is in progress, you will be directed to a page which indicates that migration is in process. The migration might take up to 20 minutes depending upon the amount of data to be migrated. Wait for some time and then try re-logging in. Please don't shutdown and restart StoreGrid as this will only further delay the migration.
Migrating from version 2.2.1 to 2.3
You can upgrade StoreGrid v2.2.1 to v2.3 by just installing v2.3 on top of the current installation. Versions older than v2.2.1 cannot be migrated directly to v2.3. You will have to first migrate them to v2.2.1 and then migrate v2.2.1 to v2.3. You can download the v2.2.1 from http://www.vembu.com/storegrid/storegrid-pro-221-downloads.php
Migration might take some time depending upon the amount of data to be migrated. Please don't restart StoreGrid as this will only further delay the migration. If you log into the StoreGrid web console during migration, you will be directed to a page indicating that the migration process is in progress. Wait for sometime and then try logging back in. In the backup server. migration could take about 5 minutes for every 100,000 files backed up. Migration in the client should not take much time.
Migrating from version 2.0/2.0.1/2.1/2.1.1 to 2.2.1
Migrating to StoreGrid 2.2.1 is completely automatic.All you have to do is to install StoreGrid 2.2.1 on top of your existing (2.0/2.0.1/2.1/2.1.1) StoreGrid installation.
Clients running version 2.0/2.0.1/2.1/2.1.1 will continue to backup to your backup server running v2.2.1 ! Section 1 below covers Server Side Migration, and Section 2 covers Client Side migration.
1. StoreGrid Server-side Migration
While updating a StoreGrid server installation to version 2.2.1, most of the migration procedures are internal and
automatic. The migration on the StoreGrid Backup Server and the StoreGrid Replication Server may take some time based on the number of files backed up on the StoreGrid Server. For example, migrating 100,000 files will take about 10 minutes and 200,000 files will take about 20 minutes.
While updating a StoreGrid server installation to version 2.2.1, most of the migration procedures are internal and automatic. But the following changes to StoreGrid 2.2.1 needs to be understood by the service provider before deploying and using StoreGrid 2.2.1.
1.1. StoreGrid 2.2.1 Groups
From StoreGrid 2.2.1, all clients are organized under Groups. In StoreGrid 2.1.1 Professional Edition, the clients were listed directly in the 'Server Admin -> Client Management'. Now in StoreGrid 2.2.1, the clients will be by default organized under the 'Default Group'. Users can create multiple Groups (up to one level) and organize their clients based on their Groups, such as Departments, Office Branches, etc.,
NOTE: The Email Filtering configurations are not migrated from 2.1.1 to 2.2.1. Hence, please reconfigure the Email filtering options after upgrading to StoreGrid 2.2.1 Release.
Migrating from version 2.0/2.0.1/2.1 to 2.1.1
There is no special migration procedure if you are updating from 2.0/2.0.1/2.1 to 2.1.1. You can just install StoreGrid 2.1.1 on top of the existing 2.0/2.0.1/2.1 version and StoreGrid will automatically migrate to the 2.1.1 release. StoreGrid will not be functional while the migration is in progress. But the migration itself will take only a few seconds. While you update from Version 2.0.1/2.1 to 2.1.1 please note that:
1. StoreGrid will not be able to schedule any backups while the migration is in progress.
2. The StoreGrid Web Console, when accessed, will come up with a message that "Migration is in progress". StoreGrid Web Console features cannot be used while the migration is in progress.
Migrating from version 1.6 to 2.0
Vembu StoreGrid 2.0 is a major upgrade release over the StoreGrid 1.6 release. StoreGrid's architecture and infrastructure have been revamped and improved significantly keeping in mind scalability, performance and flexibility in terms of
evolution of future versions of StoreGrid. Towards that end, StoreGrid 2.0 completely leverages an embedded RDBMS both in the client and the server side. Except for the backup files, which uses the native file system itself, every other
information StoreGrid generates or uses like configurations, file meta-data, file signatures, events, version information, backup reports, restore reports etc. are all driven from the RDBMS. Leveraging an RDBMS gives StoreGrid the capability to evolve rapidly in terms of new features and user-interface improvements etc. without compromising on scalability and performance. With this major re-design of StoreGrid with the 2.0 version, we expect to deliver customer focused features at a more rapid pace than before.
Whether StoreGrid installation is a Client, Server, Or Client-Server Installation, the first time it runs, StoreGrid 2.0 automatically migrates all the file meta-data and configurations maintained in flat files or the 1.6 database to the newly created 2.0 database. The StoreGrid Client side migration is quite fast. Even for 1000s of files, the client side migration will take only a few minutes. On the StoreGrid server side, where the backup data is present, depending upon the number of
files you have backed up earlier, the migration may take some time. The time taken for the migration on the server side depends upon the total number of files that were earlier backed up with StoreGrid 1.6. Migrating 10,000 files will take about 4 minutes and 100,000 files will take about 40 minutes.
StoreGrid will not be functional while the migration is in progress. While you upgrade from Version 1.6 to 2.0, please note the following points:
1. StoreGrid 2.0 will automatically migrate your 1.6 data to 2.0 formats when it runs first time after the upgrade. 2. StoreGrid 2.0 is not interoperable with StoreGrid 1.6. Hence make sure you upgrade and migrate both your client
and server installations before you resume your backups. The recommended procedure is to update and migrate your StoreGrid servers first. StoreGrid 2.0 will put all the backup schedules in the client in suspended mode after the migration process.You need to resume them manually after making sure the backup servers also have been upgraded and migrated to 2.0.
3. StoreGrid will not be able to schedule any backups while the migration is in progress.
4. The StoreGrid Web Console, when accessed, will come up with a message that "Migration is in progress". StoreGrid Web Console features cannot be used while the migration is in progress.
5. StoreGrid Migration process may use high CPU cycles and may slow down other processes on the machine/PC. Hence it is advisable to upgrade to StoreGrid 2.0 when you are not using the machine/PC for CPU intensive tasks.
Advanced Users
The following points should help you understand the internal migration process when you run StoreGrid 2.0 for the first time after upgrading from 1.6.
1. StoreGrid 1.6 to 2.0 Client Side Migration
The operations performed in client side migration are as follows:
a. User Account Migration: Read the user lists from userfiles.lst and write to Client DB.
b. Backup Configuration Migration: List the *.sbf, *.imm & *.scc files from <STOREGRID_HOME>/conf & add backup configuration to DB. After migration, the backups will be in suspended status. User has to resume the backup schedule manually only after making sure the backup servers the client was backing up to are also upgraded to the StoreGrid 2.0 version and the migration has taken place in those servers. c. Discovered Peer List Migration: Read the discovery.log (if not present, discovery.tmp) file from
<STOREGRID_HOME> and add them to Discovery DB.
d. Discovery Configuration Migration: Read the discovery.conf file from <STOREGRID_HOME>/conf and write to Discovery DB.
e. Delete Configuration & Reports Migration: List the *.sdf files from <STOREGRID_HOME>/conf & write them to Client DB.
f. File Meta Data Migration: Attach the 1.6 DB to 2.0 DB and copy the file meta-data information and signature data.
g. Backup Reports Migration: Attach the 1.6 DB to 2.0 DB and copy the backup reports information. h. Restore Reports Migration: List the *.rpt files from <STOREGRID_HOME>/report/restore and add them
2. StoreGrid 1.6 to 2.0 Server Side Migration
The operations performed in server side migration are as follows:
a. For each backup client backing up to the server, find the backup location from
<SG_HOME>/conf/diskspaceconfiguration/and migrate the backed up files to a new 2.0 directory structure which is based on directory Ids. Note that StoreGrid 2.0 will move the backed up files from the original location to the new location.
b. By default all the client's backup will be done under a directory called "1" under the backup location. c. Move Disk Space Configuration information of all clients to Server DB.
Migrating from version 1.2.1 to 2.0
If you are still using the 1.2.1 release and want to migrate from 1.2.1 to 2.0, then the migration is a two step process. Firstly you need to migrate from 1.2.1 to 1.6 by installing StoreGrid 1.6. You can check whether the migration has
completed by logging into the UI. The steps for migrating from 1.2.1 to 1.6 is given below.
After migrating to 1.6, then you can migrate StoreGrid to 2.0 by installing 2.0 on top of the 1.6 version. The steps for migrating from 1.6 to 2.0 is given above.
Migrating from version 1.2.1 to 1.6
NOTE: StoreGrid 1.6 is a minor bug fix release over 1.5.1. So there is no special
migration procedure if you are updating from 1.5.1 to 1.6
Vembu StoreGrid 1.6 has some significant improvements in terms of how a StoreGrid client internally maintains metadata information.
In earlier versions , metadata information like the signature (used for incremental backups) and file statistics (modified time, created time etc.) were stored in flat files. This was relatively inefficient as the metadata occupied more space than necessary. StoreGrid 1.6 uses an embedded relational database (RDBMS) to store the metadata efficiently. Moving to an RDBMS also enhances StoreGrid's ability to provide more detailed reports.
The first time it runs, StoreGrid 1.6 automatically migrates the metadata maintained in flat files to the embedded RDBMS. Depending upon the number of files you had backed up earlier, the migration may take some time. The time taken for the migration depends upon the total number of files that were earlier backed up with StoreGrid 1.2.1. Migrating 10,000 files will take about 2 minutes and 100,000 files will take about 30 minutes.
StoreGrid will not be functional while the migration is in progress. While you update from Version 1.2.1 to 1.6 , please note that:
1. StoreGrid will not be able to schedule any backups while the migration is in progress.
2. The StoreGrid Web Console, when accessed, will come up with a message that "Migration is in progress". StoreGrid Web Console features cannot be used while the migration is in progress.