SQL backups on Veritas

0 pts.
Tags:
Backup & recovery
Veritas
What is the best practice for backing up MSSQL databases to Veritas? Currently the database is being exported to a flat file, and the flat file is being backed up. Is there a better method?
ASKED: January 14, 2005  12:07 PM
UPDATED: January 14, 2005  1:31 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Maybe I am stating the too obvious, but Veritas has agents for specific applications such as MS SQL Server. I would purchase and install the VERITAS Backup Exec Agent for Microsoft SQL Server.

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Tullman
    Yes, it is obvious, but I wasn't clear enough in the question. We have Datacenter 4.5 FP6 and we are using the Oracle agent, I am not sure whether I need to install another agent to handle MSSQL, or use the same one. I downloaded a procedure from the Veritas site for setting up the client, so I am in the ball park. One source of my confusion is that our Oracle backups are done with RMAN, and not scheduled in Veritas. It is a User activated policy. I don't know if that is possible with MSSQL, or if the best thing to do is let Veritas initiate the backup. It sounds like it is, I just want to know what others are doing.
    0 pointsBadges:
    report
  • Calmats
    I feel that the procedure for backing up your SQL databases is one of those "it depends". The method that you stated is one that I feel is very good and one that I often use. But there can be a few drawbacks to this approach and in some instances this approach may not be feasible. I like this approach (when it's feasible) because I work in a data center where roles are more separated and specialized. The DBA's are not the same group who perform the Veritas backups. By using SQL Server to back up the databases to a flat file and pointing Veritas to this I receive the following benefits: Backing up to disk is faster Backing this up to tape provides redundancy If space allows I may try to maintain 3 to 5 days locally on disk so recovery is quicker and I don't have to contact the Veritas staff (sometimes in the middle of the night). A possible drawback of this approach is that it requires more monitoring because Databases tend to grow and you may exceed disk space on your allocated backup drive. In terms of feasibility: If you have a large database you may not have this option and would have to go directly to tape using Veritas with the SQL Agent. Hope this helps...... Best of Luck
    0 pointsBadges:
    report
  • Plewisssww
    Not to sound like a salesperson, but I recently implemented SQL LiteSpeed by Imceda software. This installs as a set of extended stored procedures in SQL, and it was capable (in my case) of reducing both time and storage requirements for my backup of a 105GB database by over 70%. I adjusted my overnight processing to incorporate the LiteSpeed backup to disk space on my SQL development box, then the development box is backed up with Veritas, including the file produced by LiteSpeed. It has helped free up a major bottleneck in morning use of a business intelligene tool here by greatly reducing the time requied for daily processing of the database and OLAP cubes.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following