Storegrid™ Frequently Asked Questions

Info

StoreGrid ID selected should be unique

Description

The StoreGrid ID specified during StoreGrid installation should be unique to the machine. Two clients with the same StoreGrid ID cannot backup to the same backup server. Similarly two backup servers with the same StoreGrid ID cannot replicate to the same replication server.

Your StoreGrid ID selected should be unique

Explanation

StoreGrid backup server stores all the details of a client machine based on the client’s StoreGrid ID. Therefore, once a client has started backing up its files to a backup server, it is not recommended to change the client’s StoreGrid ID. If the ID is changed, StoreGrid client will run the backups afresh and cannot resume from whatever has been backed up so far with the old StoreGrid ID. If the StoreGrid ID HAS to be changed and if it is acceptable that the client runs it backups afresh again, then please follow the steps mentioned below to change the StoreGrid ID of the client

  1. Stop StoreGrid application in the client machine
  2. Open the “conf/SGConfiguration.conf” file in a text editor.
  3. Modify the ‘ID’ attribute in the ‘StoreGrid’ tag to the desired StoreGrid ID value.
  4. Save the SGConfiguration.conf file.
  5. Start StoreGrid.

Like mentioned above, the client will run all its backups afresh. The StoreGrid ID selected should be unique .Also make sure the client entry in the backup server with the old StoreGrid ID is deleted from the server. If it is not deleted, then the backup server, if it is running the Service Provider Edition, will continue to use up the MSPEUs for the old client ID as well as for the new StoreGrid ID – as the backup server considers the client backing up with the new StoreGrid ID as a new client.

Connectivity between client and backup server

Description

Connectivity between client and backup server. StoreGrid client connects to the backup server using the public lookup name or static IP address of the backup server as configured in the client for the backup schedule. StoreGrid Backup Server listens on TCP port 32004 [default] for handling the backup/ restore/ delete requests from the clients. The TCP port 32004 should be open in the NAT/firewall configuration of the StoreGrid backup server

The connectivity between the client and the backup server can be verified using the steps mentioned.

Steps

At the client side,

  1. ‘nslookup < Backup Server name/IP address >’
  2. telnet <Backup Server name/IP address> 32004

If the nslookup command fails, then there is a DNS lookup issue in the client network. Check the DNS configurations at the client side and retry the above tests. If the telnet command fails, make sure that backup server port 32004 (by default) is open in the backup server network’s NAT/firewall configuration.

From StoreGrid v2.3 and above, you can check the client’s connectivity to the backup server using ‘Administration -> Test connectivity to the backup server’ feature in the client’s web console.

Cross platform compatibility of StoreGrid

Description

StoreGrid is inter-operable in different operating systems. StoreGrid client running on an operating system (OS) can backup to (and restore) from a StoreGrid server running on a different OS. Like for example, StoreGrid client running Windows XP OS can backup to a StoreGrid server running in a Linux OS.

Also, the backup data could be restored to machine running a third type of OS. Like for example, the backup from a StoreGrid client running Windows OS to a StoreGrid server running a Linux OS could be restored to a client running FreeBSD OS.

Similarly, the backed up data from a StoreGrid server running one OS can be replicated to a StoreGrid replication server running a different OS. StoreGrid client can restore its backup data directly from the replication server (useful in case the backup server is not available) even if the replication server is running different OS.

Limitation

Backups that are encrypted cannot be restored to machine with a different architecture. Like for example, encrypted backups from a Power PC client cannot be restored on a i386 based machine. This is because the encrypted/decryption of data is machine architecture dependent and data encrypted in a machine of one architecture cannot be decrypted in a machine of different architecture. Restoring non-encrypted backups over cross architecture systems doesn’t have this restriction.

List of Operating Systems in which StoreGrid is supported

Description

StoreGrid is supported in the following operating systems since StoreGrid v3.0

Server Builds

Windows Oses (on both 32 and 64 bit systems)

Supported on Windows 2000 and higher versions

  • Windows 7
  • Windows 2008 R2
  • Windows 2008 Server
  • Windows 2003 Server
  • Windows 2000 Server
  • Windows SBS 2008
  • Windows EBS 2008
  • Windows SBS 2003
  • Windows Vista
  • Windows XP
  • Windows 2000

Linux Oses (on both 32 and 64 bit systems)

  • RedHat Enterprise Linux
  • Redhat 8.0 and higher
  • Fedore Core 3 and higher
  • CentOS 4.2 and higher
  • Mandrake Linux 10.0 and higher
  • Debian 3.0 and higher
  • Ubuntu 5.10 and higher
  • Gentoo 5.10 and higher
  • SuSE Linux 9.0 and higher

Client Builds

Windows Oses (on both 32 and 64 bit systems)

Supported on Windows 2000 and higher versions

  • Windows 7
  • Windows 2008 R2
  • Windows 2008 Server
  • Windows 2003 Server
  • Windows 2000 Server
  • Windows SBS 2008
  • Windows EBS 2008
  • Windows SBS 2003
  • Windows Vista
  • Windows XP
  • Windows 2000

Linux Oses (on both 32 and 64 bit systems)

  • RedHat Enterprise Linux
  • Redhat 8.0 and higher
  • Fedore Core 3 and higher
  • CentOS 4.2 and higher
  • Mandrake Linux 10.0 and higher
  • Debian 3.0 and higher
  • Ubuntu 5.10 and higher
  • Gentoo 5.10 and higher
  • SuSE Linux 9.0 and higher

Macintosh (Client Only)

  • Intel Mac – Mac OS X 10.4.5 & above
  • PowerPC Mac – Mac OS X 10.3.x & 10.4.x

