My database is 300 GB is size using SQL Server 2000. This is a
high-availability cluster server. My present daily maintenance job backups
take approximately 4 hours to complete.
I would like to know alternatives to faster database backups without
changing the database.
Thanks,Where to do you take the backups? Same disk as data? Over network? What RAID
level? Also, consider
backup compression software. I've mentioned a few of those on my links page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backup
s
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,|||Hi,
Split-Mirror Backup is the fastest method to backup the VLDB. see the link
for details:-
http://www.microsoft.com/technet/pr...n/spltmirr.mspx
Thanks
Hari
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
> backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,|||In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backup
s
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
spam999free@.rrohio.com
remove 999 in order to email me|||Most certainly write your backups to local disk as a first option, disks
different from the LUNs your data and log files are resident on.
Next, regardless if you use the maintenance plans or hand code the backups,
having multiple files per filegroup will spawn parallel processes for SQL
Server to read from for the backup.
If you want both your backups and potential restores to be faster, you'll
have to hand code a job to backup the database. Back up to multiple backup
files. This will increase the disk throughput but also spawn multiple
processes if you should ever have to restore, reducing the outage time.
Finally, check out SQL Litespeed by Imceda. It allows you to create
multiple process even without multiple files as well as gives you several
compression options to keep your to disk backups more reasonably sized.
Sincerely,
Anthony Thomas
"Leythos" <void@.nowhere.lan> wrote in message
news:MPG.1d10169943fb39819898d1@.news-server.columbus.rr.com...
In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
spam999free@.rrohio.com
remove 999 in order to email me
Friday, March 9, 2012
Faster SQL Server Backups
Labels:
ahigh-availability,
backups,
backupstake,
cluster,
database,
job,
maintenance,
microsoft,
mysql,
oracle,
server,
size,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment