summaryrefslogtreecommitdiff
path: root/m4
diff options
context:
space:
mode:
authorDavid Disseldorp <ddiss@samba.org>2012-03-26 17:34:52 +0200
committerDavid Disseldorp <ddiss@samba.org>2012-06-08 13:34:31 +0200
commitac7b60a17bd4c4dbfaa2d9bb9e1d246800940928 (patch)
tree4efe314ee131bfbf69b55bbfbe6c248fd14c2b3b /m4
parent2836787daa8e78efc7dd166c4f462ca392b3c4c2 (diff)
downloadsamba-ac7b60a17bd4c4dbfaa2d9bb9e1d246800940928.tar.gz
samba-ac7b60a17bd4c4dbfaa2d9bb9e1d246800940928.tar.bz2
samba-ac7b60a17bd4c4dbfaa2d9bb9e1d246800940928.zip
s3-rpcclient: add fsrvp commands
fss_create_expose connects to an FSRVP server and negotiates the creation and exposure of a share shadow-copy. shadow-copies of multiple shares can be requested with a single fss_create_expose request. ddiss@plati:~> bin/rpcclient -k -U 'LURCH\administrator%password' \ ncacn_np:lutze[sign] rpcclient $> fss_create_expose backup ro hyper 381884f2-b578-45ea-b8d2-cf82491f4011: shadow-copy set created ... share hyper@{B6137E21-9CBB-4547-A21D-E7AD40D0874B} exposed as a snapshot of \\lutze\hyper fss_delete removes the shadow-copy share: rpcclient $> fss_delete hyper 381884f2-b578-45ea-b8d2-cf82491f4011 \ b6137e21-9cbb-4547-a21d-e7ad40d0874 Shadow-copies can be created read-write or read-only. Experimenting with Windows Server "8" beta, a recovery complete call is required after creating a read-write (ATTR_AUTO_RECOVERY) shadow copy. Otherwise subsequent creation requests fail with FSRVP_E_SHADOW_COPY_SET_IN_PROGRESS.
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions