Вы находитесь на странице: 1из 8

Open replicator overview:symrcopy -migrate option for FLM migration .

there can be only control device per session.


##Conisderation.
push operation - remote device should not be access by their remote host.
pull operation - remote device should not be access by their remote host.
device which is more than 2 rdf links must be obtained using platform native too
l
open can be using FBA Devices that could be mapped to the host.
engenutiy 5773 - the 1024 active session.
engenutiy 5771 - the 512 active session.
SYMAPI_RCOPY_SESSION_LIMIT can be changed .
external provisioned devices are fully supported.
encapsulated device that are not geometry limited are fully supported.
encapsulated device that are geometry limited are not supported for -pull operat
ions.
##Device GuideLines
control
symdev=arrayid:device
symdev=arrayid:device

Target
symdev=arrayid:device
wwn=9817345120341023487129341932847

Hot Push:Donor operations


hot push operation -precopy is used
differential option is default for push operation only. so it can be recreated a
ny time.
Hot Pull:the -nodifferential option for pull operations.
front end zero is availabe for -frontend_zero hot -pull only.
Cold Push:open replicator support copy operations for cold push session from virtual devic
e.vdev
open replicator/LM - for Online Pull Only.
open replicator/DM - for all functions except online pull.
SCSI inquiry of Symmetrix devices returning the
WWN for each device
######################################
Solution Enabler
#solution enabler installation packages.
list the step to install solution enabler.
for host AIX/OSF1 all the binary files will fall under /opt/emc
user installation scritp is called as se7200_install.sh
##Solution Enabler Components:BASE - Core functionality/shared libraries and run time.
SYMCLI - collection of binaries known as sycmli

SYMRECOVER - SRDF Session recovery comonent for star.


JNI - Solutions enabler java interface component.
SRM- Storage resource management components such as UDB,SYbase and Oracle.
symcli and symrecover are default for installation on windows/ yes on unix.
##Window installation Screen:three componenets
typical installation.
Customer Installation.
complete installation.
##View custome setup/
base_component,symcli_component,symrecovery_component are installed with typical
installed.
jni_component & srm_component are optional which can be selected with custom ins
tall.
##Optional restart of deamon with typical installation.
EMC
EMC
EMC
EMC
EMC
EMC

SE
SE
SE
SE
SE
SE

SYMAPI Server Daemon


STP DAEMON
EVENT Daemon
RDF Daemon
SRM Daemon
GNS deamon

##Unix Installation :./se7200_install.sh


-silent argument
##Completing the installation (setting the path)
C:\Program Files\EMC\symcli\bin
C:\Program Files\EMC\symcli\man
##Discover Symmetrix arrays.
symcfg discover -symmetrix
symcfg discover -clariion
symmetrix database can sometime referred as the host configuration database.
symapi_db.bin
/var/symapi/db/symapi_db.bin
symcfg verify -- to update the Host configuration database.
symcfg list -status
##License Management:Host based and symmetrix based license.
symmetrix arrays - Engenuity version 5874.
symmetrix array - Engenuity 5875
eLicensing - symcli or smc
##Permanent or evaluation
listing Host based License
symlmf add -type se -lic xxx xxx xxx xxx

symlmf list -type se


