REASON
Disaster recovery is deeply embedded into the design of SQL Server, and as such, it’s it is important to carefully understand and manage your database backup policies carefully. SQL Server databases must be backed up using the built-in BACKUP command, either natively within SQL Server or through the use of a SQL-specific, third-party tool. If no backup has been is done on a particular database, it will not be possible is impossible to recover in case of corruption, system failure, or accidental data deletion of data. Regular filesystem backups are not a substitute for database backups.
RESOLUTION
Refer to
| Newtablink |
|---|
| alias | this article |
|---|
| url | http://technet.microsoft.com/en-us/library/ms186865.aspx |
|---|
|
for the Microsoft Technet article Backup (Transact-SQL) for an overview of backup operations in SQL Server. All databases
have include a configured
| Newtablink |
|---|
alias | recovery model| url | http://msdn.microsoft.com/en-us/library/ms189275.aspx |
|---|
, which dictates the kinds , which dictates the type of backup and restore operations
which that are available. In all cases,
perform a full backup
should be taken of any database
which that has never
been backed upexperienced a backup. In the simple recovery model,
perform regular
, full backups
should be taken on an ongoing basis
, while using the full or bulk
-logged recovery model
. In addition,
add regular log and differential backups
should be added to the full backup schedule
.