what should the network interface setting be in samba to connect to windows network

Applies to SUSE Linux Enterprise Server 15 SP1

35 Samba #Edit source

Abstruse#

Using Samba, a Unix machine can be configured equally a file and print server for macOS, Windows, and Os/2 machines. Samba has developed into a fully-fledged and rather complex product. Configure Samba with YaST, or past editing the configuration file manually.

The post-obit are some terms used in Samba documentation and in the YaST module.

SMB protocol

Samba uses the SMB (server message cake) protocol that is based on the NetBIOS services. Microsoft released the protocol so other software manufacturers could constitute connections to a Microsoft domain network. With Samba, the SMB protocol works on top of the TCP/IP protocol, so the TCP/IP protocol must be installed on all clients.

Tip: IBM Z: NetBIOS Support

IBM Z merely supports SMB over TCP/IP. NetBIOS support is not available on these systems.

CIFS protocol

The CIFS (common Internet file organization) protocol, too known every bit SMB1 is an early on version of the SMB protocol. CIFS defines a standard remote file arrangement access protocol for use over the network, enabling groups of users to piece of work together and share documents across the network. In recent versions of Samba, information technology is disabled past default for security reasons.

NetBIOS

NetBIOS is a software interface (API) designed for advice between machines providing a proper name service. It enables machines connected to the network to reserve names for themselves. After reservation, these machines can exist addressed by name. There is no central process that checks names. Whatsoever car on the network tin can reserve every bit many names as it wants as long equally the names are non already in apply. The NetBIOS interface tin be implemented for dissimilar network architectures. An implementation that works relatively closely with network hardware is called NetBEUI, but this is often called NetBIOS. Network protocols implemented with NetBIOS are IPX from Novell (NetBIOS via TCP/IP) and TCP/IP.

The NetBIOS names sent via TCP/IP have nothing in common with the names used in /etc/hosts or those divers past DNS. NetBIOS uses its ain, completely contained naming convention. However, it is recommended to utilise names that correspond to DNS host names to make administration easier or use DNS natively. This is the default used by Samba.

Samba server

Samba server provides SMB/CIFS services and NetBIOS over IP naming services to clients. For Linux, at that place are three daemons for Samba server: smbd for SMB/CIFS services, nmbd for naming services, and winbind for authentication.

Samba client

The Samba client is a system that uses Samba services from a Samba server over the SMB protocol. Common operating systems, such as Windows and macOS back up the SMB protocol. The TCP/IP protocol must be installed on all computers. Samba provides a customer for the different Unix flavors. For Linux, there is a kernel module for SMB that allows the integration of SMB resources on the Linux system level. You do not demand to run any daemon for the Samba client.

Shares

SMB servers provide resources to the clients by ways of shares. Shares are printers and directories with their subdirectories on the server. It is exported past means of a name and tin can exist accessed by its name. The share name can exist set to any name—it does non need to be the proper name of the consign directory. A printer is also assigned a name. Clients can admission the printer by its name.

DC

A domain controller (DC) is a server that handles accounts in a domain. For data replication, additional domain controllers are available in ane domain.

To install a Samba server, start YaST and select  › . Choose  ›  and select . Confirm the installation of the required packages to finish the installation procedure.

You can beginning or stop the Samba server automatically (during boot) or manually. Starting and stopping policy is a function of the YaST Samba server configuration described in Department 35.4.one, "Configuring a Samba Server with YaST".

From a command line, stop services required for Samba with systemctl stop smb nmb and start them with systemctl get-go nmb smb. The smb service cares about winbind if needed.

Tip: winbind

winbind is an independent service, and as such is also offered every bit an individual samba-winbind packet.

A Samba server in SUSE® Linux Enterprise Server can exist configured in two different ways: with YaST or manually. Manual configuration offers a higher level of particular, but lacks the convenience of the YaST GUI.

To configure a Samba server, start YaST and select  › .

