samba.git/source3/rpcclient/cmd_fss.c, branch talloc-2.3.2

s3:rpcclient: Use C99 initializer for cmd_set in cmd_fss

2019-01-28T09:29:18+00:00

Signed-off-by: Andreas Schneider 
Reviewed-by: Douglas Bagnall

fsrvp: define FSRVP_E_SHADOWCOPYSET_ID_MISMATCH

2014-11-14T22:27:04+00:00

This was recently added to the [MS-FSRVP] specification with the errata
http://msdn.microsoft.com/en-us/library/dn785066.aspx#BKMK_FSRVP

Signed-off-by: David Disseldorp 
Reviewed-by: Jeremy Allison

Allow FSRVP access generic HRESULT error message descriptions

2014-04-02T18:25:07+00:00

FSRVP can possibly return any HRESULT error in addition to it's own
specific errors. This change searches the HRESULT errors for a description
if the error doesn't match any of the known FSRVP ones.
Also removed some errors defined in fsrvp.idl (now that they are defined
in hresult.h)

Signed-off-by: Noel Power 
Reviewed-by: David Disseldorp 
Reviewed-by: Stefan Metzmacher

rpcclient: abort shadow-copy set on commit failure

2014-03-31T22:54:05+00:00

Use similar behaviour to the diskshadow.exe FSRVP client, which aborts
the shadow-copy set if it receives a failed commit response.

Signed-off-by: David Disseldorp 
Reviewed-by: Jeremy Allison 

Autobuild-User(master): Jeremy Allison 
Autobuild-Date(master): Tue Apr  1 00:54:06 CEST 2014 on sn-devel-104

rpcclient: append a trailing slash to FSRVP request UNCs

2014-03-31T20:52:14+00:00

The Windows Server 2012 FSRVP server exhibits strange behaviour when
exposing hidden shadow copy shares. If the hidden share UNC in the
AddToShadowCopySet request includes a trailing backslash (e.g.
"\\server\share$\"), then the new shadow-copy share will also be hidden
(e.g. "\\server\share$@{ShadowCopy.ShadowCopyId}$").
However, if the UNC does not include a trailing backslash, which until
now was rpcclient's default behaviour, then the exposed shadow-copy
share is not hidden.

Thanks to the MS Open Specifications team for helping me track down this
one.

bug: https://bugzilla.samba.org/show_bug.cgi?id=10521

Signed-off-by: David Disseldorp 
Reviewed-by: Jeremy Allison

For FSRVP use textual error messages instead of hex error codes

2014-03-08T02:52:42+00:00

Signed-off-by: Noel Power 
Reviewed-by: David Disseldorp 
Reviewed-by: Jeremy Allison 

Autobuild-User(master): Jeremy Allison 
Autobuild-Date(master): Sat Mar  8 03:52:44 CET 2014 on sn-devel-104

Fix compiler warning message.

2012-07-23T22:09:46+00:00

Fix warnings using %lu to print a 64-bit value (should by %llu).

2012-06-19T17:27:23+00:00

s3-rpcclient: add fsrvp commands

2012-06-08T11:34:31+00:00

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.