Could someone please explain the pros/cons of installing the Veritas
SQL agent versus backing up the .bak file generated by SQL Server? I
have worked with both setups in the past, but never really understood
what made one better than another.
TIA,
Brad
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?
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!
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
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
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! !
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!!!
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
when I run a package from a command window using dtexec, the job immediately says success.
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 3:37:41 PM
Finished: 3:37:43 PM
Elapsed: 2.719 seconds
However the Job is still in th agent and the status is executing. The implications of this are not good. Is this how the sql server agent job task is supposed to work by design.
Thanks,
Larry
Hi All,
I would appreciate any help here at all. I am pulling my hair out!
I am unable to start the snapshot agent or log reader agent from within SQL management studio. it fails on executing step 2 with unknown username or bad password.
I have checked all account details and they are correctly using my domain admin account. I can connect to SQL using teh same account and it also has sysadmin permissions.
If i copy the step 2 paramters and start from the cmd prompt (again logged in using the same domain account) they both start fine.
Any ideas would be gratefully received.
I am testing peer to peer replication in our environment. I simulated a three node peer to peer topology and a local distributor.
For some wierd reason I cannot get the Log Reader Agent and snapshot agent to start. The domain account under which SQL Server Agent runs has administrator previlage on the box. I also use a domain account for SQL Server Service. (none of the passwords changed).
This is the error I am getting - "Executed as user: abc. A required privilege is not held by the client. The step failed"
Any ideas???
Also this domain account is a member of
SQLServer2005MSSQLUsers$ServerName$MSSQLSERVER
SQLServer2005MSAgentUser$ServerName$MSSQLSERVER
We just moved source server to newer, bigger box ... Windows 2003 and Active Directory ... Snapshot agent worked but distribution failed ... Same login as on older machine, login is sysadm, used DCOMCNFG to allow ability to launch process ... What are we missing?
View 4 Replies View RelatedSQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
Is any has the same problem ?
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
hi.I have a sql2000 database.I have orders in a table with orderdate and ordertime.I want to force database to delete any order if person didnt pay for it after 3 days.I think I can check that with sqlAgent.but I dont know how.I checked most sites but couldnt find any sources.any help would be appreciated.
View 11 Replies View RelatedI am running SQL 2000 with SP3a and Windows Server 2003 successfully. I have a associate that is attempting to set up the same configuration. Our settings match identically, but his SQL agent will not start. I have checked everything I can think of but it still will not start on his network, yet works perfectly fine on mine. The error he is getting is that the SA account failed to log in properly, yet the password is correct. Any suggestions?
View 3 Replies View Relatedhi iam new to SSIS. I have two packages which are almost identical, only difference is the table name in the query to extract data just a test package.the package is created under my windows account, with the default protection level. I have scheduled them using SQL server agent. one runs succesfully and the other fails with error
Message
Executed as user: NAdbasvc-alticor. ... 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:28:25 AM Error: 2007-07-10 11:28:26.21 Code: 0xC020838F Source: Staging LKPDataReader Source [1] Description: An error occurred executing the provided SQL command. End Error Error: 2007-07-10 11:28:26.21 Code: 0xC004706B Source: Staging DTS.Pipeline Description: "component "LKPDataReader Source" (1)" failed validation and returned validation status "VS_ISBROKEN". End Error Error: 2007-07-10 11:28:26.21 Code: 0xC004700C Source: Staging DTS.Pipeline Description: One or more component failed validation. End Error Error: 2007-07-10 11:28:26.21 Code: 0xC0024107 Source: Staging Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:28:25 AM Finished: 11:28:26 AM Elapsed: 0.906 seconds. The package execution fai... The step failed.
I understand that it is something to do with
1.protection level
2.the user account under which the package is running
3.the SQL agent account used to run job
can someone be a detailed in explaining how to get this running and one big ? is why one package fails while the other with exactly same settings is running perfectly.
Please help i bid a lot of google on this but still confusing
Hi, I am new to SSIS. I createdtwo packages which are almost identical, only difference is the table name in the query to extract data just a test package.the package is created under my windows account, with the default protection level. I have scheduled them using SQL server agent. one runs succesfully and the other fails with error
Message
Executed as user: NAdbasvc-alticor. ... 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:28:25 AM Error: 2007-07-10 11:28:26.21 Code: 0xC020838F Source: Staging LKPDataReader Source [1] Description: An error occurred executing the provided SQL command. End Error Error: 2007-07-10 11:28:26.21 Code: 0xC004706B Source: Staging DTS.Pipeline Description: "component "LKPDataReader Source" (1)" failed validation and returned validation status "VS_ISBROKEN". End Error Error: 2007-07-10 11:28:26.21 Code: 0xC004700C Source: Staging DTS.Pipeline Description: One or more component failed validation. End Error Error: 2007-07-10 11:28:26.21 Code: 0xC0024107 Source: Staging Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:28:25 AM Finished: 11:28:26 AM Elapsed: 0.906 seconds. The package execution fai... The step failed.
I understand that it is something to do with
1.protection level
2.the user account under which the package is running
3.the SQL agent account used to run job
can someone be a detailed in explaining how to get this running and one big ? is why one package fails while the other with exactly same settings is running perfectly.
Please help i bid a lot of google on this but still confusing
I got a foglight alert that sql agent is down on one sql 2000 server
But now sql services are up and running fine.
How do i investigate that why sql agent was down
Please advice?
I have successfully created a DTS package, and would like to use SQL Server Job Agent to schedule it (instead of right-clicking on the package and scheduling a plan because the dates that I need to run this package are not fixed). How would I proceed? I am using SQL Server 2000.
Thanks...
A scheduled job use a SELECT query to check a record in a table,
the query returns 1 or 0.
how to let the job agent know if the return values is 1 then go next step and stop checking,
if return values is 0 then keep try for every 30 minutes for 10 times.
thanks
Hi all,
I am using SQL Server Express with Advanced features. I used to use the SQL agent in SQL Server 2000 to run a stored procedure that populated a table in my database each night.
I cant seem to do this with SQL Server Express. Is there another way to run this stored procedure each night and populate the table with the data returned.
I read about using Scheduled Tasks in Windows but Im not really familar with this.
Would really appreciate any ideas.
Thanks,
Cathie
A scheduled job use a SELECT query to check a record in a table,
the query returns 1 or 0.
how to let the job agent know if the return values is 1 then go next step and stop checking,
if return values is 0 then keep try for every 30 minutes for 10 times.
thanks