When starting the module for the first fourth dimension, the dialog starts, prompting yous to make a few basic decisions concerning administration of the server. At the end of the configuration, it prompts for the Samba ambassador countersign (). For later starts, the dialog appears.

The dialog consists of two steps and optional detailed settings:

Workgroup or Domain Name

Select an existing name from or enter a new 1 and click .

Samba Server Blazon

In the next step, specify whether your server should act as a primary domain controller (PDC), backup domain controller (BDC), or not deed as a domain controller. Go on with .

If you lot do not desire to go on with a detailed server configuration, ostend with . Then in the final pop-up box, set up the .

You tin change all settings later on in the dialog with the , , , , and tabs.

35.iv.1.two Enabling Current Versions of the SMB Protocol on the Server #Edit source

On clients running electric current versions of SUSE Linux Enterprise Server or other recent Linux versions, the insecure SMB1/CIFS protocol is disabled by default. However, existing instances of Samba may be configured to only serve shares using the SMB1/CIFS version of the protocol. To interact with such clients, y'all need to configure Samba to serve shares using at least the SMB ii.ane protocol.

At that place are setups in which only SMB1 can exist used, for example, because they rely on SMB1's/CIFS's Unix extensions. These extensions take non been ported to newer protocol versions. If y'all are in this state of affairs, consider changing your setup or see Section 35.5.2, "Mounting SMB1/CIFS Shares on Clients".

To exercise and so, in the configuration file /etc/samba/smb.conf, prepare the global parameter server max protocol = SMB2_10. For a list of all possible values, run across human being smb.conf.

During the start kickoff of the Samba server module the dialog appears directly afterwards the 2 initial steps described in Section 35.four.one.1, "Initial Samba Configuration". Use information technology to arrange your Samba server configuration.

After editing your configuration, click to save your settings.

In the tab, configure the start of the Samba server. To showtime the service every time your system boots, select . To activate transmission start, choose . More information about starting a Samba server is provided in Section 35.3, "Starting and Stopping Samba".

In this tab, you can also open up ports in your firewall. To exercise so, select . If you have multiple network interfaces, select the network interface for Samba services by clicking , selecting the interfaces, and clicking .

In the tab, you can determine the domain with which the host is associated () and whether to use an alternative host name in the network (). It is likewise possible to use Microsoft Windows Cyberspace Name Service (WINS) for name resolution. In this case, activate and decide whether to . To set up expert global settings or set a user authentication source, for example LDAP instead of TDB database, click .

To enable users from other domains to access your domain, brand the appropriate settings in the tab. To add a new domain, click . To remove the selected domain, click .

In the tab , you tin can determine the LDAP server to use for authentication. To exam the connectedness to your LDAP server, click . To prepare expert LDAP settings or utilize default values, click .

For more information nigh LDAP configuration, run into Chapter 6, LDAP—A Directory Service.

If you intend to use Samba as a server, install samba. The primary configuration file for Samba is /etc/samba/smb.conf. This file can be divided into two logical parts. The [global] section contains the central and global settings. The following default sections incorporate the individual file and printer shares:

• [homes]

• [profiles]

• [users]

• [groups]

• [printers]

• [impress$]

Using this approach, options of the shares tin be set differently or globally in the [global] section, which makes the configuration file easier to understand.

The following parameters of the [global] section should be modified to match the requirements of your network setup, and then other machines can admission your Samba server via SMB in a Windows environment.

workgroup = WORKGROUP

This line assigns the Samba server to a workgroup. Supervene upon WORKGROUP with an appropriate workgroup of your networking environment. Your Samba server appears under its DNS name unless this name has been assigned to some other machine in the network. If the DNS name is not available, set the server proper noun using netbiosname=MYNAME . For more than details about this parameter, encounter the smb.conf homo page.

os level = 20

