Known Issues in GigaVaultStorage 2.4

1. For system state backup in Windows 2008 OS, the critical volume (where the OS is installed & the GigaVaultStorage installation drive) and a mapped drive should not be used as the local dump location

2. In the 'Backup Location Details' feature in 'Server Admin > Server Management > Server Settings' page, if the client's backup location was configured with different cases [example, E:\backupdata\, E:\BackupData\], then they will be shown as separate entries in the list of backup locations.

3. While restoring the deleted MS SQL Server database(s) using Advanced Plugin, the same cannot be restored directly to the MS SQL Server using GigaVaultStorage's complete restore feature. You should first restore the deleted database(s) locally in the client machine using GigaVaultStorage. And then you should use GigaVaultStorage's 'Plugin local restore' feature to restore the deleted MS SQL Server database(s).

4. When a backup schedule is configured with very low bandwidth throttling rate and the actual theoritical transfer rate of the network is very high, then the backup progress would appear to be frozen periodically as if the backup is not happening. But the backup would be running without any issue.

5. Changing replication server's backup storage location will be applicable only for the new customers replicating to that replication server. The existing customers & their clients would still replicate to the old backup storage location. Also, the feature to edit a customer's backup location in the replication server is not yet supported. If you wish to change the customer's backup storage location in the replication server contact our technical support team.

6. Sometimes while doing restore, the skipped files from backups are also listed for restore. The restore reports may therefore show that the restore was partially completed as it could not find the skipped files in the backup server.

7. Skipped folders may sometimes be listed in the skipped file list in the backup reports.

8. Replication progress window may not sometimes show the exact count of the total number of files to be replicated.

9. When Directory Monitoring is enabled, sometimes the Directory Monitoring service may give the short names of the files/folders backed up, in which case GigaVaultStorage will assume them to be new files/folders and will backup them a fresh.

10. Automatically discovering peers may not work properly sometimes in Mac OS X.

11. GigaVaultStorage will report error when trying to edit backups in Linux client machines where file/folder having " (double quotes) in their names are selected for backup.

12. GigaVaultStorage may consume extra MSPEUs when a client machine switches plug-in from basic to advanced, back to basic plug-in and then again from basic to advanced plug-in during the same month.

13. Delete notification may not be sent from the backup server to the replication server when a customer to which a client was migrated to (from another customer), is deleted in the backup server.

14. Cross platform restore is not possible for encrypted Mac OS X backups. But cross-platform encrypted backups are possible. The reason is that the encryption algorithm GigaVaultStorage uses is dependent on the processor architecture. This limitation is only applicable for Power PC Macs.

15. Events mechanism may not report all the important error conditions. Duplicate events may be generated for the same problem.

16. Default backup space allocated by GigaVaultStorage can be greater than the free space available in the partition of the backup location because GigaVaultStorage uses the total free space in all the partitions while computing the default backup space.

17. In SQL Server database backup schedule, multiple databases can be configured for backup. But during restore, only a single database can be restored at a time.

18. In MySQL backups, databases listed in the "Backup->Create MySQL Database Backup" page (For Windows) will be for the the last saved MySQL Server instance port in the MySQL Settings.

19. Local temporary dump location configured for a plugin(MySQL Server/System State) backup schedule cannot be changed to another location for the same backup schedule.

20. If a plugin(SQL Server/Exchange Server/MySQL Server) backup schedule is suspended while local dump is in progress, then GigaVaultStorage will not be able to suspend the creation of local backup dump. GigaVaultStorage, after finishing the local dump process will only suspend the transfer of files to the backup server. On resuming the same backup schedule, a new dump process will not occur, instead, the previously dumped files will be transferred to the server and an error message will be reported in the backup report.

21. The same Exchange Server Storage Group configured for backup using the Basic Exchange Server plugin cannot be configured with the Advanced Exchange Server Plugin. If required, the schedule has to be deleted and thereafter a new schedule has to be configured using the Advanced Exchange Server Plugin.

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