Skip to content

Commit ea1a8fd

Browse files
authored
Update sql-server-vss-writer-backup-guide.md
edit headers
1 parent 4ffad18 commit ea1a8fd

1 file changed

Lines changed: 6 additions & 8 deletions

File tree

docs/relational-databases/backup-restore/sql-server-vss-writer-backup-guide.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ The role of the SQL writer in a VSS snapshot backup operation:
5454

5555
![VSS Snapshot](media/sql-server-vss-writer-backup-guide/sql-vss-snapshot.png)
5656

57-
## Configuring the SQL Writer
57+
### Configuring the SQL Writer
5858

5959
The SQL writer service is installed in the system as part of the SQL Server installation and is configured to start automatically when Windows starts.
6060

@@ -118,17 +118,15 @@ The following table lists the kinds of snapshot backups that are supported by th
118118

119119
## Backup and Restore
120120

121-
### Version Support
122-
123-
The SQL writer is shipped as part of SQL Server and supports only SQL Server instances. The SQL writer will enumerate the SQL Server Express instances also. User instances launched by SQL Server Express will also be enumerated by the SQL writer.
124-
125-
## Supported Backup/Restore Operations
126-
127121
SQL Server (using the SQL writer) will support the following modes of VSS-based backup operations:
128122

129123
- Noncomponent-based
130124
- Component-based
131125

126+
### Version Support
127+
128+
The SQL writer is shipped as part of SQL Server and supports only SQL Server instances. The SQL writer will enumerate the SQL Server Express instances also. User instances launched by SQL Server Express will also be enumerated by the SQL writer.
129+
132130
### Noncomponent-Based Backup Operations
133131

134132
Noncomponent-based backups implicitly select databases by using the list of volumes in the snapshot set. The SQL writer checks for torn databases, raising an error if found. A torn database is one in which a subset of files is selected by the list of volumes.
@@ -411,7 +409,7 @@ A differential backup will always be with respect to the latest base backup that
411409

412410
Currently if the byte-range information (partial file information) is too large (exceeding 64 K bytes in buffer size), SQL Server will throw an error instructing the user to perform a full backup.
413411

414-
### Interesting cases during backup
412+
### Troubleshooting
415413

416414
File add/drop/shrink/growth/logical-rename/physical-rename make interesting cases in backup.
417415

0 commit comments

Comments
 (0)