Difference between revisions of "4 4 3 Beefalo:Configuring and Administering HPE Catalyst Data Store by using CLI"

From SEPsesam
Jump to: navigation, search
Line 192: Line 192:
 
* <tt><ssid>.info</tt>
 
* <tt><ssid>.info</tt>
  
<translate><!--T:93--> The saveset data is stored in the <tt>.data</tt> file. The SEP sesam saveset attributes are remembered in the <tt>.info</tt> file. Both files are identical to those of other data stores, e.g. 'Path' data store.</translate>
+
<translate><!--T:93--> The saveset data is stored in the <tt>.data</tt> file. The SEP sesam saveset attributes are remembered in the <tt>.info</tt> file. Both objects are identical to those of other data stores, e.g. 'Path' data store with files <tt><ssid>.data</tt> and <tt><ssid>.info</tt>.</translate>
  
 
==What is next?== <!--T:96-->
 
==What is next?== <!--T:96-->

Revision as of 15:01, 31 July 2019

Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2020. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3 Beefalo. For previous documentation version(s), check documentation archive.


Overview

This article describes details about the configuration of HPE StoreOnce Data Stores on SEP sesam.

Configuring using CLI

The sm_config_drives command is used to configure the access to the HPE Catalyst store on the HPE StoreOnce server.

sm_config_drives

The sm_config_drives retrieves the HPE StoreOnce Server address and the HPE Catalyst Store name with optional Client and password settings. These parameters are automatically copied to the HPE StoreOnce data store drive configuration file, which resides in the folder <SESAM_VAR>/ini/stpd_conf.

stpd_conf

The HPE StoreOnce Data Store configuration is saved in an stpd .ini file in the directory gv_rw_ini:stpd_conf.

The .ini file name is derived from the Data Store name data_stores.name ('HPE_Store1'), as is the case for every other Data Store and the drive number of the first drive for this data_store, e.g. 'HPE_Store1_2.ini'. The Data Store name is also used as device name in the hw_drives table together with prefix 'DS@' and the drive number, e.g. hw_drives.device='DS@HPE_Store1_2'.

bigsrv1:/var/opt/sesam/var/ini/stpd_conf # cat HPE_Store_1_2.ini

[CATALYST]
backend=catalyst_store
hostname=storeoncevsa.srv.qa.mycompany.com
catalyst_store=HPE_Store_1
command_port=9387
data_port=9388
access_key="bigsrv1"
secret_key={8494a4b4c4d4e4f4675bfe5226281414d14a58c0f514f524eda63797b8114749}

[DISK_STORE]
Storage_Location=/HPE_Store_1
Size=-10GB
backend=catalyst_store
hostname=localhost

Advanced CLI Administration

The sm_dedup_interface command is used as a front end for the HPE Catalyst store on the HPE StoreOnce server.

sm_dedup_interface

Valid commands and usage

sm_dedup_interface -d <datastore> <command>

sm_dedup_interface.exe -d 40 usage
2019-07-31 13:12:50 gitID: $Id: e89e3e461f (HEAD -> v4_4_3_5, tag: v4_4_3_5_build, origin/v4_4_3_5) 2019-07-19 13:20:59 +0200 $, Si3/Si3-NG & StoreOnce
Common options:
 init -u <uuid> -t <label>    initiate upper data store directory structure
 init -t <tape_spec>          initiate lower data store directory structure
 status                       get data store status
 df                           get full summary of available and used disk space usage of file system
 du                           get used disk space usage of file system
 list|dir [<saveset>*]        get saveset information
 delete <saveset> [<saveset>*]
                              remove saveset from data store
 getlabel                     get data store label
 getpath                      get data store path
 getuuid                      get data store uuid
 put <input filename> <dest filename> [over]
                              upload file into data store
 get <remote filename> <dest filename> [<bytes skipped then> [<bytes read at beginning>]]
                              download file or it's part from data store

Note: Some of the parameters are for internal use or for future use only.

status

Provides information about encryption, used space, saved data and object summary.

