Full and Incremental Backup Question

1) We are doing Weekly Full & DAILY night incremental backup of TL using Veritas Backup Manager to Tape.

One day I took Incremental Backup of TL file manually using studio and deleted the backup file.

Will I able to restore completed if something happens on next day ? Is automated backup takes care of Incremental backup from last night instead of manual interim backup ?

What is the recommendation ? If automated backup is enabled, we should not do manual backup ?

2) In Full Recovery Modek , If I do full backup , Does it backup Transactional Log also or only Datafiles ?

Thanks

Full Backup makes a copy of all database objects and data, including any changes that occur while the Backup is running.

Differential Backup makes a copy of all changes since the last Full Backup.

There is NO 'Incremental Backup'. That is accomplished using the Transaction Log Backup.

If you make a Full Backup on Sunday, and Differential Backups every night, then you will be able to restore your database to its condition when the last differential backup was made. Any datachanges since the Differential backup may be at risk.

Transaction Log Backups make a copy of all changes to the database since the last Full Backup OR the last Transaction Log Backup. IF your Recovery model is set for 'Full', or 'Bulk Logged', and you are making Transaction Log Backups, then you 'should' be able to recover up until a moment before the data corruption event.

|||

We are doing weekly full backup for all databases & daily incremental other than system databases.

Is weekly full backup of System databases good enough to restore from failure ?

|||

In a 'static' environment, weekly backups for the system databases may be just fine. The only significant loss would be the Job History since the last msdb backup. (By static, I mean no new logins, no new Jobs, no new databases, etc.

In a developing environment, more frequent backups of system database will help prevent the loss of any changes to system settings, logins, jobs, job history, etc.

|||It is always hard to tell if a backup strategy is sufficient for your needs, as this depends on how much data loss you are willing to allow, how much money you can spend on your backup strategy, how the backups interfer with the productive system, how long the recovery process can be, etc. First of all I would start by defining how much data loss you can afford. if you don′t care about a one day loss, you can leave it up to one full backup (But remember that even this backup could be destroyed for some reason), if you need more backup and more data availbility you will have to scale it through differential and transactionlog backups.

Jens K. Suessmeyer.

http://www.sqlserver2005.de