CloudBoost integration with ECS part 2

cloudboost-and-ecs-part-2Part 2.

In that post I’ll continue discussing how to integrate backup solution based on CloudBoost with ECS.

Part 1 is here.

  • We proceed with a share configuration.

cloudboost-and-ecs-16

  • Cloud Storage Profile is the ECS Profile we already created.

cloudboost-and-ecs-17

  • Share creation process takes some time…

cloudboost-and-ecs-18

  • Share is active now.

cloudboost-and-ecs-19

  • Several objects were added.

cloudboost-and-ecs-20

  • Enable remote and ssh access.

cloudboost-and-ecs-21

  • ssh to CB. User “maginatics” and the password we assigned on the previous step have to be used.
# ssh maginatics@10.76.246.10

maginatics@10.76.246.10's password:
                       ____  
                       |___ \
   _____ __ __ ____   __) |
   | ____| \/ |/ ___| / __/
   | _| | |\/| | |   |_____|
   | |___| | | | |___        
   |_____|_| |_|\____|      
Welcome to the EMC Management Console (3.2.6)
  • Check access to ECS.

Some details for a blobstore validate command are here:

maginatics@cb:/mnt/magfs/base$ cd /opt/maginatics/blobstore-cli
maginatics@cb:/opt/maginatics/blobstore-cli$ java -jar blobstore-cli.jar --provider s3 --endpoint https://object.ecstestdrive.com --identity 130790262785219969@ecstestdrive.emc.com --credential wIe2HzvgnrEGhassL+iTPv6wggi+5G86YS+5wz3D validate
Checking list containers/blobstore credentials ...
Checking create container ...
Checking listing blobs (empty container) ...
Checking blob creation ...
Checking listing blobs ...
Checking blob retrieval ...
Checking signed get (without timeout) ...
Checking blob removal ...
Checking signed put (without timeout)
Checking blobstore time skew ...
Checking clear container ...
Checking delete container ...

RESULTS:
LIST                     : SUPPORTED
CREATE_CONTAINER         : SUPPORTED
LIST_BLOBS_EMPTY_CONTAINER: SUPPORTED
CREATE_BLOB               : SUPPORTED
LIST_BLOBS               : SUPPORTED
FETCH_BLOB               : SUPPORTED
FETCH_BLOB_SIGNED         : SUPPORTED
REMOVE_BLOB               : SUPPORTED
CREATE_BLOB_SIGNED       : SUPPORTED
CLOCK_SKEW_CHECK         : PASSED
CLEAR_CONTAINER           : SUPPORTED
REMOVE_CONTAINER         : SUPPORTED
  • Lets check a performance to get access to our ECS.

Some details for a blobstore benchmark command are here:

maginatics@cb:/opt/maginatics/blobstore-cli$ java -jar blobstore-cli.jar --provider s3 --endpoint https/object.ecstestdrive.com --identity 130790262785219969@ecstestdrive.emc.com --credential wIe2HzvgnrEGhassL+iTPv6wggi+5G86YS+5wz3D benchmark --num-parallel-requests 16 --blob-size 262144 --max-runtime 60 --container gcs-benchmark WRITE
Starting benchmark ...

Benchmark done in 61 seconds
Number of operations: 988
Number of failures: 0
Blob size: 262144
Number of parallel requests: 16
Number of configured retries: 0
Elapsed time (s): 61
Bandwidth (KB/s): 4146.4
Throughput (Obj/s): 16.2

Successful transfer latency:
Minimum (ms): 253.0
50% (ms): 852.5
95% (ms): 2016.6
99% (ms): 2860.0
99 .9% (ms): 4365.0
Maximum (ms): 4365.0
Mean (ms): 975.7
Standard deviation: 524.0
  • Cloudboost performance can be viewed from the WebUI: https://<CB IP>:4444/client-performance

cloudboost-and-ecs-22

  • Currently I don’t have a NetWorker installed in my lab (will be tested shortly and describe in the next blog post). But I still like to check if backups can be written to CB. Let’s check CB system backups.

Currently I have 63 objects in the CB bucket.

cloudboost-and-ecs-23

  • Navigate to Shares > Manage Share Backups.

cloudboost-and-ecs-24

  • Start backup Now.

cloudboost-and-ecs-25

  • Backup is done.

cloudboost-and-ecs-26

  • Number of objects in the bucket was increased to 67.

cloudboost-and-ecs-27

  • In the next blog post I’ll test NetWorker cloning with CloudBoost. When that is done, you’ll see a folder structure under /mnt/magfs/base. But now it is empty.
maginatics@cb:/opt/maginatics/blobstore-cli$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/mapper/TrollGroup-TrollVolume on /lvm type ext4 (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
//cloud.emc.com/cloud on /mnt/magfs type fuse.magfs (rw,nosuid,nodev,allow_other)

maginatics@cb:~$ ls /mnt/magfs/base/

maginatics@cb:~$

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s