Hi,
The last five days, the SQL Server Production backups to tape have been incredibly slow. Actually, they don't complete because they have been going on for 60 hours. Everything on the servers (clustered production environment) seems fine. Nothing untoward unusual. Any ideas what could be causing it? We're thinking of rebooting tonight.
Any help would be appreciated.
Maria
Can anyone help. This is the only failure that is occuring in the backup.
Can anyone shed any light
Thanks
An error occurred on a query to filegroup master..PRIMARY.
^ ^ ^ ^ ^
SQL Server returned the following error message:
You can only perform a full backup of the master database. Use BACKUP DATABASE to back up the entire master database.
^ ^ ^ ^ ^
Unable to open the item master?PRIMARY - skipped.
I have Veritas Backup Exec. The software does a good job with the backup. However a few of my SQL 7 Databases the files are skipped even though I have told the software to lock the file. Specificaly this happens on my EPICOR Accounting Databases. Is there a command I can issue to stop the SQL server from running prior to the backup and then re-start after the backup has completed. Any help would be appreciated. Thanks
View 1 Replies View RelatedHI All,
Bit confuse and please help to setup correct way of backup.
I got SQL Server 2000 and Veritas Backupexec 10.0
So what is your recommended way to backup SQL Servers.
1. Veritas Backup agent with Differtial (Mon-Thu) and full backup on Friday?
Set SQL recovery Model to FULL and only backup Transaction (.TRN) logs to server disk , No backup (.bak) from MP ?
or
2. Create SQL MP and backup to SQL Server DB & Logs to disk every night- full backup
Keep only 1 day worth of backup. ( not enough space)
Use veritas to backup .bak file only not using that veritas SQL Backup?
Or knowledge me with the proper method?
hi ,
pls define a veritas backup,tel be briefly pls help
Can anyone tell me how to RESTORE a Table, not an entire Database, to the live server.
Please Help
Anyone have experience using Veritas to backup SQL Server databases?
I just started with a client who's SQL Server froze with the CPU pegged at 99% on my first day. I think it might be related to using Veritas SQL Server component to run hot backups of the database, while the SQL Server Agent was running simultaneous independent backups. All this on a live database of course, while a user was completing a large transaction.
I advised them to disable the Veritas SQL Server backup component and let SQL Server back up its own databases. Then use Veritas just to archive SQL Server's backup files.
I think I saw a similiar issue at a previous client site that was using Veritas. Please let me know if you have prior experience in this area, and your evaluation of the quality of Veritas database backup component.
Thanks!
I run an Operating system backup nightly using Veritas Backup exec (v8), immediatly after I run a SQL written backup job.
1. Can I use the same tape? Appending to the media that Veritas has written to?
2. How do I run the backup from cmd line from within Veritas? It has an option to "execute after backup job:"
- How do I run a SQL job from operating system?
Thanks,
AJ
I've installed SQL Server 7.0 SP2 and Backup Exec 7.3.
When i try to start backup exec a dr. Watson error appears.
Backup exec doesn't start. The same effect with version 8.0 and 8.5 from Veritas Backup Exec. When i try to install MDAC 2.5 after installing Backup exec, error 90332 (?) appears. Backup exec "hangs".
When i've installed Backup exec 7.0 or 7.2 there are no problems.
(also with SQL Agent)
Does somebody know to reolve this?
Thanks! !
Is it safe to backup while the database is running 1000 transaction/sec.? If yes - why should I buy Veritas Backup Exec Server Edition and Veritas Backup Exec Online Backup Pack ?
Michael
Hi,
Does any one have an idea why the backup to disk it takes 6 Hrs and to Tape it take 1 Hr.? Also what will be the diference
bettewn creating the a backup device and just creating the file on the fly when I setup the backup?
Thanks Felix.
Hi Team,
I have a SQL 2000 instance with 46 Databases (all databases put together will be 15 GB in size). I am running a SQL Backup using a third party software.
My full backup of the SQL instance which backs up 15 GB of data finishes within 30-45 minutes. But, my differential backup of the same instance which backs up only 150 -250 MB of data takes 12 hours to backup.
I found a knowledge article from MS Support site which says, differntial backup would take more time than full in few scenarios.
http://support.microsoft.com/default.aspx?scid=kb;en-us;196658
But the above document is for SQL 7.0. Will it be the same for SQL 2000 and 2005 too? If yes, can you please tell if I can increase the speed of differential backup in my environment. Should I modify any SQL Parameters?
Please let me know your thoughts on this..
Thanks
Santhosh
2 Boxes in HA, identical hardware (VMs) and both utilising identical storage systems (Nimble SANs).Was needing to do a copy only backup of a few databases for an escrow environment we have, so decided to perform this on the secondary box.Small ~10GB ish database first, seemed to be really slow, so opened resource monitor and noticed that disk read / write was getting limited to about 15MB/s so took a little while (the big one is over 1TB)
Tried this again on the primary it was done in seconds disk rate in the order of 250MB/s (same settings re compression etc).. I decided to make a copy of the backup file on the secondary, the copy disk to disk went in the region of 150MB/s , so it appears that SQL Server is the bottleneck?
Hello,
We use Veritas BE with SQL agent to backup all the company's databases. Has anyone used Veritas for SQL backups and restores, adn what are the pros/cons verses some scripting.
I've been in a few recovery situations with veritas although limited it's easy for a network analyst to restore, but I prefer scripts to restore. Our SQL shop is young and still in alot of it's development phase. I'd like to break the trend we have now and write some decent batch/sql scipts for backups?
Right now veritas backs up all our NT boxes, hence why we use it for SQL. I have scripts, but haven't implimented. Should we switch to scripts or stay with Veritas?
thanks,
AJ
Hi ,
I greatly appreciate if anybody can tell me where can i get information regarding SQL Server 7.0 using Veritas media management tool for backup and restore.
thanks in advance
Mohan
Has anyone had any problems with the Veritas Netbackup for Microsoft SQL Server?
Suggestions?
Thanks,
Kavitha
Could someone please explain the pros/cons of installing the VeritasSQL agent versus backing up the .bak file generated by SQL Server? Ihave worked with both setups in the past, but never really understoodwhat made one better than another.TIA,Brad
View 2 Replies View RelatedHello,
I really hope someone can help...
I am having great difficulty backing up my SQL database through Veritas/symantec backup exec here is the error being reported in log:
Backup- servername V-79-57344-33938 -
An error occurred on a query to database "databasename".
my sql database is setup for both windows and sql authentication...
What settings does a database need for Backup exec to be able to query it?
any help much appreciated
While ago my SBS 2003 which had SQL 2000 crashed so I had to rebuild everything and this time I used SBS 2003 R2. My SQL 2000 databases were backed up under Veritas 10 and now I'm trying to restore them under SQL 2005. Is this possible?
Please advice.
Thanks,
Mike
While ago my SBS 2003 which had SQL 2000 crashed so I had to rebuild everything and this time I used SBS 2003 R2. My SQL 2000 databases were backed up under Veritas 10 and now I'm trying to restore them under SQL 2005. Is this possible?
Please advice.
Thanks,
Mike
Michael writes "We are running SQL and Veritas to backup the databases. Supposedly the SQL agent in Veritas, after a full backup, truncates the log files but for some reason this isn't happening... any ideas?"
View 4 Replies View RelatedWe are running SQL 2000 sp4, only one user database (SAP) the database is 63 GB.
The ldf files were trashed so I went to tape to restore.
We are using veritas backup exec 9.1 sp4. Veritas is on the same server. I can restore the master db and the msdb fine. However when we attempt to restore the DEV db it runs for 2 hours and then fails with a communication error from veritas.
When we restore the master the DEV db comes up suspect as there are no files for it to attach to) so we cannot attach to it to restore, so I have deleted it and attempted to restore - same communication error. I have recreated a db named DEV with the mdf etc created to the size needed plus some to be sure, no good same behavior (behavior described below).
The job starts and it creates all the folders for the database (there are 1 MDF, 5 NDF, and 4 LDF files each in its own folder). Then it begins to create teh individual files it gets ~half way through at about an hour-hour and fifteen. During this time there are a large number of writes being performed by SQL (I assume it is creating the structures). Then it switches over to reading from tape a large number of read by beengine for another 45-1.5 hours then the job fails with the error unable to communicate with the device. I ahve noticed that once it starts reading from tape the db is gone from enterprise manager, and the mdf etc. files that were being created are now gone.
Help this has gone on for three days!!!
Hi there
I'm getting this message on my third automated backup of the transaction logs of the day. Both databases are in full recovery mode, both successfully backed up at 01.00. The transaction logs backed up perfectly happily at 01:30 and 05:30, but failed at 09:30.
The only difference between 05:30 and 09:30's backups is that the log files were shrunk at 08:15 (the databases in question are the ones that sit under ILM2007, and keeping the log files small keeps the system running better).
Is it possible that shrinking the log files causes the database to think that there hasn't been a full database backup?
Thanks
Jane
On the SQL Server the Event Viewer shows the same messages and errors every evening between 22:05:00 and 22:08:00. The following information messages are shown for every database:
"I/O is frozen on database <database name>. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup."
"I/O was resumed on database <database name>. No user action is required."
"Database backed up. Database: <database name>, creation date(time): 2003/04/08(09:13:36), pages dumped: 306, first LSN: 44:148:37, last LSN: 44:165:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{A79410F7-4AC5-47CE-9E9B-F91660F1072B}4'}). This is an informational message only. No user action is required."
After the 3 messages the following error message is shown for every database:
"BACKUP failed to complete the command BACKUP LOG <database name>. Check the backup application log for detailed messages."
I have added a Maintenance Plan but these jobs run after 02:00:00 at night.
Where can I find the command or setup which will backup all databases and log files at 22:00:00 in the evening?
SQL Server 2008 r2 - 6 GB memory...I attempted a backup on a 500GB database but it was taking way too long. I checked the resources on the box and saw the CPU at 100%. I checked the SQL Server activity log and saw a hung query (user was not even logged on) that had multiple threads so I killed it and now the CPU utilization is back to normal.
Trouble is, now all of the threads in the activity monitor for the backup show 'suspended' and the backup appears to be not doing anything.
Hi,
I use the Transact-SQL BACKUP statement in Visual Basic to backup my local MSSQL Database. It give me this error
Error 3041
BACKUP failed to complete the command BACKUP DATABASE [BCFPC] to BCFPCBKP
I already created a backup device called BCFPCBKP and it is backup to the disk.
I tried to run the same BACKUP statement in SQL Query Analyzer and it worked fine. I tried to run my VB application in another PC. It worked fine when i use this command remotely. Can anyone tell me what's the problem?
Thanks in advance
regards,
M.Y. Yap
Using Ola Hallengren's scripts I do a full backup of a database on a Sunday. Then differential backups every 6 hours and log backups every hour. I would like to keep a full week of backups based off the full backup done on Sunday. Is there a way for me to clear out the diff and log folders after the successful full backup on Sunday nights?
View 2 Replies View RelatedNeed to restore database,here's the scenario:
Data got deleted on Friday evening, need to have database restored to FRiday afternoon and also some data has been entered on Monday, which needs to be there.
Windows 2003 backup utility uses the shadow copy option that allows it to copy open files.
Therefore, can I use this utility to backup the .mdf and .ldf files for my SQL 2000 database?
I can then attach the .mdf files if I need to restore the database to another server.
Can anyone tell me if this is safe? I've tried it and it worked but I'm worried there maybe some lurking danger in using this approach.
We take a full backup in the early morning and hourly transaction log back during the working hours for one database in the production server. The application team made certain changes to the design of the said database in their development server. The backup from the development server was restored to the production server during working hours. After the restoration should we take a full backup before next transactional logbackup? Would the transactional log backup with out a full backup after the restoration of a database be valid?
View 5 Replies View RelatedI've written a custom script to delete backup files from location. But unable to modify now to count the number of files are deleted. How to modify the script...
/* Script to delete older than N days backup from a specific directory */
USE [db_admin]
GO
IF OBJECT_ID('usp_DeleteBackup', 'P') IS NOT NULL
DROP PROC usp_DeleteBackup
GO
[Code] .....
Using SQL Server 2005 Server Management Studio, I attempted to back up a database, and received this error:
Backup failed: System.Data.SqlClient.SqlError: Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized. Reissue the satement after the current backup or file manipulation is completed (Microsoft.SqlServer.Smo)
Program location:
at Microsoft.SqlServer.Management.Smo.Backup.SqlBackup(Server srv)
at Microsoft.SqlServer.Management.SqlManagerUI.BackupPropOptions.OnRunNow(Object sender)
Backup Options were set to:
Back up to the existing media set
Overwrite all existing backup sets
I am fairly new to SQL 2005. Can someone help me get past this issue? What other information do I need to provide?
I'm looking to schedule a maintenance plan for my databases which I have done.I'd like this database to be copied to another folder and the name altered to include the file name and the current date time stamp.Is this possible in the scheduled maintenance plan?
View 4 Replies View Related