Hey Ed,
My opinion on this extends to pretty much all DB agent backups vs.
backup to disk.
Disadvantages:
Disk First:
You either have to write prescripts that make this happen before your
job starts(this, in my experience, is a very unreliable setup), or your
have to schedule your backups to finish after you disk backup finishes
and before it starts again. This can be difficult with large databases
that take a long time to backup to disk. It also makes for an error
prone/ unflexible setup. When the database grows and the backup to disk
doesn't end until after your Networker backup starts then you'll have
worthless backups. This can go unnoticed until a restore is required
then it's too late.
Requires twice the disk space, or you can compress but that is very
resource intensive.
Agent Backups:
Initial setup can be more complex (specifically the oracle agent). The
MSSQL agent is very simple to setup.
Advantages:
Disk First:
You have a current backup on disk ready to be restored quickly.
Although, I've found that it is quite fast to restore from tape with the
Sybase and MSSQL agents. Not much experience with the Oracle agent...
seems a bit convoluted.
It makes DBAs feel good(not sure why but it does in my experience).
Agent Backups:
Very flexible. Resource requirement aside you have no time restraints
for scheduling or rescheduling.
No extra disk required.
No need to develop pre/post scripts
Just my opinions... we do it both ways, and if I had my preference I'd
have every database backed up through an agent.
Hope this helps,
Joel
-----Original Message-----
From: Ed Skolnik [mailto:eskolnik AT INTERPUBLIC DOT COM]
Sent: Thursday, April 03, 2003 12:14 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] advantages and disadvantages in using the Legato
Microsoft SQL module for backing up MS SQL
What are the advantages and disadvantages in using the Legato Microsoft
SQL
module for backing up MS SQL databases? Could some one explain why
using
Legato to perform this function is better way to go than using the
standard
SQL maintenance plans to dump SQL to flat files and then have the
standard
NetWorker client dump those files to tape (or lower cost disk).
Ed Skolnik
The Interpublic Group Of Companies, Inc.
GIS Chicago System Administrator
676 North St. Clair Street
Chicago, Illinois 60611
Phone: 312-425-6554
Fax: 312-425-6924
e-mail: eskolnik AT Interpublic DOT com
Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of the company. Also this
message may contain information which may be confidential and
privileged.
Unless you are the intended recipient (or authorized to receive this
message for the intended recipient), you may not use, copy, disseminate
or
disclose to anyone the message or any information contained in the
message.
If you have received the message in error, please advise the sender by
reply e-mail, and delete the message. Thank you very much.
--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