Unix OSes

  • FreeBSD 5.4 and later
  • Solaris 10 (5.10)

Note

All-mode build (client, server, client-server) is supported on Mac for Professional Edition but not for Service Provider Edition. Only Client-Only build is available on Mac for Service Provider Edition.

Setting up authentication and authorization between server and the client

Description

Client authentication is an additional layer of security to check the unauthorized clients from connecting to the backup server. This is done by setting a password in the client’s web console by going to ‘Administration > Authenticate Client‘ page. Once a password is set, the password is transferred and stored in the server when the client connects to the server for the first time. For every subsequent new connection request from the client, the server verifies this password before authenticating the client. This option is most suitable in an environment where an administrator sets up StoreGrid in the client machines and needs to authenticate them with a secret password. This will prevent unauthorized clients (not managed by the administrator) from backing up to the server.

Details

Authorization of clients can be done on top of Authentication for added security. There are two types of authorization between the client and server.

Auto-Authorization disabled

  1. Add the client under the appropriate customer in the backup server before the client can start backing up to the server.
  2. A customer in the backup server can be set to deny Auto-Authorization by clicking on the ‘Lock‘ icon in the ‘Server Admin > Customer Management > List Customers ‘page. An ‘Open Lock‘ icon indicates that the customer is set to deny Auto-Authorization. Once this is done, no new clients can connect to the backup server under this customer until the client is explicitly added in the backup server through the ‘Server Admin > Customer Management > Add Customer‘ page in the backup server web console.

Auto-Authorization enabled

In this mode of authentication, a new client can simply connect to the backup server and start backing up. The client doesn’t have to be explicitly added in the backup server before it can start backing up.

Automatic Directory Monitoring

Description

By default, in Windows, StoreGrid uses the Automatic Directory Monitoring service to identify the files or folders that have changed since the last backup. Though it is generally useful to enable this service, in large backups, it might be helpful if Directory monitoring is turned off.

Explanation

In Windows, StoreGrid by default uses the Automatic Directory Monitoring service. When this service is enabled, the OS sends notifications to StoreGrid when a file or folder is changed. StoreGrid stores these notifications in its database and uses them to backup the changed files during the incremental backups.

If the Automatic Directory Monitoring option is disabled, then during the beginning of a backup schedule, StoreGrid checks all the files and folders configured for backup to identify the files that have changed since last backup – which could slow down the backup. Therefore, in general it is recommended that Directory Monitoring in left enabled (in advanced options) while configuring the backup schedules.

However, when the number of files and folders configured for backup is huge and if several of these files change very frequently, then the Windows OS could send large number of notifications (sends one notification for each file/folder change) which StoreGrid has to process. This could lead to StoreGrid using system resources (to process the notifications) even when it is not actively backing up. Also, this could actually slow down the backup process. In such cases – when the backup set is huge or the files changes too frequently, it is recommended that you configure the backup schedules with Directory Monitoring disabled.

Also, Directory Monitoring should be disabled in the backup schedule if it is configured to backup files from a mapped drive. This is because Windows OS does not send notifications when files/folders present in the mapped drive change. If Directory Monitoring is enabled, StoreGrid will backup only those files/folders for which it has received the notifications and therefore, it will not be able to backup the modified mapped drive files.

Note

  • In non-Windows machines, automatic directory monitoring service is not available. Enabling this option in the backup schedule is therefore of little use.
  • Even if the directory monitoring is disabled, StoreGrid will still do the rsync-based delta backup of the changed files – StoreGrid would still only backup the changes bytes of the modified files alone during the incremental backups.

External drives supported on the backup server

Description

StoreGrid backup server supports storing the backup data in external and mapped drives.

Details

The external drives supported on the backup server are:

  1. External USB hard disk
  2. Mounted or Mapped NAS device
  3. Mounted or Mapped Network hard drive

The backup server is separated into application level (machine where StoreGrid runs) and the storage level (device where the data is stored). In case the backup server crashes, the data will still be intact in the external storage devices and therefore it is much easier to reconstruct the backup server to its original state.

To store the backup data in a network drive or a NAS, you just have to specify the UNC path to the storage location in the Backup Location field in the Server Admin -> Server Settings page in the backup server web console. If you want to enter the mapped drive instead of the UNC path, then you can map the drive through StoreGrid and then use that mapped drive letter in the Backup Location field. For more information on mapping a drive through StoreGrid,

StoreGrid and Data Security

Description

StoreGrid and Data Security

StoreGrid ensures security of backup data in the following ways:

    1. Authenticated connection between client and the backup server. During the client-server connection initialization, the client and the backup server generates random private/public key pairs and based on these random key pairs, the authentication takes place with the client password (hashed and encrypted with the private key). The private keys are never sent out from the client or the server.
    2. The backup data encryption password is hashed before sending it to the backup server. Also, StoreGrid uses its own protocol over raw TCP sockets over SSL for communication between the client and the backup server. The passwords are never transmitted in clear text. Even if the connection between the client and server is through raw TCP sockets (and not using SSL over TCP) the passwords can never be read as they are all hashed and sent.
    3. In StoreGrid’s design the backup server never requires the encryption password at all. The hashed encryption password is sent just for the backup server to verify that the encryption password has not changed across different schedules for the backup. If it did, the backup server will not accept the backup as encryption passwords cannot change across schedules.

Therefore, even if the data is sniffed while in transition from the client to the backup server, the encryption password cannot be captured. Without the encryption password, the encrypted (BlowFish encrypted, up to 448 bit ) backup data cannot be decrypted. And same is the case with the authentication password used for connection between the client and the backup server.

