Author
|
Topic: Good Server Back-up Software
|
|
|
|
|
Serengeti
Sarge
Member # 51
Rate Member
|
posted 09-30-2006 12:23 AM
As a DBA, I'm going to suggest not attempting to backup the SQL Server database files directly. When it comes time to restore, you're likely to find the database is not in a consistent state and cannot be opened.What you'll want to do is to fire up the SQL Server enterprise manager and create a maintenance plan that includes a complete backup of the database to the filesystem on a daily basis. I'd also create a seperate maintenance plan for log backups once hourly at a minimum. If the DB isn't super busy (ie, you can spare the disk i/o), I'd run the tlog backup every 15 mins. See here for more info on SQL Server maintenance plan backups. Of course, if by SQL you meant MySQL, then you can execute a mysqldump command for a full backup, and then run hourly (or 15-minute-ly) mysqlbinlog log dumps, assuming you're running the db in binary logging mode. Good info on MySQL backups here. At any rate, the point is, don't just backup the database files and expect to be able to recover successfully. DBs are very sensitive to consistency, and will not open if they're not consistent when they're brought online.
Posts: 1045 | From: your grocer's freezer | Registered: Jun 1999 | IP: Logged
|
|
|
|