FULL and Tran Backup

The .bak and .trn seem to eat up too much disk space. What are the best
practices? We have to have point -in- time capability so it needs to be in
Full recovery mode. How do you prevent this from crashing the server? Do i
have to buy more disk. Appreciate any advice...> The .bak and .trn seem to eat up too much disk space. What are the best
> practices?
Delete the old backup files, determined by the number of backup generations
you want to have on
disk. If you don't use the maint wizard, make sure that you do overwrite at
suitable schedule (see
the INIT and NOINIT options to the backup command).
And, needless to say, make sure you also copy the backup files to other mach
ine, tape and/or
offsite.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"morphius" <morphius@.discussions.microsoft.com> wrote in message
news:EFD903D5-3AD8-44E2-B7AC-815BD14DBC94@.microsoft.com...
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...|||Hi
You don't say how long you keep the backups on disc and when it would be
acceptable to delete them. If they are stored safely elsewhere you can delet
e
the files but this will be at the expense of increased time needed to
recover. You will need to decide what the cut off is for this and if you
don't have enough disc space to hold that many backups, then you will need t
o
get more.
HTH
John
"morphius" wrote:

> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...