Listado de indicadores para las variables dependientes

Exchange Server is not installed or not available in the system.

Cause : If Exchange Server services running in the local machine were not detected during StoreGrid installation process.

Solution: Please verify that the following files "XchangeServer.sgpl" & "ExchangeServer.sgpl" exist in "< StoreGrid_Home>\ Vembu\StoreGrid\plugins" folder. If these files don't exist in the location, please try installing StoreGrid on top of the existing installation and check if you were able to create Exchange Server Backup schedule without errors.

The following message is displayed in the backup report "The database missed a previous full backup before the incremental backup".

Cause 1: After a successful restore, if incremental or differential logs backup is performed before running a full backup then Exchange Server backup report will display the above error message.

Backup Schedule" page to run additional full backup and then proceed with the incremental or differential log backup. Cause 2: If a new Database is added to existing Storage Group which was already configured for backup.

Solution 2: Check the option "Run additional full backup after saving this configuration" in the "Edit Exchange Server Backup Schedule" page to run additional full backup and then proceed with the incremental or differential log backup. Cause 3: This issue could arise when StoreGrid is trying to run an incremental backup on a database in a Storage Group when at least one of the remaining databases in the Storage Group had not been configured for full backup at least once. In such a situation, Exchange Server will not allow StoreGrid to purge the logs files for the configured database.

Solution 3: Configure full backup for the remaining databases temporarily. And later you can delete this backup schedule if this backup is not needed.

The following message is displayed in the backup report. "No new/modified files for backup". Cause 1 : If you try to do an incremental or a differential log backup on a exchange server that has circular logging enabled, Exchange server generates the above error message that the incremental or differential backup cannot be done.

Solution 1 : Turn off circular logging do an incremental or a differential log backup. To verify that circular logging is disabled, open Exchange System Manager and navigate through the console tree to Administrative Groups -> your administrative group -> Servers -> your server -> the storage group you want to check. Right click on the storage group, select properties, and verify that the "Enable Circular Logging" checkbox is not selected.

Cause 2 : If the temporary dump directory configured for backup schedule doesn't have enough space.

Solution 2 : Please ensure that you have enough disk space in the configured temporary location (where the backup dump has to be saved).

The following message is displayed in the backup report. "Backup is already active". Cause : This message would be displayed in the client backup report in the following conditions :

i. If the same Storage Group or the Database from the same Storage Group configured for backup is backed up by some other process.

ii. If StoreGrid is killed or stopped and started immediately, while exchange server data dump was in progress. Then a previous instance of Backup (ESE API) could still be running in the background and it still has a connection open to the specified service. In this case a second instance will not be able to connect to the exchange server.

Solution : If the failed backup is a full backup, then edit the backup schedule to take an immediate full backup. For other backup schedules click schedule now button in the "List of Backup Schedule" for the backup schedule to take the backup.

The backup schedule fails with connection failure message [SG083, SG132...] in the backup report.

Cause : When StoreGrid is doing the local dump of the exchange server data, the client's socket connection to the backup server will be idle. Depending upon the time the dump process takes, some firewall/router/NAT settings may close this idle socket connection after a timeout period. Hence, after the dump process, when StoreGrid tries to transfer the dump file to the backup server, the connection is found to be invalid and the backup schedule fails.

Solution : Enable the Keep Alive setting for the backup in the StoreGrid configuration file [< StoreGrid Path>\conf\SGConfiguration.conf] by following the instructions given below:

Stop StoreGrid

Edit < StoreGrid Path>\conf\SGConfiguration.conf

Set the <StoreGrid><Configuration><Module> tag, "KeepAliveEnabled" attribute's value as "1" and set the "KeepAliveTime" attribute value to desired value.

Save the configuration file and restart StoreGrid.

Limitations

1. If locally dumped Exchange Server backup data is deleted manually while backup is in progress, then StoreGrid will not have the information about the manually deleted file in client machine backup report and in server backup report.

2. Local Dump path configured for Exchange Server backup should not contain special characters like single quote('), double quote("), forward slash(/), backward slash(\), question(?), colon(:), asterisk(*), lesser than(<), greater than(>), pipe(|) and plus(+).

3. If Exchange Server backup schedule is suspended while local dump is in progress, then StoreGrid will suspend the transfer of files to the backup server (till after the local dump process is completed). On resuming the same backup schedule, the dump process will not occur in the next schedule; instead, the locally dumped files will be transferred to server and an error message will be reported in backup report.

4. Please ensure that the dump location configured for the backup schedule has enough space and has valid read and write permission to accommodate the exchange dump data. Also, the dump location (full path) should be less than 256 characters.

5. If the Storage Group or Database is configured as part of one schedule, then it cannot be included in other backup schedules. If Databases under same Storage Group are configured as separate schedules, then enabling Multi- threaded scheduling in StoreGrid is not recommended for Exchange Server backups.

6. A Storage Group configured for backup in a backup schedule cannot be configured in a second backup schedule. If required, the first schedule has to be deleted first and thereafter configured in the second backup schedule. 7. Everytime a new Database is added under a Storage Group of the Exchange Server, then before running a

differential or incremental backup, "Additional Full Backup" should be configured to run through the "Edit Exchange Server Backup" configuration.

8. When you try to restore an Exchange Database's full backup which was empty during its first full backup, then restore operation will fail. Hence you should ensure that Exchange Database is not empty when a full backup is scheduled.

9. Currently you can seed the local data to the remote server only. After performing the seed migration, you can continue this backup schedule only to the remote server, not to both remote server and local backup.

Exchange Server Cluster Backup