This parameter triggers whether your Samba server tries to become LMB (local master browser) for its workgroup. Choose a very depression value such as 2 to spare the existing Windows network from any interruptions caused by a misconfigured Samba server. More information near this topic tin exist plant in the Network Browsing chapter of the Samba iii Howto; for more information on the Samba three Howto, run into Department 35.9, "For More Information".

If no other SMB server is in your network (such every bit a Windows 2000 server) and you want the Samba server to keep a list of all systems present in the local surroundings, set the os level to a higher value (for example, 65). Your Samba server is then chosen as LMB for your local network.

When changing this setting, consider advisedly how this could affect an existing Windows network environment. First exam the changes in an isolated network or at a noncritical time of mean solar day.

wins support and wins server

To integrate your Samba server into an existing Windows network with an agile WINS server, enable the wins server pick and set its value to the IP address of that WINS server.

If your Windows machines are connected to carve up subnets and need to nonetheless exist enlightened of each other, you have to ready a WINS server. To turn a Samba server into such a WINS server, set up the option wins support = Yes. Make sure that just one Samba server of the network has this setting enabled. The options wins server and wins support must never exist enabled at the same fourth dimension in your smb.conf file.

To improve security, each share access can be protected with a countersign. SMB offers the following ways of checking permissions:

User Level Security (security = user)

This variant introduces the concept of the user to SMB. Each user must annals with the server with their own password. After registration, the server tin grant access to individual exported shares dependent on user names.

ADS Level Security (security = ADS)

In this mode, Samba will deed as a domain member in an Active Directory environs. To operate in this fashion, the auto running Samba needs Kerberos installed and configured. You must join the machine using Samba to the ADS realm. This can exist done using the YaST module.

Domain Level Security (security = domain)

This manner will only work correctly if the machine has been joined into a Windows NT Domain. Samba will try to validate user name and password by passing it to a Windows NT Primary or Backup Domain Controller. The same way as a Windows NT Server would do. It expects the encrypted passwords parameter to be set to yeah.

The selection of share, user, server, or domain level security applies to the entire server. It is not possible to offer individual shares of a server configuration with share level security and others with user level security. However, you can run a split up Samba server for each configured IP address on a system.

More than information virtually this bailiwick can exist found in the Samba three HOWTO. For multiple servers on ane arrangement, pay attention to the options interfaces and demark interfaces simply.

Clients can only access the Samba server via TCP/IP. NetBEUI and NetBIOS via IPX cannot be used with Samba.

Configure a Samba client to access resources (files or printers) on the Samba or Windows server. Enter the NT or Agile Directory domain or workgroup in the dialog  › . If y'all activate , the user authentication runs over the Samba, NT or Kerberos server.

Click for advanced configuration options. For example, use the tabular array to enable mounting server dwelling house directory automatically with hallmark. This style users tin can access their dwelling house directories when hosted on CIFS. For details, meet the pam_mount human being page.

After completing all settings, confirm the dialog to cease the configuration.

The first version of the SMB network protocol, SMB1 or CIFS, is an former and insecure protocol which has been deprecated by its originator, Microsoft. For security reasons, the mount command on SUSE Linux Enterprise Server volition only mount SMB shares using newer protocol versions by default, namely SMB two.one, SMB three.0, or SMB 3.02.

However, this change only affects mountain and mounting via /etc/fstab. SMB1 is still bachelor past explicitly requiring information technology. Apply the post-obit control:

• The smbclient tool.

• The Samba server software shipped with SUSE Linux Enterprise Server.

There are setups in which this default setting volition lead to connexion failures, because only SMB1 tin be used:

• Setups using an SMB server that does not support newer SMB protocol versions. Windows has offered SMB 2.1 back up since Windows vii and Windows Server 2008.

• Setups that rely on SMB1'south/CIFS's Unix extensions. These extensions have non been ported to newer protocol versions.

