Attachment 6737 Details for Bug 37933

file share docs (EN)

migrate-fileshares-en.xml (text/xml), 4.25 KB, created by Moritz Muehlenhoff on 2015-03-04 10:51 CET

(hide)

Description:

Filename:

MIME Type:

Creator: Moritz Muehlenhoff

Created: 2015-03-04 10:51 CET

Size: 4.25 KB

patch

obsolete

>	<section id="bestpractice:migration:fileshare">
>	  <title>Migration of file shares</title>
>
>	  <para>
>		Every UCS Samba server (domain controllers and member servers) provides file services by
>		default. There is no standardised tool available for the migration of file shares on Windows
>		servers: the shares must be re-created on the UCS server and the data copied.	
>	  </para>
>
>	  <para>
>		To achieve a correct takeover of the file permissions, the AD server must access the same
>		user base. This can be achieved in two ways:
>
>		<itemizedlist>
>		  <listitem><simpara>
>			The AD server is joined in the UCS domain as a member server.
>		  </simpara></listitem>
>
>		  <listitem><simpara>
>			The AD server is a domain controller and temporarily joins the UCS domain during an AD
>			takeover migration (before it is permanently switched off).
>		  </simpara></listitem>
>		</itemizedlist>
>
>		The file ownership rights of the files are saved on the AD server using the SID
>		information. If the files of the file server were migrated to the UCS system before the user
>		data were available, it would not be subsequently possible to assign the files to individual
>		users without additional efforts.
>	  </para>
>
>	  <para>
>		The file shares available on an AD server can be found under <guimenu>Start ->
>		Administrative Tools -> Share and Storage Management </guimenu> The <guimenu>Shares</guimenu> tab
>		lists all the published shares. The <guimenu>Properties</guimenu> section in the context
>		menu of a share lists the properties of the share. In the following example, a share with
>		the name <emphasis>Documentation</emphasis>, which provides the path
>		<filename class="directory">C:\Documentation</filename> under the share path
>		<uri>\\ADSERVER\Documentation</uri>.
>
>		<figure id="bestpractice-migrate-cifs">
>		  <title>The file share to migrate</title>
>		  <graphic scalefit="1" width="80%" fileref="illustrations/cifs-migrate-en.png"/>
>		</figure>
>
>		A share is now created in the share management of the &ucsUMC;. The share module offers a
>		range of possibilities, which are documented in the UCS manual <biblioref
>		linkend="ucs-shares"/>. However, just a few settings are enough for the takeover of the
>		data. The following values need to be saved as a minimum when creating the share(s) in the
>		UMC module <guimenu>Shares</guimenu>:
>
>		<itemizedlist>
>		  <listitem><simpara>
>			<emphasis>Name</emphasis>: The name that the share uses in Windows. The rules for the
>			shares are stricter in UCS than in AD. If the name used in Windows is not permitted, an
>			additional name can be configured in the <guimenu>Samba name</guimenu> tab, which is
>			displayed during access via CIFS. The name does not necessarily need to be
>			identical. Nevertheless, to minimise irritations among the users, it is recommended.
>		  </simpara></listitem>
>
>		  <listitem><simpara>
>			<emphasis>Host</emphasis>: The UCS server providing the file share
>		  </simpara></listitem>
>
>		  <listitem><simpara>
>			<emphasis>Directory</emphasis>: The path under which the share data are saved on the UCS
>			server. It the path does not already exist, it will be created automatically. The rights
>			of the directory can be found under <emphasis>Permissions for the shares' root
>			directory</emphasis>.
>		  </simpara></listitem>
>		</itemizedlist>
>	  </para>
>
>	  <para>
>		The share data is now copied from the Windows server to the UCS system. A login is then
>		performed on the Windows server and the data is copied with <command>robocopy</command>
>		(preinstalled as of Windows 2008 and can be subsequently installed with the Windows Server
>		2003 Resource Kit Tools in Windows 2003). Example:
>
>		<programlisting language="sh">
>		  robocopy /mir /sec /z \\ADSERVER\Documentation \\UCSSERVER\Documentation
>		</programlisting>
>
>		Then the access to the share on the UCS server should be tested from a Windows client. All
>		the permissions should still be correctly applied. 
>	  </para>
>
>	  <para>
>		To prevent further changes to the share on the Windows server, the share on the Windows
>		server should be disabled following migration of the data. This is done by selecting the
>		<guimenu>Stop sharing</guimenu> option in the context menu of the migrated share under
>		<guimenu>Start -> Administrative Tools -> Share and Storage Management</guimenu>.
>	  </para>
>
>	</section>

Actions: View

Attachments on bug 37933: 6736 | 6737 | 6738 | 6739 | 6740