June 28, 2003 at 6:51 am
I have followed many of the ideas from previous posts, mainly doing a full backup daily to another directory and then backing that up to tape.
Quick Question - When I do the tape backup I get only three errors listed below in my backup log file. I just want to know if these would stop me from being able to do a restore. Thanks - TG
***************************
JAESDATA\D:\MYSQL\data
ib_logfile0 : Bkp : 209 - Object is busy
ibdata1 : Bkp : 209 - Object is busy
jaesdata.err : Bkp : 209 - Object is busy
Background...
**************************
I recently converted from Access to SQL Server. Well the frontend is still Access but the tables are SQL Server with ODBC.
So I have to make sure the tables are backed up. They are not very big but they are important.
I created a Maintenance Plan which runs a complete backup of database and transaction files at 10:00 PM and creates files in a separate directory on the local drive.
This directory is then backed up on tape with normal backup at 11:00 PM. I don't have a backup program which can directly backup SQL server
Any suggestions would be great.
TIA-TOMG
June 28, 2003 at 4:55 pm
Probably need to consult with the tape drive manufacturer. Most of us prefer to backup to disk and from there to tape, that way if the tape backup fails, you at least have one day or so on disk.
Andy
June 29, 2003 at 11:44 pm
Those busy objects are MYSQL components (data, log and error files).
Looks like you're trying to back up MYSQL database files whilst the Mysql service is still running.
Cheers,
- Mark
June 30, 2003 at 6:43 am
DUH - I should have noticed that the files were D:\MYSQL not D:\MSSQL. Yes I was playing with MYSQL before I decide to try MS-SQL
Thanks for the tipoff
July 1, 2003 at 7:39 am
How are you doing the backups?
To backup MS SQL you must do one of three things:
1. use the 'native' BACKUP DATABASE commands.
2. detach the database and backup the .mdf and .ldf files.
3. use a third-party backup program that allows you to backup SQL while it's in use (OPEN). Usually this requires an SQL Agent. (for example, Veritas' Backup Exec has SQL Agent option that is required to properly backup MS SQL.)
This might be the same for MYSQL, but I've never used it so I can't be sure.
-SQLBill
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply