BACKUP, MAXTRANSFERSIZE edit

BYHAM · web-flow · commit fe7bdfa49e60 · 2017-09-05T08:17:08.000-07:00
Per Content Idea Request 65513.
diff --git a/docs/t-sql/statements/backup-transact-sql.md b/docs/t-sql/statements/backup-transact-sql.md
@@ -1,7 +1,7 @@
 ---
 title: "BACKUP (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "08/07/2017"
+ms.date: "09/05/2017"
 ms.prod: "sql-non-specified"
 ms.reviewer: ""
 ms.suite: ""
@@ -453,6 +453,8 @@ See "\<backup_device>," earlier in this section.
   
  MAXTRANSFERSIZE **=** { *maxtransfersize* | **@***maxtransfersize_variable* }  
  Specifies the largest unit of transfer in bytes to be used between [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and the backup media. The possible values are multiples of 65536 bytes (64 KB) ranging up to 4194304 bytes (4 MB).  
+> [!NOTE]  
+>  When using SQL Writer (VSS\VDI) if the `MAXTRANSFER` size is set to 4 MB on backup, then 4 MB must be used on restore, otherwise they encounter the following error: **RESTORE requires MAXTRANSFERSIZE=4194304 but 65536 was specified.**  This only happens on [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] databases where FileStream or In-Memory OLTP File Groups are involved.
   
  **Error Management Options**  
   
