LCDI Instances

Synopsis

• ins_gettag [-d destsys] -i id

• ins_create [-d destsys] -a appname -r restyp [-I{AUTORES_ISP|INIT_ISP| INIT_OSU}] [-v info] -t tag -i id [-Q quickChkInt] [-DdeepChkInt] [-l localRecover{Y/N}] [ -s AUTOMATIC/INTELLIGENT]

• ins_remove [-d destsys] [-R roottag] [-a appname] [-r restyp] [-ttag] [-i id] [-v] [-I] [-N] [-G]

• ins_setin [-d destsys] -t tag [-v info]

• ins_setit [-d destsys] -t tag -I {AUTORES_ISP|INIT_ISP|INIT_OSU}

• ins_setst [-d destsys] -t tag -S {ISP|ISU|OSU} [-R reason] [-A]

• ins_list [-d destsys] [-fC] [-R top] [-a appname] [-r typ] [-t tag] [-i id]

• ins_setchkint [-d destsys] -t tag -c {q=quick|d=deep} -vinterval

• ins_setlocalrecover [-d destsys] -t tag -l {Y=enable|N=disable}

• ins_setas [-d destsys] -t tag -s {INTELLIGENT|AUTOMATIC}

Description

Resources are used by LifeKeeper to represent volumes, applications, or system objects known by the system. Resource types are classifications of resources; resource instances are actual instances of a resource type. For example, resource types would include file system volumes, file shares, IP addresses, LAN Manager names and various servers like SQLServer. Generic, user-definable types permit users to build custom fault resilient setups. Multiple instances may exist for a resource type.

Resource instances may exist in a number of states. These states may take on the following values and meanings:

Exit Codes

All commands exit to 0 if they are successful. Commands exit with a nonzero code and print to standard error if they fail. The following exit codes could be returned by these commands: