BackupExec & SQL Problem
Feb 26, 2002
We've been using BackupExec for a while to back up our SQL 2000 databases, but we've suddenly encountered a problem while trying to back up some of them. It seems that it won't back up databases that have a recovery model of "simple". Our Network Admin can't find anything in BackupExec that references Recovery Model, and we haven't changed the recovery model on the databases since they were created .....
Here's the error from the event log ... any ideas ?
An error occurred while executing the following query: "BACKUP DATABASE [TI] FILEGROUP='PRIMARY' TO virtual_device = 'BackupExecSqlAgent_PRIMARY_00'".
On server: "SQLDB-01".
SQL error number: "1070".
SQL error message: "The statement BACKUP DATABASE...FILE=<name> is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
".
View 2 Replies
Jul 3, 2001
I've recently set up Backup Exec on our SQL Server to backup our databases to DLT tape everynight. However when backing up the mdf and log files these are skipped because its says they are in use. However if you look in the Current Activity they are not in use. Plse could someone help/advise.
View 1 Replies
View Related
Jul 24, 2001
I'm reviewing our Backup Stategy. Can anyone advise me what advantage there is to using Backup Exec instead if just backing up the database and transaction logs straight to a DLT tape. Thanking you in advance.
View 1 Replies
View Related
Oct 24, 2007
Hi
I currently have Backup Exec 11 w/ SQL Agent backing up my databases on a daily full, and 4 hour incremental basis. I want to configure log shipping as an additional level fault tolerance for my data. I have a few test databases setup with the log shipping and they are working correctly. But my question is related to Backup Exec.
Now that I have logs going to a second SQL server how will Backup Exec play with the primary server logs? Do I need to configure Backup Exec in a certain way, say do not truncate logs, etc? Or can I just keep the backups going as I have them and log shipping will just work at the same time.
TIA
Michael HamSeattle, WA
View 1 Replies
View Related
Jun 21, 1999
We currently use CA ArcServe (ArcServe 6.5 Enterprise and Single Server Editions) to backup our Windows NT files and MS-SQL Server databases. We have experienced significant reliability issues with ArcServe. Many times we have found ourselves rebuilding a corrupt ArcServe Job (ArcServe’s backup schedule) database. One of our NT server occasionally NT bug checks when ArcServe is performing backups. Occasionally ArcServe Jobs incorrectly reschedule themselves. Sometimes the Jobs do not complete but stay executing, not performing any work, and to cancel them may require a lot of effort. The ArcServe job DB repair utility generally does not work. The user interface is lacking. For example, the job scheduling options are very limited. CA tech support for this product has been poor. Because we have issues with ArcServe stability we are now evaluating Veritas (formally Seagate) Backup Exec for NT. What are other people’s experiences with these 2 products?
View 1 Replies
View Related
May 31, 2000
I'm going back and forth on an issue and was looking for some outside observations. I have over a dozen SQL NT servers, both 6.5 and 7.0. On some servers I'm dumping the databases and backing up the dumps with Veritas BackupExec, on 4 (two SQL 6.5, two v7) I'm backing up with the Veritas SQL Backup Agent.
Obviously, if you don't have room to dump a database, you must use the backup agent. That is the case on one of my servers and becoming so on a second. But my personal preference is to do the dump/backup.
(as a side note, one server is not backing up correctly with the backup agent but ultimately that box will require it due to DB growth, so it is something that I have to resolve)
I like the dump system for a few reasons. I find it easier to load from a dump, particularly a single table. Likewise, I find it easier to copy a database by loading from a dump rather than going from a backup, but that's mainly because of BackupExec being a little bit strange on redirecting restores.
Here's my clincher. I find restores via the backup agent to be ridiculously slow. Let's say I have a 5gig DB that has 1.5gig in it. The dump size will probably be somewhere below 2gig. The restore via backup agent carefully writes the entire 5gig even though 3.5g of that is empty. This takes a lot of time. Add to that the "post-restore DBCC". I had such a restore take something on the order of 13 HOURS which, needless to say, conflicted with my nightly DBCC's and backups.
OK. End of rant. Any suggestions or thoughts on the subject?
View 1 Replies
View Related
