Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

vfs_media_harmony(8) [centos man page]

VFS_MEDIA_HARMONY(8)					    System Administration tools 				      VFS_MEDIA_HARMONY(8)

NAME

       vfs_media_harmony - Allow multiple Avid clients to share a network drive.

SYNOPSIS

       vfs objects = media_harmony

DESCRIPTION

       This VFS module is part of the samba(7) suite.

       The vfs_media_harmony VFS module allows Avid editorial workstations to share a network drive. It does this by:

	1. Giving each client their own copy of the Avid msmMMOB.mdb and msmFMID.pmr files and Creating directories.

	2. Allowing each client to explicitly control the write time the Avid application sees on Avid media directories.

       This module is stackable.

CONFIGURATION

       vfs_media_harmony automatically redirects requests from clients for Avid database files or an Avid Creating directory to a client-specific
       version of the file. No configuration beyond enabling the module is needed to get this portion of its functionality working.

       If Mac and Windows Avid clients will be accessing the same folder, they should be given separate share definitions, with hidden Mac files
       vetoed on the Windows share. See EXAMPLES.

       To allow each client to control when the Avid application refreshes their Avid databases, create files for each client and each Avid media
       directory with the name [avid_dir_name]_[client_ip_address]_[client_username]. To trigger Avid database refreshes, update the write time on
       those files. See EXAMPLES.

       It is also necessary for the cache locked write times = no option to be set for clients to be able to control their Avid media folder write
       times.

EXAMPLES

       Enable media_harmony for Mac and Windows clients:

		   [avid_mac]
		path = /avid
		vfs objects = media_harmony
		cache locked write times = no
		   [avid_win]
		path = /avid
		vfs objects = media_harmony
		cache locked write times = no
		veto files = /.DS_Store/._@/.Trash@/.Spotlight@/.hidden/.hotfiles@/.vol/
		delete veto files = yes

       Create the files that will allow users david and susan to control their own Avid database refreshes:

		touch '/avid/OMFI MediaFiles_192.168.1.10_david' 
		     '/avid/OMFI MediaFiles_192.168.1.11_susan' 
		     '/avid/Avid MediaFiles/MXF/1_192.168.1.10_david' 
		     '/avid/Avid MediaFiles/MXF/1_192.168.1.11_susan'

       Trigger an Avid database refresh for user david:

		touch '/avid/OMFI MediaFiles_192.168.1.10_david' 
		     '/avid/Avid MediaFiles/MXF/1_192.168.1.10_david'

       If you have a large number of Avid media folders to manage, you can give each editor a suitably modified version of
       examples/scripts/vfs/media_harmony/trigger_avid_update.py to create and update these files.

CAVEATS

       vfs_media_harmony is designed to work with Avid editing applications that look in the Avid MediaFiles or OMFI MediaFiles directories for
       media. It is not designed to work as expected in all circumstances for general use. For example: It is possible to open a client-specific
       file such as msmMMOB.mdb_192.168.1.10_userx even though it doesn't show up in a directory listing.

VERSION

       This man page is correct for version 3.2.7 of the Samba suite.

AUTHOR

       The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open
       Source project similar to the way the Linux kernel is developed.

Samba 4.0							    06/17/2014						      VFS_MEDIA_HARMONY(8)

Check Out this Related Man Page

VFS_SHADOW_COPY(8)					    System Administration tools 					VFS_SHADOW_COPY(8)

NAME

       vfs_shadow_copy - Make a Samba share read only for a specified time period

SYNOPSIS

       vfs objects = shadow_copy

DESCRIPTION

       This VFS module is part of the samba(7) suite.

       The vfs_shadow_copy VFS module functionality that is similar to Microsoft Shadow Copy services. When setup properly, this module allows
       Microsoft Shadow Copy clients to browse "shadow copies" on Samba shares.

       This module is stackable.

CONFIGURATION

       vfs_shadow_copy relies on a filesystem snapshot implementation. Many common filesystems have native support for this.

       Filesystem snapshots must be mounted on specially named directories in order to be recognized by vfs_shadow_copy. The snapshot mount points
       must be immediate children of a the directory being shared.

       The snapshot naming convention is @GMT-YYYY.MM.DD-hh.mm.ss, where:

       o   YYYY is the 4 digit year

       o   MM is the 2 digit month

       o   DD is the 2 digit day

       o   hh is the 2 digit hour

       o   mm is the 2 digit minute

       o   ss is the 2 digit second.

       The vfs_shadow_copy snapshot naming convention can be produced with the following date(1) command:

		TZ=GMT date +@GMT-%Y.%m.%d-%H.%M.%S

EXAMPLES

       Add shadow copy support to user home directories:

		   [homes]
		vfs objects = shadow_copy

CAVEATS

       This is not a backup, archival, or version control solution.

       With Samba or Windows servers, vfs_shadow_copy is designed to be an end-user tool only. It does not replace or enhance your backup and
       archival solutions and should in no way be considered as such. Additionally, if you need version control, implement a version control
       system.

VERSION

       This man page is correct for version 3.0.25 of the Samba suite.

AUTHOR

       The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open
       Source project similar to the way the Linux kernel is developed.

Samba 4.0							    06/17/2014							VFS_SHADOW_COPY(8)
Man Page