DNA Sync 3.0 Administrator & User Guide

Transcription

1 DNA Sync 3.0: Administrator & User Guide DNA Sync 3.0 Administrator & User Guide The owner or authorized user of a valid copy of DNA Sync may reproduce this publication for the purpose of learning to use such software. No part of this publication may be reproduced or transmitted for commercial purposes, such as selling copies. StorageDNA, DNA Evolution and DNA Sync are registered trademarks of StorageDNA, Inc. Third-party trademarks are the property of their respective owners DNA Sync 3.0 Admin & User Guide 2010 StorageDNA, Inc., All rights reserved.

2 Table Of Contents 1. INTRODUCTION DNASync Components DNASync Web Management DNASync Manager Appliance DNASync Client Seat Understanding Point-to-Point Syncs Point-to-point Local Synchronization Point-to-point Network Synchronization Technology Highlights & Details SETUP AND INSTALLATION DNASync Manager Better Understanding the DNASync Manager Appliance Before setting up your DNASync Manager Turning on your DNASync Manager DNASync Manager and HTTPS DNASync Web Interface DNASync Seat Better Understanding point-to-point Transfers (Local & Network) Full versus Quick Install Mode Create a Quick Install Invite Before you Setup a DNASync Seat DNASync Seat Installation and Setup (Quick and Full Mode) ACCESSDNA Getting to AccessDNA Enable Folder Access Client Machine point-to-point Host Connectivity (Full DNASync seat only) Manual Automatic Enable UNC Drives View and Restart Services Enable Client Logging LICENSE MANAGEMENT... 18

3 4.1. License Usage and Policy License Listing To add a user to a machine To remove/uninstall a client machine and reclaim the license ADMINISTERING SYNC JOBS To Add a New Sync Job To Edit a Sync Job To Delete a Sync Job To View The Dashboard To Enable Snapshots ADMINISTERING MACHINES To Add a New Client Machine To Delete a Client Machine To Disable a Client Machine To Edit a Client Machine Client Machine point-to-point Host Connectivity ADMINISTERING USERS To Add a New User To Delete a User To Refresh User List ADMINISTERING DNASYNC MANAGER Networking Change the IP address Display current MAC address Display current IP address Display current routing table Change Hostname... 29

4 8.3. Change Sysadmin Password System Services Menu Reboot/Shutdown Server Empty Trash Folder Recover LDAP/Database WORKFLOW GUIDE Install/Setup Local Syncs Install/Setup LAN Syncs Install/Setup WAN Syncs... 31