If you demand to enable SMB1 shares on the current SUSE Linux Enterprise Server kernel, add the option vers=1.0 to the mount command line you apply:

                root #                mount -t cifs //HOST/SHARE                /MOUNT_POINT                –o username=USER_ID,                  vers=1.0                              

Alternatively, you lot can enable SMB1 shares globally within your SUSE Linux Enterprise Server installation. To do so, add the following to /etc/samba/smb.conf nether the section [global]:

                client min protocol = Core

In enterprise settings, it is often desirable to permit admission only to users registered on a key instance. In a Windows-based network, this task is handled past a master domain controller (PDC). You tin use a Windows NT server configured as PDC, merely this task can as well be done with a Samba server. The entries that must be made in the [global] section of smb.conf are shown in Instance 35.three, "Global Section in smb.conf".

Example 35.3: Global Section in smb.conf #

[global]     workgroup = WORKGROUP     domain logons = Yes     domain main = Yes

It is necessary to prepare user accounts and passwords in an encryption format that conforms with Windows. Practice this with the command smbpasswd -a name. Create the domain account for the computers, required by the Windows domain concept, with the following commands:

useradd hostname smbpasswd -a -one thousand hostname

With the useradd command, a dollar sign is added. The command smbpasswd inserts this automatically when the parameter -m is used. The commented configuration instance (/usr/share/medico/packages/samba/examples/smb.conf.SUSE) contains settings that automate this job.

add machine script = /usr/sbin/useradd -1000 nogroup -c "NT Machine Account" \ -s /bin/false %chiliad

To make sure that Samba can execute this script correctly, choose a Samba user with the required administrator permissions and add it to the ntadmin group. Then all users belonging to this Linux group tin be assigned Domain Admin status with the command:

cyberspace groupmap add together ntgroup="Domain Admins" unixgroup=ntadmin

35.7 Samba Server in the Network with Active Directory #Edit source

If you run Linux servers and Windows servers together, you can build two independent authentication systems and networks or connect servers to one network with one central hallmark organisation. Because Samba can cooperate with an agile directory domain, yous can join your SUSE Linux Enterprise Server server with an Agile Directory (AD) domain.

To join an AD domain go along as follows:

1. Log in as root and start YaST.

2. Starting time  › .

3. Enter the domain to join at in the screen.

   

   Figure 35.1: Determining Windows Domain Membership #

4. Cheque to employ the SMB source for Linux authentication on your server.

5. Click and confirm the domain bring together when prompted for it.

6. Provide the countersign for the Windows Administrator on the AD server and click .

   Your server is at present fix to pull in all authentication information from the Active Directory domain controller.

Tip: Identity Mapping

In an environs with more than than 1 Samba server, UIDs and GIDs will not be created consistently. The UIDs that go assigned to users will be dependent on the order in which they first log in, which results in UID conflicts across servers. To fix this, y'all need to use identity mapping. Run across https://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/idmapper.html for more details.

This department introduces more advanced techniques to manage both the customer and server part of the Samba suite.

Samba allows clients to remotely manipulate file and directory pinch flags for shares placed on the Btrfs file arrangement. Windows Explorer provides the ability to flag files/directories for transparent compression via the  ›  ›  dialog:

Figure 35.2: Windows Explorer Dialog #

Files flagged for compression are transparently compressed and decompressed by the underlying file system when accessed or modified. This ordinarily results in storage chapters savings at the expense of extra CPU overhead when accessing the file. New files and directories inherit the compression flag from the parent directory, unless created with the FILE_NO_COMPRESSION pick.

Windows Explorer presents compressed files and directories visually differently to those that are non compressed:

Figure 35.iii: Windows Explorer Directory List with Compressed Files #

Yous can enable Samba share compression either manually by adding

to the share configuration in /etc/samba/smb.conf, or using YaST:  ›  › , and checking .

A full general overview of compression on Btrfs can be found in Section 1.2.2.i, "Mounting Compressed Btrfs File Systems".

