Bandwidth throttling is not supported for the local backups (backup to another location in the same machine).
Retention policy feature is not supported for Microsoft SQL Server, Microsoft Exchange Server backups.
Windows system state backup is always run as a full backup. That is the full system state data, as opposed to only changed blocks, is always uplodaed during backups
Bandwidth throttling is applicable only for backup processes from clients to the backup server. Bandwidth throttling is not supported for restore and replication processes.
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.
If any special charatacter 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.
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.
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 trasfering a large file, the restore job, when it resumes, will restore that file again from the beginning.
In MSPEU usage history page, the MSPEU balance value for the Backup Server and the Customers may not be available after migrating StoreGrid from a older version. These details will be available only after the clients connect to the backup server.
After doing server side disaster recovery, the MSPEU usage history page will not contain all the MSPEU usage details.
StoreGrid sends Email alerts for low available disk space and license expiry once every 24 hours and not immediately when the alert condition occurs.
Discovery of StoreGrid clients/servers may not work properly if multicasting is disabled in the network.
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.
Encryption key for a backup cannot and should not be changed across backup schedules.
When the user configures multiple destination servers for backup, then during restore, the server which has the latest backup is not automatically detected.
All the users configured to log-in to StoreGrid have the same permissions. Fine grained access control is not supported.
StoreGrid does not support automatic directory and file monitoring in Mac OS X, FreeBSD 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 StoreGrid 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 and Linux machines.
The tree display in the StoreGrid Web Console will take a long time to load if a directory contains 1000s of files/directories under it.
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 StoreGrid uses is dependent on the processor architecture. This limitation is only applicable for Power PC Macs.
StoreGrid discovery takes between 2 to 5 minutes to detect when other StoreGrid peers become available or unavailable.
If a backup schedule is configured to two backup servers (StoreGrid 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.
Recovering from network interruption by re-establishing the connection works only for the connectivity between the client and the backup server, not for the connectivity between backup server and replication server.
Replication Server Migration of backup data from the backup server cannot be done for additional full backups along with incremental backup data. However, it can be done with just the additional full backup data.
Aborting a continuous backup from the server side will only make the client begin the next schedule, making the backup start again.
StoreGrid 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.
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.
Search and restoring individual mails is not supported, however restoring up to mailbox folders is supported using StoreGrid Advanced Exchange Mailbox plugin.
Home 
Print
