-
Description of the Error Codes
Common GigaVaultStorage 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 help@gigavaultstorage.com
| Error Codes |
What does this error code mean? |
| SG0083 |
This error occurs when :
- 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
- 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 GigaVaultStorage not running. Click here for the resolution |
| SG0200 |
No drive space available in the Backup Server to continue the backups |
| SG0191 |
Active backup is suspended in the client or the Backup Server |
| SG0178 |
Exceeding allotted backup space in Backup Server |
| SG0180 |
Backup space not configured for the client in the Backup Server |
| SG0601 |
Failed to initialize the compression module to compress file contents for backup |
| SG0094 |
Unable to read the file during time of backup |
| SG0290 |
Backup schedule is active during delete schedule configuration, suspend the 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 GigaVaultStorage or Error in Starting GigaVaultStorage. Click here for the resolution |
Top
-
GigaVaultStorage reports an error "Unable to list the Exchange mailbox users. Make sure sufficient permissions are available for the user account under which GigaVaultStorage 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 GigaVaultStorage webconsole, then follow the steps given below to resolve the issue:
Create a new user with sufficient rights through Active Directory Users and Computers.
Assign "Full Mailbox Access" permission to that new user.
Add that new user in the 'PluginConfiguration.conf' file located in "<SG_Home>/plugins" folder.
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.
Top
-
GigaVaultStorage doesn’t start after upgrading an old version of GigaVaultStorage to the latest version.
Cause :
GigaVaultStorage databases not upgraded properly.
Resolution :
Please refer this online detailed help document on upgrading GigaVaultStorage and on how to recover from a bad upgrade http://www.storegrid.net/docs/storegrid/recovering-bad-multi-version-upgrade.pdf
Top
-
GigaVaultStorage reports an error "Unable to list the Exchange mailbox users..." when trying to configure Exchange Mailbox level backup in 2007 Exchange server (64 bit) machines.
Resolution :
GigaVaultStorage 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, GigaVaultStorage uses its 32-bit exe to list, backup and restore the Exchange Mailboxes in 64-bit machines. To accomplish this, GigaVaultStorage 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.
Top
-
SG0147/SG0136: Unable to connect to the Backup Server
Cause:
This error occurs when
Client is not able to connect to the Backup Server's Backup Port (default 32004).
GigaVaultStorage is not started in the server machine, therefore Backup Port (default 32004) is not occupied by GigaVaultStorage.
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 GigaVaultStorage Client system through the command prompt.
If the telnet command doesn't work, then check the firewall configuration of the GigaVaultStorage Server and make sure the Backup Port (default 32004) is open for the incoming traffic.
Check that the GigaVaultStorage server is running in your GigaVaultStorage 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 GigaVaultStorage Backup Server system.
If Backup Port is not in LISTEN state, start the GigaVaultStorage in the Backup Server. Also make sure GigaVaultStorage is running in either Server Only or in Client-Server mode in the GigaVaultStorage 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 <GigaVaultStorage Home>/conf/SGConfiguration.conf file.
- Refer the following URL to know more about NAT/Firewall configurations. nat-firewall-configuration.html
Top
-
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 GigaVaultStorage is actively processing the backup data to the Backup Server. The external forces may be:
NAT/Firewall configurations.
Low end routers/switches.
Intrusion detection software.
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 GigaVaultStorage 2.2 Release) For details, refer to the FAQ section at help@gigavaultstorage.com
Top
-
SG0132: Invalid remote socket
Cause:
This error message occurs when GigaVaultStorage 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:
'GigaVaultStorage stopped during backup' – This error indicates that either the GigaVaultStorage process was stopped during backup or the GigaVaultStorage 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 GigaVaultStorage FAQ on the same error at http://www.vembu.com/storegrid/network-backup-faq.html #Network-Backup-Faq34
Top
-
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.
nslookup <Backup Server Name> command.
If the above commands work, then the GigaVaultStorage should be able to resolve the Backup Server's hostname. If the above commands fail, then check the DNS configurations on the client side and make sure that the client is able to lookup Backup Server's hostname. Also, try running the telnet <Backup Server Name> <Backup Port> (by default the Backup Port is 32004) command in the client machine. If the telnet command works (shows a blank console screen), then backup should work.
Resolution:
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 GigaVaultStorage Client web console.
Delete the Backup Server name from the list of GigaVaultStorage 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.
Top
-
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.
Backup Server is not able to resolve the Replication Server's hostname due to DNS lookup issue.
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:
ping <Replication Server Name>
nslookup <Replication Server Name>
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 GigaVaultStorage Replication Server is running in that port.
Top
-
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 -> Customer Management -> [Customer_Name] ->Edit Configuration (Action for the particular Client) page and enter the required space in Space Allotted field. Refer to the URL client-backup-configuration.html
Top
-
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, GigaVaultStorage will reset the status of the backup schedule in the Backup Server. If the reset of active status completes successfully, then the GigaVaultStorage 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.
Top
-
Clients not backing up to the server after moving the clients from trial customer
Cause:
This error could occur if the client is deactivated or the customer doesn't have enough MSPEUs.
Resolution:
Make sure that the customer and client are not deactivated by going to the Server Admin -> Customer Management page and then checking the action (activate/deactivate) for the particular customer. To check the client status, go to Server Admin -> Customer Management -> <Customer Name> page and check the action (activate/deactivate) for the particular client.
Ensure sufficient MSPEUs are available for the customer.
Check the MSPEU's configuration to verify the MSPEU's limit set to the particular customer.
Increase the allotted MSPEU or edit the MSPEU configuration for the customer to AUTO by choosing the option Automatically use MSPEUs from the Server Admin -> Customer Management -> <Customer Name> -> Edit Configuration page.
Now, try configuring the backups from the client to the server and check if the error is resolved.
Top
-
Problem in accessing the snapshot device while opening file
Cause:
This error appears when the GigaVaultStorage 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 GigaVaultStorage is listing the files for backup.
Resolution:
GigaVaultStorage 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.
Top
-
“Error Code 21 Cannot Start GigaVaultStorage” message from the tray / “Error in Starting GigaVaultStorage" message from GigaVaultStorage Tray
Cause:
These errors occur when the GigaVaultStorage tray is unable to start the GigaVaultStorage Application or the Service. The reason could be one of the following:
The GigaVaultStorage Tray application doesn't have permissions to start the GigaVaultStorage Service.
The GigaVaultStorage Application file is not available at the GigaVaultStorage Tray Applications path, i.e <GigaVaultStorage Home>\bin location.
Another instance of GigaVaultStorage is already running in the machine.
Resolution:
Check if the GigaVaultStorage Tray Application is running in an user account who has privileges to start the GigaVaultStorage Service.
Check if the GigaVaultStorage service's logon user has enough privileges to start Windows services.
-
Check if any other GigaVaultStorage 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.
Top
-
Your GigaVaultStorage license has expired. Number of GigaVaultStorage Installations exceeded 1. Backups disabled.
Cause 1:
System name/IP addresses are duplicated in the Administration -> Add/Delete Peer page
Resolution:
Stop GigaVaultStorage application.
Rename the "<DB Storage Location>/data/sgdisc.db" to "sgdisc.db.org" file.
Start the GigaVaultStorage application.
Cause 2:
More than one GigaVaultStorage instance is trying to use the same license key. The applied GigaVaultStorage license is shared by other GigaVaultStorage instances running in the same network. If there is a GigaVaultStorage 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 GigaVaultStorage 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 GigaVaultStorage application to a particular IP address/subnet only by following the steps below.
Stop the GigaVaultStorage.
Open <GigaVaultStorage Home>\conf\SGConfiguration.conf file in a text editor.
Provide the private IP address value in the IPAddress attribute of the <StoreGrid> tag and save the file.
Restart the GigaVaultStorage application.
The GigaVaultStorage 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 GigaVaultStorage peers again and update itself correctly after restart.
Stop GigaVaultStorage application.
Rename the "<DB Storage Location>/data/sgdisc.db" to "sgdisc.db.org" file.
Start the GigaVaultStorage application.
Top
-
Client did not receive a valid license from the Backup Server
Cause:
This error occurs if the client does not have enough MSPEUs for the Customer in the Backup Server. GigaVaultStorage will validate the MSPEU allotted for the client based on the MSPEU pool allotted to the Customer or globally on the Server. The MSPEUs will be used every month for the clients in the Backup Server based on the client's operating system and the usage of Advanced SQL & Exchange Server Plugins in the client.
Resolution:
Apply MSPEUs for the customer. For more information on MSPEUs and their usage in the Backup Server, refer to the following URLs:
For MSPEU Management : mspeu-management.html
To Add MSPEUs : add-mspeus.html
For MSPEU Utilization : mspeu-utilization.html
Top
-
Your GigaVaultStorage license has expired. License period elapsed, Backups disabled
Cause:
This error might occur in a GigaVaultStorage client if GigaVaultStorage is installed in Client-Server mode in the client machine.
Resolution:
If the GigaVaultStorage 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 GigaVaultStorage Tray icon, go to Change GigaVaultStorage Mode menu and select the Client option mode.
If the client is running in a non-Windows machine, then the GigaVaultStorage mode can be changed manually by following the steps given below:
Stop GigaVaultStorage.
-
Edit the <GigaVaultStorage_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 GigaVaultStorage 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 GigaVaultStorage.
Top
-
Customer Migration failed. The target customer does not have enough licenses (MSPEUs)
Cause:
The error message occurs when there are not enough MSPEUs available for the customer to which the clients are being migrated. If the 2.1.1 Backup Server has been upgraded to 2.2.1 version, then the client license details are automatically migrated to the necessary MSPEUs when the client license is added in the Backup Server. If the older version is uninstalled and 2.2.1 installed afresh in the Backup Server, the licenses added in the 2.1.1 version will not be converted to MSPEUs.
Resolution:
-
If the paid customer doesn't have enough MSPEUs for the new clients, generate the necessary MSPEUs through the Partner Zone from your existing SPEU credits and add them to the Backup Server using Server Admin -> MSPEU management -> Add MSPEUs page in the GigaVaultStorage Web console.
Top
-
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 customer 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 GigaVaultStorage Backup Server. Go to Server Admin -> Customer Management -> [Customer 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 GigaVaultStorage client's web console.
-
Authorize a new password (for both client and server) by editing the password in the Backup Server in Server Admin -> Customer Management -> [Customer 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.
Top
-
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 GigaVaultStorage client to the GigaVaultStorage Replication Server.
The GigaVaultStorage Replication Server will not accept the backup request from GigaVaultStorage Clients.
GigaVaultStorage 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 GigaVaultStorage Backup Server is designed for receiving Backup/Restore Requests from the client.
Hence, Replication Server will not process the backup request from the GigaVaultStorage client.
Resolution:
Configure backup from GigaVaultStorage client to GigaVaultStorage Backup Server.
Enable replication in the GigaVaultStorage Backup Server for the corresponding customer.
The client will backup to their server and the backup data on the server will be replicated to Replication Server.
Top
-
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.
-
GigaVaultStorage 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, GigaVaultStorage will not be able to identify the changed files when Automatic Directory Monitoring is enabled for backup of files from a mapped drive.
Resolution:
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 GigaVaultStorage list all files/folders for backup again and therefore the files will get picked up.
Top
-
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.
Top
-
GigaVaultStorage not able to backup over the internet
Cause:
GigaVaultStorage 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.
Top
-
GigaVaultStorage doesn't seem to work in XP SP2/SP3
Cause:
In Windows XP SP2/SP3, the firewall is enabled by default. GigaVaultStorage can neither discover other GigaVaultStorage peers nor it can backup data to other machines.
Resolution:
Either disable the firewall settings or enable the ports for GigaVaultStorage to work.
-
To disable the firewall, follow the steps below:
Open START->CONTROL PANEL->WINDOWS FIREWALL
Select Exceptions tab
Under 'Programs and Services', click on Add Programs button
Browse and choose the StoreGrid.exe and Apache.exe. StoreGrid.exe is located at "InstallDir"\GigaVaultStorageInc\GigaVaultStorage\bin directory. Apache.exe is located at "InstallDir"\GigaVaultStorageInc\GigaVaultStorage\apache directory. "InstallDir " is the location where GigaVaultStorage is installed (by default it is C:\Program Files).
Select OK to save the configuration and exit. GigaVaultStorage can now use any TCP/UDP ports as the firewall settings have been disabled for the GigaVaultStorage and Apache applications.
-
Enable to the following ports:
TCP Ports: 32004, 32005, 32007, 32008, 6060, 6061
UDP Ports: 32006, 6363, 6364
Open START->CONTROL PANEL->WINDOWS FIREWALL
Select Exceptions tab
Under Programs and Services, click Add Port button
-
Add 4 TCP Ports with unique names, allowing TCP Port numbers 32004,32005, 32007, 32008, 6060 and 6061.
Add 3 UDP Ports with unique names, allowing UDP Port numbers 32006,6363 and 6364.
Select OK to save the configuration and exit.
Top
-
Backup of trial customers stop at 100MB though enough space is allocated in the server
Cause:
From GigaVaultStorage 2.2 release, GigaVaultStorage Backup Server by default allocates 100 MB of disk space for the trial customers.
Resolution:
This default value can be changed through the server webconsole Server Admin -> Customer Management -> Configuration Settings For Trial Clients (icon) page. However, the changed space allocation configuration will be applicable only to the new trial clients
To change the space allocated for the existing trial customers, go to Server Admin -> Customer Management -> <Customer_Name> (Link) -> Edit Configuration (Action for the particular client) page in the GigaVaultStorage server webconsole.
Top
-
GigaVaultStorage Server is not listed in the "Backup Servers" list
Cause:
GigaVaultStorage automatically discovers other GigaVaultStorage peers in a network using various means (multicast, UDP port scan, TCP port scan etc). If for some reason a GigaVaultStorage server or client is not discovered automatically, it will not be listed in the 'Backup Servers' list.
Resolution:
Manually add the GigaVaultStorage peer to the list from the menu item Administration->Add Peer. In the "Add Peer" page, enter the GigaVaultStorage 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).
Top
-
GigaVaultStorage has exited, do you want to restart it
Cause:
This error appears when GigaVaultStorage 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.
Top
-
"Apache.exe could not be replaced" message during installation
Cause:
This happens when the GigaVaultStorage web server service (which uses Apache) did not exit properly when the previous installation of GigaVaultStorage 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 GigaVaultStorage Web server service and then proceed with the install.
Top
-
Linux installation fails while installing GD/PHP (applicable only to versions older than 2.3)
Cause:
GigaVaultStorage uses Apache, GD and PHP for its browser based user interface. GigaVaultStorage is bundled with Apache, GD and PHP source files and these files get compiled during installation. GigaVaultStorage installs Apache, GD and PHP in "/GigaVaultStorageInc/GigaVaultStorage" directory. And it is packaged with the modules that are required for GigaVaultStorage user interface. If the required packages or third party libraries are not present, then the compilation will fail.
Resolution:
Before installing GigaVaultStorage 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/
Top
-
Unable to log you in. Make sure GigaVaultStorage is running / No connection could be made because the target machine actively refused it
Cause 1:
GigaVaultStorage application is not running in the system.
Resolution:
In Windows OS.
Confirm that the GigaVaultStorage application [StoreGrid.exe] is running in the system by using "Task Manager".
If the application is not running, start GigaVaultStorage through the GigaVaultStorage system tray application.
In Linux OS
Verify if the GigaVaultStorage application is running in the system by executing the command 'ps -e |grep GigaVaultStorage'.
If the application is not running, start it with the command "sh startGigaVaultStorage.sh" in <GigaVaultStorage_HOME> directory.
If you see the following error message: "error while loading shared libraries: libstdc++.so.5..." while trying to start GigaVaultStorage, 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 GigaVaultStorage 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 GigaVaultStorage.
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 GigaVaultStorage web console is unable to connect the GigaVaultStorage applications UI communication port [by default, 32005].
Resolution:
Confirm if the GigaVaultStorage 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 GigaVaultStorage 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 GigaVaultStorage’s web console.
Top
-
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 GigaVaultStorage build exe.
-
Right click the exe and "run as an administrator".
Top
-
GigaVaultStorage doesn't seem to run properly after upgrading Windows to Vista.
Cause 1:
If GigaVaultStorage was installed in an older version of Windows and then if the OS was upgraded to Vista, GigaVaultStorage may fail to run.
Resolution 1:
Install (upgrade) the same version of GigaVaultStorage again on top of the existing install.
Cause 2:
GigaVaultStorage is installed under C:/Program Files in Vista.
Resolution 2:
Make sure you run GigaVaultStorage 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 <GigaVaultStorage 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 GigaVaultStorage under the administrator account, make sure you install GigaVaultStorage under your user account folder or install it in a folder which is not under 'Program Files'.
Top
-
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
Top
-
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.
Top
-
Error while creating the dump location <Dump_Location>
Cause :
The configured dump location for that particular backup schedule is not accessible or GigaVaultStorage does not have enough permission to access the directory.
Resolution :
Make sure that the dump location drive exist in your GigaVaultStorage client. If that drive exist, provide enough write permission to the user under which GigaVaultStorage is installed.
Top
-
Users Mailbox/folder are not listed in the "Create Exchange Mailbox Backup" page.
Cause :
GigaVaultStorage 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 GigaVaultStorage service is running. Please refer Granting Mailbox Rights document on creating a new user and granting the sufficient rights to access the mailboxes.
Top
-
GigaVaultStorage fails to list some files/folders during a backup schedule.
GigaVaultStorage fails to list the files/folders due to the following reasons:
Cause 1:
In Windows, GigaVaultStorage logon user is not in the Backup Operators group.
Resolution 1:
Check if the GigaVaultStorage logon user is added in the Backup Operators group. If the GigaVaultStorage logon user is a member of Backup Operators group, GigaVaultStorage 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 GigaVaultStorage user.
Resolution 2:
Check if GigaVaultStorage logon user has ‘Read’ and 'List Folder Contents' access permissions for the skipped folder by going to 'Folder Properties -> Security' dialog.
If GigaVaultStorage logon user doesn't have permission, enable the required permissions.
Reschedule the backup and check.
Cause 3:
File/folder name contains Unicode characters.
Resolution 3:
Rename the file/folder without the Unicode characters.
Top
-
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 <GigaVaultStorage><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.
Top
Home 
Print
