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 RepliesHi,
I am cleaning database backup history as "Delete history if 4 months old" for backup file, and "Delete history if 1 week old" for Log file back.
lets say, I have disaster after 3 months, and I recover database with data and log backup files. Will I be able to recover with 3 month old backup file with just 1 week Log file backup. As I am keeing my Log backups only for 1 week.
Thanks,
Hello -
How can I truncate log files of all Databases daily automatically.
Thanks
I proposed on a new server that we separate Data Files, Log Files, tempDB, Backups, etc. onto separate LUNS on a SAN with High Speed Solid State Drives.I was told that with the new technology with solid state SAN's that it would decrease performance and that it did not work the same way as it did when you had RAID 5's etc.I thought that if things were cared out correctly by a SAN Administrator they would know how to configure for optimal performance.
View 2 Replies View RelatedAnyone 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!
Hello,
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
We 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!!!
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
Hello Group,
I have a SQL Server 2000 database that has never been backed up. The SQL Server database can't be logged into due to an SSL Security Error, thus I can't get to the backup utilities within Enterprise Manager.
What data files do I need to backup manually and what steps do I have to take to backup these files to a tape and rebuild the server?
Thanks
Kevin Kraus
i have a maintenance plan running on my database, in which I told the wizard, on creation, to "remove files older than 4 week" and yet it doesn't seem to be doing so, as on checking this morning, diskspace was getting low, due to over 300gb of backups and trn' dating back to september.
Anyone have ny problems with maintenance plans not cleaning up when told?
a
My scenario -
-Dev server lost all its raid drives (which included user data/log files and ALL backups)
-Raid drives were removed from server, so we could try and recover the data (not sure why they had to remove them)
-Recreating the user db's isn't an issue, but I REALLY need to retrieve the jobs from the MSDB (developer was working on dts package for the last 2 months, but didn't check it in to VSS)
-Since the System DB's (model, master, msdb) were installed on the C drive, I was able to recover their mdf/ldf files.
So we build an new server and recreated the user db's.
How do I go about getting the jobs data from the msdb database?
I've tried the following -
Started SQL server with the -T3608 and was able to detach the MSDB database, but when I go to reattach using the mdf/ldf files from the other server I get the following error message.
Error 5172: The header for the file 'C:mssqldatamsdbdata.mdf' is not a valid database file header. The PageAudit property is incorrect
I've been doing some research and found a lot of great articles on how to RESTORE (from backup - dont have) or Rebuild (wipes out the data I'm looking for) the MSDB, but not how to replace it with only the ldf/mdf files....
Any idea's would be greatly appreciated.
Thanks
PS - All backups are now being copied to another server (lesson learned)
Hey guys,
I'm wondering how most people manage very very large backups. What is the best approach to breaking up the backup files if you're restricted to a drive size (450gig in my case). I unix, you can pipe the backup to gzip and split, I'm not sure how the same thing could be accomplished in windows.
Thanks,
-Kilka
We have a SQL 2K5 10GB database that, as part of the recovery plan, gets a differential backup every six hours. Log file backups occur every hour, and a full backup is done every 24 hours. Over the weekend, the differential backup produced a 55GB backup file which caused us a lot of issues besides disk space usage (log backups couldnt finish, mirroring broke, etc.). This is also the max growth size that the log file is set to. There are no errors in the ERRORLOG, or in the job history. It's as if the backup was successful, which I assume it was, but the file was sparse.
I should mention that our full backup is typically 10GB, log file backups are typically 100 to 500MB, and the diff backup is generally 1GB to 3GB.
Has anyone experienced this issue before?
What causes it?
How do we resolve it?
Thank you in advance for your help,
Greg
where in sql server 2005 ( and 2000 for that matter) do i find the path to the location where backups are placed (.bak files)? is there sql i can use to find this out
View 6 Replies View RelatedThere is a table need truncate and then insert a huge data (more than million rows) every day. Does database grow up every day?
View 2 Replies View RelatedUntil yesterday I had a server running SQL Server 2008 R2 - with all the SQL Server DB files on an attached disk array.
The server died - so I attached the disk array to a new server - and all the DB data files are visible there.
I installed SQL Server 2014 on the new server and am trying to work out how to point it at the existing database files.
I also have backups of the DB's - but they will take ages to copy over and restore - so it would be much easier to just use the db files. Should I restore the master db first (easy as its small)?
Hi,
Does anybody have a script for truncating all the tables in an database??????
I have an user request asking me to restore an database into a new database,and to truncate all the data,leaving the structure and objects intact.I tried using DTS,etc,etc,but i'm running into Foriegn key problems/login problems,etc.Any new ideas???
I have a production database which uses merge and snapshot replication. The Merge is for 3 tables. The snapshot is to update the rest of the data once daily. I use a Full recovery model and perform database backups (full, differential) and transaction log backups.
I have a database optimization plan which runs 4 times a week. This plan performs and integrity check and rebuilds the indexes. This optimization plan is growing the transaction log by about 8MB each time it is run and we are running out of space on the drive for our log files. The space is not being reused.
I saw in another post where Gail Shaw suggesting using SELECT name, log_reuse_wait_desc FROM master.sys.databases to see why the log space is not being reused. On the database in question, the above returns "REPLICATION".
A colleague tried to backup the transaction log a couple of times to truncate the log this weekend. She was going to perform a DBCC Shrinkfile command afterwards. But the truncate failed. Again looking into things it seems replication prevented the truncation.
We are looking at stopping the merge replication or even removing it to truncate the log file and then recreate the merge replication. How to handle shrinking the log file for now and then seeing if there are any checks or changes I can perform which will allow the transaction log space to be reused.
The space allocated to the Log in question is 180 GB. During this time period I was running TLog backups every 5 minutes, yet the log continued to chew through to 80 GB used, even after the process was complete and a final TLog backup had been taken. It continued to stay very large until the Full backup was complete -- or something else that I'm unaware of completed. Like every other DBA I typically take a TLog backup to shrink the log, but what appeared to be the case here was the Full completed and it released the used log space. All said, will Transaction Log backups not free up the log during Full backups?
View 3 Replies View RelatedWhy is my database backup file so big? It's about 10 X bigger than the actual data files
View 1 Replies View RelatedI know that I have read not to backup a database over a netwrok. So I am curious as to what others are doing out there. BAckup to your local hard drive on the server and then move the backup files to a repository some where on the network? Do others have a file structure out on another server that stores all of the backups from all of the different servers that have SQL 7.0 on them? We are a small company and are just starting to migrate data to SQL Server 7.0.
View 1 Replies View RelatedI have to perform a backup for disaster recovery purposes before an application upgrade. The upgrade will alter the database and stored procedures. My cuurent backup takes a backup of master and msdb weekly. The user database uses the Full Recovery model and is backed up daily at 21:00 and the logs daily at 13:00. Assuming the databse is modified between the last backup and the upgrade starting at 9:00am what should my backup stratergy be for roll back purposes.
1) backup master, msdb and the user Database to a different location than the normal backups. Use these to restore if required
2) backup the master, msdb and user databases using the same jobs and therefore overwriting the original evening backups
3) do nothing and just restore master and msdb from a backup and replay the logs to a given point in time for thr user database should the upgrade fail
Any help or suggestions will be much appreciated.
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
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?
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 Related
hi ,
pls define a veritas backup,tel be briefly pls help
Hello,
Can anyone tell me what the impact of dynamic database backups in sql 6.06.5
will have on users using the database?
Will their user processes be blocked?
Will their queries run slower than normal (how slower)?
Will there be a lot of locking activity as the SQl tries to backup?
Will the serverdatabase run slower
Anything else I may be missing?
Regards,
Hitesh
I am looking for the best method to backup SQL Server databases. Currently we are
running a dump database statement to disk and backing up the files to tape through Arcserve.
One problem that I am having is the statement to dump the database. I would like to retain
the dump for at least three days and be able to restore the database from any one of those
three days. My current statement is:
"DUMP DATABASE CHOISDAT TO DISK=`D:BACKUPCHOIS.BAK` WITH
NOUNLOAD , STATS = 10, INIT , RETAINDAYS = 3, NOSKIP"
but, every other day I receive the message from SQL executive:
"Can`t open dump device `D:BACKUPCHOIS.BAK`, device error or device off line.
Please consult the SQL Server error log for more details. (Message 3201)"
What am I doing wrong? Any suggestions?
P.S.
Is there anyway to tell the Maintenance Wizard to delete the backups. I tried using the wizard but
the backup files still remain on the disk and I have to delete them every week.
Hi All
I have a database which is 72GB, which is backed up every night as part of the maintenance plan. I have plenty of storage space, and the server that runs the database is fairly powerful (quad-processor 3.2ghz, 64bit, 48GB RAM) and is part of an active-passive cluster. The database backup is also copied to a SAN location.
My issue is with the size of the backup file. As part of the Disaster Recovery plan, I need to copy this database backup file accross the network to a remote site, so that in the event of a disaster at the site, business can continue at the remote site after restoring the database backup file. However, my database backup file is so big that I cannot copy it accross the network in time for the next morning. I have tried using WinRar and have managed to achieve a file about 20% of its original size, but it takes 2 hours to produce this file.
Is there any recommended reeading for this type of issue? Log shipping / mirroring has been investigated and will be part of the DR model but the 'powers that be' insist on having a full copy performed to the remote site.
Any suggestions? Thanks in advance guys n gals :-)