Snapshots, also called Shadow Copies, are copies of the state of a file system subvolume at a certain point of time. Snapper is the tool to manage these snapshots in Linux. Snapshots are supported on the Btrfs file arrangement or thinly-provisioned LVM volumes. The Samba suite supports managing remote snapshots through the FSRVP protocol on both the server and customer side.

Snapshots on a Samba server can be exposed to remote Windows clients equally file or directory previous versions.

To enable snapshots on a Samba server, the following atmospheric condition must be fulfilled:

• The SMB network share resides on a Btrfs subvolume.

• The SMB network share path has a related snapper configuration file. You can create the snapper file with

                          tux >                                                sudo                        snapper -c <cfg_name> create-config                        /path/to/share                      

  For more information on snapper, see Affiliate 7, Organisation Recovery and Snapshot Management with Snapper.

• The snapshot directory tree must allow access for relevant users. For more than information, run into the PERMISSIONS section of the vfs_snapper transmission page (man 8 vfs_snapper).

To support remote snapshots, yous need to modify the /etc/samba/smb.conf file. You lot can practise it either with  ›  › , or manually past enhancing the relevant share section with

Notation that you need to restart the Samba service for manual smb.conf changes to take effect:

                  tux >                                    sudo                  systemctl restart nmb smb

Figure 35.iv: Adding a New Samba Share with Snapshotting Enabled #

Afterward being configured, snapshots created by snapper for the Samba share path can be accessed from Windows Explorer from a file or directory'south tab.

Figure 35.v: The tab in Windows Explorer #

By default, snapshots can merely be created and deleted on the Samba server locally, via the snapper command line utility, or using snapper'southward fourth dimension line feature.

Samba can be configured to procedure share snapshot cosmos and deletion requests from remote hosts using the File Server Remote VSS Protocol (FSRVP).

In improver to the configuration and prerequisites documented in Section 35.eight.2.1, "Previous Versions", the following global configuration is required in /etc/samba/smb.conf:

[global] rpc_daemon:fssd = fork registry shares = yes include = registry

FSRVP clients, including Samba's rpcclient and Windows Server 2012 DiskShadow.exe, can so instruct Samba to create or delete a snapshot for a given share, and betrayal the snapshot equally a new share.

35.8.ii.3 Managing Snapshots Remotely from Linux with rpcclient #Edit source

The samba-client package contains an FSRVP client that tin remotely request a Windows/Samba server to create and expose a snapshot of a given share. You can then employ existing tools in SUSE Linux Enterprise Server to mount the exposed share and support its files. Requests to the server are sent using the rpcclient binary.

Case 35.four: Using rpcclient to Request a Windows Server 2012 Share Snapshot #

Connect to win-server.example.com server as an administrator in an EXAMPLE domain:

                      root #                      rpcclient -U 'Example\Administrator' ncacn_np:win-server.example.com[ndr64,sign] Enter Example/Administrator'due south password:

Check that the SMB share is visible for rpcclient:

                      root #                      rpcclient $> netshareenum netname: windows_server_2012_share remark: path:   C:\Shares\windows_server_2012_share countersign:       (null)

Check that the SMB share supports snapshot cosmos:

                      root #                      rpcclient $> fss_is_path_sup windows_server_2012_share \ UNC \\WIN-SERVER\windows_server_2012_share\ supports shadow copy requests

Request the cosmos of a share snapshot:

                      root #                      rpcclient $> fss_create_expose backup ro windows_server_2012_share 13fe880e-e232-493d-87e9-402f21019fb6: shadow-re-create set created 13fe880e-e232-493d-87e9-402f21019fb6(1c26544e-8251-445f-be89-d1e0a3938777): \ \\WIN-SERVER\windows_server_2012_share\ shadow-copy added to ready 13fe880e-e232-493d-87e9-402f21019fb6: gear up completed in 0 secs 13fe880e-e232-493d-87e9-402f21019fb6: commit completed in 1 secs 13fe880e-e232-493d-87e9-402f21019fb6(1c26544e-8251-445f-be89-d1e0a3938777): \ share windows_server_2012_share@{1C26544E-8251-445F-BE89-D1E0A3938777} \ exposed equally a snapshot of \\WIN-SERVER\windows_server_2012_share\

