Submitted by Anonymous on Thu, 08/30/2007 - 20:39.
David: thanks for stopping by and thanks for the tip. However, one of the things that users should consider is that if they are relying on Carbonite to backup a file with these extensions, AND the file names themselves are dynamically created like scheduled SQL Server backup files, then this means the user must manually select the file each time one is created, which is not practical. With SQL Server backup files, a user can simply change the backup file extension, but that is not the case with other applications' backup files. Users of Carbonite should be aware that it is not always set and forget. Simply setting the directory to backup does not mean all the files will be sent to Carbonite servers.
I think it would be a good feature if the users could have just a little more control of what is excluded by default and what is not - make it an advanced feature - and that should solve it.
David: thanks for stopping by and thanks for the tip. However, one of the things that users should consider is that if they are relying on Carbonite to backup a file with these extensions, AND the file names themselves are dynamically created like scheduled SQL Server backup files, then this means the user must manually select the file each time one is created, which is not practical. With SQL Server backup files, a user can simply change the backup file extension, but that is not the case with other applications' backup files. Users of Carbonite should be aware that it is not always set and forget. Simply setting the directory to backup does not mean all the files will be sent to Carbonite servers.
I think it would be a good feature if the users could have just a little more control of what is excluded by default and what is not - make it an advanced feature - and that should solve it.