symlmf delete -type se -lic xxx xxx xxx xxx
##Host Based License are stored in Files
symapi_licenses.dat
Default Location :C:/Program Files/EMC/SYMAPI/Config
UNIX - /var/symapi/config
##Managing Symmetrix Based Licenses :symlmf add -type emclm -sid 12 -file Filename -v
Registration Table:symlmf add -type emclm -sid -file filname -v
##managing Symmetrix based e-Licenses
symlmf query -type emclm -sid 12
##Options and Environement Variable :symapi option file :UNIX - /var/symapi/config/options
Windows - C:\Program Files\EMC\SYMAPI\config\option
##Option File Parameter :SYMAPI_USE_GNS :- stores and maintain SYMAPI Device Group & Composite group defi
nition across symmetrix arrays which is visible to all local hosts.
SYMAPI_USE_RDFD :- consistency group managed by rdf daemon.
SYMAPI_WAIT_ON_LOCKED_GK :- it specifies where to wiat when the gatekeeper lock
is encountered. it will force symcli to wait when a locked gatekeeper
is encountered.
##Daemon Option file :storapid:inquiry_timeout
storevntd:symm_poll_interval
stor???:logfile_size
stor???:autorestart
daemon_option
EMC\SYMAPI\config\daemon_option
var\symapi\config\daemon_option
autorestart specifies whether wathdog daemon will restart this daemon
log file size represent after how long this each file shoold grow before wrappin
g.
storapid - base daemon
storgnsd - GNS daemon
storrdfd - RDF daemon
storevntd - event daemon
watchdog daemon - storwatchd
symapi server - storsrvd
##Environment def
symcli -env -- to check which of the environment variable can be set.
symcli -def --

symcli mode - it reprsents output reporting style to be compatible wiht prior ve


rsion of symcli.
symcli_output_mode :- this can be set default ,XML_ELEMENT or XML_ATTRIBUTE
symcli_noprompt :- is set to 0 by default which can be set to 1.
symcli_component_scope
symcli_mode and symcli_output_mode
##Environement Variable for Timefinder Operations :symcli_clone_copy_mode :- NOCOPY_NODIFF,COPY_NODIFF,PRECOPY_NODIFF,PRECOPY_DIFF
symcli_clone_emulation :- Timefinder/Clone Activites.
symcli_multi_virtual_snap :- if you have 16 snap sessions or more.
##More Environement Variable :SYMCLI_RCOPY_COPY_MODE:- COPY_DIFF,COPY_NODIFF,NOCOPY_DIFF,
SYMCLI_REMOVE_SYSMS:- if set 1 it will remove all configuration of symmetrix whe
n the symmetrix is no longer reachable. remove device group,
SYMCLI_SKIP_ON_FAILURE:- if set 1 during scanning of symmetrix , it will skip t
hat and continue to scan other arrays. will discover all the scans .
SYMCLI_VERBOSE:- enable verbose output.
SYMCLI_WAIT_ON_DB:- waits to obtain a lock on configuration datbase when locked
by another user.
SYMCLI_WAIT_ON_GK:- ask the symcli to wait when the gatekeeper is busy unless it
will generated the error.
##Symavoid :for avoiding specific array symmetrix.
on id perline.
/var/symapi/config
/emc/SYMAPI/Config
symcfg discover command .
##Gatekeeper Management :Gatekeeper selection files - gkselect & gkavoid
Gatekeeper Overview :3 Cylinder.
Number required strongly correlated with host application performance.
3 - 5 cylinders , 1 cylinder = 960 KB.
##Gatekeeper Candidates :bcv cannot be used as gatekeeper devices.
fifth are standard non-rdf and non-meta devices.
pre-establish priority list
1. defined and associated.
2. defined.
3. small non-powerpath with gk inquiry flag.
4. small non-powerpath.
5. standard non-rdf and non-meta.
6. R1.
7. R2.
##Managing Gatekeeper Devices :symgate define -- can be used to make them higher in gatekeeper priority list.
Gatekeeper devices must be atleast as the min. volume sized configured 3 cylind
er.

##Gatekeeper selection and avoidance :designates particular devices


overrides symgate definition
gkavoid designates are excluded from consideration during gatekeeper selection.
gkavoid takes the precedance over gkselect.
/var/symapi/config
/emc/SYMAPI/Config
gkselect is formatted with physical device name with 1 pdevname per line.
if there is same entry exists in both the files gkselect and gkavoid. the pdevn
ame will not be considered as

##ACLX Device :engenutiy 5874 onwards.