5 1. Introduction StorageDNA s DNASync is a point-to-point data and media synchronization solution. Sync enables automatic and seamless syncing of files without the need to perform any manual transfers. SDNA s sync technology is built to work in the background and monitors for changes in one or more source folders. As changes (edits, deletes, creates etc.) are made, they are analyzed and applied to the target folder. DNASync determines the fastest direct transfer route between the two sync points and uses advanced data transfer algorithms (WAN Acceleration, Delta Transfers, SSL Encryption etc.) to securely and efficiently move data DNASync Components DNASync Web Management Management tasks are performed via a secure (https) based web interface. The web interface is hosted on the DNASync Manager (an out-of-band management appliance). All aspects of the DNASync environment including users, groups, seats and job related functions are performed via the centralized web interface. A web interface gives the flexibility to monitor and administer the environment from any web-enabled browser DNASync Manager Appliance The DNASync Manager is a 1u Linux Appliance. It is an out-of-band management appliance hosted at your site. Once configured with a static IP address, it opens SSL connections, which are used for management purposes and for enabling DNAsync seats to communicate with the DNASync Manager. The DNASync Manager is a policy manager and presents a web interface to administrators and normal users. It is responsible for the following: - Setup and Administration of Sync Jobs - User and Group Management - Client Machine Management - Storing all policy information regarding the DNASync environment (sync policies, user policies, group policies, reporting etc DNASync Client Seat The DNASync seat is a lightweight background application that is installed directly onto a laptop, desktop or server. It runs natively on a number of host operating systems including

6 Mac, Linux and Windows. The transfer seat is responsible for performing point-to-point transfers and can perform transfers in (a) local/network-less mode (between any set of folders visible on the system that the seat is installed on) and (b) network mode (where it makes a connection to a seat installed on another system) and moves data to and from the remote system over LAN/WAN Ethernet. The sync seat maintains a connection to the DNASync Manager for the following purposes: Heartbeats the DNASync manager letting it know that it is alive Retrieves job run-time parameters on every run from the DNASync Manager Reports errors, warnings and progress information about the health of a job It DOES NOT send any user files or information about users files (meta-data, attributes etc.) to the DNASync Manager 1.2. Understanding Point-to-Point Syncs DNASync seats perform direct point-to-point synchronization. The sync technology works in two modes: Point-to-point Local Synchronization In local sync mode, changes made on source folder(s) are synced to the target folder. The sync is performed from one storage system, via the mediating CPU, directly to the target storage system. Local synchronization workflows are setup to automatically move data between folders on drives visible locally on the system. Examples include moving data between folders existing on a FC disk array (Avid Unity/ISIS, Apple XSAN, Facilis etc.) to folders existing on another FC disk array (Promise drives, Generic JBOD etc.). It is possible to sync data between any combinations of storage systems as long as all folders are visible to the DNASync agent via the local system. Advantages of Local Synchronization Storage interconnects (SCSI, SAS, FC, iscsi Firewire etc.) are all block based protocols. They traditionally offer faster transfer speeds (bandwidths) than other protocols such as NFS, CIFS that are powered over Ethernet. Local synchronization is built to take advantage of these faster storage interconnects. It is possible that the mediating CPU will become a bottleneck long before the storage system or storage interconnects become a bottleneck. In such cases, multiple DNASync seats can be used in parallel to achieve maximum bandwidth numbers. DNASync seats have achieved well over 3 Gbits/sec in throughput in these scenarios. Limitations of Local Synchronization Both drives must be visible from the same machine. This may not always be possible (e.g. syncing data between two separate Avid Unity systems as one client cannot mount workspaces from two separate Avid Unity systems). Further, local syncs involve one transfer system. Hence it is a deployment that works only in a local environment as storage interconnects are not built to span large distances.

7 Local Synchronization Based Workflow Examples Sync your expensive primary SAN to any Nearline storage of choice Snapshot your expensive primary SAN to any Nearline storage of choice. Snapshots give you time travel ability to instantly recover from media corruptions, operator errors or drive failures. Offload your inactive content from your primary SANs to Nearline storage Point-to-point Network Synchronization In network sync mode, changes made on source folder(s) are synced to the target folder. The sync is performed from one folder, over the intermediate network connection to the target folder. Network synchronization workflows are setup to seamlessly move data from one system to another system using the intermediate Ethernet connection between the two systems. The Ethernet connection can be LAN or WAN based. On network syncs, new or updated data on the source system is incrementally transmitted to the target using WAN acceleration, SSL encryption and Delta transmission. Additionally, DNASync has the ability to automatically recover from network drops. DNASync is tuned to perform seamless, background syncing without requiring any manual intervention. Network Synchronization Based Workflow Examples Sync SANs over LAN/WAN connections e.g. You can synchronize workspaces from one Avid Unity to another Avid Unity. This is useful for remote collaboration without having to manually send data or ship drives. DNASync can keep your remote teams in sync. Disaster Recovery: Sync content across sites to build disaster recovery scenarios. Distribute Approvals and Dailies: Sync dailies directly to producer s laptops and desktops without any manual steps. Build Remote Pipelines: Seamlessly sync content from render, transcode, digitize stations to other remote sites Technology Highlights & Details Point-to-Point versus Client-Server DNASync is designed on a point-to-point (peer-to-peer) file transfer technology. While client server technologies FTP, Web Upload, Traditional Backup Solutions have worked reasonably well to date, they start presenting bottlenecks as the amount of data gets larger and file transfers become more prevalent. DNASync avoids traditional client-server bottlenecks as it is built on a modular peer to peer architecture. Since there is no central server that the data flows through, you can add multiple peer devices to aggregate bandwidth and scale your infrastructure. Local and Network Syncs DNASync is designed to perform high-speed syncs in both a local and network scenarios. In local syncs, DNASync uses techniques such as DirectIO, large read/write buffer sizes etc. to achieve the maximum available bandwidth over local interconnects such as FC, SCSI, SATA etc. Further DNASync automatically lays down files in alphanumeric order meaning that files likely to be accessed sequentially (e.g. frames) are laid down sequentially minimizing disk

8 fragmentation. In network syncs, DNASync selects the shortest, direct path between the two systems. Hence, you can maximize your network bandwidth on both local and remote network syncs. Direct Connect DNASync utilizes direct connections between source and target folders. In either local or network scenarios, data is synced over a direct connection and does not travel via the DNASync Manager in any way. Direct connections enable high performance as well as guarantee security of data in transit as data is not cached or passed through middle servers. Out of Band, Highly Scalable, Web Management DNASync s web management is designed to scale with your environment. Unlike current solutions that require you to upgrade your server hardware as you add more seats, DNASync s Management is built to automatically scale. This is due to its out-of-band management design. As the DNASync Manager does not participate in the actual data transfer (the critical source of bottlenecks), you can add seats, as you like without having to deploy multiple DNASync Managers. Further, all management is performed via a HTTPS based web interface accessible via any browser enabled machine. TCP/IP Based WAN Acceleration DNASync utilizes TCP/IP based acceleration techniques to maximize available bandwidth on high latency, high bandwidth links. UDP and TCP are both transport protocols built on top of IP. TCP has higher levels of delivery guarantee and fairness built in. However, as TCP was largely designed to work on low latency links, it suffers from over compensation and hence loss of bandwidth on high latency links. DNASync s protocol runs over an optimized version of TCP, which provides you the network security inherent in TCP and allows you to achieve maximum bandwidth. We use a combination of multi-file sending, multi-streaming, chunking, send/receive buffer sizing, selective acknowledgements etc. all of which combined provide desired performance numbers on TCP. Highly Resilient Network Transfer Management DNASync utilizes advanced timeout and retry algorithms to deal with real world network issues. These issues arise from user operation (such as turning the system off, changing wireless networks etc.) to ISP problems with dropping connections. DNASync is able to handle a variety of such network conditions automatically for you. SSL Transfers with End-Point Authentication DNASync is designed to perform highly secure network transfers. All network syncs are performed using SSL based encryption. In addition to encryption, DNASync allows you to deploy your own public key infrastructure and certificates. Multilevel Authentication DNASync provides multiple levels of authentication and security to prevent against any form of unauthorized access or data movement. Web username and password protection Multi-level user, group and administrative access levels Manage access control based on users to folders on DNASync seats Local machine username and password ensuring only machine owners have ultimate authority to create syncs Sync and Snapshots Sync and snapshots are a more efficient technology for data protection than traditional backup and restore. Synchronization creates a direct byte-for-byte replica of the primary data onto Nearline disk storage. This mirror copy serves as an instantly accessible copy in case of any kind of data loss on the primary. Secondly, snapshots serve as previous point in time copies which are instantly accessible. Rather than having to restore files from multiple previous versions, snapshots provide a quick and easy way to access previous versions of files.

9 2. Setup and Installation This chapter will highlight how to deploy a DNASync Manager and DNASync seats in your environment DNASync Manager Better Understanding the DNASync Manager Appliance The DNASync Manager is a1u Linux powered appliance that sits at the heart of every DNASync environment. It is installed at your site and simply needs an IP address. DNASync seats open connections to the DNASync Manager and heartbeat the manager notifying the manager of their presence. Additionally, the DNASync Manager provides an HTTP/HTTPS based centralized web interface Before setting up your DNASync Manager The DNASync Manager uses in-bound ports (4545, 443/80, 9094) for management and communication from DNASync client systems. You must configure your network accordingly to ensure that the DNASync manager and ports are reachable by all DNASync client machines. If a DNASync client cannot access the DNASync Manager, you will not be able to install and operate the DNASync client seat. The DNASync Manager does not need any out-bound ports configured Turning on your DNASync Manager When you turn on the DNASync Manager for the first time, you will need to wait for it to completely boot-up. Use a monitor and keyboard to login into the system administrator setup menu. Access the system administrator setup menu using the following username and password: Username: sysadmin Password: password Once you are logged in, the first thing you should do is to set a static IP address. You can do this by accessing menu item (1) Networking Menu and then sub-menu item (1) Change IP address. Once you have configured the IP address, the DNASync Manager is ready for use. (Refer to Chapter 8: Administering the DNASync Manager for more details)

10 It is highly recommended you reset the sysadmin password using the menu item (3) Change Setup User Password. The DNASync Manager setup menu can be accessed remotely via ssh once you have given the DNASync Manager a static IP address DNASync Manager and HTTPS The DNASync manager is configured both for http and https for management and for DNASync client installation and communication. However, by default DNASync is configured with a StorageDNA signed certificate assigned to dnaserver. Hence, if you desire to use https with the default certificate and hostname ( dnasever ), you will need to use the IP address when prompted for the IP address/hostname during the DNASync client installation. Upon providing the IP address, the DNASync client installer automatically adds an entry to the client machine s hosts file. If you would like to configure your own certificate, please contact StorageDNA for more information DNASync Web Interface The DNASync web interface can be accessed via any web browser. Simply point your browser to Manager IP or Hostname>. Upon login, you will see the following screen: Each tab is explained in more detail in the user guide. The first step before performing any syncs is to setup and install DNASync seats.

11 2.3. DNASync Seat Better Understanding point-to-point Transfers (Local & Network) DNASync seats are installed directly onto customer laptop, desktop or servers. Once installed, it runs in the background. The DNASync seat communicates with the DNASync Manager for progress and job related information. This communication is performed via http or https based outbound connection and as such does not require any inbound ports to be opened for management purposes. Every DNASync seat is composed of 2 key components, the Initiator and Host. If you are performing local syncs, you do not need to open any in-bound ports for data transfers as the initiator process runs in local mode. However, if you are doing network syncs, you will need to configure your machines and network to ensure that the initiator (DNASync client making the connection) is able to connect to the host machine (DNASync client machine receiving the connection). Lets take a look at a network point-to-point sync process in more detail: Full versus Quick Install Mode DNASync clients can be installed in Full versus Quick mode. These two modes exist to simplify the deployment process especially in WAN configurations where numerous Firewalls and NAT routers are in play. As described previously, in a network transfer, the DNASync client software relies on an Initiator making a connection to the Host. Hence, the system acting as the Host must be configured across its Firewall and must contain the appropriate NAT translations in the host side router. These Host settings are not easily configurable by end users and result in IT involvement. The key differences between Quick versus Full are as follows: - Quick mode installs ONLY the Initiator. Full mode installs both the Initiator and Host. - Quick mode does not require any inbound ports to be set.

12 - Quick mode does not require username/passwords to be provided when you create or edit a job. - You cannot sync between two Quick installs. If you need to, you will need to setup a cached workflow where you will sync content from a Quick install machine to a Full install machine and then create a sync from the Full Install machine to the second Quick Install machine. The two modes makes it possible in a remote file transfer scenario to only have to configure one side with the Full mode and then provide a quick install process for all the other remote users Create a Quick Install Invite The DNASync manager makes it easy to send a Quick Installer invite to a remote user. Follow these steps to create an invite: - Login to the web management interface - Browse to Clients -> License Information - Pick a free license key (highlighted in green) and click Generate Quick Invite - You will be prompted for an IP address/hostname that will be used to tell the end user where they can get the installer and what is the visible IP address or hostname of the DNASync manager. - The web manager will create an invite, with instructions that you can paste in your browser and send to the remote user Before you Setup a DNASync Seat In full mode, the DNASync installer configures the seat as a host and initiator. In quick mode, the DNASync seat is configured ONLY as an initiator. The quick mode is useful for nontechnical end users who will not be required to configure their network for inbound connections as well. As described above, before you install and setup your DNASync seat, you must ensure you have made the appropriate network changes and allocated system resources. Follow the step-by-step guide below to ensure your machine is ready for install and setup: Step 1: Check System Operating System and Resources

13 Currently you can install a DNASync seat on the following operating systems: Mac OSX 10.4 and above Windows XP, 2003 Server, Vista, 7 Linux (All flavors) Step 2: Ensure the DNASync Manager is visible to the seat and that management outbound ports are opened Firstly, you can execute ping from the client machine to the DNASync Manager to ensure it is network reachable. A good tutorial on ping can be found on Wikipedia ( Secondly, as every DNASync seat communicates with the DNASync Manager over ports 4545, 443/80 (https or http) and 9094, these ports need to be contactable. You can ensure that the port is contactable by running telnet to the port. telnet <ip address/hostname of DNASync Manager> <port #>. Try this for each of the port numbers. If it successfully connects, then the port is reachable. As long as the machine can see these ports on the DNASync Manager, you will be able to install the seat. Step 3: If this DNASync seat will be used for local transfers If the seat will be used purely for local transfers, you will not need to configure any in-bound ports. Step 4: If this DNASync seat will be used for network transfers and will host connections. (FULL MODE) If you expect this machine to receive connections for network transfers, you will have to ensure that it is contactable by all initiator machines. You can select the port that the host process will listen on for incoming network connections. This is done at Install time (covered in the next section). DNASync offers tools to help you setup a machine s ports to host connections. Refer to the AccessDNA chapter and the Point-to-Point Connectivity section under Managing Client Machines chapter. Step 5: If this DNASync seat will be used for network transfers and will initiate connections (QUICK MODE) If the seat will be initiating connections to other host systems for network transfers, you will not need to configure any in-bound ports DNASync Seat Installation and Setup (Quick and Full Mode) Once you have qualified your environment, you can begin your DNASync installation and setup. Step 1: Download the DNASync seat The seat can be downloaded directly from the DNASync Manager. In the Job Listing pane under DNASync Space, select the Client Installers icon. Simply download the Mac or Windows version. Step 2a: Installation For Full Mode After you agree to the End User License Agreement, you will need to provide the following information: 1. DNASync Manager to connect to - IP address: Provide the IP address of the DNASync Manager IF you wish to use the default SSL certificate. OR

14 - Hostname: Only if you have configured the DNASync Manager with a custom SSL certificate should a hostname be provided here. 2. A valid license key The information is verified against the DNASync Manager and if accurate, it will proceed to the next screen of the wizard. In this screen, you can provide a client machine identifier. This defaults to the hostname of the machine but you can change that to another name. Note that this name is not used for network connectivity and is for labeling purposes only. In this screen, you can select the port that the host process will listen on. By default this port is You can click though the next few screens and the installer will complete the process. Step 2b: Installation For Quick Mode After you agree to the End User License Agreement, you will need to provide the following information: 1. DNASync Manager to connect to - IP address: Provide the IP address of the DNASync Manager IF you wish to use the default SSL certificate. OR - Hostname: Only if you have configured the DNASync Manager with a custom SSL certificate should a hostname be provided here. 2. A valid license key In quick mode, this is the only configuration required as the DNASync client is not configured to be a host. Step 3: Setup AccessDNA The installer will automatically launch AccessDNA after installation is complete. You will have to add the folders you want exposed to the DNASync system. Once exposed, a user with access to the web console can automatically create jobs to and from your system. To add one or more folders, click on Add. Browse and select the folder you want exposed. You can also select which specific user to expose the folder to. By default it will be exposed to all DNASync users. Repeat for multiple folders and once done, click Save. NOTE: If you do not SAVE, your changes will not take effect. Please refer to the AccessDNA chapter for more information.

15 3. AccessDNA AccessDNA is an application that is installed automatically when you install a DNASync seat. AccessDNA is built to give the owner of DNASync client admin access to certain key attributes such as: - Which specific folders should be exposed to the DNASync environment - Which DNASync users are allowed to access these folders from the online web GUI - Which UNC drives should be accessible - If local hostnames and IPs should be reported to the online web GUI - If DNASync should manage incoming point-to-point network connections using upnp 3.1. Getting to AccessDNA On Mac, AccessDNA can be found under Applications->StorageDNA->accessDNA.app On Windows, AccessDNA can be found under Programs->StorageDNA->AccessDNA 3.2. Enable Folder Access Only a user with physical access to the machine has ultimate authority over which folders to expose and to which users in a DNASync environment. If the Restrict StorageDNA access to selected folders is checked, then DNASync will restrict folders according to the rules setup by the user. If this checkbox is not enabled, all folders will be visible to the DNASync environment. NOTE: DNASync restricts not just the DNASync source and target folder browser in the web GUI but also enforces these rules on sync jobs.

16 Once restriction is enabled, you can make folders visible to the DNASync environment by adding them to the list. When you click the add button, you can select the folder, and decide if you would like to expose this folder to all DNASync users or to just select users and groups. You can edit and delete these entries when required Client Machine point-to-point Host Connectivity (Full DNASync seat only) AccessDNA makes it easier to setup your network to enable the machine to be a contactable host for point-to-point network syncs. This is relevant for systems configured as Hosts with the Full Install Mode Manual In this mode, DNASync does not auto-report or auto-configure IP addresses. It uses only manually provided IP/ hostnames when initiator machines need to connect to this machine in a point-to-point network sync. The IP/hostnames can be entered via the Point-to-Point connectivity tab under Clients in the online web GUI Automatic In this mode, DNASync will report IPs and hostnames that it has found by scanning the local network interfaces. In addition to trying the manually provided addresses, initiators will also try these auto-reported addresses. It is useful to run this if you expect to have all machines on the same local or private subnet Enable UNC Drives AccessDNA requires you to explicitly add networked machines that you will access over UNC. This check is put in place to prevent unauthorized access to other computers in your networked environment. Check the Enable UNC Support checkbox to enable UNC access for this machine. To configure UNC, click on Configure. After the configuration dialog is open, you can add UNC machines. To add a new machine, you can browse the network for machines or type in the UNC machine name. You can optionally add the network provider. Once you have done adding the UNC machines, you can add UNC paths in the folder access list. NOTES FOR Avid Unity/ISIS: While setting up Unity/ISIS Connection Manager, the following information can be helpful: Username/password of windows box must exactly match the password provided for the username under the Connection Manager OR the username should be entirely different. To Find the Unity/ISIS system name: First one workspace. On windows, under My Computer, you will see the workspace listed as projects under a Unity/ISIS server name. Use that name as the server name for AccessDNA View and Restart Services You can view and restart essential DNASync client services from this menu. If your client machine is not browsable or is unable to sync jobs, it is a good idea to restart client services via this menu option Enable Client Logging You can enable and disable client logging for debugging purposes. This is an advanced option and should be used under guidance from a StorageDNA support professional.

17 4. License Management Machines that have DNASync client software installed are administered via the Clients -> Licenses tab on the web management console. DNASync enables you to manage licenses if you are the assigned owner of the license. If you do not see any licenses, it means you have not been assigned any licenses. Please NOTE that owning a license pertains to administration rights. The owner of a machine can assign other users to create syncs on that machine as described below. However the assigned user will not be able to administer that machine 4.1. License Usage and Policy All DNASync licenses are assigned by default and owned by the admin user. Only the user who is the owner of a license ( admin user by default) can see the licenses in the Clients -> Licenses tab. If you need licenses assigned to another user, you need to advise StorageDNA during license purchase. Upon client software installation using a license key, the client machine by default will appear only for the admin. The admin user will need to assign the machine to a normal user before the normal user can create syncs to and from the installed machine License Listing All licenses are listed under the Clients -> Licenses tab. Use the following key for licenses: - Black: Assigned valid license - Green: Available and unassigned license - Red: Expired license 4.3. To add a user to a machine Browse to the Clients tab. In the General Information section, you can add users to the authorized users list. Add the user you would like to give access and save. Now the normal user will be able to use the client machine for syncs To remove/uninstall a client machine and reclaim the license When a DNASync client machine is uninstalled, the associated license key will be reclaimed. Additionally, you can simply delete a machine from the client list. This has the same effect in returning the license to the available pool.

18 5. Administering Sync Jobs Sync jobs are administered via the DNASync My Syncs tab on the web management console To Add a New Sync Job Both local and network sync jobs are added by clicking the plus icon in the job action bar. All client machines that will be involved in the sync need to be online and accessible. In network syncs, ensure that the client machine that will host the sync is network accessible to the client machine that will initiate the transfer. Refer to the networking setup section for more details in the chapter on point-to-point network connectivity. Click the plus icon on the job action bar On Screen 1 of the wizard, provide the following: The Basics: Provide a job name and the DNASync user/group the job will run as. This allows admin users to set jobs as other users and allows normal users to save a job as a group so all

19 members of the group can view the job. NOTE: This is a DNASync user/group and should not be confused with a local machine username/group. Source and Target Machine: Select the source machine and target machine where the source and target folders reside NOTE: Select the same machine for both source and target to indicate a local sync job and select separate source and target machines to indicate a network sync job. NOTE: In a network sync, the source machine (initiator) by default attempts to make a direct point-to-point connection to the target machine (host). Hence, it is essential that you ensure that the target machine is contactable. However, DNASync has the flexibility to reverse the initiator so that the target machine initiates the connection to the host machine. This can be achieved by clicking the Reverse Initiator option on the last screen of the wizard. On Screen 2 of the wizard select one or more source folders for syncing. NOTE: Avid MXF/OMF media folders will appear with project names below them. Use the OMF/MXF folder if you want the entire folder to be synced as is. You can select the PMR virtual folder and DNASync will sync the media into separate project folders on the target. You can also select individual projects. You can also browse UNC shares and Avid Unity/ISIS workspaces directly without mounting them. Refer to the AccessDNA section for more details (Chapter 3, AccessDNA) On Screen 3 of the wizard select one target folder. You will not be allowed to select more than one target folder. On Screen 4 of the wizard, you can apply one or more include and exclude file filters. On Screen 5 of the wizard, you can add a scheduling policy. You can choose to run the job on a minute, hourly, daily, weekly or manual interval. On Screen 6 of the wizard, you have the option to set a number of options on the sync: Limit Bandwdith: You can control bandwidth allocation for every sync job. This number is specified in KB/sec (where 1 KB = 8 Kbits/sec). NOTE: If multiple streams are specified, this number will limit each stream. Limit Scan Speed: You can control the total number of IO requests sent to the source disk subsystem by filling in this option. Please refer to your disk subsystem manuals for what settings you should use here. Set Buffer Size: You can control the TCP/IP send and receive buffer size with this option. This option when used in conjunction with multi-streaming is useful for optimizing WAN transfers. For more information on optimizing WAN transfers, refer to Chapter 9, Workflow Guide, Setup WAN syncs. NOTE: Available only on network sync jobs. For more information on optimizing WAN transfers, refer to Chapter 9, Workflow Guide, Setup WAN syncs. Multi-Streaming: You can control the multi-streaming option that enables network sync jobs to overcome any TCP/IP related congestion problems and to help achieve higher bandwidth number on high bandwidth, high latency Ethernet links. On multi-streaming, multiple parallel TCP/IP streams are used, where multiple files and multiple chunks of same file are sent at the same time. Multi-streaming is also useful in jobs running on a LAN where there are many small files that need to be synced. Number of Streams Option: Set this number from the drop down. Split Files Options: Set this number to split large files into chunks. NOTE: Available only on network sync jobs. For more information on optimizing WAN transfers, refer to Chapter 9, Workflow Guide, Setup WAN syncs. Encryption: You can enable SSL encryption to ensure data is not compromised during transit. It is recommended that you setup your own public key certificate to ensure the most secure environment. To learn more, read our DNASync Public Key Setup Guide.

20 NOTE: This option is available only on network sync jobs. Delta: Delta transfers efficiently moved changed portions of files. For deltas to successfully work, the file type must support it. Sync Delete: Sync jobs with this option enabled will delete any target files not found in the source. This option should be used with great caution (especially with path mapping) as it can result in accidental mass deletion. Refer to the following examples on how the delete option with path mapping can result in unwanted deletes on the target file system if not used properly. NOTE: This is an admin only option and should be used with great care. Please play close attention to the WARNING as it will highlight directories that might get accidentally deleted. Example1: Multiple Sources to Single Target with Path Mapping Sources Folders: Assume we select the following source folders: /Volumes/Drive1/FolderA (Path Mapped to NO PATH) /Volumes/Drive1/FolderB (Path Mapped to NO PATH) So no source path information is retained in this example. Target Folder: Assume the target folder is /Volumes/Drive2 with some pre-existing files. As an example, consider the following: /Volumes/Drive2/FolderC, /Volumes/Drive2/FolderD already exist. Now when the sync with deletes executes, it will compare the path mapped source (all files under /Volumes/Drive1/FolderA and /Volumes/Drive1/FolderB ) to the target ( /Volumes/Drive2 ); find no subfolders by the label FolderC or FolderD in the source; then proceed to delete both target folders after the syncing the files to the base of the target folder /Volumes/Drive2 to sync any missing files from source to target. Transfer New Files Only: Sync jobs with this option enabled will transfer only files on the source that is newer than the target. Avid Workflow: This provides a clue to DNASync that it is reading or writing from an Avid Unity/ISIS storage system and enables DNASync to use read/write semantics that are Avid compatible. Enable Scripting: Every sync job can be configured to initiate other third party APIs via pre/post scripts. Pre-scripts are executed prior to the transfer on the initiator system. Currently, scripts cannot be executed on the host machine. For more information on hosts and initiators refer to Chapter 2, Setup and Installation. To configure pre/post scripts, follow these instructions on the initiator machine: Type in the scripts folder in the Directory text box that will contain all the pre/post scripts you wish to run. Follow this naming convention for pre-scripts: Name any prescripts with a preceding s_ DNASync will automatically run any scripts with this convention in alphabetical order Follow this naming convention for post-scripts: Name any prescripts with a preceding e_ DNASync will automatically run any scripts with this convention in alphabetical order NOTE: At any anytime during the execution process, if the return status is non-successful (exit code non zero), the job will fail and the next step will not be run. As an example, if any of the prescripts fail, the Sync Job portion will not run and the DNASync server will report Pre- Script Failed as the status. If the Sync Job fails, the post scripting will not run. If any of the post scripts fail, then the server will report Post-Scripting Failed on the web interface.

21 Notification: A comma-delimited list of addresses can be provided to setup notifications on sync job runs. alerts can be sent out on Warnings, Warnings and Failures or Always. On Screen 7 of the wizard, you can set path mapping for each source folder you have selected. Path mapping is a convenient feature when you are syncing data between different folder paths. Often times, you may want to configure exactly how much of the path information gets retained from source to target. NOTE: Path mapping can impact how Delete Target option works. Please refer to the Delete Target section. Take a look the following example: Suppose you want to sync the following source folders: /Volumes/DriveA/FolderA /Volumes/DriveA/FolderB To the following target folder: /Volumes/DriveB/TARGET Path mapping gives you options on how much source path information you want to retain: If you want your target to retain all path information, simply perform no path mapping. This is how your target will appear: /Volumes/DriveB/TARGET/Volumes/DriveA/FolderA and /Volumes/DriveB/TARGET/Volumes/DriveA/FolderB If you do not want to retain partial path information, simply move the path information slider all the way to the right. This is how your target will appear: /Volumes/DriveB/TARGET/files (from FolderA) and /Volumes/DriveB/TARGET/files (from Folder B) Use the slider as required for retaining any subset of the path information. On Screen 8 of the wizard, you will be required to provide end user credentials. Every sync job executes under a local user s credentials. Hence, every job must be authenticated against all systems that will be involved in the sync. For local jobs, you will see only one username (single machine involved in sync) versus network jobs that require usernames/passwords on both systems. Provided passwords are used for authentication against the local system and discarded (NOT CACHED BY SDNA). Usernames are however cached for convenience. If a machine is setup using Quick Install, you will not be required to provide a password. In a network sync, the source machine (initiator) by default attempts to make a direct pointto-point connection to the target machine (host). Hence, it is essential that you ensure that the target machine is contactable. However, DNASync has the flexibility to reverse the initiator so that the target machine initiates the connection to the host machine. This can be achieved by clicking the Reverse Initiator option. NOTE: You do not need to provide username/password credentials for quick install systems To Edit a Sync Job A sync job can be edited by selecting the appropriate job from the list and clicking on the Edit/Tool button in the job action pane. Any edit requires a re-authentication to take effect. All options as described in the Add section can be edited except the following: - Source or Target Machines - DNASync Run As User/Group 5.3. To Delete a Sync Job

22 A sync job can be deleted by selecting the appropriate job from the list and clicking on the Delete button in the job action pane. To Manually Start/Stop a Sync Job A sync job can be manually started and stopped by selecting the appropriate job from the list and clicking on the Start/Stop button in the job action pane. To Disable a Sync Job A sync job can be disabled by selecting the appropriate job from the list and clicking on the Disable button in the job action pane. A disabled job will appear grayed out. To Refresh the Job List Simply click on the Refresh button in the job action pane, to refresh the job listings. To Filter the Job List Simply click on the Make Filter Appear button in the job action pane, to make the filters action box appear. You can then choose to display jobs by user, group or machine. To Monitor an Actively Running Sync When you select a sync job, its active state is shown in the Job Run Summary Pane. If you want to monitor an actively executing sync, click on the progress icon above the Pane. Active statistics such as time to-completion, amount of data transferred, amount of data remaining etc. are displayed and updated in real time. To Get A Detailed Job Run Report When you select a sync job, its previous job runs are displayed in the Job Run Summary Pane. You can select a previous run and click on the download icon above the pane to get a detailed report on the run. Details on Job Run Codes SUCCESS: The job completed successfully with no known errors. WARNING: This status represents a partial success. The job completed but it is possible some files or folders were not successfully moved. If any file could not be moved on account of the following reasons, the job will be marked with a WARNING state: File changed in content during the sync. File size changed during the sync. File vanished during the sync. FAILED: If any file transfer errors were encountered that are not included in the WARNING will result in an overall status of FAILED. CONNECTION_LOST: This status represents a permanent connection loss during a sync. COULD_NOT_CONNECT: This status is an indication that your network is not configured correctly. When the initiator system is unable to make a connection to the host, it reports this error. Ensure the initiator can connect to the host. You may have to configure your host system for if the connecting machines are not on the same LAN or connecting via an external LAN. DIR_NOT_EMPTY: If the delete option is enabled and content was not successfully deleted, this error will be reported. INTERNAL_ERROR: This status represents an error that needs to be diagnosed by a StorageDNA representative. FILE_LOCKED: This status is reported if a file is locked and cannot be updated. FILE_OUT_OF_SPACE: This status is reported if the target system runs out of space. FILE_PERMISSIONS: This status is reported if the source or target files do not have the correct permissions to be read or written. FILE_RENAME: DNASync creates a temporary file when a file is being synced. On completion, it renames this temporary file to the permanent file name.

23 FILE_TARGET_NAME_TOO_LONG: This status is reported if a filename is too long for the target. FIILE_TRANFERRING: This status is reported if the job is actively moving files. NO_DIRECTORIES: This status is reported if the source or target folders are missing due to deletion or because someone moved it. OUT_OF_MEM: This status is reported when the DNASync process has run out of memory. PRE/POST_SCRIPT_FAILED: This status is reported when one or more pre or post scripts have failed. SCRIPTING_DIR_NOT_FOUND: This status is reported if the selected scripting directory is not found. WRITE_ERROR: This status is reported when a disk or file system error is encountered. SCANNING: This status is reported when files are being actively scanned during a sync. UNDIAGNOSED: This status is reported when these was an unknown error To View The Dashboard New to release 3.0, DNASync now exposes a dashboard designed to give you an instantaneous view of all your jobs. The dashboard can be viewed by clicking the dashboard icon on the job action pane. The dashboard will open in a new window To Enable Snapshots Snapshots can be enabled on point-to-point local and network sync jobs. Snapshots are currently enabled via DNA s pre/post script infrastructure. The following are requirements to enable Snapshots: Snapshot Requirements Snapshots can be run only on the Initiator machine (NOTE: Snapshots are run as part of the DNASync pre/post scripting infrastructure and currently scripting can only be executed on the Initiator machine) The directory where the snapshots will reside has to be on the same volume as the target of the sync.

24 The target file-system should support hard links. Please refer to your target file-system s user guide to ensure this. Snapshot scripts are enclosed along with the DNASync installation. The snapshot script can be found in the following locations: /Applications/StorageDNA/DNAClient/snapshot.sh <snapsource> <snaptarget> <numsnaps> (Mac Snapshot Location) C:\Program Files\StorageDNA\winsnapshot.exe -max <numsnaps> <snapsource> <snaptarget> (Windows Snapshot Location) Create a post-script and provide the above command line parameters with the full snapshot script path. Snapsource: This is the base folder of the target synchronization folder Snaptarget: This is the base folder where the snapshots will be placed. NOTE: Ensure this target resides on the same mounted file-system as snap source Numsnaps: This is the maximum number of snapshots DNASync should maintain. DNASync automatically rolls snapshots over after the numsnaps number is reached.

25 6. Administering Machines Machines that have DNASync Seats installed are administered via the Clients tab on the web management console. Client machines when installed with a DNASync Seat appear in the Client Machine List. Each machine is marked with a name and an icon representing the host OS on the machine. A machine highlighted in italicized red is disconnected. A machine highlighted in italicized gray is disabled To Add a New Client Machine There is no explicit way to add a machine from the UI. Machines automatically appear in the Machine Listing once a DNASync seat has been successfully installed To Delete a Client Machine When you delete a client machine, the machine will be removed and its associated license will be reclaimed. Once reclaimed, you can re-use the license key To Disable a Client Machine When you disable a client machine, all jobs to and from that machine will also be disabled.

26 6.4. To Edit a Client Machine The administrator can modify the following attributes of a client machine: Label: This is just an identifier label for the client machine and should not be confused with the hostname. Default Run As User: This default user is not a DNASync user but the user id on the local system account. When a job is created and needs to be authenticated, this user id will be automatically filled in for convenience. User/Group Access Control: The administrator can grant access to normal users or entire groups that can access the client machine for sync job creation 6.5. Client Machine point-to-point Host Connectivity In a point-to-point network transfer, a direct connection is made between the two DNASync machines. Hence, at least one machine must be contactable by the other. The machine that gets contacted is referred to as the host (DNASync defaults the target machine in a point-to-point sync as the host). This can be easily reversed in the job creation wizard. The Point-to-Point connectivity tab displays the current known IP addresses and hostnames for the client machine. These addresses will be used in a point-to-point sync when initiators attempt to connect to this machine. User Defined Connections: This screen allows you to add IP addresses and hostnames that are mapped to the specific client machine. Initiator machines use these IPs and hostnames to contact this host. User defined addresses always take precedence over automatically reported connections. Reported Connections: If this option is enabled via AccessDNA, this screen reports the hostnames and IP addresses that the DNASync Agent automatically determines from the machine. Simply querying the local network interfaces does this and is useful if a NAT router does not separate the machines (e.g. on a LAN, in a VPN etc.). AccessDNA can also be used to automatically manage incoming connections across a NAT(using upnp). This option is configurable from AccessDNA.

27 7. Administering Users DNASync users are administered via the Users tab. DNASync users are created by administrators and allow for the separation of sync jobs and client machine assignment To Add a New User Click on the Add icon to add a new DNASync user. Fill in the new user information and assign the user to any groups you wish. A user can be of the following types: Administrative Users: Access to all DNASync web management tools Normal Users: Access to only sync jobs they create and sync jobs of groups they belong to. Normal users cannot administer client machines, other users or groups To Delete a User Click on the Delete icon to delete an existing DNASync user. When you delete an DNASync user, all related sync jobs must be deleted To Refresh User List The Refresh List icon refreshes the user list with any updates that might have been made by another administrative user.