 |
|
United States-English | |
|
|
 |
|
NonStop computing
> News
Manageability improvements and more with new release of HP NonStop RDF software, v1 – Update 9 |
|
|
With RDF 1.9, users now have the option for faster browse access of replicated data on their backup system via FASTUPDATEMODE (the older version was called SLOWMODE). This new option forces RDF to write data to its target system faster and will assist customers who wish to read updates on the backup system within a second or two of their appearance on the primary system. There is potential impact on overall RDF throughput with this choice, so the RDF manual has been updated to cover all considerations in detail. Note that this feature also supports the replication of changes in TMF’s master audit trail (MAT) as well as those in auxiliary audit trails. More available – faster takeover and more flexible updater mode changes The RDF System Management Manual has been significantly improved and expanded with Update 9. In particular, there are more guidelines for ensuring the fastest switchover and takeover procedures for a variety of replication environments. Generating periodic online dumps of TMF audit is a disaster tolerance best practice and a new RDF feature makes this easier. Doing the procedure previously required stopping and then restarting the RDF updaters, to modify the UPDATEOPEN option online. This option is usually set to Protected, to secure the backup database from rogue operations. Now you can change status from Protected to Shared, generate online dumps, and then change UPDATEROPEN back to Protected, without stopping and restarting updaters. Better manageability – more controls, greater flexibility and useability Previously, RDF events involving Shared Access DDL operations for SQL/MX tables only showed the internal Guardian filename of the table. Now these same events will include the MX table names. RDF, as well, now supports longer process names, allowing a maximum of 6 characters, including <$>. Also, in earlier versions, RDF had one option for replicating all purge operations and, if turned on, all purges were replicated (although this option was discouraged). Now there is more flexibility to selectively replicate purges at the subvolume and file level, as needed – this is very useful for IBM Websphere MQ Series users, in particular. In earlier product versions, an RDFCOM error message displayed when initialization failed due to the presence of control files – users needed to purge these manually before RDF could not be initialized. Now, in RDF 1.9, the error message will include the fully qualified name of the control subvolume, along with the name of the node in the error message. But, moreover, there is also a new option to purge control files automatically during initialization. Previously, whenever a SQL SHARED ACCESS DDL operation occurred, RDF on the backup system would access the primary system to get the ANSI name of the table. However, this would not work if the primary system was inaccessible. Now, the RDF updater process will try to get the ANSI name of the table from the backup system itself. If it is successful, it logs an event with the ANSI name; if not successful, it logs a different event, with the Guardian name. As mentioned earlier, the RDF manual has been upgraded. Among many improvements, it covers useful details on controlling multiple RDF configurations from a single RDFCOM session or in an OBEY file. The manual also describes how to trigger a Takeover procedure in an OBEY file and shows options for using RDF/ZLT in a Triple Contingency architecture. More information Update 9 is available (downloadable) upon request for systems licensed for any version of HSA44V1, HSA88V1, QSA44V1 and QSA88V1software, at no additional charge. This update will be shipped for new RDF orders on HP NonStop Integrity Servers and BladeSystems. Thus, the previous version of RDF for HP NonStop servers is now mature. Note that for current owners of RDF on G Series wanting an upgrade (for SA44v1, SA88v1), Update 9 will available in the June 2009 timeframe, via download from the HP Scout website. All the features listed above will be available except for one: ANSI names will not be displayed in EMS event messages when an RDF updater encounters SQL SHARED ACCESS DDL operations on SQL/MX objects. Also, note that some features from the earlier RDF v1 Update 8 were not available for G-Series. However, these enhancements are being considered as possibilities in the future, with Update 10. For more details on RDF 1.9, see the included documentation, the most recent manual set at www.docs.hp.com, or ask your local account team. For more on business continuity products, see www.hp.com/go/nonstopcontinuity. This news is published on HP websites, May 2009.
|
||||||||||||||||||||||||||||||||||||||||||||||
Printable version
|
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||