User Tools

Site Tools


cluster:151

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
cluster:151 [2016/10/31 19:36]
hmeij07 [Mirror Data]
cluster:151 [2016/11/10 19:58]
hmeij07 [Mirror Meta]
Line 24: Line 24:
  
   * ''cottontail:/usr/local/bin/beegfs-admin-gui''   * ''cottontail:/usr/local/bin/beegfs-admin-gui''
 +
 +==== Resync Data ====
 +
 +[[http://www.beegfs.com/wiki/StorageSynchronization|StorageSynchronization Link]]
 +
 +//If the primary storage target of a buddy group is unreachable, it will get marked as offline and a failover to the secondary target will be issued. In this case, the former secondary target will become the new primary target.//
 +
 +Testing out fail over and deletion of data on secondary then a full resync process:
 +
 + 
 +  * started a full --resyncstorage --mirrorgroupid=101 --timestamp=0
 +  * got --getentryinfo EntryID for a file in my /mnt/beegfs/home/path/to/file and did the same for the directory the file was located in
 +  * did a cat /mnt.beegfs/home/path/to/file on a client (just fine)
 +  * brought primary storage down
 +  * redid the cat above (it hangs for a couple of minutes, then displays the file content)
 +  * while primary down, I ran rm -rf   /mnt/beegfs/home/path/to/ removing directory holding file
 +  * a cat now generates the expected file not found error
 +  * brought up primary and started a full --resyncstorage --mirrorgroupid=101 --timestamp=0
 +  * the nr of files and dirs discovered is as expected lower by the correct values
 +  * when I now search for the EntryIDs obtained before they are gone from /data/beegfs-storage (as expected).
 +
 +Nice that it works.
 +
 +So you can full storage content mirror. You'll still need rsnapshots to recover lost data or point in time restores.
  
 ==== Mirror Data ==== ==== Mirror Data ====
 +
 +When not all storage servers are up, client mounts will fail. This is just an optional "sanity check" which the client performs when it is  mounted. Disable this check by setting "sysMountSanityCheckMS=0" in beegfs-client.conf. When the sanity check is disabled, the client mount will succeed even if no servers are running.
 +
 +In order to able able to take a storage server off line without any impact, all content needs to mirrored.
  
 ** Before ** ** Before **
Line 59: Line 87:
                              
 # enable mirroring for data by directory -numTargets needs to be set to max nr of storage servers? # enable mirroring for data by directory -numTargets needs to be set to max nr of storage servers?
 +# changed to 11/02/2016:
 +[root@n7 ~]# beegfs-ctl --setpattern --buddymirror /mnt/beegfs/home --chunksize=512k 
 [root@n7 ~]# beegfs-ctl --setpattern --buddymirror /mnt/beegfs/hmeij-mirror-data --chunksize=512k --numtargets=2 [root@n7 ~]# beegfs-ctl --setpattern --buddymirror /mnt/beegfs/hmeij-mirror-data --chunksize=512k --numtargets=2
 New chunksize: 524288 New chunksize: 524288
Line 101: Line 131:
  
 # copy on primary # copy on primary
-[root@swallowtail ~]# find /var/chroots/data/beegfs_storage -name 178-581797C8-30 
-/var/chroots/data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30 
 [root@petaltail chroots]# ls -lh /var/chroots/data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30 [root@petaltail chroots]# ls -lh /var/chroots/data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30
 -rw-rw-rw- 1 root root 4.9G Apr  7  2014 /var/chroots/data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30 -rw-rw-rw- 1 root root 4.9G Apr  7  2014 /var/chroots/data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30
Line 112: Line 140:
 -rw-rw-rw- 1 root root 4.9G Apr  7  2014 /data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30 -rw-rw-rw- 1 root root 4.9G Apr  7  2014 /data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30
  
-# seems to work+# seems to work, notice the ''buddymir'' directory on primary/secondary
  
 </code> </code>
 +
 +Here is an important note, from community list:
 +
 +  * "actual: 1" means "1 buddy mirror group"
 +    * so the important line that tells you that this file is mirrored is "Type: Buddy Mirror".
 +  * "desired: 2" means you would like to stripe across 2 buddy groups. (targets are buddygroups here)
 +
 +Another note: I changed paths for mirrormd and buddymirror to ''/mnt/beegfs/home'' and now I see connectivity data for meta node cottontail2 which was previously missing because I working on sub directory level.
 +
 +<code>
 +
 +[root@cottontail2 ~]# beegfs-net
 +meta_nodes
 +=============
 +cottontail2 [ID: 250]
 +   Connections: RDMA: 1 (10.11.103.250:8005);
 +
 +[root@cottontail2 ~]# beegfs-ctl --listnodes --nodetype=meta --details
 +cottontail2 [ID: 250]
 +   Ports: UDP: 8005; TCP: 8005
 +   Interfaces: ib1(RDMA) ib1(TCP) eth1(TCP) eth0(TCP)
 +               ^^^
 +
 +</code>
 +
 ==== Quota ==== ==== Quota ====
  
Line 126: Line 179:
  
 ==== Mirror Meta ==== ==== Mirror Meta ====
 +
 +//Metadata mirroring can currently not be disabled after it has been enabled for a certain directory//
  
 Definitely want Meta content mirrored, that way I can use the n38-n45 nodes with local 15K disk, plus maybe cottontail2 (raid 1 with hot and cold spare). Definitely want Meta content mirrored, that way I can use the n38-n45 nodes with local 15K disk, plus maybe cottontail2 (raid 1 with hot and cold spare).
Line 135: Line 190:
  
 # enable meta mirroring, directory based # enable meta mirroring, directory based
 +# change to 11/04/2016: used --createdir to make this home. 
 +[root@n7 ~]# beegfs-ctl --mirrormd /mnt/beegfs/home
 [root@n7 ~]# beegfs-ctl --mirrormd /mnt/beegfs/hmeij-mirror [root@n7 ~]# beegfs-ctl --mirrormd /mnt/beegfs/hmeij-mirror
 Mount: '/mnt/beegfs'; Path: '/hmeij-mirror' Mount: '/mnt/beegfs'; Path: '/hmeij-mirror'
cluster/151.txt · Last modified: 2016/12/06 20:14 by hmeij07