We have some databases (100-130 gig) that take 30 plus hours to backup. Is
this normal and is there a better way to do this than using the built in
backup tools? Or a bteer way to use the tools?
I know we can do patial backups but I am specifically looking for
information on the full backup procedure.
OS server 2003, 4gig ram, database sql2000.
Thanks!Hi
You don't say what you are backing up to! You could use multiple backup
devices to cut down this time. Make sure that you do not have contention for
resources when backing up i.e. split data files from backup files
John
"Stedak" wrote:
> We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> this normal and is there a better way to do this than using the built in
> backup tools? Or a bteer way to use the tools?
> I know we can do patial backups but I am specifically looking for
> information on the full backup procedure.
> OS server 2003, 4gig ram, database sql2000.
> Thanks!|||Stedak wrote:
> We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> this normal and is there a better way to do this than using the built in
> backup tools? Or a bteer way to use the tools?
> I know we can do patial backups but I am specifically looking for
> information on the full backup procedure.
> OS server 2003, 4gig ram, database sql2000.
> Thanks!
Something is wrong... We have multiple databases here that are nearly
200GB each, and none of them takes longer than 45 minutes to backup to
disk. Are you backing up to disk or tape?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Stedak wrote:
> We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> this normal and is there a better way to do this than using the built in
> backup tools? Or a bteer way to use the tools?
> I know we can do patial backups but I am specifically looking for
> information on the full backup procedure.
> OS server 2003, 4gig ram, database sql2000.
> Thanks!
In addition to my other post, make sure you don't have anti-virus
software that is scanning the backup file as you're writing it. Also
check for disk fragmentation.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are backing up to an external USB hard drive.
"Tracy McKibben" wrote:
> Stedak wrote:
> Something is wrong... We have multiple databases here that are nearly
> 200GB each, and none of them takes longer than 45 minutes to backup to
> disk. Are you backing up to disk or tape?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Probably an IDE 7200 RPM?
Yes, that will take a whole lot longert than an internal SCSI RAID set of
drives.
30 hours seems excessive. have you done a local backup to compare, or is
the reason for the external that you don't have enough drive space locally?
Also, there are backup compression utilities on teh market...LiteSpeed from
Quest and SQL Backup from Red Gate are the two I know well.
Kevin Hill
3NF Consulting
www.3nf-inc.com
"Stedak" <Stedak@.discussions.microsoft.com> wrote in message
news:617BD7F1-D85D-46D6-979E-B9090BA795DE@.microsoft.com...[vbcol=seagreen]
> We are backing up to an external USB hard drive.
> "Tracy McKibben" wrote:
>|||Stedak wrote:
> We are backing up to an external USB hard drive.
>
Probably not the best choice for high-speed SQL Server backups...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Stedak" <Stedak@.discussions.microsoft.com> wrote in message
news:617BD7F1-D85D-46D6-979E-B9090BA795DE@.microsoft.com...
> We are backing up to an external USB hard drive.
>
Not a great choice.
I like the idea of backing up to disk though.
I use Snap Servers (specifically the 4200 right now) and get 100+ gig of
backups done in about 4+ hours.
And there's other tricks one can do to get even faster backups.
(for example writing to TWO snap servers would cut that about in 1/2.)
[vbcol=seagreen]
> "Tracy McKibben" wrote:
>
Showing posts with label plus. Show all posts
Showing posts with label plus. Show all posts
Friday, March 9, 2012
Larger (100gig+) SQl database backup time
We have some databases (100-130 gig) that take 30 plus hours to backup. Is
this normal and is there a better way to do this than using the built in
backup tools? Or a bteer way to use the tools?
I know we can do patial backups but I am specifically looking for
information on the full backup procedure.
OS server 2003, 4gig ram, database sql2000.
Thanks!Hi
You don't say what you are backing up to! You could use multiple backup
devices to cut down this time. Make sure that you do not have contention for
resources when backing up i.e. split data files from backup files
John
"Stedak" wrote:
> We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> this normal and is there a better way to do this than using the built in
> backup tools? Or a bteer way to use the tools?
> I know we can do patial backups but I am specifically looking for
> information on the full backup procedure.
> OS server 2003, 4gig ram, database sql2000.
> Thanks!|||Stedak wrote:
> We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> this normal and is there a better way to do this than using the built in
> backup tools? Or a bteer way to use the tools?
> I know we can do patial backups but I am specifically looking for
> information on the full backup procedure.
> OS server 2003, 4gig ram, database sql2000.
> Thanks!
Something is wrong... We have multiple databases here that are nearly
200GB each, and none of them takes longer than 45 minutes to backup to
disk. Are you backing up to disk or tape?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Stedak wrote:
> We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> this normal and is there a better way to do this than using the built in
> backup tools? Or a bteer way to use the tools?
> I know we can do patial backups but I am specifically looking for
> information on the full backup procedure.
> OS server 2003, 4gig ram, database sql2000.
> Thanks!
In addition to my other post, make sure you don't have anti-virus
software that is scanning the backup file as you're writing it. Also
check for disk fragmentation.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are backing up to an external USB hard drive.
"Tracy McKibben" wrote:
> Stedak wrote:
> > We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> > this normal and is there a better way to do this than using the built in
> > backup tools? Or a bteer way to use the tools?
> >
> > I know we can do patial backups but I am specifically looking for
> > information on the full backup procedure.
> >
> > OS server 2003, 4gig ram, database sql2000.
> >
> > Thanks!
> Something is wrong... We have multiple databases here that are nearly
> 200GB each, and none of them takes longer than 45 minutes to backup to
> disk. Are you backing up to disk or tape?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Probably an IDE 7200 RPM?
Yes, that will take a whole lot longert than an internal SCSI RAID set of
drives.
30 hours seems excessive. have you done a local backup to compare, or is
the reason for the external that you don't have enough drive space locally?
Also, there are backup compression utilities on teh market...LiteSpeed from
Quest and SQL Backup from Red Gate are the two I know well.
--
Kevin Hill
3NF Consulting
www.3nf-inc.com
"Stedak" <Stedak@.discussions.microsoft.com> wrote in message
news:617BD7F1-D85D-46D6-979E-B9090BA795DE@.microsoft.com...
> We are backing up to an external USB hard drive.
> "Tracy McKibben" wrote:
>> Stedak wrote:
>> > We have some databases (100-130 gig) that take 30 plus hours to backup.
>> > Is
>> > this normal and is there a better way to do this than using the built
>> > in
>> > backup tools? Or a bteer way to use the tools?
>> >
>> > I know we can do patial backups but I am specifically looking for
>> > information on the full backup procedure.
>> >
>> > OS server 2003, 4gig ram, database sql2000.
>> >
>> > Thanks!
>> Something is wrong... We have multiple databases here that are nearly
>> 200GB each, and none of them takes longer than 45 minutes to backup to
>> disk. Are you backing up to disk or tape?
>>
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com|||Stedak wrote:
> We are backing up to an external USB hard drive.
>
Probably not the best choice for high-speed SQL Server backups...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Stedak" <Stedak@.discussions.microsoft.com> wrote in message
news:617BD7F1-D85D-46D6-979E-B9090BA795DE@.microsoft.com...
> We are backing up to an external USB hard drive.
>
Not a great choice.
I like the idea of backing up to disk though.
I use Snap Servers (specifically the 4200 right now) and get 100+ gig of
backups done in about 4+ hours.
And there's other tricks one can do to get even faster backups.
(for example writing to TWO snap servers would cut that about in 1/2.)
> "Tracy McKibben" wrote:
>> Stedak wrote:
>> > We have some databases (100-130 gig) that take 30 plus hours to backup.
>> > Is
>> > this normal and is there a better way to do this than using the built
>> > in
>> > backup tools? Or a bteer way to use the tools?
>> >
>> > I know we can do patial backups but I am specifically looking for
>> > information on the full backup procedure.
>> >
>> > OS server 2003, 4gig ram, database sql2000.
>> >
>> > Thanks!
>> Something is wrong... We have multiple databases here that are nearly
>> 200GB each, and none of them takes longer than 45 minutes to backup to
>> disk. Are you backing up to disk or tape?
>>
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com
this normal and is there a better way to do this than using the built in
backup tools? Or a bteer way to use the tools?
I know we can do patial backups but I am specifically looking for
information on the full backup procedure.
OS server 2003, 4gig ram, database sql2000.
Thanks!Hi
You don't say what you are backing up to! You could use multiple backup
devices to cut down this time. Make sure that you do not have contention for
resources when backing up i.e. split data files from backup files
John
"Stedak" wrote:
> We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> this normal and is there a better way to do this than using the built in
> backup tools? Or a bteer way to use the tools?
> I know we can do patial backups but I am specifically looking for
> information on the full backup procedure.
> OS server 2003, 4gig ram, database sql2000.
> Thanks!|||Stedak wrote:
> We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> this normal and is there a better way to do this than using the built in
> backup tools? Or a bteer way to use the tools?
> I know we can do patial backups but I am specifically looking for
> information on the full backup procedure.
> OS server 2003, 4gig ram, database sql2000.
> Thanks!
Something is wrong... We have multiple databases here that are nearly
200GB each, and none of them takes longer than 45 minutes to backup to
disk. Are you backing up to disk or tape?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Stedak wrote:
> We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> this normal and is there a better way to do this than using the built in
> backup tools? Or a bteer way to use the tools?
> I know we can do patial backups but I am specifically looking for
> information on the full backup procedure.
> OS server 2003, 4gig ram, database sql2000.
> Thanks!
In addition to my other post, make sure you don't have anti-virus
software that is scanning the backup file as you're writing it. Also
check for disk fragmentation.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are backing up to an external USB hard drive.
"Tracy McKibben" wrote:
> Stedak wrote:
> > We have some databases (100-130 gig) that take 30 plus hours to backup. Is
> > this normal and is there a better way to do this than using the built in
> > backup tools? Or a bteer way to use the tools?
> >
> > I know we can do patial backups but I am specifically looking for
> > information on the full backup procedure.
> >
> > OS server 2003, 4gig ram, database sql2000.
> >
> > Thanks!
> Something is wrong... We have multiple databases here that are nearly
> 200GB each, and none of them takes longer than 45 minutes to backup to
> disk. Are you backing up to disk or tape?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Probably an IDE 7200 RPM?
Yes, that will take a whole lot longert than an internal SCSI RAID set of
drives.
30 hours seems excessive. have you done a local backup to compare, or is
the reason for the external that you don't have enough drive space locally?
Also, there are backup compression utilities on teh market...LiteSpeed from
Quest and SQL Backup from Red Gate are the two I know well.
--
Kevin Hill
3NF Consulting
www.3nf-inc.com
"Stedak" <Stedak@.discussions.microsoft.com> wrote in message
news:617BD7F1-D85D-46D6-979E-B9090BA795DE@.microsoft.com...
> We are backing up to an external USB hard drive.
> "Tracy McKibben" wrote:
>> Stedak wrote:
>> > We have some databases (100-130 gig) that take 30 plus hours to backup.
>> > Is
>> > this normal and is there a better way to do this than using the built
>> > in
>> > backup tools? Or a bteer way to use the tools?
>> >
>> > I know we can do patial backups but I am specifically looking for
>> > information on the full backup procedure.
>> >
>> > OS server 2003, 4gig ram, database sql2000.
>> >
>> > Thanks!
>> Something is wrong... We have multiple databases here that are nearly
>> 200GB each, and none of them takes longer than 45 minutes to backup to
>> disk. Are you backing up to disk or tape?
>>
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com|||Stedak wrote:
> We are backing up to an external USB hard drive.
>
Probably not the best choice for high-speed SQL Server backups...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Stedak" <Stedak@.discussions.microsoft.com> wrote in message
news:617BD7F1-D85D-46D6-979E-B9090BA795DE@.microsoft.com...
> We are backing up to an external USB hard drive.
>
Not a great choice.
I like the idea of backing up to disk though.
I use Snap Servers (specifically the 4200 right now) and get 100+ gig of
backups done in about 4+ hours.
And there's other tricks one can do to get even faster backups.
(for example writing to TWO snap servers would cut that about in 1/2.)
> "Tracy McKibben" wrote:
>> Stedak wrote:
>> > We have some databases (100-130 gig) that take 30 plus hours to backup.
>> > Is
>> > this normal and is there a better way to do this than using the built
>> > in
>> > backup tools? Or a bteer way to use the tools?
>> >
>> > I know we can do patial backups but I am specifically looking for
>> > information on the full backup procedure.
>> >
>> > OS server 2003, 4gig ram, database sql2000.
>> >
>> > Thanks!
>> Something is wrong... We have multiple databases here that are nearly
>> 200GB each, and none of them takes longer than 45 minutes to backup to
>> disk. Are you backing up to disk or tape?
>>
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com
Subscribe to:
Posts (Atom)