Veritas Risk Advisor: Working with tickets
Veritas Risk Advisor (VRA) is a data protection and downtime avoidance risk assessment solution. VRA lets you diagnose disaster recovery and high availability (clustering) problems (also called “gaps”) and optimize data protection and reduce risk of downtime. VRA scans your environment and alerts you to any potential gaps, best practice violations, or service level agreement (SLA) breaches. What is a ticket? When VRA detects a gap in your disaster recovery and/or high availability, it issues a ticket. The ticket specifies the problem and the environment entities associated with that problem. For example, VRA can identify: Critical data that is not protected properly. Standby hosts that do not have access to the replicated data. Service Level Agreements (SLAs) that are too strict or too lenient. Inconsistent access to storage by cluster nodes. Searching for tickets The VRA Tickets module lets you filter the list of tickets in your system to find a specific ticket or ticket type. After VRA displays your query search results, you can: Group the results by criteria that you specify. Drill down to see ticket details. View the network topology related to the ticket in the Topology module. Group the results by criteria that you specify. A full description of the ticket is provided, including an explanation of the problem and the items in your environment that are involved. The impact on your system is also shown with suggestions on how to resolve the ticket. Working with tickets You can perform a variety of operations on a ticket during its lifecycle. Mark the ticket as resolved. The next time VRA scans your system, it will consider this issue closed. Suppress a ticket. A suppressed ticket indicates that you are aware of this problem, but you do not want to be informed about it again during the next full system scan. Open the Topology module. You can open the topology module displaying the items relevant to the ticket. Add a note to a ticket. You can add a note to a ticket that describes it in more detail. You can filter by note text to make it easier to find a specific ticket(s). Add a star rating to indicate its level of important. (One star is the lowest ticket rating and five stars the highest.) You can then sort your tickets by rating to quickly see your most important issues. You can also perform operations on multiple tickets. Learning more For more information on working with tickets, see “Using the Tickets Module” in the Veritas Risk Advisor User’s Guide. You can access the User’s Guide and other VRA documentation in the Documents area of the SORT website.
Veritas InfoScale 7.0: Introduction to the vxdbd daemon
The Storage Foundation for Databases (SFDB) commands use the vxdbd daemon to run privileged commands. For example, a database administrator is allowed to run commands for creating snapshots using the SFDB scripts. In addition, SFDB uses the daemon to establish communication between the host and the SFDB repository that is deployed on a different host. To run the vxdbd daemon in the authenticated mode, log in as a superuser (root) and authenticate the daemon. After the authentication process is successful, the SFDB tools communicate with the daemon through the authenticated user. For more information see: Configuring vxdbd for SFDB tools authentication Adding nodes to a cluster that is using authentication for SFDB tools Authorizing users to run SFDB commands Generally, the vxdbd daemon is configured to automatically start when the system does. However, if the daemon fails to start or is unresponsive, you can manually start and stop vxdbd using the /opt/VRTS/bin/sfae_config script. This script can also determine the status of the daemon. For more information on using the script, see: Starting and stopping vxdbd The vxdbd daemon uses an insignificant amount of your resources to perform its routine operations. However, you can restrict the resource usage by setting the MAX_CONNECTIONS and MAX_REQUEST_SIZE parameters. Before you set these parameter values, refer to the documentation. Lower values for these parameters may cause the SFDB commands to fail. For more information, see: Limiting vxdbd resource usage. For more information on the vxdbd daemon, see: Configuring listening port for the vxdbd daemon Configuring encryption ciphers for vxdbd If the vxdbd daemon fails to run, perform the troubleshooting instructions available at: Troubleshooting vxdbd For detailed information, see the Veritas InfoScale™ 7.0 Storage and Availability Management for Oracle Databases. Veritas InfoScale documentation can be found on the SORT website.
Listener failed
Team, During a database activity, we did not freeze the cluster due to some reason,the listener went down due to the activity however database team has confirmed that DB is up and online. Initially, when i tried to check the faulted resource it was not showing.But, when I tried to clear and online the listener resource, it went to Waiting_to_online and then it failed. Could you please statehow we can resolve and make the listener online. Below are the information, A turks RUNNING 0 A madagascar RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B ClusterService turks Y N OFFLINE B ClusterService madagascar Y N ONLINE B DB_TRS_PRD turks Y N OFFLINE B DB_TRS_PRD madagascar Y N PARTIAL -- RESOURCES FAILED -- Group Type Resource System D DB_TRS_PRD Netlsnr trsprd_LSNR madagascar ================================================================ Main.cf O/P - /etc/VRTSvcs/conf/config/main.cf include "OracleASMTypes.cf" include "types.cf" include "Db2udbTypes.cf" include "OracleTypes.cf" include "SybaseTypes.cf" cluster TRS-PRD-MG ( UserNames = { admin = cmnFmhMjnInnLvnHmk, rengasak = JiiMjeHljEikEdfDef, g023154 = hifEfiEciGjiHhiP, sparisd = aPPsMSnONjPNoNMlMR, guptan2 = JljQifKmlNltHhkKliLi, g035006 = hqqWrnQqqSqyPlqVns } Administrators = { admin, rengasav, g023154, sparisd, guptau5, g035006 } ) system turks( ) system madagascar( ) group ClusterService ( SystemList = { turks= 0, madagascar= 1 } AutoStartList = { turks, madagascar} OnlineRetryLimit = 3 OnlineRetryInterval = 120 ) NIC csgnic ( Device = en2 NetworkHosts = { "132.189.210.1" } ) NotifierMngr ntfr ( SmtpServer = "mapintmail@infi.com" SmtpRecipients = { "systemsunix@infi.com" = Error } ) ntfr requires csgnic // resource dependency tree // // group ClusterService // { // NotifierMngr ntfr // { // NIC csgnic // } // } group DB_TRS_PRD ( SystemList = { madagascar= 0, turks= 1 } Frozen = 1 ) IP trsprd_ora_vip ( Device = en2 Address = "132.189.210.138" NetMask = "255.255.255.0" ) LVMVG trsprd_ora_lvmvg ( VolumeGroup = db_trsprd MajorNumber = 40 ) Mount db_trsprd_arch ( MountPoint = "/db_trsprd/arch" BlockDevice = "/dev/trsprd_arch" FSType = jfs2 FsckOpt = "-y" ) Mount db_trsprd_backup ( MountPoint = "/db_trsprd/backup" BlockDevice = "/dev/trsprd_backup" FSType = jfs2 FsckOpt = "-y" ) Mount db_trsprd_data1 ( MountPoint = "/db_trsprd/data1" BlockDevice = "/dev/trsprd_data1" FSType = jfs2 FsckOpt = "-y" ) Mount db_trsprd_data2 ( MountPoint = "/db_trsprd/data2" BlockDevice = "/dev/trsprd_data2" FSType = jfs2 FsckOpt = "-y" ) Mount db_trsprd_data3 ( MountPoint = "/db_trsprd/data3" BlockDevice = "/dev/trsprd_data3" FSType = jfs2 FsckOpt = "-y" ) Mount db_trsprd_dba ( MountPoint = "/db_trsprd/dba" BlockDevice = "/dev/trsprd_dba" FSType = jfs2 FsckOpt = "-y" ) Mount db_trsprd_oracle ( MountPoint = "/db_trsprd/oracle" BlockDevice = "/dev/trsprd_oracle" FSType = jfs2 FsckOpt = "-y" ) Mount db_trsprd_redo1 ( MountPoint = "/db_trsprd/redo1" BlockDevice = "/dev/trsprd_redo1" FSType = jfs2 FsckOpt = "-y" ) Mount db_trsprd_redo2 ( MountPoint = "/db_trsprd/redo2" BlockDevice = "/dev/trsprd_redo2" FSType = jfs2 FsckOpt = "-y" ) Mount db_trsprd_temp ( MountPoint = "/db_trsprd/temp" BlockDevice = "/dev/trsprd_temp" FSType = jfs2 FsckOpt = "-y" ) Netlsnr trsprd_LSNR ( Critical = 0 Owner = oracle Home = "/db_trsprd/oracle/product/11.2.0.2" TnsAdmin = "/var/opt/oracle" Listener = LISTENER_TRSPRD EnvFile = "/oracle/home/.profile" ) Oracle trsprd_ORA ( Critical = 0 Sid = trsprd Owner = oracle Home = "/db_trsprd/oracle/product/11.2.0.2" EnvFile = "/oracle/home/.profile" ) Proxy trsprd_NIC ( TargetResName = csgnic ) db_trsprd_arch requires trsprd_ora_lvmvg db_trsprd_backup requires trsprd_ora_lvmvg db_trsprd_data1 requires trsprd_ora_lvmvg db_trsprd_data2 requires trsprd_ora_lvmvg db_trsprd_data3 requires trsprd_ora_lvmvg db_trsprd_dba requires trsprd_ora_lvmvg db_trsprd_oracle requires trsprd_ora_lvmvg db_trsprd_redo1 requires trsprd_ora_lvmvg db_trsprd_redo2 requires trsprd_ora_lvmvg db_trsprd_temp requires trsprd_ora_lvmvg trsprd_LSNR requires trsprd_ORA trsprd_LSNR requires trsprd_ora_vip trsprd_ORA requires db_trsprd_arch trsprd_ORA requires db_trsprd_backup trsprd_ORA requires db_trsprd_data1 trsprd_ORA requires db_trsprd_data2 trsprd_ORA requires db_trsprd_data3 trsprd_ORA requires db_trsprd_dba trsprd_ORA requires db_trsprd_oracle trsprd_ORA requires db_trsprd_redo1 trsprd_ORA requires db_trsprd_redo2 trsprd_ORA requires db_trsprd_temp trsprd_ora_vip requires trsprd_NIC // resource dependency tree // // group DB_TRS_PRD // { // Netlsnr trsprd_LSNR // { // IP trsprd_ora_vip // { // Proxy trsprd_NIC // } // Oracle trsprd_ORA // { // Mount db_trsprd_temp // { // LVMVG trsprd_ora_lvmvg // } // Mount db_trsprd_backup // { // LVMVG trsprd_ora_lvmvg // } // Mount db_trsprd_arch // { // LVMVG trsprd_ora_lvmvg // } // Mount db_trsprd_redo2 // { // LVMVG trsprd_ora_lvmvg // } // Mount db_trsprd_redo1 // { // LVMVG trsprd_ora_lvmvg // } // Mount db_trsprd_oracle // { // LVMVG trsprd_ora_lvmvg // } // Mount db_trsprd_dba // { // LVMVG trsprd_ora_lvmvg // } // Mount db_trsprd_data2 // { // LVMVG trsprd_ora_lvmvg // } // Mount db_trsprd_data1 // { // LVMVG trsprd_ora_lvmvg // } // Mount db_trsprd_data3 // { // LVMVG trsprd_ora_lvmvg // } // } // } // } =======================================================Creation of new filesystem in vcs environment.
Hi Team, We have to create a new filesystem and it is in2 node cluster. /RMPRDR01/oradata5---> Add this new mount point of 252 GB we have a request to create new filesystem which is in vcs cluster 5.0 For reference about main.cf, attached is the document enclosed. df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 15G 9.3G 5.4G 64% / /devices 0K 0K 0K 0% /devices ctfs 0K 0K 0K 0% /system/contract proc 0K 0K 0K 0% /proc mnttab 0K 0K 0K 0% /etc/mnttab swap 34G 1.7M 34G 1% /etc/svc/volatile objfs 0K 0K 0K 0% /system/object sharefs 0K 0K 0K 0% /etc/dfs/sharetab fd 0K 0K 0K 0% /dev/fd /dev/md/dsk/d6 9.9G 7.5G 2.3G 77% /var swap 36G 2.2G 34G 7% /tmp swap 34G 104K 34G 1% /var/run swap 34G 0K 34G 0% /dev/vx/dmp swap 34G 0K 34G 0% /dev/vx/rdmp /dev/md/dsk/d9 32G 1.9G 29G 7% /var/crash /dev/odm 0K 0K 0K 0% /dev/odm /dev/vx/dsk/RMPRDR01_ora_data_dg/oratemp 135G 127G 7.2G 95% /RMPRDR01/oratemp /dev/vx/dsk/RMPRDR01_ora_data_dg/oradata4 252G 244G 7.0G 98% /RMPRDR01/oradata4 /dev/vx/dsk/RMPRDR01_ora_data_dg/oradata2 252G 251G 310M 100% /RMPRDR01/oradata2 /dev/vx/dsk/RMPRDR01_ora_data_dg/oradata3 252G 243G 8.3G 97% /RMPRDR01/oradata3 /dev/vx/dsk/RMPRDR01_ora_data_dg/oradata1 252G 251G 882M 100% /RMPRDR01/oradata1 /dev/vx/dsk/RMPRDR01_ora_arch_dg/orafra 107G 5.0G 96G 5% /RMPRDR01/orafra /dev/vx/dsk/RMPRDR01_ora_arch_dg/oradmp 67G 17G 48G 26% /RMPRDR01/oradmp /dev/vx/dsk/RMPRDR01_ora_bin_dg/oraredo2 10G 7.9G 1.9G 81% /RMPRDR01/oraredo2 /dev/vx/dsk/RMPRDR01_ora_bin_dg/oraredo1 10G 7.9G 1.9G 81% /RMPRDR01/oraredo1 /dev/vx/dsk/RMPRDR01_ora_bin_dg/oractl3 2.0G 38M 1.8G 2% /RMPRDR01/oractl3 /dev/vx/dsk/RMPRDR01_ora_bin_dg/oractl2 2.0G 38M 1.8G 2% /RMPRDR01/oractl2 /dev/vx/dsk/RMPRDR01_ora_bin_dg/oractl1 2.0G 38M 1.8G 2% /RMPRDR01/oractl1 /dev/vx/dsk/RMPRDR01_ora_bin_dg/oracle 20G 12G 7.5G 62% /RMPRDR01/oracle ==================================================================== vxdisk -o alldgs list o/p - DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online invalid c0t1d0s2 auto:none - - online invalid emcpower0s2 auto:cdsdisk emcpowerN17 RMPRDR01_ora_arch_dg online emcpower1s2 auto:cdsdisk emcpowerN27 RMPRDR01_ora_data_dg online emcpower2s2 auto:cdsdisk emcpowerN28 RMPRDR01_ora_data_dg online emcpower3s2 auto:cdsdisk emcpowerN31 RMPRDR01_ora_arch_dg online emcpower4s2 auto:cdsdisk emcpowerN34 RMPRDR01_ora_data_dg online emcpower5s2 auto:cdsdisk RMPRDR01_ora_bin_dg01 RMPRDR01_ora_bin_dg online emcpower6s2 auto:cdsdisk emcpowerN32 RMPRDR01_ora_data_dg online emcpower7s2 auto:cdsdisk emcpowerN24 RMPRDR01_ora_data_dg online emcpower8s2 auto:cdsdisk emcpowerN26 RMPRDR01_ora_data_dg online emcpower9s2 auto:cdsdisk emcpowerN29 RMPRDR01_ora_data_dg online emcpower10s2 auto:cdsdisk emcpowerN16 RMPRDR01_ora_arch_dg online emcpower11s2 auto:cdsdisk emcpowerN30 RMPRDR01_ora_arch_dg online emcpower12s2 auto:cdsdisk emcpowerN33 RMPRDR01_ora_data_dg online emcpower15s2 auto:cdsdisk emcpowerN35 RMPRDR01_ora_data_dg online emcpower16s2 auto:cdsdisk emcpowerN23 RMPRDR01_ora_data_dg online emcpower44s2 auto:cdsdisk emcpowerN19 RMPRDR01_ora_data_dg online emcpower45s2 auto:cdsdisk emcpowerN20 RMPRDR01_ora_data_dg online emcpower46s2 auto:cdsdisk emcpowerN21 RMPRDR01_ora_data_dg online emcpower47s2 auto:cdsdisk emcpowerN22 RMPRDR01_ora_data_dg online emcpower50s2 auto:cdsdisk emcpowerN25 RMPRDR01_ora_data_dg online =========================================================================== vxassist -g RMPRDR01_ora_data_dg maxsize Maximum volume size: 963203072 (470314Mb) We have a free size available in RMPRDR01_ora_data_dg to 459.29 GB as the system is in cluster ============================================================================ hastatus -summ -- SYSTEM STATE -- System State Frozen A francona RUNNING 0 A lackey RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B MODELN_RPT francona Y N OFFLINE B MODELN_RPT lackey Y N ONLINE Kindly assist the steps to create a new filesystem, as in this request, /RMPRDR01/oradata5---> Add this new mount point of 252 GB. Let me know if any other info required.