Introduction to SQL Server information during PlateSpin backup
## I wrote an article before The article IO is frozen on database xxx, No user action is required", mainly introduces PlateSpin in When doing DR backup at the server level, the SQL Server log contains "I/O is frozen on database xxxx" and "I/O was resumed on database xxx" information, For detailed information, please refer to that blog. This article is mainly from the side. Support, supplement!
# In fact, I discovered later that when the PlateSpin job is running, you will find that the database will record a complete backup of the database in msdb.dbo.backupset and back it up to the Virtual Device record. This is also a side evidence! Of course, there is not much information on PlateSpine on the Internet about more detailed and in-depth principles and knowledge points, so I don’t have time to understand it in depth. This is just a detail I discovered when collecting backup information. I was very confused at that time. At that time, there was no full backup or backup to the virtual device (Virtual Device)? After searching for the reason later, I found that this was related to PlateSpin. Hereby record it! ##SELECT CONVERT(CHAR(100), SERVERPROPERTY('Servername')) AS servername ,
bs.database_name ,
bs.backup_start_date ,
bs.backup_finish_date ,
DATEDIFF(MINUTE,bs.backup_start_date, bs.backup_finish_date) AS backup_consume_time,
bs.expiration_date ,
CASE bs.type
WHEN 'D' THEN 'Full Backup'
WHEN 'I' THEN 'Diff Backup'
WHEN 'L' THEN 'Log Bacup'
WHEN 'F' THEN 'File Backup'
WHEN 'G' THEN 'File Diff'
WHEN 'P' THEN 'Partial Backup'
WHEN 'Q' THEN 'Partial Diff Backup'
END AS backup_type ,
CASE bf.device_type
WHEN 2 THEN 'Disk'
WHEN 5 THEN 'Tape'
WHEN 7 THEN 'Virtual Device'
WHEN 105 THEN 'permanent backup device'
END AS backup_media,
bs.backup_size/1024/1024/1024 AS [backup_size(GB)] ,
bs.compressed_backup_size/1024/1024/1024 AS [compressed_backup_size(GB)],
bf.logical_device_name ,
bf.physical_device_name ,
bs.name AS backupset_name ,
bs.first_lsn,
bs.last_lsn,
bs.checkpoint_lsn,
bs.description
FROM msdb.dbo.backupmediafamily bf
INNER JOIN msdb.dbo.backupset bs ON bf.media_set_id = bs.media_set_id
WHERE ( CONVERT(DATETIME, bs.backup_start_date, 102) >= CAST('2017-10-18 21:00' AS DATETIME))
AND ( CONVERT(DATETIME, bs.backup_start_date, 102) <= CAST('2017-10-18 23:59' AS DATETIME))
AND
bs.type='D' AND bs.database_name='HistoryData'
ORDER BY bs.database_name ,
bs.backup_finish_date;
##
The above is the detailed content of Introduction to SQL Server information during PlateSpin backup. For more information, please follow other related articles on the PHP Chinese website!

MySQL processes data replication through three modes: asynchronous, semi-synchronous and group replication. 1) Asynchronous replication performance is high but data may be lost. 2) Semi-synchronous replication improves data security but increases latency. 3) Group replication supports multi-master replication and failover, suitable for high availability requirements.

The EXPLAIN statement can be used to analyze and improve SQL query performance. 1. Execute the EXPLAIN statement to view the query plan. 2. Analyze the output results, pay attention to access type, index usage and JOIN order. 3. Create or adjust indexes based on the analysis results, optimize JOIN operations, and avoid full table scanning to improve query efficiency.

Using mysqldump for logical backup and MySQLEnterpriseBackup for hot backup are effective ways to back up MySQL databases. 1. Use mysqldump to back up the database: mysqldump-uroot-pmydatabase>mydatabase_backup.sql. 2. Use MySQLEnterpriseBackup for hot backup: mysqlbackup--user=root-password=password--backup-dir=/path/to/backupbackup. When recovering, use the corresponding life

The main reasons for slow MySQL query include missing or improper use of indexes, query complexity, excessive data volume and insufficient hardware resources. Optimization suggestions include: 1. Create appropriate indexes; 2. Optimize query statements; 3. Use table partitioning technology; 4. Appropriately upgrade hardware.

MySQL view is a virtual table based on SQL query results and does not store data. 1) Views simplify complex queries, 2) Enhance data security, and 3) Maintain data consistency. Views are stored queries in databases that can be used like tables, but data is generated dynamically.

MySQLdiffersfromotherSQLdialectsinsyntaxforLIMIT,auto-increment,stringcomparison,subqueries,andperformanceanalysis.1)MySQLusesLIMIT,whileSQLServerusesTOPandOracleusesROWNUM.2)MySQL'sAUTO_INCREMENTcontrastswithPostgreSQL'sSERIALandOracle'ssequenceandt

MySQL partitioning improves performance and simplifies maintenance. 1) Divide large tables into small pieces by specific criteria (such as date ranges), 2) physically divide data into independent files, 3) MySQL can focus on related partitions when querying, 4) Query optimizer can skip unrelated partitions, 5) Choosing the right partition strategy and maintaining it regularly is key.

How to grant and revoke permissions in MySQL? 1. Use the GRANT statement to grant permissions, such as GRANTALLPRIVILEGESONdatabase_name.TO'username'@'host'; 2. Use the REVOKE statement to revoke permissions, such as REVOKEALLPRIVILEGESONdatabase_name.FROM'username'@'host' to ensure timely communication of permission changes.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Dreamweaver CS6
Visual web development tools

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool

SublimeText3 Chinese version
Chinese version, very easy to use

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Mac version
God-level code editing software (SublimeText3)
