This shows you the differences between two versions of the page.
Next revision | Previous revision Last revision Both sides next revision | ||
cluster:135 [2014/12/02 14:02] hmeij created |
cluster:135 [2018/07/25 13:52] hmeij07 |
||
---|---|---|---|
Line 1: | Line 1: | ||
\\ | \\ | ||
**[[cluster: | **[[cluster: | ||
+ | |||
+ | The process of migrating off Flexstorage to the new Rstore platform. | ||
+ | This is not a storage policy document but information could be gleaned from it. | ||
==== RSTORE FAQ ==== | ==== RSTORE FAQ ==== | ||
+ | |||
+ | Your Flexstorage storage share will be migrated to our new platform dubbed Rstore. | ||
+ | Details below, not all may apply to your share. | ||
+ | Once you have tested the new environment we need to coordinate a final update from Flexstorage to Rstore before you formally switch over. | ||
=== What is it? === | === What is it? === | ||
+ | |||
+ | Our current platform to provide disk storage capacity for users and groups is called Flexstorage (2x28TB). | ||
=== How do I access it? === | === How do I access it? === | ||
- | === Is my data safe? === | + | You will use your Wesleyan Active Directory (AD) credentials, |
+ | |||
+ | There are several ways to access your contents; either by logging in or mounting the shares. | ||
+ | More information is provided below. | ||
+ | |||
+ | === How is it configured? === | ||
+ | |||
+ | Each primary/ | ||
+ | |||
+ | Replication is duplicating data of primary member to be in sync with data on secondary member. | ||
+ | |||
+ | Only the shares located on the third data filesystem (/data/3), in addition to replication, | ||
+ | |||
+ | Note: Because of replication, | ||
+ | |||
+ | Note: For very large filesystems whose contents does not change, the replication actions can take a long time and is typically unnecessary after first copy event. | ||
+ | |||
+ | Note: During an initial seeding of share contents, or adding large volumes of new contents, it is possible to skip replication avoiding any race conditions. | ||
+ | |||
+ | === Is my content | ||
+ | |||
+ | Your content is protected using these methods: | ||
+ | |||
+ | * When the content was transferred from Flexstorage to Rstore the -c option of rsync was used meaning perform a checksum check guaranteeing that both files have the same unique finger print. | ||
+ | * Once copied to Rstore disk arrays the content is protected with redundant array of independent disk technology, in our case RAID 60. This technique keeps multiple copies of data chunks so that failed disks can be repaired. | ||
+ | * RAID cards managing the arrays continually scrub and test the disks for signs of probable near future failure events thus reducing actual failures. | ||
+ | * In the event of a primary catastrophic failure of a member in a pair, the content is available on the secondary member in a state defined by last replication event. | ||
+ | * In an accidental deletion of content in shares in /data/3 (ONLY), there will be snapshots available for restoration (daily, weekly, monthly). | ||
+ | * Both primary/ | ||
+ | * Both primary/ | ||
+ | * Upon deployment of your share, checksums will be calculated for each file on both primary and secondary members. | ||
+ | |||
+ | === How do I test? === | ||
+ | |||
+ | [TEMPLATE] | ||
+ | |||
+ | Hello, | ||
+ | |||
+ | You're Rstore share has been created. Although most folks will connect to their shares via Samba, SSH/SFTP access is also allowed. Please consult the details at https:// | ||
+ | |||
+ | In general you can access your share in the following manner on your desktop: | ||
+ | |||
+ | For windows, map a network drive | ||
+ | < | ||
+ | \\service_address\share_name | ||
+ | </ | ||
+ | |||
+ | For Macs, in a terminal mount the share | ||
+ | < | ||
+ | smb:// | ||
+ | </ | ||
+ | * Your share' | ||
+ | * Your share' | ||
+ | * Your share' | ||
+ | * Your share' | ||
+ | * Your share' | ||
+ | * share owner rwx, share group rwx, others none | ||
+ | * share members own their own folders and files they create | ||
+ | * share members have group access to folders and files created | ||
+ | * This default policy can be changed to a certain extent | ||
+ | * Your share' | ||
+ | * Please let us know if you wish to receive nightly replication/ | ||
+ | |||
+ | The Rstore Team | ||
+ | |||
+ | [TEMPLATE] | ||
+ | |||
+ | Note: UID/GID name space. Every user has a uid/gid identification number which determines permissions to files and directories. | ||
- | note to large users | + | * SSH access |
+ | * open any ssh client and connect | ||
+ | * then change directories ('' | ||
+ | * view contents ('' | ||
+ | * These are not computational servers but running maintenance scripts etc is allowed | ||
+ | * If you will be running programs that will take a long time please notify us | ||
+ | * Your uid/gid comes from AD but your gid may not be the share group gid (for example it can '' | ||
+ | * to force the correct gid type '' | ||
+ | * Samba access (Preferred) | ||
+ | * Windows users, map a network drive and use your AD credentials | ||
+ | * < | ||
+ | * Mac users, mount a samba share | ||
+ | * < | ||
+ | * In both cases, the uid/gid will be forced by Samba to be correct. | ||
+ | * NFS (only for HPCC environment) | ||
+ | * On the high performance compute cluster head nodes (the " | ||
+ | * Shares are mounted at / | ||
+ | * Like SSH access you may have change your group gid | ||
+ | | ||
+ | * CIFS (mount the Samba share on remote clients) | ||
+ | * This can be done but remote client is responsible for proper uig/gid settings | ||
+ | * SFTP/SCP is probably easier. | ||
+ | * < | ||
\\ | \\ |