Difference between revisions of "Server-Side Copy"
(add details for FSCTL_DUPLICATE_EXTENTS_TO_FILE)
m (fix categories)
|Line 150:||Line 150:|
Revision as of 11:44, 18 May 2018
Samba 4.1.0 was the first release to ship with support for server-side copy operations via the SMB2 FSCTL_SRV_COPYCHUNK request. Clients making use of server-side copy support, such as Windows Server 2012 and Windows 8, can experience considerable performance improvements for file copy operations, as file data need not traverse the network. This feature is enabled by default on the smbd file server.
Samba 4.7.0 introduced support for FSCTL_DUPLICATE_EXTENTS_TO_FILE, which similarly allows for offloaded clone operations.
- Windows Server 2012 and later: via Windows Explorer or Robocopy
- Windows 8 and later: via Windows Explorer or Robocopy
- Windows Server 2008: via Robocopy only
- Windows 7: via Robocopy only
For other tools, ask the respective vendor for SMB2 FSCTL_SRV_COPYCHUNK support.
The Linux Kernel CIFS client includes support for issuing SMB2 FSCTL_SRV_COPYCHUNK_WRITE server-side copy requests. This feature can currently only be utilised by issuing a special CIFS_IOC_COPYCHUNK_FILE ioctl, as done by cloner in the xfstests Git repository.
FSCTL_SRV_COPYCHUNK works with any filesystem backing the Samba share. There are some additional improvements for Btrfs in comparison with other filesystems. FSCTL_DUPLICATE_EXTENTS_TO_FILE is currently only supported atop Btrfs.
Traditional File Copy
Prior to Samba 4.1.0, clients traditionally copied files by reading the source file data over the network and writing it back to the server through to the destination file on disk.
Server-Side Copy Offload
With Samba 4.1.0 and later, clients can offload copy operations to the server using Copy-Chunk requests. In processing such a request, the network round-trip is avoided.
Samba's smbd file server supports SMB2 Copy-Chunk requests by default, no additional configuration is required.
- The client must support, and issue SMB2 FSCTL_SRV_COPYCHUNK server-side copy requests.
- Both source and destination files must reside on the same Samba share!
Btrfs Enhanced Server-Side Copy Offload
Along with server-side copy support, a Btrfs specific Samba VFS Module was newly added with 4.1.0. This module improves the performance and efficiency of server-side copy operations on Btrfs backed shares, by using the Btrfs clone-range IOCTL. As of Samba 4.7.0, the VFS Module also offers support for FSCTL_DUPLICATE_EXTENTS_TO_FILE.
Btrfs enhanced server-side copy can be enabled in smb.conf on a per share basis with:
[share] path = /mnt/btrfs_fs/ # must reside within a Btrfs filesystem vfs objects = btrfs
- The client's FSCTL_SRV_COPYCHUNK or FSCTL_DUPLICATE_EXTENTS_TO_FILE server-side copy request must be Btrfs filesystem aligned.
- Otherwise, Samba FSCTL_SRV_COPYCHUNK falls back to a regular server-side copy.
- FSCTL_DUPLICATE_EXTENTS_TO_FILE does not offer any local fall back, and instead leaves it up to the client.
- All other limitations associated with regular server-side copies.
Offload Data Transfer (ODX)
ODX makes use of the FSCTL_OFFLOAD_READ and FSCTL_OFFLOAD_WRITE requests, such that the underlying storage subsystem independently transfers data, represented by tokens, between source and destination. This allows for offloaded data transfer between independent servers, provided that they are connected to an intelligent storage subsystem capable of generating and handling the ODX tokens. See Neal Christiansen's SNIA SDC slides for further details.
Samba does not currently support ODX - SMB2 FSCTL_SRV_COPYCHUNK server-side copies offer similar benefits, without the need for an ODX capable storage array or emulation within Samba.