Confirm that the snapshot share is exposed by the server:

                      root #                      rpcclient $> netshareenum netname: windows_server_2012_share remark: path:   C:\Shares\windows_server_2012_share password:       (zip)  netname: windows_server_2012_share@{1C26544E-8251-445F-BE89-D1E0A3938777} remark: (zippo) path:   \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy{F6E6507E-F537-11E3-9404-B8AC6F927453}\Shares\windows_server_2012_share\ password:       (null)

Effort to delete the snapshot share:

                      root #                      rpcclient $> fss_delete windows_server_2012_share \ 13fe880e-e232-493d-87e9-402f21019fb6 1c26544e-8251-445f-be89-d1e0a3938777 13fe880e-e232-493d-87e9-402f21019fb6(1c26544e-8251-445f-be89-d1e0a3938777): \ \\WIN-SERVER\windows_server_2012_share\ shadow-copy deleted

Confirm that the snapshot share has been removed past the server:

                      root #                      rpcclient $> netshareenum netname: windows_server_2012_share remark: path:   C:\Shares\windows_server_2012_share password:       (null)

35.8.ii.4 Managing Snapshots Remotely from Windows with DiskShadow.exe #Edit source

You tin can manage snapshots of SMB shares on the Linux Samba server from the Windows environment acting as a customer as well. Windows Server 2012 includes the DiskShadow.exe utility that can manage remote shares like to the rpcclient described in Section 35.8.2.3, "Managing Snapshots Remotely from Linux with rpcclient". Notation that you need to carefully ready upwards the Samba server first.

Post-obit is an example process to set upwards the Samba server so that the Windows Server client can manage its share'southward snapshots. Note that Example is the Active Directory domain used in the testing environment, fsrvp-server.instance.com is the host name of the Samba server, and /srv/smb is the path to the SMB share.

Procedure 35.one: Detailed Samba Server Configuration #

1. Join Active Directory domain via YaST. For more than data, Department 35.7, "Samba Server in the Network with Agile Directory".

2. Ensure that the Active Domain DNS entry was correct:

   fsrvp-server:~ # net -U 'Administrator' ads dns register \ fsrvp-server.example.com <IP address> Successfully registered hostname with DNS

3. Create Btrfs subvolume at /srv/smb

   fsrvp-server:~ # btrfs subvolume create /srv/smb

4. Create snapper configuration file for path /srv/smb

   fsrvp-server:~ # snapper -c <snapper_config> create-config /srv/smb

5. Create new share with path /srv/smb, and YaST check box enabled. Make sure to add the post-obit snippets to the global department of /etc/samba/smb.conf equally mentioned in Section 35.8.two.2, "Remote Share Snapshots":

   [global]  rpc_daemon:fssd = fork  registry shares = yes  include = registry

6. Restart Samba with systemctl restart nmb smb

7. Configure snapper permissions:

   fsrvp-server:~ # snapper -c <snapper_config> set-config \ ALLOW_USERS="Case\\\\Ambassador Case\\\\win-client$"

   Ensure that any ALLOW_USERS are too permitted traversal of the .snapshots subdirectory.

   fsrvp-server:~ # snapper -c <snapper_config> set up-config SYNC_ACL=yeah

   

   Of import: Path Escaping

   Be conscientious about the '\' escapes! Escape twice to ensure that the value stored in /etc/snapper/configs/<snapper_config> is escaped once.

   "Case\win-client$" corresponds to the Windows client computer account. Windows problems initial FSRVP requests while authenticated with this account.