bigsrv1:/var/opt/sesam/var/ini/stpd_conf # sm_dedup_interface -d 2 status
2019-07-31 13:15:38 gitID: $Id: e89e3e461f (HEAD -> v4_4_3_5, tag: v4_4_3_5_build, origin/v4_4_3_5) 2019-07-19 13:20:59 +0200 $, Si3/Si3-NG & StoreOnce
Using HPE StoreOnce Catalyst Client
Ctl_SetCredentials [storeoncevsa-v4.srv.qa.hk.sep.de]
Ctl_SetLogDescriptor [C:\ProgramData\SEPsesam\var\log\sms/stpd_so_20190731.log] Log size: [2621440] Log level: [0]
Ctl_GetServerProp [storeoncevsa-v4.srv.qa.hk.sep.de]
Server Status:
 Repository information:      2019-07-31 13:15:39
  HPE StoreOnce time:         2019-07-31 11:15:39
  Creation time:              2019-07-09 13:14:07
  Last modified time:         2019-07-18 11:30:29
  Path:                       HPE_Store_1
  Version:                    2 (Server version: 4.1.1-1849.3)
  Encryption:                 Off
  Bytes in repository:          23.5 GiB
  Jobs:                       All: 414 Data jobs: 314 Dest copy jobs: 0 Origin copy jobs: 0
  Status:                     Online (Ok: Online)
  Free data sessions:         13/32
  Object lock resources:      Available
  HPE Storage:                Bytes All: 882079956992, Use: 53624758272, Free: 828455198720, Used: 6%
  Logical  Storage Quota:     Bytes All: -, Use: 239273889320, Free: -, Used: 0%
  Physical Storage Quota:     Bytes All: -, Use: 25270237105, Free -, Used: 0% 
 Object information:
  Objects stored:             102
  Data before deduplication:   222.8 GiB
  Data after  deduplication:    23.5 GiB
  Overall DeDup ratio:        1 / 9.80
  Saved storage space:        89.44 % 

STATUS=SUCCESS MSG=

The value Overall DeDup ratio shows by what percentage the stored data has been reduced.

list|dir [<saveset>*]
  • List all objects or the given savesets in the HPE Catalyst store.
delete <saveset> [<saveset>*]
  • Deletes all given savesets from the HPE Catalyst store.
get
  • Reads an object (file, saveset) from the HPE Catalyst store.
  • '-' can be used to specify STDIN
put
  • Writes an object (file, saveset) to the HPE Catalyst store.
  • '-' can be used to specify STDOUT

Logging

The HPE Catalyst Client library logging is written to the file gv_rw_sms:stpd_so_<day>.log, example logging file name /var/opt/sesam/var/log/sms/stpd_so_20190731.log.

The log settings are defined with the log settings Log_Levels and Log_Size (size in KiB) from the gv_rw_ini:stpd.ini.

[STPD_Logging]
Log_Levels=2
Log_Size=1024

Note: Available Log_Levels=0 1 2 3 4 5 6 with -1=NO_LOG, 0=ERROR, 1=EMERGENCY, 2=WARNING,3=NOTICE, 4=INFO, 5=DEBUG, 6=TRACE. These logging levels are mapped to the corresponding HPE StoreOnce Catalyst Client Library logging levels OSCLT_LOG_LEVEL_ERROR, OSCLT_LOG_LEVEL_QUIET, OSCLT_LOG_LEVEL_INFO, OSCLT_LOG_LEVEL_TRACE, OSCLT_LOG_LEVEL_DEBUG and OSCLT_LOG_LEVEL_EXTENDED_DEBUG.

Auto rotation happens if the log file size reaches the maximum log size defined via Log_Size.

Additional log settings.

The logging level settings defined in gv_rw_ini:stpd.ini may be overwritten with specific settings in the HPE StoreOnce data store drive configuration file gv_rw_ini:stpd_conf/{name}_{drive_num}.ini.

  • Example /var/opt/sesam/var/ini/stpd_conf/HPE_Store_1_2.ini with increased logging level and size.
[CATALYST]
Log_Levels=5
Log_Size=20480
backend=catalyst_store
hostname=storeoncevsa.srv.qa.mycompany.com
catalyst_store=HPE_Store_1
command_port=9387
data_port=9388
access_key="bigsrv1"
secret_key={8494a4b4c4d4e4f4675bfe5226281414d14a58c0f514f524eda63797b8114749}

[DISK_STORE]
Storage_Location=/HPE_Store_1
Size=-10GB
backend=catalyst_store
hostname=localhost

HPE Catalyst Store Objects

Objects created in the HPE Catalyst Store

For every SEP sesam saveset, two objects are stored in the HPE Catalyst store:

  • <ssid>.data
  • <ssid>.info

The saveset data is stored in the .data file. The SEP sesam saveset attributes are remembered in the .info file. Both objects are identical to those of other data stores, e.g. 'Path' data store with files <ssid>.data and <ssid>.info.

What is next?

After configuring the HPE StoreOnce Data Store, configure the media pools first then set up your backup strategy.