While configuring the backups using StoreGrid, to eliminate security concerns you should do the following:

  1. Enable SSL in StoreGrid client and backup server so that all communication between the client and the backup server are secure.
  2. Configure the backup server to accept connections only from clients which use password based authentication.
  3. Choose a good backup data encryption password.

Backup Speed and Performance

Description

What are the factors that affect StoreGrid’s backup speed and performance in general.

Explanation

StoreGrid performance diagram

The above diagram shows a typical installation of a StoreGrid client machine backing up to a StoreGrid backup server over WAN/Internet. The different elements of the installation that determine the backup speed are marked in red and details of each of these factors are given below:

  1. Speed of the drive where StoreGrid’s internal DB is stored in the backup serverStoreGrid backup server stores the metadata of the backed data in a database. During a backup, StoreGrid backup server accesses and updates its databases several times. If the drive which stores these databases is slow, then the backups from the client machines will also take a longer time to complete. Other factors been equal, the performance of the backup server therefore will be better if its DB is stored in a local drive as opposed to storing them in a NAS or a network mounted drive.When multiple concurrent backups are sent to the backup server, the backup server spawns different threads; each thread handling one backup job. These multiple threads could then be updating the databases concurrently. Therefore, it is important that the drive where the databases are stored performs well for concurrent disk reads and writes. One way to check the speed of the drive for concurrent reads/writes is to run simultaneously multiple ‘copy’ commands to copy files to the drive and see how long it takes. Like for example, if running a single copy command to copy of a file of size 100 MB to the drive takes 10 seconds but running 10 such copy commands concurrently takes say 1000 seconds (much more than 10*10=100 seconds), then it implies that the drive doesn’t scale well as the number of read/writes goes up. In such drives, you will see a drastic reduction in transfer rate when several client machines are backing up to the backup server simultaneously.
  2. Speed of the drive where the backed up data is stored in the backup serverSimilar to how the speed of the database drive affects the backup speed (mentioned above), the speed of the drive where the backup data is stored in the backup server also affects the backup transfer rate. When handling multiple backup jobs, the backup server could be concurrently accessing/writing multiple files in the backup storage location. Therefore, the backup storage drive should not only be fast but should also be able to perform well for concurrent disk reads and writes.
  3. Backup Server machineAnother obvious factor that affects the performance of backups is the available resources – CPU, memory, disk I/O and network bandwidth, in the backup server machine. StoreGrid backup server doesn’t require a dedicated machine to run on. However, if the machine is running several other processes that take up significant resources in the backup server, it could slow down the backups. Therefore it is important to choose a machine for your backup server according to your backup needs – the number of clients backing up to, the amount of data each client machine is backing up, how frequently the client machines backup etc. You can refer the Sizing Guide to estimate the hardware requirements for your backup server.If you have replication enabled in the backup server to replicate your backups to a replication server, it is recommended that you choose the option ‘Replicate immediately after backup’ instead of the option ‘Replicate while backing up’. The reason been, like backups, each replication job runs in its own thread. Running replications while backup jobs are running will therefore use up the backup server resources that much more.Running firewall, antivirus, intrusion detection, file synchronization software etc in the backup server machine could also slow down the backups as typically such applications are process and IO intensive.
  4. Available bandwidth in the network connecting the client machine to the backup serverAvailable network bandwidth is often a limiting factor when the client and the backup server are connected over a WAN or the Internet. To check if network is the limiting factor, you could try ftping data from the client to the backup server machine and check the transfer rate. Since StoreGrid also updates its databases (for reports, book keeping etc) while transferring data, the backup transfer rate will be less that the transfer rate that you see while ftping the data. However, if available bandwidth is limiting factor, then StoreGrid’s backup transfer rate will be close to what you see while ftping the data.
  5. Speed of the drive where the files to be backed up are storedThe speed of the drive where the files to be backed up are stored can also determine the backup transfer rate. This could be a limiting factor especially when the client and the backup server are in the same network where bandwidth is not the limiting factor. Though this is something that you don’t have a control on, it is nevertheless important to understand that client’s side factors such as this often determines the backup speed. A network mounted drive or a shared drive often tend to be slower compared to local drives. Also, if multiple applications are actively accessing a shared drive, StoreGrid might take longer to read the files from it to back them up.
  6. Client server machineDuring incremental backup, StoreGrid client checks for the changed bytes and it then compresses and encrypts the changed bytes before uploading it to the backup server. Identifying the changes bytes, compressing the data and encrypting it require processing power in the client machine. Therefore, the backup speed also depends upon the resources the client machine has. If the client machine is running several other resource intensive applications, the backups might run that much slower.
  7. Client machine’s drive where StoreGrid’s DB files are storedStoreGrid client creates signature/checksum of the files that it backs up in its databases. It uses the signature/checksum to identify the bytes of the file that have changed since the file’s first full backup. Since these databases are updated several times during a backup schedule, the performance of the drive where the DB files are stored in the client machine affects the backup speed. Normally the DB files are created in the same location where StoreGrid is installed in the client machine. If the drive where the DB files are present is heavily accessed by other applications running in the client machine, then StoreGrid might take longer to update the databases and therefore it could lead to slowing down of the backups.

The flow chart below shows the steps you can follow to identify the reasons for the slow backup speed. The flow chart may not exclusively cover all the factors that could be affecting a particular setup but it highlights some of the commonly occurring factors that are typically seen.

Diagram of slow backup

Product version

Applicable to all versions of StoreGrid Service Provider edition, Education Edition and Professional edition

How To

Changing StoreGrid ID

Description

StoreGrid backup server identifies the client by the client’s StoreGrid ID provided while installing StoreGrid on the client machine. This unique ID is used for managing the client’s backup data and configurations. Therefore, it is not recommended to change the StoreGrid ID in the client system once backups have run from the client to the backup server

