Using Shared Storage With Jet

There are two methods for setting up a Signiant SDCX Server to use a shared storage location via a UNC path. You can configure the shared storage file server to allow access when using accounts local to the storage server, such as the local System account, or you can configure Jet to run as an account that has access to the shared storage.

To configure Jet with access to shared storage, the account must be able to run a service and have access to the file server and files.

Once your account is properly configured, you can use shared storage via a UNC path.

Linux: //<servername>/<path>
Windows: \\<servername>\<path>

Configuring a Username for Shared Storage

Linux

During initial Linux installation, all SDCX Server services run as root. If a distributed file system protocol, like NFS, is used with the root squashing feature enabled, a remote NFS client running as root will be mapped to a non-root user ( nfsnobody).

If a service running as root in this scenario produces access errors when trying to read or write from a network share, configure the NFS server user permissions to match the root squashing user.

Windows

During initial Windows installation, all SDCX Server services run as NT-Authority\System, which allows for unrestricted access to local system resources. Some SDCX Server services must be configured to run under a different account in order to access remote resources like NAS.

To configure a username for shared storage on Windows:

1. Open the Windows Services control panel.
2. Select the Signiant Jet Server Service.
3. Edit the service properties and click the Log On tab.
4. Select This account.
5. Enter the domain, username and password to access network storage. This user requires local administrator privilege on the local machine. (e.g. domain\userName)

Note: The NAS server itself may be on a Windows domain. If the server is not associated with a Windows domain, do not enter a domain.

6. Click OK to save the configuration changes.
7. Restart the service to apply the changes.
8. Repeat steps 1-7 for the Signiant Media Shuttle Web Server service and the Media Shuttle Process Controller service using the same credentials as the Signiant Jet Server service.
9. Configure endpoints to use your shared storage by specifying a UNC path. (e.g. \\server\share\jet-source)

Testing Access

It is best to test access to shared storage immediately after system startup as the operating system can cache credentials in your login session.

To test if the account has access to files:

Linux

1. Log into the server as a user with sudo privileges.
2. Verify that the network share is mounted and accessible.
3. On the network share, create a directory:
   sudo mkdir -p temp
4. Verify that you can write to the network share:
   sudo touch temp/tempfile.tmp
5. Once the network share is successfully tested, delete the temp directory and its contents.

Windows

1. Log into the server.
2. Verify that the user has read/write access to the mounted network share by entering the UNC path or mapped drive letter in the File Explorer address bar.
3. Create and delete a test directory and test file.

Note: You can check that the SDCX Server services have the same privileges by adding a Jet job with the same test directory and test file.