I have a 30 gig SQL 2000 database to backup to disk. The problem is I only
have 20 gigs free on the server after the backup is done. When a new backup
is created it doesn't delete the old one until after it tries to write the
new one. How can I set the full backup (t log backups run every hour) to
delete the previous days full first and then write the new one.
Tia
jj"jj" <jeff_detoro@.urmc.rochester.edu> wrote in message
news:ursIxSh4EHA.2428@.TK2MSFTNGP14.phx.gbl...
> I have a 30 gig SQL 2000 database to backup to disk. The problem is I
only
> have 20 gigs free on the server after the backup is done. When a new
backup
> is created it doesn't delete the old one until after it tries to write the
> new one. How can I set the full backup (t log backups run every hour) to
> delete the previous days full first and then write the new one.
You'd have to do this by hand. (i.e. it's not a default option).
however, what happens if you delete the old backup and full backup fails for
some reason (say the database becomes corrupt before the latest backup?)
I'd get a bigger disk.
(or one option which we use is a NAS like a snap server... lots of room,
RAID, etc.)
> Tia
> jj
>
Showing posts with label gigs. Show all posts
Showing posts with label gigs. Show all posts
Sunday, March 11, 2012
Backup Problem
I have a database that is around 30 gigs in size. It has always taken a
couple of hours to back up. Now all of a sudden it never stops backing
up...It started around 8:00pm last night and when I came in at 8:00am this
morning it was still backing up. There has been no major size change or
anything like that. I need to be able to back it up, but this is crazy.
I'm backing up to disk and then backing the disk file up to tape.Hi John,
First, take a look at errorlog, and NT System and application log to see if
there is any error related to the backup.
Then, Take a look at master..sysprocesses table to see if there is any
blocking problem. sp_lock output would help as well.
Sincerely,
Yih-Yoon Lee
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
couple of hours to back up. Now all of a sudden it never stops backing
up...It started around 8:00pm last night and when I came in at 8:00am this
morning it was still backing up. There has been no major size change or
anything like that. I need to be able to back it up, but this is crazy.
I'm backing up to disk and then backing the disk file up to tape.Hi John,
First, take a look at errorlog, and NT System and application log to see if
there is any error related to the backup.
Then, Take a look at master..sysprocesses table to see if there is any
blocking problem. sp_lock output would help as well.
Sincerely,
Yih-Yoon Lee
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
backup problem
I have a 30 gig SQL 2000 database to backup to disk. The problem is I only
have 20 gigs free on the server after the backup is done. When a new backup
is created it doesn't delete the old one until after it tries to write the
new one. How can I set the full backup (t log backups run every hour) to
delete the previous days full first and then write the new one.
Tia
jj
"jj" <jeff_detoro@.urmc.rochester.edu> wrote in message
news:ursIxSh4EHA.2428@.TK2MSFTNGP14.phx.gbl...
> I have a 30 gig SQL 2000 database to backup to disk. The problem is I
only
> have 20 gigs free on the server after the backup is done. When a new
backup
> is created it doesn't delete the old one until after it tries to write the
> new one. How can I set the full backup (t log backups run every hour) to
> delete the previous days full first and then write the new one.
You'd have to do this by hand. (i.e. it's not a default option).
however, what happens if you delete the old backup and full backup fails for
some reason (say the database becomes corrupt before the latest backup?)
I'd get a bigger disk.
(or one option which we use is a NAS like a snap server... lots of room,
RAID, etc.)
> Tia
> jj
>
have 20 gigs free on the server after the backup is done. When a new backup
is created it doesn't delete the old one until after it tries to write the
new one. How can I set the full backup (t log backups run every hour) to
delete the previous days full first and then write the new one.
Tia
jj
"jj" <jeff_detoro@.urmc.rochester.edu> wrote in message
news:ursIxSh4EHA.2428@.TK2MSFTNGP14.phx.gbl...
> I have a 30 gig SQL 2000 database to backup to disk. The problem is I
only
> have 20 gigs free on the server after the backup is done. When a new
backup
> is created it doesn't delete the old one until after it tries to write the
> new one. How can I set the full backup (t log backups run every hour) to
> delete the previous days full first and then write the new one.
You'd have to do this by hand. (i.e. it's not a default option).
however, what happens if you delete the old backup and full backup fails for
some reason (say the database becomes corrupt before the latest backup?)
I'd get a bigger disk.
(or one option which we use is a NAS like a snap server... lots of room,
RAID, etc.)
> Tia
> jj
>
Subscribe to:
Posts (Atom)