Limitations in

1. In advanced disk image plugin backup schedule, additional disk drives cannot be added or removed from the schedule, once configured.

2. Keep the advanced disk image plugin backup data to local location (along with to remote backup server) option is not supported.

3. Backing up dynamic disk drives using advanced disk image plugin is not supported.

4. Only NTFS formatted disk drives are supported by advanced disk image backup plugin.

5. Restore advanced disk image backup data to physical disk/drive is not supported in Linux OS.

6. Aborting/suspending the active export backup data process is not supported.

7. Export backup data feature is not supported in Amazon machine instances.

8. In clustered backup server environment, export backup data feature is supported only at client's 'node locked' backup server.

9. The backup schedules recovered from exported backup data cannot be edited or scheduled to continue the backup. The imported backups are for restore purposes only. After restoring the backup data, the imported backup schedules can be deleted.

10. Bandwidth throttling is not supported for the local backups (backup to another location in the same machine).

11. Bandwidth throttling is applicable only for backup processes from clients to the backup server and replication process from the backup server to the replication server. Bandwidth throttling is not supported for restore processes.

12. If an Exchange Mailbox name(user name) contains forward slash(/) or reverse slash(\), that mailbox might not be backed up. You will need to change the full name of that mailbox without the slash characters to get them backed up.

13. If any special character is present in any folder name (present under a user), that character will be replaced with other set of valid characters while creating the dump file.

14. The feature to resume a restore from where it left off is not supported for restoring backups to a different client other than the client from which backup was done.

15. The feature to resume a restore from where it left off is supported only at a file level and not at a block level. That is, if a restore failed/aborted while transferring a large file, the restore job, when it resumes, will restore that file again from the beginning.

16. In MCAL usage history page, the MCAL balance value for the Backup Server and the Groups may not be available after migrating from a older version. These details will be available only after the clients connect to the backup server.

17. After doing server side disaster recovery, the MCAL usage history page will not contain all the MCAL usage details.

18. sends Email alerts for low available disk space and shortage of MCALs once every 24 hours and not immediately when the alert condition occurs.

19. If the user forgets the encryption key/password, then there is no way to restore the data. The data cannot be decrypted and hence the backup is as good as lost.

20. Encryption key for a backup cannot and should not be changed across backup schedules.

21. does not support automatic directory and file monitoring in Mac OS X, FreeBSD, Solaris and Linux machines. So, when a continuous backup is configured, the backup will check for modified files continuously by listing all the files and checking with backup meta data. This process will affect the performance of other applications. Hence configuring a continuous backup is not recommended in Mac OS X, FreeBSD, Solaris and Linux OS machines.

22. The tree display in the Web Console will take a long time to load if a directory contains 1000s of files/directories under it.

23. 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 uses is dependent on the processor architecture. This limitation is only applicable for Power PC Macs.

24. If a backup schedule is configured to two backup servers ( peers), then the backup data in both the servers need not be the same. As the backup is done to the servers one by one, the data, files etc. can differ between the backups.

25. Aborting a continuous backup from the server side will only make the client begin the next schedule, making the backup start again.

26. When a client's backup fails due to insufficient MCALs in the backup server, reports or events are not shown for the error in the backup server.

27. does not allow restoring the selected mailbox to an alternate Exchange Server. If needed, .PST files can be restored to alternate Exchange Server manually after restoring the files to local disk from backup server.

28. While restoring the complete contents of the selected folder to the original mailbox folder, the existing folder contents will not be deleted prior to performing the restore and restore process will append all emails to the folders. It may result in duplicate email items within the original folder.

29. Search and restoring individual mails is not supported, however restoring up to mailbox folders is supported using Exchange Mailbox plugin.

30. When sharding is enabled, before shipping data from backup server to another backup server, you need to manually export the meta-data. After exporting, data can be shipped to destination backup/replication server. To export meta-data, execute the following commands from <_HOME> directory,
    
    bin\StoreGrid.exe ExportToSQLiteDatabase
    
    bin\StoreGrid.exe ExportToSQLiteDatabase <Client_Name>
    
    bin\StoreGrid.exe ExportToSQLiteDatabase <Client_Name> <Backup_Name>
    
    These steps need to performed before migrating data to replication server.

31. In 'Add backup schedule' page, files/folders with Unicode name will not be listed.

32. Advanced filter option will not work for Unicode name files/folders and the normal files inside folders with Unicode names.

33. Include/exclude file/folders with search pattern for restore/delete will not work for Unicode files/folders.

34. Delete notification will not be processed for Unicode files/folders and also for the normal files/folders inside the Unicode folders.

35. Storage Location configured in Server Settings or Group should be available & accessible in all cluster nodes. If not, the backups might fail when client chose to backup to the specific cluster node where the Storage Location is inaccessible.

36. For basic disk image plugin backup and system state backups in Windows Vista & above operating systems, uses Windows operating system's built-in "wbadmin" utility. Hence, all the following limitations of "wbadmin" utility is applicable to basic disk image plugin & system state backup in Windows Vista & above operating systems.
    

    • The FAT32 file system drives will not be listed in the drives list.
    • You cannot dump Disk Image data to Critical volume (system drive).
    • You cannot dump Disk Image data to the drive where is installed.
    • You cannot configure the dump location as a network shared folder or mapped drive or a tape drive.
    • If the given dump location is CD/DVD, confirm that there is a media which is writable during backup.
    • VSS services should be enabled for image backups.

37. For WSS2.0/SPS2003, only the sites added from 'SharePoint Settings' page will be listed in 'Add SharePoint Site Backup' page.

38. Though the whole SharePoint Server or a whole portal site is selected for backup, only a site-collection level of backup will be done. Hence, to restore all the site-collections under a portal site, you need to restore the site-collections under that portal site one by one using STSADM.EXE.

39. A site-collection whose total size exceeds 15 GB cannot be backed up as this is being a limitation with STSADM.EXE [which uses] itself. However, in such cases, you can use 's SQL Server backup feature for backing up the SQL databases being used by the SharePoint Server.

40. should be run with Administrator privileges to list and backup SharePoint sites as STSADM.EXE can be run only with Administrator permissions.

41. If the dump path of the SharePoint backup exceeds 255 characters, dump process will fail. Hence, make sure, you have entered a shorter dump path to enable the dump to complete successfully.

42. If clustering is enabled in the backup server, then you will not be able to migrate a client if it is (or the client's parent Group) node locked to one cluster node and the group to which the client is to be migrated is node locked to a different cluster node.

43. If you have configured Clustered Exchange Server backups, then Exchange Server name cannot be edited from the Exchange Server configuration page. If you would like to backup a different Exchange Server, then you need to delete the Exchange Server backups that have already been created.

44. In cluster enabled replication server, restored data/compressed restored data file is available only in the cluster not it is backing up. i.e., if the client is backing up to backup_node2, then the client's restored data will be available only in the backup_node2 system. But the restore report will be available in all the backup server cluster nodes.