|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Database backup maintenance plan to disk with individual files (no append)In the past I've backed up my systems via maintenance plans that would
perform full database backups to disk and having the job place them in separate directories named according to the database name. Each time the job was run it would create a new uniquely named file database_datetime.bak . The maintenance jobs would also purge old files over a specified age. I only see a way to append to existing files in the 2005 version. I prefer having them in individual files so that OS tape jobs only have to backup the actual new files versus a growing (appended) file + it is easier to do file cleanups when they are separate viewable files in the directories. Any suggestions? Did I miss something obvious in the Maintenance Job Wizard? Nevermind... I got it.. I was doing my testing too quickly causing it to
append to existing files (within same minute). :) Henrik wrote:Show quote > In the past I've backed up my systems via maintenance plans that would > perform full database backups to disk and having the job place them in > separate directories named according to the database name. Each time > the job was run it would create a new uniquely named file > database_datetime.bak . The maintenance jobs would also purge old files > over a specified age. > > I only see a way to append to existing files in the 2005 version. I > prefer having them in individual files so that OS tape jobs only have to > backup the actual new files versus a growing (appended) file + it is > easier to do file cleanups when they are separate viewable files in > the directories. > > Any suggestions? Did I miss something obvious in the Maintenance Job > Wizard? |
|||||||||||||||||||||||