Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...

More documents

Recommendations

Info

56Picture Perfect 4.6 Enterprise EditionUser ManualTable 5.ercmd.sh optionsOptionDescription--recover_table -b table_name -s source_host [-a action ] [-g triggeraction ]--recover_allhosts -s [-a action ] [-g triggeraction ]--recover_subhost -t [-a action ] [-g triggeraction ]This option calls cdr_er_recover_table.sh according to the parametersentered.• (required parameter) - name of the table to recover• (required parameter) - master server name to recover from- When run on nethost, must be specified (must be oneof the subhosts).- When run on subhost, defaults to nethost. If is specified, it must be the nethost.• [- a action d|m] (optional) - ‘d’ for deleting records on the target server;‘m’ for merging those records back to the server.If no action is specified, it defaults to 'm' - merge.• [-g triggeraction ] (optional) - ‘on’ to indicate triggers are fired on the target server; ‘off’ to indicate triggers are not fired on the target server.The trigger action (sync or check) is determined per table, based on dataon the target server for base/badge data and based on the number ofdifferences.- If there is no data on the target or if the number of differences betweensource and target server for given table is >= 100000, then sync is used.- If there is data on the target with < 100000 diffs, then check is used.Note: When the triggers do not fire, depending on the table that is beingrecovered, the micros will not get the changes or cache will not be updated.This option is available only on the nethost. It recovers all hosts.This option calls cdr_er_recover_table.sh for each target host and foreach replicated table.The argument can be the nethost or any one of the subhosts.The other parameters have same defaults and meaning, as described for therecover_table option above.This option is available on nethost and subhosts. It recovers replicated tables.• If run on the nethost, for each of the replicated tables, callscdr_er_recover_table.sh with subhost hostname.• If run on the subhost, for each of the replicated tables, callscdr_er_recover_table.sh with the local hostname as target.The other parameters have same defaults and meaning as described for therecover_table option above.--recover_status [-b table_name]--remove_ERThis option displays the recovery status for replicated tables; it optionally takesthe table_name argument to display the recovery status for the specifiedtable.• If a table is currently being recovered, the status shows Started. Whendone, it shows Completed.• The recovery status on a host (nethost or subhost) shows data for itselfonly if a recovery was run on that host.This option is available on the nethost and subhosts.• When run on the nethost, it removes ER from the whole Enterprise system.• When run on a subhost, it removes that subhost from ER.
Chapter 4Managing your network database57hostconfigWith the introduction of ER, the existing /cas/bin/hostconfig script is given additionalfunctionality.During initial installation, hostconfig adds the subhosts to the ER configuration. The script readsthe host table on the nethost and defines every subhost in the installation.The hostconfig script performs the following tasks:• Starts up the database on the nethost• Checks if it is necessary to stop Picture Perfect on the nethost• Checks if all subhosts configured in the host table are reachable through the network• Checks if SSH is properly configured for all subhosts• Enters a loop on all subhosts to configure services and Informix sqlhosts files• Checks the UTC time configuration• Starts up the subhost database• Begins setting all items needed by ER:- Informix sqlhosts file- Sequence objects- Primary keys and shadow columns- Triggers and stored procedures- ER server and table replicates• Synchronizes all servers• Shows a report of final statusWhile hostconfig is running, all new (except nethost) or recovered servers automatically enter in aprocess of database synchronization, depending on the database restore status. Since the processof synchronizing a database can take several minutes, depending on the number of records in thereplicated tables, a progress report is shown on the screen. The progress report indicates the currenttable, number of records to synchronize, start time and expected time to finish the process as shownin the example below:----------------------------------------------------------------------Picture Perfect hostconfig utility - Version 4.6 04/25/2011Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.----------------------------------------------------------------------Checking sqlhosts file... bctalford[*]Processing [bctdover]Server [bctdover] already set up for ER... [skipping].Processing [bctalford]Service and port were okayChecking for [bctalford] database.... Starting up, please wait .... [Done].Updating sqlhosts file for [bctalford]...Stopping Informix database to update sqlhosts with subhost‘bctalford’..[Done].Starting the Informix database.. [Done].Copying .netrc to bctalford ppadmin and ppapp home directories [Done].Updating hcomm_ingrp field on host table...Checking for replication status... [Done}.Configuring sqlhost file for ER... [Done].Configuring remote sqlhosts file(s) for ER... [Done].
Page 1:
Picture Perfect 4.6 Enterprise Edit
Page 5 and 6:
iiiChapter 6. Troubleshooting and s
Page 7 and 8:
iPrefaceThis document is designed t
Page 9 and 10:
Chapter 1 Enterprise system overvie
Page 11 and 12:
Chapter 1Enterprise system overview
Page 13 and 14: Chapter 2 Installing the Picture Pe
Page 15 and 16: Chapter 2Installing the Picture Per
Page 34 and 35: 26Picture Perfect 4.6 Enterprise Ed
Page 108 and 109: 100Picture Perfect 4.6 Enterprise E
Page 114 and 115:
106Picture Perfect 4.6 Enterprise E
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126:
show all

Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...

Create successful ePaper yourself

Delete template?

Save as template?