Details

If you really need to change the StoreGrid ID of the client, uninstall StoreGrid in the client machine and delete the previous installation folder. Then, reinstall StoreGrid in the client machine with different StoreGrid ID.

NOTE

StoreGrid backup server identifies the client by the client’s StoreGrid ID provided while installing StoreGrid on the client machine. , the client loses all the earlier backups and configuration. The backup server will now consider the client as a new client.

Reset StoreGrid web console username and password

Description

StoreGrid user name and password can be reset by following the steps mentioned below:

Details

StoreGrid user name and password can be reset by following the steps mentioned below:

  1. Stop the StoreGrid application.
  2. Go to the folder location “<StoreGrid_Home>/lib/” (for Linux) OR <StoreGrid_Home>/lib/sqlite” (for Windows).
  3. Access the StoreGrid client database using the commandsqlite.bin <DBStorageLocation>/data/sgclient.db (for Linux)sqlite3.exe <DBStorageLocation>/data/sgclient.db (for Windows)
    The <DBStorageLocation> is value of the “Path” attribute under “DBStorageLocation” tag in “SGConfiguration.conf” file under the “<StoreGrid_Home> conf” folder. By Default the DB Storage location will be <StoreGrid_Home>.
  4. Insert an additional user to the database using the following query:insert or replace into SG_USER values (1,1,’admin’, ‘21232f297a57a5a743894a0e4a801fc3’);where, “admin” is the user name, replace it with your preferred user name, and ”21232f297a57a5a743894a0e4a801fc3” is the encrypted password (the value given here is hard coded for “admin” – password
  5. Start the StoreGrid application.
  6. Now you can login to the StoreGrid web console using user name “admin” and password “admin”.
  7. After logging in to the StoreGrid web console, change the password to the desired value by going to “Administration -> Advanced Options -> User Management (tab)” .

Uninstall StoreGrid Completely

Description

How to Uninstall StoreGrid Completely if required.For upgrading StoreGrid, you should NOT uninstall the existing StoreGrid installation. You should install the new version on top of the existing installation.

But in case you need to uninstall StoreGrid and delete all its files, follow the steps outlined below:

In Windows

  1. Go to Start -> All Programs -> Vembu StoreGrid and select Uninstall StoreGrid menu. This will automatically shutdown and uninstall the StoreGrid application in the system.
  2. Delete the StoreGrid installation directory (‘Vembu’ Folder) from the system.

In Linux, Mac, FreeBSD

  1. Uninstall StoreGrid in the system by running “sh uninstall.sh” command from the StoreGrid installation location.
  2. Delete the StoreGrid installation directory (‘Vembu’ Folder) from the system.

Note: If you are uninstalling StoreGrid from a backup/replication server system, you may have to manually delete the clients backed up data as well from the storage location (external drives/NAS/non-default location within the server).

Changing the StoreGrid installation location in client machine

Description

Once StoreGrid is installed in a particular location in a client machine, the location cannot be changed by reinstalling StoreGrid on top of the existing installation. The existing installation has to be uninstalled and StoreGrid has to be installed afresh. Now, if the existing backups have to be preserved, then some of the files from the earlier installation have to be saved (copied to a safe location) before uninstalling StoreGrid.

Details

Follow the steps mentioned below to change the StoreGrid installation location in a client system:

  1. Before uninstalling StoreGrid from the old location, take a copy of both the StoreGrid internal database files (<DBStorageLocation>\data\*.db*) and (<DBStorageLocation>\data\<backup_name>) folders to some other location (say D:\). The ‘<DBStorageLocation>’ is the location in the current installation where StoreGrid’s internal DB files are stored and you can get this from the ‘Path’ attribute of the ‘<DBStorageLocation>’ tag in the <storegrid_home>\conf\SGConfiguration.conf file. By default this DB location will be the StoreGrid installation location.
  2. Uninstall StoreGrid
  3. Install StoreGrid in the new location with the same StoreGrid ID as installed in the old location.
  4. After installing StoreGrid, choose the option not to start StoreGrid immediately after installation. StoreGrid can be started after a little tweak in the installation.
  5. Delete the <StoreGrid_Home>/data/dbpopulation.txt file in the newly completed StoreGrid installation.
  6. Copy both the old StoreGrid internal database files and <backup_name> (saved in step 1) to the new ‘<dbstoragelocation>\data’ location.
  7. Start StoreGrid.
Please note that if you running System State or Registry backup, the StoreGrid will continue to dump in the old dump location

Reset StoreGrid web console username and password for backup server

For StoreGrid backup server running version higher than 2.5.1, web console username and password can be reset by following the steps mentioned below:

Details

    1. Stop the StoreGrid application.
    2. Login to MySQL.
    3. Access StoreGrid database using the given command. For example if the database name is StoreGridDb, then:

use StoreGridDb

    1. Insert an additional user to the database using the following query:

insert into SG_USER values (1,1,’admin’,’21232f297a57a5a743894a0e4a801fc3′);

where, “admin” is the user name. Replace it with your preferred user name, and ‘21232f297a57a5a743894a0e4a801fc3’ is the encrypted password (the value given here is hard coded for “admin” – password)

Note: In the above command, the first parameter (‘1’) and the third parameter (‘admin’) should be unique. A record in the sg_user table with same values will give an error message ‘Duplicate entry ….’. Hence, before executing the above command, execute the following command to check if a record already exists with the same values:

select * from SG_USER;

If a record exists, then specify different values for the first and third parameters.

    1. To insert an additional user in SG_USER table, update the ‘SG_GROUP_USER’ table. Execute the following query to insert additional user

insert into SG_GROUP_USER values(1,1,1,1);

Note: In the above command, the first parameter(‘1’) should be same as specified in SG_USER table and other three parameters should be default ‘1’;

  1. Start the StoreGrid application.
  2. Now you can login to the StoreGrid webconsole using user name “admin” and password “admin”.
  3. After logging in to the StoreGrid webconsole, change the password to the desired value by going to “Administration -> Advanced Options -> User Management (tab)”

Error

StoreGrid TCP port 32004/32005/6060/6061/6363/6264 already in use

Description

This error message occurs in the following cases.

  1. If there is any other application using StoreGrid’s TCP/UDP ports. [TCP ports 32005, 32004 and UDP ports 6363, 6364, web console ports 6060, 6061].
  2. StoreGrid is already running in the system and you are trying to start another StoreGrid instance.
  3. The port has not been cleaned by the OS when StoreGrid was earlier shutdown.

Resolution

To resolve StoreGrid TCP port 32004/32005/6060/6061/6363/6264 already in use errors

To check if some other application is accessing the TCP ports, run the following command:

Windows: ‘netstat -an | find “32005”‘

Linux/Mac/FreeBSD: ‘netstat -an | grep 32005’

If there is any other application using StoreGrid TCP/UDP port, then you can change the backup port number [default 32004], UI communication port [default 32005] or the web console ports [default 6060, 6061] while installing StoreGrid [client/server mode] in the system. You can also change the backup port/UI communication of the existing StoreGrid installations by editing the StoreGrid configuration file by following the steps given below:

  1. Stop StoreGrid process.
  2. Open the “<Storegrid Home >/conf/SGConfiguration.conf” file.
  3. Edit the “<StoreGrid><Configuration>< Ports> Server” attribute value to any valid backup port. Similarly edit the “GUI” attribute value to any valid UI communication port.
  4. Save the configuration file and start StoreGrid application.

Now, StoreGrid will run on the modified backup/UI communication port.

Note

  • You can follow the above steps to change the backup port both for your backup server and the client system.
  • The backup port number should be same at both the backup server and the client systems.

Fatal Error – Maximum Execution Time of 300 seconds Exceeded . . .

Description

This error message occurs in StoreGrid web console when there is no response from the StoreGrid application for 5 minutes.

Resolution

To check if StoreGrid application is running in the machine, confirm that the port 32005 is in LISTEN state by executing the commands ‘netstat -an | find “32005” in the system.

If port 32005 is not in LISTEN state,

  1. Start StoreGrid in the system.
  2. Verify if StoreGrid application is accessible to webconsole requests by executing the “< machine name> 32005″command in the system.
  3. If the StoreGrid application doesn’t start still, then try starting StoreGrid from the command prompt by going to StoreGrid’s installation location and running the command:.\bin\StoreGrid.exe
    Check the output of the above command that you see in the command line.

Error in Starting StoreGrid

Description

This error occurs when the StoreGrid tray is unable to start the StoreGrid Application or the Service.

Details

This error can occur due to one of the following reasons:

  1. StoreGrid Tray application doesn’t have permissions to start the StoreGrid Service.
  2. StoreGrid Application file is not available at the StoreGrid Tray Applications path, i.e. <StoreGrid Home>\bin location
  3. Another instance of StoreGrid is already running in the machine. 

    Resolution

    1. Check if the StoreGrid Tray Application is running in an user account who has privileges to start the StoreGrid Service.
    2. Check if the StoreGrid service’s logon user has enough privileges to start Windows services.
    3. 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 that process and then starting it again.

Invalid License Key. License not applied

Description

“Invalid License Key. License not applied” error appears when trying to apply a license key

Details

This error will occur if a Desktop Os license key is been applied in StoreGrid running in an Server OS machine or vice versa. From version 2.1 onwards, StoreGrid has different license keys for Desktop Operating Systems and Server Operating Systems. The following is how StoreGrid decides whether an Operating System StoreGrid is installed on is a Desktop or a Server OS.

Also, make sure you have entered all the details exactly as it is in the license key. To avoid typos, we recommend you copy and paste the entries from your license key.

Desktop OS: Windows 98, 2000, XP, Vista, Mac OS X.

Server OS : Windows 2000 Server, Windows 2008/2003 Server, Small Business Server, All Linux flavors and FreeBSD

 Desktop OS license will not work on a Server OS system and vice versa.

This error could also occur if some of the details are not entered correctly. To avoid such errors., while applying license key make sure you copy and paste the license key details to avoid any typo errors.

Connection refused . . .

Description

‘Connection refused…’

Details

This error message would occur if StoreGrid web console is unable to connect to StoreGrid application. This could be caused due to the following reasons:

  1. StoreGrid is not running in the system.
  2. System Firewall is not configured to accept requests to port 32005 from the StoreGrid webconsole. It can be verified by running ‘telnet <machine name> 32005’ command.

 

Resolution

Confirm if StoreGrid is running in the system by executing the following command:

‘netstat -an |find 32005″‘ for Windows

”netstat -an |grep 32005’ for Linux.

Check if port 32005 is in ‘LISTEN’ state.

If the port 32005 is not in ‘LISTEN’ state, then StoreGrid might not be running in the system. Start StoreGrid in the machine and then try to login the web console. If StoreGrid still fails to come up, try running StoreGrid from the command line:

  1. cd  to the StoreGrid installation location
  2. run the command
.\bin\StoreGrid.exe (for windows machines)
./bin/StoreGrid (for Linux and Unix machines)

Check the output of the above commands. If you are not able to figure out the reason why StoreGrid is not starting from the output, send the output messages to the StoreGrid support team.

If StoreGrid is already running and still you are not able to access the web console, check the firewall configurations and open port 32005 for the StoreGrid web console to communicate with StoreGrid Application. Also check whether any other application in the system is using 32005 port.

Error

This error is shown if there is a DSN name mismatch between StoreGrid and ODBC connector. This can be verified from StoreGrid configuration file

In a Windows machine, verify this from the StoreGrid configuration file “<StoreGrid_Home>/conf/SGConfiguration.conf” with ODBC connector “Control Panel -> Administrative Tools -> Data Sources(ODBC) -> System DSN” tab. If the DSN name differs then change it in the “<StoreGrid_Home>/conf/SGConfiguration.conf” file by editing <Database .. DSName=””> tag value, then restart StoreGrid. Now try login to your StoreGrid webconsole and check.

In a Linux machine, verify this from the StoreGrid configuration file “”<StoreGrid_Home</conf/SGConfiguration.conf” with ODBC connector configuration in ‘odbc.ini’ file. If the DSN name differs then change it in the “/conf/SGConfiguration.conf” file by editing tag value and then restart StoreGrid machine. Now try login to your StoreGrid webconsole and check

Help FAQ

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.

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

StoreGrid reports an error “Unable to list the Exchange mailbox users…” when trying to configure 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 to get more details.

How is StoreGrid™ different from other desktop backup and laptop backup products?

StoreGrid™ is a flexible backup solution that works with your existing hardware. This flexibility allows it to be deployed in multiple modes – Service Provider Hosted Online Backup, Trusted Peer To Peer Backup and Typical Client-Server deployments.

Service Provider Hosted Online Backup – Online Backup service providers including MSPs, VARs, SIs etc. can use this 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 user desktops in a network for backup purposes. StoreGrid’s P2P deployment capability is based on the concept of trusted peers in an intranet whose desktop space can be utilized in a peer-to-peer fashion.

Typical Client-Server deployments – 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.

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. Store Grid also allows centralized administration from a Web Console (Browser based), to make it easy for system administrators to manage and monitor StoreGrid deployments.

Can StoreGrid be used to backup desktops and laptops to a dedicated backup server inside the intranet?

Can StoreGrid be used to backup desktops and laptops? Yes, StoreGrid can be used to backup desktops and laptops to a dedicated backup server inside the intranet. In this deployment, the dedicated backup server(s) should run StoreGrid in server mode and desktops and laptops should run StoreGrid in client mode.

I already have Apache & PHP running on my system! Do I let StoreGrid install them anyway? Does it interfere with the Apache and PHP I already have?

StoreGrid installs its own installation of Apache and PHP during the installation. Since StoreGrid is well tested with the bundled version of Apache and PHP, it is best not to use other existing installations of Apache and PHP. In general StoreGrid installation of Apache and PHP will not interfere with the existing Apache and PHP. But if your existing apache uses port 6060 or port 6061, then you need to configure StoreGrid to use a different port during the installation as StoreGrid’s apache webserver uses port 6060 and 6061 (for HTTPS) by default.

Why does my StoreGrid™ peer not discover other StoreGrid™ peers in my network automatically?

StoreGrid™ relies on multi-casting, UDP and TCP port scan to discover at least one StoreGrid™ Client/Server(peer)in the network. But if multi-casting is disabled in the network, then discovery may be delayed because UDP or TCP port scans can be time consuming. Also, StoreGrid™ is configured to discover StoreGrid™ peers only in a subnet. You can manually discover a StoreGrid™ peer (both within and outside the subnet) using the “Add Peer” feature from the StoreGrid™ Web Console.
If you are using Windows XP with Service Pack 2 installed, please click here.

How does StoreGrid™ do Open File Backups?

When StoreGrid™ backs up a file, it can detect automatically if the file has been changed. Hence StoreGrid™ can ensure that no file is backed up incorrectly. For files that change during a backup, StoreGrid™ does a best effort attempt continuously (in the background) until the backup for the file succeeds. In a desktop/laptop environment this strategy almost never fails. However, it is important that StoreGrid™ be allowed the requisite permission to access the file(s) that are to be backed up. For example, Microsoft Outlook cannot be backed up if it is open as StoreGrid™ cannot access the requisite files. The best way to handle open file backups is to use StoreGrid™’s Open File Plugin.

Open File Backup Plugin. This plugin is pre-configured to allow StoreGrid™ process to access the open files.

 

Can the StoreGrid™ Client be installed on a NAS file server to back it up to user desktop machines or other dedicated backup servers?

Can the StoreGrid™ Client be installed on a NAS file server to back it up to user desktop machines or other dedicated backup servers? StoreGrid™can be installed on Linux or Windows based NAS servers. It is possible to backup a NAS file server over the network to other user desktops or a dedicated backup server. If StoreGrid™ cannot be installed on a NAS filer, it will be possible to install StoreGrid™ on a PC, mount the NAS server and then back it up. In the case of NAS file servers, open file backup may not happen if a file is being continuously modified by an application. In Windows Storage Server, it is possible to use the Volume Shadow Copy feature to support Open File backups. In NAS filers where files are not modified continuously StoreGrid™’s open file backup should suffice.

What type of encryption does StoreGrid™ use to secure the data being backed up? How secure is my data?

StoreGrid™ uses the Blowfish encryption algorithm. You can get more information about blowfish algorithm at http://www.schneier.com/blowfish.html

Excerpts from the blowfish website:
“Blowfish was designed in 1993 by Bruce Schneier as a fast, free alternative to existing encryption algorithms. Since then it has been analyzed considerably, and it is slowly gaining acceptance as a strong encryption algorithm”.
StoreGrid™ will support other encryption algorithms as options in the future. As such your data is very secure as blowfish based encryption has never been broken before.

What happens if I forget my backup encryption password?

Whoops! If you forget the backup encryption password, then there is no known way to decrypt your backed up data. So it is recommended that you write down the backup encryption password in a safe and secure place

Why does StoreGrid™ restart automatically even after I shut it down?

During installation, StoreGrid™ also installs a separate application called StoreGrid™ Tray. This application appears as an icon in your Windows Tray. If you want to stop the StoreGrid™ application, you need to stop it through the menu that pops up while right clicking the StoreGrid™ Tray. If you stop the StoreGrid™ application in any other way, StoreGrid™ Tray will automatically restart the StoreGrid™ application. This feature is to ensure that StoreGrid™ application is always running to protect your data even if it exits unexpectedly because of any bugs or other reasons.

Does StoreGrid™ support backing up to peers over the internet?

StoreGrid™ (Professional Edition) peers can communicate with each other and backup data over the internet if there is direct connectivity between the peers. If the two peers are behind NAT, then you need to configure port forwarding in your NAT device to enable StoreGrid™ peers to connect to each other. If the two peers are just backing up to each other then you need to configure TCP port 32004 for port forwarding in your NAT device. Please check the”NAT/Firewall” configuration in the StoreGrid™ help documentation for more details.

When I click on StoreGrid™ Web Console, I am redirected to a search/directory page. Why does this happen and how do I get around it?

Some toolbars and related software can take over your browser window even if you don’t want them to! Uninstalling them usually solves the problem. Alternatively, you could manually type in the URL in your browser’s address bar: http://machine-name:6060 where “machine-name” is the name of your machine, eg. http://joe:6060

If I shut down and restart StoreGrid™ after a period of time, will StoreGrid™ automatically detect modified files and newly created files and back them up?

It depends on the settings you’ve selected when creating the backup schedule. StoreGrid™ will automatically detect all the modified and newly created files and back them up after a restart if:

  1. You selected the continuous backup option
  2. You selected the ‘run every __ hours __minutes” option. In this case, StoreGrid™ will run this schedule whenever it restarts, and thereafter schedule the next backup after the period you’ve selected.
  3. You’ve selected the “Run this Backup each time StoreGrid™ restarts” option in Advanced Options

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 enabled incremental backups (which you should be doing if you’re backing up online), only changes in files/folders are backed up. These incremental backups consume lot less time & bandwidth! StoreGrid™ has a feature that allows you to take the first ‘heavy’ backup locally to say, a USB Disk, physically move the data to a remote server, and thereafter seamlessly continue with incremental backups directly to the remote server. Details on using this feature are covered under the section ‘Seed Backup Migration’ in the Help Documentation.

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 machine with the same StoreGrid™ ID you used before. And you will first need to restore your Client configurations from the 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 can restore your data from the Restore menu. Note that you will have to authenticate your new StoreGrid™ with the server before the server will allow you to connect.

My server was set up to backup data to a certain location. I now wish to change that location. How do I do this?

By default, StoreGrid™ server uses the installation location or Server Backup Storage Location value configured during installation as the backup location to store the client’s backup data. You can change the backup location of the server from the “Server Admin->Server Management-> Server Settings” page in the backup server’s StoreGrid™ webconsole. But if you already have clients backing up to the server, then those existing clients will not use the new backup location for further backups. The new location will only take effect for the new clients backing up to the server.

You can also change the backup storage location for individual clients. The client’s backup storage location can be changed by going to ‘Server Admin ->Group Management -> <Group Name> -> Edit Client Configuration (action for the particular client)’ page in the backup server webconsole.

I’m currently using the Free Edition. I wish to move to StoreGrid Professional. How do I do this?

From StoreGrid v2.4 onwards, upgrading from Free edition to Professional edition is not directly supported. For upgrading StoreGrid free edition to professional edition, you can save the Free edition backup data and configurations to another location. Then, uninstall free edition installation and install the professional edition build afresh. After that, you can migrate free edition backup data to professional edition by using Seed Backup Migration feature.

Sometimes when I try deleting an existing backup schedule, it takes a lot of time. Why is this?

While deleting a backup, StoreGrid tries to connect to the server machine to delete the backed up data. So, please verify that the server machine is accessible from the client machine and that StoreGrid is running on the Server machine in “Server/ Server-Client” mode. The delete operation will be scheduled every 5 minutes. If a backup could not be deleted because of some reason (the backup server being down permanently, etc.) then the delete operation will be rescheduled every5 minutes. There is no way to cancel the delete operation. It will be scheduled again even when StoreGrid is stopped and restarted. Hence, ideally, StoreGrid must be running on the server machine for completing the backup delete schedule. In a ‘not so ideal’ situation, you could use the “Delete Backup Schedule even if the server is down” option from the “Delete Backup Data/Schedule” page. The backup configuration will be deleted from the client side in the next delete schedule, ie about 5 minutes. Please note that the backed up data in server might not be deleted by selecting this option.

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 in files/folders are backed up during future backups. However, in some cases, you may prefer to take a full backup every 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’ button under Step 5 (Scheduling) in the ‘Backup–>Backup Schedule’ menu.

I have backups scheduled in my laptop for a certain day and time. If the backup server is not powered on at the scheduled backup time, how do I ensure that StoreGrid in my laptop 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 a problem (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) in the ‘Backup–>Add Backup Schedule’ menu.

How do I delete files & folders that I’ve backed up but no longer need. I’ve deleted them on 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. Instead StoreGrid will backup the fact that the files are deleted and the backup server will tag the files with that information. But StoreGrid WebConsole UI provides a way to delete files permanently from the server. Please check the “Backup->Permanently Delete Files From Server” section in the StoreGrid help documentation to learn more about how to delete backed up files permanently from the server. Future releases of StoreGrid will have a feature to automatically delete files permanently from the server after a configurable time period.

I tried the Internet Explorer Settings preconfigured backup. While I expected it to just backup 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 if you need to restore, you get your IE exactly as it was earlier. If you wish to only backup the bookmarks file, you simply need to configure this as any other file backup after manually selecting the file.

Can StoreGrid work in any Linux distribution?

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, Debian 4.x, Ubuntu 7.x. We expect StoreGrid to work in most flavors of Linux if the installation of StoreGrid goes through fine. During installation StoreGrid compiles its own bundled Apache and PHP. SoStoreGrid installation will require the following packages to be installed in the Linux system: make, gcc, g++, libc6-dev, libxml2, libxml2-dev and libstdc++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 at support@storegrid.co.za for help.

I know StoreGrid works across Windows, Linux, Mac, FreeBSD operating Systems. Does that 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 supported operating systems. That is, you can backup your Mac OS X to a Windows or Linux OR backup your Windows to a Linux or Mac OS X and so on. The only limitation is that when you restore your data to any client machine (other than the originator machine), the new client machine has to support the same matching endian byte order. For example, a Mac OS X can backup to a Windows. But the backed up data has to be restored by only another Mac OS X system. This is because the blowfish encryption algorithm StoreGrid uses is based on the endianess of the machine. If all the different machines are based on Intel processor, then there should not be any problems with the restore across operating systems.

I see that StoreGrid uses the MySQL database. Can I replace the MySQL database in my backup 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 are currently working on supporting other databases (such as, PostgreSQL, Microsoft SQL Server) for StoreGrid internal databases and will be available in future versions of StoreGrid.

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 the StoreGrid application.

  1. If your system is configured with any firewall settings, please add the following to your firewall exception list.
    1. <StoreGrid_Home>\apache\Apache.exe
    2. <StoreGrid_Home>\bin\SGTray.exe
    3. <StoreGrid_Home>\bin\StoreGrid.exe
    4. 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.
    1. When “Include all local(intranet) sites not listed in other zones” option in “Tools -> Internet Options -> Security -> Local intranet -> Sites” is disabled.
    2. And if the privacy settings is set to “High” in “Tools -> Internet Options -> Privacy” tab.

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 and try using the StoreGrid webconsole.

I am getting “Unable to send backup details to server . An operation was attempted on something that is not a socket.” error when running large number of files/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 to reestablish the connection and proceed with the backup from where it left off. However, if the client is not able 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 some reason.

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 may fail 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 you run StoreGrid with the option “Run as Administrator”. The reason been, Vista allows an application to access the ‘Program Files’ folder only when run as an administrator user. You can enable the ‘Run as Administrator’ option for the <StoreGrid Home>\bin\StoreGrid.exe application through it’s file properties dialog through ‘Compatibility’ tab -> ‘Privelege Level’ -> ‘Run this application as administrator’ option. If you don’t have administrator access or if you don’t want to run StoreGrid under the administrator account, make sure you install StoreGrid under your user account folder or other than the ‘Program Files’ folder.

Error while dumping the Exchange Mail Boxes. Unable to create the PST file [or] “No new/modified files for 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 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

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 to store the *.PST files. To resolve this, 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 ‘view backup configuration’ of that backup schedule in the Backup->List Backup Schedule page in the client web console.

Error while creating the dump location

When the configured dump location for that particular backup schedule is not accessible or StoreGrid does not have enough permission to access the directory, then this error might occur. Make sure that the dump location drive exist in your StoreGrid client. If that drive exist, provide enough permissions to the user under which StoreGrid is installed to be able to write to the location.

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 to list 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 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.

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 not installed then you will get this error. Please refer the System State backup trouble shooting page to get more details.

How is StoreGrid different from other laptop backup and desktop backup products?

StoreGrid is a flexible backup solution that works with your existing hardware. This flexibility allows it to be deployed in multiple modes – Service Provider Hosted Online Backup, Trusted Peer To Peer Backup and Typical Client-Server deployments.

Service Provider Hosted Online Backup – Online Backup service providers including MSPs, VARs, SIs etc. can use this 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 user desktops in a network for backup purposes. StoreGrid’s P2P deployment capability is based on the concept of trusted peers in an intranet whose desktop space can be utilized in a peer-to-peer fashion.

Typical Client-Server deployments – 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.

Another important feature of StoreGrid is the ease with which end users can configure backups and restore them, when required, without the help of system administrators. StoreGrid also allows centralized administration from a Web Console (Browser based), to make it easy for system administrators to manage and monitor StoreGrid deployments.

Can StoreGrid be used for Remote Backups?

Can StoreGrid be used for Remote Backups? Yes, StoreGrid can be used to backup a computer to a Remote location provided the computer has direct connectivity to the Remote Backup server runningStoreGrid. This facility is however not available in the Free Edition!

I have given a daily backup schedule to run at 5.00 PM. But at times, StoreGrid seems to be running this backup schedule at other times as well. Why?

There are two reasons why StoreGrid will run a backup schedule at a time different from the configured schedule time.

  1. When StoreGrid is shutdown and restarted, it will run all backup schedules once before scheduling them at the configured time. This is to ensure that any files created/modified when StoreGrid was shutdown are backed up as soon as possible.
  2. If you selected “Attempt to run this backup every five minutes…” in Advanced options, and a backup schedule is incomplete because of various reasons (like network connection problem etc.), StoreGrid will schedule the backup every 5 minutes to ensure the backup schedule is completed as soon as possible. In this case, only after the backup schedule is completed will StoreGrid schedule it at the configured time.