Bootstrap guide for the File Station

Transcription

1 Bootstrap guide for the File Station

2 Introduction Through the File Server it is possible to store files and create automated backups on a reliable, redundant storage system. NOTE: this guide considers the following terms to be completely equivalent: server, file station, rack station, NAS, RackStation, file server: they all refer to the same remote storage unit. The system consists in a array of large magnetic storage devices and it is located at the 5 th floor of our building. It is basically a small computer which is connected to the network and offers easy interfaces to read/write files on its storage units. Such computer system is often called NAS: Network Attached Storage. This small computer offers such interfaces through a software it runs. This software is a full blown operative system, and it s the software we need to talk to in order to give read/write commnads to the file server. In addition, users have access to the following shared folders. Backup : Used for backup of data from old computers no longer in use.

3 Conferences : Collection of conference material, e.g. conference proceedings, which are often only distributed in electronic form. Currents : Surface current data from simulations and external sources. Documents Experiments : Collection of measurement data from our field experiments file_exchange : Folder used for data exchange with users outside the Wavelab group. These users must also have an account on waveserv, but will have limited access to data. Pictures upload Visual_wave_observations : Collection of all digitized wave observations records WAM : Data files used as input for WAM simulations. Waves : Collection of wave measurement data. Mostly duplicates data in the Experiments folder. wind_data : Wind data from external sources, mostly used as input for WAM simulations It is possible to connect to the file server in three main ways: 1. Through File Transfer Protocol (FTP) users can remotely log in into the RackStation and perform file operations as on a normal remote location. This is a common option for uploading large batches of files. 2. Access through the Web Interface. Basically this system is able to render access from a Web Browser and a convenient user interface. This is the most common option for quick operations and download of files. 3. Access through dedicated local software running on the user's machine. Let s examine these three options in detail. Access via FTP The system implements FTP (File Transfer Protocol) interfaces to the outside, on standard port 21 (and 22 for Secure FTP). FTP is built on a client-server architecture and uses separate control and data connections between the client and the server. The first FTP client applications were command-line applications developed before operating systems had graphical user interfaces, and are still shipped with most Windows, Unix, and Linux operating systems. Dozens of FTP clients and automation utilities have since been developed for desktops, servers, mobile devices. In this guide we will use Filezilla as our FTP Client software. Filezilla is free software and can be downloaded from here. Once the program has been installed, it is possible to procced to configure it in order to connect to the file station.

4 Open the program and fill in the Quick Connection bar with the needed information: Please use the following data for the Host field: waveserv.ioc.ee when connecting from outside the institute waveserv.kybi when connecting from inside the institute Fill the Username and Password fields with your credentials (issues regarding login information can be forwarded to Andrea. You can leave the Port field blank, it will automatically assume that standard FTP Port 21 is in use. Press Quickconnect. The connection log should now show a list of text commands being sent and received from the server, ending in successful welcome message. Also, the list of remote files should become populated (5). The next step is to get familiar with FileZilla's window layout. Here is a quick introduction: Below the toolbar (1) and quick connect bar (2), the message log (3) displays transfer and connection related messages. Below, you can find the file listings. The left column (local pane, 4) displays the local files and directories, i.e. the stuff on the PC you're using FileZilla on. The right column (server pane, 5) displays the files and directories on the server you are connected to. Both columns have a directory tree at the top and a detailed listing of the currently selected directory's contents at the bottom. You can easily navigate either of the trees and lists by clicking around like in any other file manager. At the bottom of the window, the transfer queue (6) lists the to-be-transferred and already transferred files.

5 Uploading files to the RackStation through FTP and Filezilla: First - in the local pane - bring the directory into view which contains data to be uploaded (e.g. index.html and images/). Now, navigate to the desired target directory on the server (using the server pane's file listings). To upload the data, select the respective files/directories and drag them from the local to the remote pane. You will notice that the files will be added to the transfer queue at the bottom of the window and soon thereafter get removed again - since they were (hopefully, if nothing went wrong) just uploaded to the file station. The uploaded files and directories should now be displayed in the server content listing at the right side of the window. Downloading files from the RackStation to the local computer: Downloading files, or complete directories, works essentially the same way as uploading - you just drag the files/directories from the remote pane to the local pane this time, instead of the other way round. Note: In case you (accidentally) try to overwrite a file during upload or download, FileZilla will by default display a dialog asking what to do (overwrite, rename, skip...).

6 Once file operations are completed, it is sufficient to close the program Filezilla. Your session will automatically be terminated on the RackStation Access via online Web Interface Using the File station s built in web interface is a convenient way to perform quick file operations. It requires no installation of extra software and all the users need is a javascript-enabled modern web browser. In order to access your storage quota using this option, first point your browser to: Waveserv.kybi:7000 when connecting from inside the institute. Remember to always specify the port 7000 as it differs from the standard. waveserv.kybi:7001 when connecting from inside the institute. Port 7001 is specified to force a secure encrypted connection. Use this option as the preferred one as it is a good security practice. Waveserv.ioc.ee When connecting from outside the institute. Please note that this connection is not encrypted and data safety may be compromised when using public access points. At this point, the file server answers with the login page:

7 Simply use your credentials and you will be presented to the file browsing interface corresponding to your privilege level. The default user s interface looks like this: A number of customizations and special operations is available, but the usage of this interface should be pretty straightforward. The interface also offers a convenient Help function which guides the user through any available functionality.

8 Access via dedicated software Synology, the manufacturer of the file server, offers two useful utilities that can be used to access files on the server, and to perform specialized backup/personal cloud operations and automate them with ease. These software are available from this address. The ones we are potentially interested in using are: - Cloud Station: To sync files among your computer and the file server - Data Replicator: to create automated backup of local files onto the file server Their usage is very straightforward and they both have a Wizard program to help the user set up the connection in no time. As in other cases, the setting for the parameter server address shall be specified as follows, whenever asked:

9 waveserv.ioc.ee when connecting from outside the institute waveserv.kybi when connecting from inside the institute