3.1.1.9 Staging File Object

  • Article

FRS uses staging files to transfer files between Partners during replication. There is one staging file per file replicated. The staging file for a file to be replicated is created by first writing a STAGE_HEADER to disk. If the replicated file is a reparse point, the STAGE_HEADER is followed by the reparse data. Finally, the file data is written to the staging file. The file data in the staging file can be compressed to save disk space and network bandwidth.

FRS MUST use the format specified in [MS-BKUP] section 2.1 to read and write the replicated file. When the replicated file is installed into the new file system, backup semantics are again used to reconstitute the replicated file from the contents of the staging file. The staging file is sent to downstream partners on request (CMD_SEND_STAGE). See section 3.3.4.4.7.

The staging file object contains the following parts:

  • Staging Header.

  • Reparse Data: Reparse point data. This data only exists if the file is a reparse point. <34>

  • File Data: Contents of the file. This data can be compressed.

For the staging header, reparse data, and file data, see section 2.2.3.10.