replaces VCM device as liason b/w host and symmetrix array.
designate with symconfigure device.
the host communicate with array through a pass device with aclx device attribut
e set.
##Lesson 5:- Solution enabler daemon :name the solution enabler daemon.
basedaemon - storapid
storevntd
storgnsd
stordfd
storsrvd
##Daemon and their control :installed localled /SYMAPI/daemon
stordaemon command.
list
install
start
enable
setvar
to improve performance on a number of devices :stordaemon to control the daemons
stordaemon setvar -- command to change the daemon behaviour.
only the event daemon which runs on both client and server end.
##Base Daemon:Centralized GK manager :/SYMAPI/log/storapid-yyyymmdd.log
time tag
process id
source of the event
related api function call.
storapid maintains centralized gatekeeper device management for all solution en
abler application requires access to symmetrix array.
with gns and rdf daemons. when using base daemon to use gatekeeper all , any ac
tion performed with the symgate will be ignored.

base daemon monitors -- SEL symmetrix external Locks & DEL Device External Lock
s :each host running rdfd must run base daemon as well.
Base Daemon Behaviour :- when there is error with base daemon as it requires th
e use of gatekeeper management service.
check the log file -- storapid.log0 and storapid.log1
##Event DAEMON :clearing-house for all event on host.
entity event relates to
sub-component event realtes to
severity level
timestamp
description of event
SYMAPI/log/storevent.log0 and storevent.log1
if your client/server mode,event are forwarded from event daemon on remote serv
eer to client. from there to application node.
log storeventd.log0 and storeventd.log1
both located in the SYMAPI's Log directory.
##GNS Demon.
common repository to store CG/DG definitions.
each host performing management has to run gns deamon.
the solution enabler symapi and symcli do not directly access the gns daemon.
request are forwarded to gns daemon which process all gns daemon
this daemon is the only entity that directly access the gns shared repository.
responsible so that each host has access to most current gns.
enabling gns enables shared repository in symmetrix array.
##GNS Configuration :Enabled/Disabled on each host via SYMAPI_USE_GNS
can be enabled disabled on host using SYMAPI_USE_GNS.
client/server mode.
SYMAPI_GNS_CS_STALE_DATA_TIMEOUT --how frequently the host should check the sym
api dat.access
symapi/log/storgnsd.log0 and storgnsd.log1
##GNS Configuration :symapi_use_gns :symapi/log/storgnsd.log0 and /storgnsd.log1
symapi_conn_type_remote_cached -- every second the gns is enabled and client ca
ching is enabled.
then the client checks periodically with the server determine if the group defi
nition need updating.
diagnostive message logging - storgnsd.log0 and storgnsd.log1
##RDF Daemon :SRDF/A MSC and RDF-ECA CGs
provides consistency.
/SYMAPI/log/storrdfd.log0

log entries include Error Code


##RDF Daemon:provides consistency.
run on each hsot as required.
rdf daemon storrdfd --rdf consistency for SRDF/A MSC and RDF ECA composite grou
p.
storrdfd.log0 and stordfd.log1
##symapi server daemon = storsrvd
storsrvd daemon
accepts management requests.
can be configured to work on few host through nethost
SSL can be confgured.
daemon_option file
you can create nethost file in the /SYMAPI/config directory that lists the trus
ted connection. so server know who has to authorize
when client executes remote symapi connections. if you do not create this file
, then all symapi connection are permitted to connect to
the symapi server.
##Solution Enabler Virtual Appliance :virtual machine that runs VMware esx server 3.5 and later.
runs linux os.
solution enabler.
SYMAPI Server for solution Enabler.
SMI-S
Solution Enabler virtual appliance configuration manager.
storsrvd daemon and solution Enabler Network client access :the Virtual Appliance runs the suse 10 sp2 Jeos operating system.
##Storage Enabler Virtual Appliance configuration Manager:http://appliance:5480
Monitor the application status.
start/stop solution enabler daemon
import/export of persistent data is used when one has to update the virtual app
liance.
##Solution Enabler appliance :VMware ESX/ESXi server 3.5 or later
6 GB Disk Space,512 MB memory,1 CPU.
##Deploying Solution Enabler Virtual Appliance :seconfig

Вам также может понравиться