Jul 26, 2017 Aimbetter support

SQL: Full backup (.bak)
MS-SQL, SQL

Risk :

A missing full backup can cause loss of data. In case of database fault , we won’t be able to restore the database.

Description:

A full backup contains all the data in a specific database or set of file groups or files. It is the base of both differential backup and transaction log backup.

Normally:

Full SQL backup should execute successfully every 24 hours.

What went wrong?

  • A Large backup file caused long backup execute.
  • No available disk space.
  • Network is not available.

What to do:

  • Check backup system.
  • Check server network connection

 

 

 

 

 

 

You may also like this

Mar 24, 2018 Alon

SQL: Buffer Cache Hit Ratio

Reports the ratio of the data pages found and read from the SQL Server buffer cache and all data page requests. Pages that are not found in the buffer cache must be read from disk

MS-SQL, Performance, SQL
Apr 22, 2018 Alon

Host: CPU Utilization

Measures the load of all the tasks that are being performed by the server. CPU usage below 70% is considered normal. Unusual levels of CPU load activities may be coming from anti-virus scans, backups, restores etc.

Operating System, Performance, Windows

RECENT POSTS