The Staging module supports synchronization of the following data:
•Document data - documents in the website content tree. Timeout defined for documents that are part of a workflow is not synchronized for consistency reasons.
•Document attachments - if a document contains attachments or file fields, the files are synchronized together with the document.
•Document relationships - relationships between documents are synchronized if the relationship type and both documents exist on the target server. Synchronization is NOT supported for relationships between documents on different sites.
•Workflow process - only published document versions are synchronized to the target server and both servers need to have the same workflow schemas defined.
•Custom tables and their data.
•Media libraries and the files and folders in them
•Global objects - all global objects except for the cases mentioned in the list below.
The Staging module does not support synchronization of the following data:
•Blog comments (blogs and blog posts are synchronized as documents)
•Contacts (the state of contacts in automation processes is also not synchronized)
•Forms data (the actual form objects are synchronized)
•Forum posts (forum objects are synchronized)
•Message board messages (message board objects are synchronized)
•Physical files associated with global objects (for example web part source file, form control files, ASPX page template files)
You can limit the maximum size of synchronized media library files as described in the Staging large files topic.
Changes in media library files and folders are logged as content staging tasks only when performed via the UI. If you make changes directly in the library folder in the file system, e.g., upload or update files using FTP, the changes are not logged.
Also, if you make a change to a file via the UI and then update the file using FTP, the current file (the one updated using FTP) will be transferred to the target server, even if the staging task was created before the file upload. This happens because binary data of the files are loaded in synchronization time, not when the synchronization task is logged.