OK, so again, this is important to understand. First, not to be rude, but do you not have billing or any other import documents on your server.
When you back up a database, it is best, if possible, to back up the entire instance and not just the user databases. This then would look like this:
SERVER\AMAZINGCHARTS
Amazing Charts
Codes
Meds
Master
Model
MSDB
If you were going to back up just the user databases, then you could back up the six databases, but you would only need the AmazingCharts.mdf and if you want the .ldf file.
The problem is this: My guess is you did not purchase the Business Premier. As stated many times, you must have a backup solution that is able to back up databases. Even Business Premier ($599 a year) cannot do this by itself. It isn't compatible with VSS or it wouldn't be an issue. You will need a snapshot of SQL first and then back up the snapshow. There are back up programs which are capable of doing this such as BackupAssist or iBackup.
This is a direct quote from their website:
?Carbonite does not back up databases, however we can back up a snapshot of your database.
?Make a backup of your database with a separate tool and then use Carbonite to back up the separate backup file that was created.
How to Back Up Your SQL or Other Databases
With Carbonite, your backup should not include the files that make up your database program; this is because the various files that make up your databases are interconnected and as a result Carbonite cannot back them up and restore them in a readable format. To back up your database with Carbonite, you should first back up your database using a separate tool specifically designed for the program that you are using, and then use Carbonite for the backup file. Database programs usually come with an embedded tool for creating backups of your database that you can save on your local machine. If you are not sure how to make a backup file for your database, please contact the vendor for the program you are using.
Once your backup tool creates a backup file of the database on the hard drive, you can then use Carbonite to "back up the backup" to our servers for protection against computer disaster.
Note: When making the backup file for SQL, please remember to use the alternate .TRN file extension, as the .BAK file extension is excluded from our backup.
I found this site. I don't know if it is a good product.
http://sqlbackupandftp.comI admit this pertains to the entire instance. Not quite sure about backing up user databases only. You wouldn't want a user to be connected to the database during the automatic backup.
