Moses, Yes... you have the basic idea. I would recommend adding a scheduled log backup to this as well. There is a section in the Data Protection for SQL User's Guide, Chapter 1, called: "Data Protection for SQL backup strategy considerations" that explains the different backup strategies and when to consider one type over another.
For example, this is the excerpt from the book: "Full plus differential plus log backup This strategy allows for a faster restore scenario by reducing the number of transaction logs that may need to be restored and applied. If, for example, a full backup is done weekly, a differential nightly, and a log backup every four hours, the restore would involve the full backup, a differential, and at most five log backups. However, simply a full plus log backup scheme on the same cycle could require a full plus up to forty-one log backups to be restored (six days times six log backups per day plus up to five backups on the day the full backup was done)." Look in the book for more details. Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 11/02/2004 11:30:49 AM: > Hi People, > We currently have various SQL servers which are being backed up > using TDP for SQL. Currently we are doing full backups on a daily basis, > but with server space being at a premium we have decided to begin > implementing incremental backups alongside full backups. > The intended method is to create a batch file and call it sqldiff. Next > would then have to create a schedule for the differential backup, decide > upon the frequency it should be run and then attach a client to the > schedule. It is anticipated that differentials will run during the week > (Mon-Fri) and then full backups at the weekends. > > Can anyone advise on whether this is a good way to start with or if there > is indeed a simpler and more efficient way to achieve our goal > > Thanks in advance.