8. Grant Windows client account necessary privileges:

   fsrvp-server:~ # internet -U 'Administrator' rpc rights grant \ "EXAMPLE\\win-customer$" SeBackupPrivilege Successfully granted rights.

   The previous command is not needed for the "EXAMPLE\Administrator" user, which has privileges already granted.

Procedure 35.2: Windows Client Setup and DiskShadow.exe in Action #

1. Boot Windows Server 2012 (example host name WIN-Client).

2. Join the same Active Directory domain Example as with the SUSE Linux Enterprise Server .

3. Reboot.

4. Open Powershell.

5. Starting time DiskShadow.exe and begin the fill-in process:

   PS C:\Users\Administrator.Case> diskshadow.exe Microsoft DiskShadow version 1.0 Copyright (C) 2012 Microsoft Corporation On estimator:  WIN-Client,  half dozen/17/2014 3:53:54 PM  DISKSHADOW> begin fill-in

6. Specify that shadow copy persists beyond program exit, reset or reboot:

   DISKSHADOW> gear up context PERSISTENT

7. Check whether the specified share supports snapshots, and create one:

   DISKSHADOW> add volume \\fsrvp-server\sles_snapper  DISKSHADOW> create Alias VSS_SHADOW_1 for shadow ID {de4ddca4-4978-4805-8776-cdf82d190a4a} set up every bit \  environment variable. Alias VSS_SHADOW_SET for shadow set ID {c58e1452-c554-400e-a266-d11d5c837cb1} \  set as environs variable.  Querying all shadow copies with the shadow copy set ID \  {c58e1452-c554-400e-a266-d11d5c837cb1}   * Shadow copy ID = {de4ddca4-4978-4805-8776-cdf82d190a4a}     %VSS_SHADOW_1%     - Shadow copy gear up: {c58e1452-c554-400e-a266-d11d5c837cb1}  %VSS_SHADOW_SET%     - Original count of shadow copies = ane     - Original volume name: \\FSRVP-SERVER\SLES_SNAPPER\ \       [volume not on this auto]     - Creation time: 6/17/2014 3:54:43 PM     - Shadow re-create device proper name:       \\FSRVP-SERVER\SLES_SNAPPER@{31afd84a-44a7-41be-b9b0-751898756faa}     - Originating motorcar: FSRVP-SERVER     - Service machine: win-client.example.com     - Not exposed     - Provider ID: {89300202-3cec-4981-9171-19f59559e0f2}     - Attributes:  No_Auto_Release Persistent FileShare  Number of shadow copies listed: ane

8. Cease the backup procedure:

9. After the snapshot was created, try to delete information technology and verify the deletion:

   DISKSHADOW> delete shadows volume \\FSRVP-SERVER\SLES_SNAPPER\ Deleting shadow copy {de4ddca4-4978-4805-8776-cdf82d190a4a} on volume \  \\FSRVP-SERVER\SLES_SNAPPER\ from provider \ {89300202-3cec-4981-9171-19f59559e0f2} [Attributes: 0x04000009]...  Number of shadow copies deleted: i  DISKSHADOW> list shadows all  Querying all shadow copies on the computer ... No shadow copies found in system.

• Man Pages: To run across a list of all man pages installed with the package samba, run concerning samba. Open up whatever of the human being pages with man NAME_OF_MAN_PAGE .

• SUSE-specific README file: The packet samba-customer contains the file /usr/share/physician/packages/samba/README.SUSE.

• Additional Packaged Documentation: Install the bundle samba-md with zypper install samba-doc.

  This documentation installs into /usr/share/doc/packages/samba. Information technology contains an HTML version of the human being pages and a library of example configurations (such as smb.conf.SUSE).

• Online Documentation: The Samba wiki contains extensive User Documentation at https://wiki.samba.org/index.php/User_Documentation.

thornskeethe1959.blogspot.com

Source: https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-samba.html

Share this post