Technical FAQ - VERITAS Database EditionTM 1.0 for DB2 EE


General Questions

1.   What is VERITAS Database Edition™ for ...
6.   What are the availability benefits of VERITAS Database Edition for DB2?
     Database Edition for DB2 provides higher...
(their physical nature fixes their size) and you have to combine physical devices of fixed sizes (which may not be
     op...
VERITAS Quick I/O

11. What is Quick I/O?
    Quick I/O is a unique database accelerator technology that is available only...
16. What is Cached Quick I/O?
    Cached Quick I/O is an enhancement to File System Quick I/O technology designed to impro...
19. What is VERITAS FlashSnap?
    VERITAS FlashSnap is a new option for VERITAS Volume Manager (included in Database Edit...
24. IBM DMS provides a VERITAS Cluster Server Agent for DB2 on the DB2 v7.2 CD. Is this the same agent that
    is used wi...
DB2 and Platform Compatibility

28. What versions of DB2 does the VERITAS Database Edition for DB2 support?
    Database E...
32. Is the VERITAS Cluster Server Agent for DB2 available separately?
    The VERITAS Cluster Server Agent for DB2 is avai...
Upcoming SlideShare
Loading in …5
×

VERITAS Storage Solutions for IBM AIX 5

567 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
567
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

VERITAS Storage Solutions for IBM AIX 5

  1. 1. Technical FAQ - VERITAS Database EditionTM 1.0 for DB2 EE General Questions 1. What is VERITAS Database Edition™ for DB2? VERITAS Database Edition™ for DB2 is an integrated suite of data and storage management products optimized for the DB2 Universal Database (UDB) environment. This DB2-certified product suite combines the performance and data integrity of raw devices with the manageability of building DB2 databases on file systems. The Database Edition also increases availability through RAID redundancy techniques, online administration and failover capabilities, providing unprecedented performance, availability and manageability for DB2 databases. To deliver the superior performance of raw devices coupled with the administrative benefits of file systems for DB2 databases, VERITAS developed a breakthrough file system interface technology called VERITAS Quick I/O™. Incorporating Quick I/O and its Cached Quick I/O enhancements into VERITAS File System™, the Database Edition enables DB2 databases to meet the challenges of enterprise computing. Additionally, there is a high availability (HA) version of Database Edition, VERITAS Database Edition/HA for DB2 that supports availability clustering and is designed to meet demanding 7x24 uptime requirements. The HA version adds VERITAS Cluster Server™ and the VERITAS Cluster Server Agent for DB2. The Cluster Server Agent for DB2 manages the availability of one or more DB2 databases, leveraging the Cluster Server availability engine to maximize the uptime of DB2 database environments. 2. What problems does VERITAS Database Edition for DB2 address? Database Edition for DB2 solves the traditional raw device dilemma faced by DB2 administrators. While raw devices offer higher levels of performance, they are more difficult and costly to administer than file systems. IBM Data Management Systems (DMS), the vendor of DB2 UDB software, traditionally has allowed customers to implement DB2 on either raw devices or file systems, but provided appropriate guidance regarding the manageability, reliability and performance trade-offs associated with each alternative. In large and/or dynamic database environments, the raw device option often is untenable. As businesses increasingly depend on databases, more database environments are experiencing very high growth, raising the requirements for data availability and performance. At the same time, administrative budgets are not keeping pace, creating a disconnect in many database environments today between the need for high performance and availability with low administrative costs. Database Edition is a perfect fit for these types of environments, providing improved manageability for DB2 environments with high performance and high availability. 3. How is VERITAS Database Edition for DB2 supported? As Database Edition for DB2 is a VERITAS product only available through VERITAS-authorized distribution channels, VERITAS performs all first-line call support. We have a Cooperative Support Agreement in place with IBM DMS and have cross-trained our respective technical support teams on this product. IBM DMS and VERITAS have jointly tested VERITAS Database Edition for DB2. IBM DMS has fully certified its use with DB2 and supported it. Benefits of VERITAS Database Edition for DB2 4. What are the performance benefits of VERITAS Database Edition for DB2? Database Edition for DB2 increases performance in DB2 environments by: • Delivering raw device or better performance for DB2 running on the VERITAS File System • Improving throughput and bandwidth for online transaction processing (OLTP) • Enabling unsurpassed performance for large file I/O applications such as multimedia and imaging 5. Does VERITAS Database Edition for DB2 support VERITAS QuickLog™? No, QuickLog is not supported on DB2 at this time. November 2002 1
  2. 2. 6. What are the availability benefits of VERITAS Database Edition for DB2? Database Edition for DB2 provides higher availability than conventional DB2 environments (whether they use raw devices or file systems) by: • Providing online management of underlying volumes and file systems; data layout options including resizing and/or defragmenting file systems, mirror manipulation (add, attach, detach) and stripe depth/width modification. All can be done online without impacting DB2 database availability • Allowing redundant storage configurations (RAID 1, RAID 0+1, RAID 1+0, RAID 5) to provide uninterrupted access to data despite physical disk failures • Achieving fast recovery of file systems (literally within seconds, regardless of file system sizes) following a system crash or reboot through VERITAS’ file system journaling capability, a feature that is always enabled. (Note that the quoted performance characteristics of the Database Edition for DB2 accrue with the journaling running) The base Database Edition provides the above benefits for DB2. If the high availability version (VERITAS Database Edition™/HA for DB2) is purchased, the following additional benefits also exist: • All critical hardware and software components comprising the DB2 database are proactively managed to maintain high availability, including all database server hardware, the VERITAS Database Edition software components themselves and all DB2 databases • If for any reason the DB2 database hangs or disappears, the VERITAS Cluster Server availability engine diagnoses the problem and automatically takes the steps necessary to recover the data service as quickly as possible, which could include restarting the DB2 database on the same node or failing it over to any one of up to 31 additional servers that can be configured in a Cluster Server cluster • Using the manual failover option to keep DB2 databases up and running, even during system upgrade or maintenance activities that absolutely require server downtime; the manual failover option allows DB2 databases to be moved to other systems in the cluster that will be unaffected by the upgrade or maintenance activities 7. What are the manageability benefits of VERITAS Database Edition for DB2? Database Edition for DB2 improves manageability by reducing the complexity and time required to perform the necessary administrative tasks to keep DB2 running in an optimized manner by: • Allowing administrators to use familiar file system naming and utilities to manage DB2 database containers • Simplifying the management of large DB2 database configurations by using large file systems whose sizes are not limited to underlying physical device sizes (reduces the number of file systems required per DB2 database) • Providing online growth capability through Database Edition’s online expandability feature. (Administrators can simply create new containers or extend existing ones to accommodate DB2 database growth once the underlying file system is expanded, also an online option) • Enabling simple, online DB2 database storage configuration, including modifying DB2 container sizes, adding new containers, migrating data from one physical drive to another and file system defragmentation (useful for system managed storage or SMS tablespaces) • Offering storage and file system configuration and management through a goal-oriented, Java-based graphical user interface (VERITAS Volume Manager Storage Administrator™ on Solaris and VERITAS Enterprise Administrator on AIX) • Supporting the quick, reliable deployment of high availability DB2 configurations through the simple installation of Cluster Server and an off-the-shelf, fully supported Cluster Server Agent for DB2. Advantages of VERITAS Database Edition for DB2 Relative to Raw Devices 8. What are the administrative costs of using raw devices for DB2 databases? While raw devices provide increased performance compared to conventional file systems such as UNIX File System (UFS on Solaris and JFS/JFS2 on AIX), they are more costly to administer because raw device sizes are fixed by the physical disk size and operating system and do not have flexible naming conventions. This makes them inherently less manageable. Database growth can be extremely difficult to accommodate because you cannot grow existing devices Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans 2 are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.
  3. 3. (their physical nature fixes their size) and you have to combine physical devices of fixed sizes (which may not be optimal for your database environment) to meet your capacity requirements. Backups of raw devices also are limited to using the dd command, an archaic and very limited tool, for backup purposes. VERITAS Database Edition for DB2 addresses these issues. By building DB2 databases on file systems running on logical volumes, administrators can create logical devices that more accurately meet their capacity requirements by flexibly allocating new storage for creating new or extending existing containers. Flexible naming conventions significantly ease the management of underlying containers. These features mean that database growth is much easier to accommodate. File systems also can be backed up using familiar file system commands, such as cpio and tar, and any of a variety of backup/restore solutions, such as VERITAS NetBackup™. The use of NetBackup enables the inclusion of DB2 databases, through sqluv, the DB2 online backup application program interface (API), in a comprehensive backup/restore solution that can automate backup job scheduling across the entire enterprise. Note that some of these manageability advantages, such as the use of logically defined DB2 containers that allow easier new device addition, existing device expansion and more flexible naming conventions, are a result of running DB2 on VERITAS Volume Manager™. Database Edition for DB2 would not be required to achieve these specific manageability improvements, but Database Edition clearly offers more manageability advantages than just running DB2 on Volume Manager. 9. What is a DB2 container? Many of the major relational database management system (RDBMS) products use their own specific terminology to describe common concepts. A DB2 container is a logical construct that is analogous to a Sybase database device or an Oracle datafile. The DB2 containers are the logically defined devices on top of which a DB2 database runs. DB2 containers can be comprised of raw devices, file systems or directories. 10. What has IBM DMS traditional position been about building DB2 databases on traditional UNIX file systems such as UFS or JFS? IBM DMS traditionally has allowed customers to implement DB2 on either raw devices or file systems, but provided appropriate guidance regarding the manageability, availability, performance and reliability trade-offs associated with each alternative. If customers choose to run DB2 on a conventional file system, they achieve better manageability in some areas at the expense of performance, availability and potentially data integrity. DB2 databases use their own buffer pools to manage page allocation more efficiently than a conventional file system cache manager. When DB2 is run on a conventional file system, double buffering of data occurs, resulting in data being copied twice — once between the database buffer and the system buffer and then later between the system buffer and disk. This additional buffering the file system imposes uses memory inefficiently, effectively cutting usable memory in half. DB2 databases built on raw devices bypass the system buffer cache, resulting in increased performance on every read and write. A conventional UNIX file system such as UFS or JFS uses an exclusive write lock at the file system level. As a result, all write operations to a single file system are serialized. DB2 supports the processing of read and write requests in parallel (with locking at the row level) for performance, but this write serialization imposed by the file system (UFS or JFS) effectively blocks DB2 from performing any parallel processing at the file system level. As the size of a database grows, more users often are attempting to simultaneously access the files — each of which may hold many database records — and this performance degradation becomes more pronounced. When DB2 writes from its buffers, it assumes that it is writing directly out to disk and that updates are safely stored on nonvolatile media. If DB2 is run on a conventional UNIX file system such as UFS or JFS, however, it is not writing directly to disk, but to file system buffers that are stored in main memory, a volatile media. If a DB2 or system crash occurs, the DB2 transaction log may reflect transactions it assumes have been successfully written to disk when in fact they have not. As a result, data could be lost or corrupted. Given that customers are made aware of these limitations, they may decide to deploy DB2 on file systems to achieve improved manageability because these issues do not adversely affect the nature of the application environment. The customers are informed of the trade-offs and allowed to make their own decisions concerning the deployment configuration. Database Edition for DB2 addresses and resolves all of these above issues while still providing improved manageability. Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans 3 are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.
  4. 4. VERITAS Quick I/O 11. What is Quick I/O? Quick I/O is a unique database accelerator technology that is available only from VERITAS. It provides a file definition mechanism that allows VERITAS File System files to appear as raw character devices from a database point of view, while simultaneously appearing as files from a management point of view. This provides all the advantages of running DB2 on raw devices (no double buffering, DB2-controlled locking, direct writes to disk, asynchronous I/O support) along with all the advantages of running DB2 on file systems (file system-oriented management). 12. How do I configure regular files to use Quick I/O? Using Quick I/O, you can access regular, pre-allocated VERITAS File System files as raw character devices. This alternate view of a regular file is dynamically created when the file is accessed with the File System naming extension of ::cdev:vxfs:. For example, a file named dbfile is accessed as a raw device when the name dbfile::cdev:vxfs: is used. VERITAS Database Edition for DB2 simplifies DB2 container setups by providing a utility to create Quick I/O files and appropriate symbolic links, allowing the administrator to use familiar file system naming conventions. 13. How does Quick I/O improve performance and reliability? Quick I/O enables DB2 databases built on file systems to achieve raw device performance by presenting files to DB2 as raw character devices. This bypasses the UNIX system buffer cache, eliminating double buffering and ensuring that data is safely written directly from DB2’s own buffer cache directly to disk, removing the potential for data corruption. By eliminating file system-based buffering, the redundant copying of data also is reduced, resulting in further improved performance. Quick I/O attains its performance gains through shared update locks and kernel-supported asynchronous I/O (KAIO) in Solaris environments and AIX asynchronous I/O in AIX environments. Quick I/O supports shared update locks for database devices at the File System level. Quick I/O allows DB2 to process multiple requests in parallel, relying on DB2 to manage locking. Quick I/O further improves DB2 performance by taking advantage of asynchronous I/O, a feature previously only available for raw devices. Quick I/O allows the asynchronous I/O to be leveraged to gain performance for DB2 running in Database Edition environments on both Solaris and AIX. 14. How is Quick I/O different from the direct I/O access method that VERITAS File System, Solaris UFS and AIX JFS offer? Direct I/O and Quick I/O do share some common characteristics. Like Quick I/O, direct I/O bypasses the kernel buffering of data for performance improvements. Data is directly transferred between disk and the DB2 buffer cache, eliminating double buffering and redundant data copying, as well as processor overhead. Unlike Quick I/O, direct I/O still requires the exclusive write lock at the file system level, preventing DB2 from processing multiple write requests in parallel. In addition, direct I/O cannot take advantage of asynchronous I/O, a feature that only is available to raw devices and Quick I/O files. The bottom line for customers is that Quick I/O still provides performance advantages, and in some cases significant performance advantages, over using UFS or JFS with direct I/O enabled. Use the Database Edition for DB2 performance white paper as the proof point for this fact and to determine in which environments VERITAS Quick I/O offers the greatest advantages over direct I/O. 15. Can I use VERITAS Quick I/O to improve the performance of non-database applications running on top of VERITAS File System? Yes. Using the VERITAS File System name space extension, raw device views of any regular, pre-allocated File System file can be created. Any application that supports parallel writes and controls data access through exclusive locking to ensure data integrity can potentially benefit from Quick I/O. In many cases, imaging applications may be good potential candidates for Quick I/O usage. Note that DB2, because it supports parallel writes and more granular locking than conventional file systems, fits this profile and is an excellent candidate for Quick I/O usage. Conventional UNIX file systems lock an entire file while DB2 locks at the record level, and each file may contain many records. If you do decide to take advantage of this feature, please make sure you understand the impact on reads and writes of using what appear to be raw devices (Quick I/O files) on your particular application environment. Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans 4 are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.
  5. 5. 16. What is Cached Quick I/O? Cached Quick I/O is an enhancement to File System Quick I/O technology designed to improve performance by leveraging the large physical memory capacity on many of today’s higher-end systems. In 32-bit operating system and/or database environments, Cached Quick I/O can provide significant performance increases when workloads have a high percentage of reads. For read operations, Cached Quick I/O allows database blocks to be cached in the system buffer cache. This caching potentially reduces the number of physical I/O operations required and thus improves read performance. For write operations, Cached Quick I/O uses a direct-write, copy-behind technique to preserve its buffer copy of the data. After the direct I/O is scheduled, and while the file system is waiting for completion of the I/O, the file system updates its buffer to reflect the changed data being written out. For online transaction processing environments, Cached Quick I/O achieves better-than-raw device performance by leveraging very large physical memory without having to manage a large buffer cache. Cached Quick I/O provides its most significant performance gains in 32-bit environments by effectively bypassing 32-bit memory limitations. DB2 v7.2 (the minimum DB2 requirement for VERITAS Database Edition for DB2) can be installed as either a 32-bit or a 64-bit application. In 64-bit database environments, Cached Quick I/O may not provide the same level of performance enhancements as in 32-bit environments. It may, however, offer performance advantages for 64- bit environments in large file I/O applications such as multimedia and imaging or for sequential scans of large database tables. Although DB2 v7.2 supports 64-bit operation, many DB2 customers still choose to run in 32-bit mode, as DB2 is supporting legacy 32-bit applications in their environments. 17. How do I use Cached Quick I/O? Cached Quick I/O can be enabled or disabled as required on a per-file basis, providing maximum flexibility for configuring it for optimum performance in DB2 environments. To determine which files will benefit the most from Cached Quick I/O enablement, collect and analyze caching statistics: 1.Turn on caching for all files in file systems being used using the vxtunefs command 2.Run qiostat –r to reset the counters 3.Run the system under full normal load for a sufficient period of time 4.Run qiostat –l to report caching statistics 5.Analyze the output to determine the cache hit ratios 6.Determine the cache hit ratio above which you want to enable Cached Quick I/O, and enable all files above that level 7.Rerun the test and examine the caching statistics to determine performance improvement. Cached Quick I/O is a powerful tool that can be used to optimize performance in DB2 environments by fully utilizing all of the resources available on a system. Note that performance improvements should be more pronounced on 32-bit systems due to the 2GB memory limitations of DB2 in 32-bit Solaris and 32-bit AIX environments. DB2 Database Backup Using VERITAS Database Edition for DB2 18. How does VERITAS Database Edition for DB2 improve my overall DB2 backup strategy? When used with cold DB2 database backup strategies, the snapshot feature of VERITAS File System reduces backup windows to only a couple of seconds and simplifies restore procedures. Although cold backups are easy to perform, provide a simple restore procedure and safeguard against media failures, they do not promote high availability of mission-critical DB2 databases. Because the time required to snapshot a file system is typically only a few seconds, the administrator can obtain a fully consistent image of a database or an entire system with minimal database downtime. After suspending a DB2 database, the administrator can take a snapshot of all file systems containing DB2 containers, and then bring the DB2 database back online (resume) to restart operations. The administrator then can perform backup from the point-in-time snapshot, while the DB2 database continues to process its regular workload against the original copy of the data. Database Edition for DB2 also can be used with VERITAS NetBackup and the DB2 agent for NetBackup to perform online backups. The DB2 agent leverages the DB2 sqluv backup API to perform backups without having to shut down the database. Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans 5 are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.
  6. 6. 19. What is VERITAS FlashSnap? VERITAS FlashSnap is a new option for VERITAS Volume Manager (included in Database Edition for DB2) that enables database administrators to take snapshots and use them on separate servers for off-host processing. FlashSnap incorporates several technologies: • VERITAS Dynamic Disk Group Split and Join — This feature allows a volume snapshot to be split off from the original and the associated disk groups to be imported on another server • VERITAS Fast Mirror Resynchronization — Uses a persistent data change log to speed the resynchronization of disk groups after off-host processing is complete • File System-based VERITAS Storage Checkpoints™ — Provides point-in-time snapshots that are persistent across application crashes or server reboots Please note that the first release of Database Edition for DB2 does not support File System-based Storage Checkpoints. FlashSnap provides management flexibility in performing normal processing (off-host data analysis in decision support and data mining applications) and administrative tasks (backups, creating up-to-date copies for testing) with minimal downtime to the DB2 database of record. For more information about FlashSnap, see the FlashSnap data sheet or sales FAQ. 20. Does VERITAS Database Edition for DB2 support VERITAS FlashSnap? Yes, FlashSnap is supported, but the Storage Checkpoint functionality is currently not supported. Storage Checkpoint will be supported with an upcoming version of Database Edition for DB2. VERITAS Database Edition/HA for DB2 21. How does VERITAS Database Edition/HA for DB2 further improve database availability? Database Edition/HA for DB2 includes VERITAS Cluster Server and uses the VERITAS Cluster Server Agent for DB2. Together, these two components monitor and proactively manage the availability of one or more DB2 databases across clustered nodes (up to 32 nodes in Solaris environments; 16 nodes in AIX environments). DB2 database failures, regardless of whether they are due to hardware or software component failures in the database server, will be detected, and the affected DB2 databases will be restarted automatically, either on the same node or on another node, depending on the type of failure. 22. How does VERITAS Database Edition/HA for DB2 actually manage the failover process? The Cluster Server Agent for DB2 is specifically designed to provide start, stop, test and clean services for the DB2 data service and plugs into the Cluster Server Agent API to leverage the Cluster Server availability engine-recovery capabilities. A configurable test routine runs periodically to determine the service status of the DB2 database. If DB2 hangs or crashes, the DB2 agent will detect that and take steps to restart DB2. The start and stop scripts are used to restart DB2 upon failover or to manually shut down DB2 for manual failover. The clean service is used to reliably remove a hung DB2 database from a server prior to attempting a restart on that server. Because VERITAS Cluster Server fully automates failure detection and recovery, any failure in the data service will be recovered quickly without operator intervention, maximizing overall DB2 availability. Depending upon the type of failure, manual intervention may be required to repair a failed server (replace failed hardware), but mean time to repair does not impact DB2 availability. 23. Why would I want to manually failover a DB2 database? Manually failing over a DB2 database is helpful in minimizing the impact of server maintenance. Assume a 2-node cluster with nodes A and B. If the operating system of node A must be upgraded, that node will have to be taken offline, bringing down any applications that may be running on it. Using the manual failover capability, DB2 may be migrated to node B so that the data service is kept up and running during the operating system upgrade on node A. Once the upgrade is complete, DB2 may be left running on node B or manually failed-back to node A so that node B’s operating system may be upgraded. VERITAS Database Edition/HA for DB2 was designed automatically to allow nodes running different operating system releases to coexist for short periods of time so that these types of upgrades (called “rolling upgrades”) may be performed with minimal impact to DB2 availability. For long-term operation, it is recommended, however, that all cluster nodes run the same operating system release. Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans 6 are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.
  7. 7. 24. IBM DMS provides a VERITAS Cluster Server Agent for DB2 on the DB2 v7.2 CD. Is this the same agent that is used with VERITAS Database Edition/HA for DB2? Yes. VERITAS developed a VERITAS Cluster Server Agent for DB2 that supports DB2 v7.1, and this is the agent that VERITAS has been selling off of its price list prior to the introduction of the Database Edition/HA for DB2. Database Edition/HA for DB2 requires DB2 v7.2 at a minimum, and IBM DMS developed an agent that supports DB2 v7 (v7.1 and v7.2). VERITAS cluster engineering tested this agent, documented it as part of the Database Edition for DB2 development effort and uses this agent in Database Edition/HA for DB2. After the introduction of Database Edition/HA for DB2, we will be using the same Cluster Server Agent for DB2 across our product offerings. Again, note that IBM provides this agent at no charge on its DB2 UDB CD, but we need to maintain consistency for support reasons, so we will use this agent on all of our highly available DB2 offerings. 25. Can I customize how the VERITAS Cluster Server Agent for DB2 manages DB2 databases? Yes. The VERITAS Cluster Server Agent for DB2 performs the start, stop, test and clean services described above, but the agent works like a general-purpose event/response engine. Other agent-supported options include defining the recovery response (attempt to failover immediately upon failure detection, attempt n restarts prior to failing over, failover to the least-loaded node, etc.), customizing failure notification (send a simple network management protocol (SNMP) trap, send an e-mail to a predefined list of addressees) or executing a series of UNIX commands. It can be modified to detect a variety of events (as long as there is a way to monitor event status) and automatically perform other tasks in response. Note, however, that modifying the agent may result in a change in VERITAS ability to support this agent, depending on the nature of the changes. Please ensure you understand the impact of any changes you may plan to make in terms of support. 26. Does VERITAS Database Edition/HA for DB2 support cascading failover? Yes, VERITAS Database Edition/HA for DB2 supports the full feature set of VERITAS Cluster Server, including cascading failover. Cascading failover refers to a cluster’s ability to handle consecutive node failures without operator intervention, and only is an issue in clusters with three or more nodes. Assume a 4-node cluster with nodes A, B, C and D. If a DB2 database is running on A and A crashes, then DB2 may be failed-over to B. If B crashes before A is repaired, Cluster Server has the ability to failover DB2 yet again to C. If C crashes before A and B are repaired, Cluster Server can failover DB2 to D. This is called cascading failover, and it can provide additional uptime insurance on those rare occasions when two or more cluster nodes fail close together. Note, however, that cascading failover may cause certain servers to be overloaded, thus slowing performance. In the example given, if all nodes were running their own independent DB2 databases, and after three consecutive node failures all instances ended up on D, D may not be providing sufficient database throughput due to its overloaded condition. Cascading failover may be enabled or disabled through the Cluster Server management graphical user interface. 27. Is DB2 Extended Enterprise Edition (EEE) supported under VERITAS Database Edition/HA for DB2? DB2 EEE can be run in one of two modes: symmetric multiprocessing (SMP) or massively parallel processing (MPP). In SMP mode, multiple DB2 server instances are run on a single, big SMP that is running a single operating system image. In SMP mode, all DB2 binaries are loaded on the mirrored private disks (internal), while all data is on the shared disks (external). In this mode, Cluster Server would manage DB2 EEE like a single node application rather than a parallel application. A cluster file system is not required for this configuration. The Cluster Server Agent for DB2 that is used for DB2 EEE can be configured slightly differently to support DB2 EEE SMP. Note that while VERITAS is investigating this, it is not currently a supported configuration. In MPP mode, multiple DB2 server instances are being run across nodes (such as in a cluster) or between partitions on a big SMP (such as an E10000). This type of support requires the use of a cluster file system for certain directories, and is not supported in VERITAS Database Edition for DB2. It is being investigated for support in 2002. Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans 7 are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.
  8. 8. DB2 and Platform Compatibility 28. What versions of DB2 does the VERITAS Database Edition for DB2 support? Database Edition for DB2 (and the HA version) 1.0 supports DB2 v7.2 (AIX 5.1 requires FixPak 6 or later). VERITAS product management evaluated the functionality of DB2 and, based on requirements for future versions of Database Edition for DB2 that will look more like Database Edition for Oracle, decided to base development efforts on DB2 v7.2. Specifically, DB2 v7.2 supports a DB2 database suspend/resume capability that will be leveraged in a future release to support VERITAS VERTEX™-based backup. 29. Will VERITAS support earlier releases of DB2 under the VERITAS Database Edition for DB2? No, VERITAS does not support versions of DB2 earlier than DB2v7.2. DB2 V7.2 is a simple patch upgrade from 7.1 30. What platforms does VERITAS Database Edition for DB2 support? Database Edition for DB2 is designed to support: • SPARC/Solaris platforms running Solaris 2.6, 7 or 8. This includes Sun’s Enterprise Server product line, as well as the new Sun Fire servers (3800, 4800, 4810, 6800) • IBM’s RISC (Power) based servers (e.g. p-series and s-series) running AIX 5.1 (Maintenance Level 1 or higher) Database Edition for DB2 supports all servers and storage that have been qualified for use with VERITAS Foundation Suite™ HA, including the IBM ESS (Shark), EMC Symmetrix, HDS 7700s and 9900s and the Sun A5000s and T3s. VERITAS Volume Manager dynamic multipathing (DMP) is supported on these storage systems. For more specific information about configurations tested, please see the iSolutions database. Product Components and Availability 31. What are the components of VERITAS Database Edition for DB2? VERITAS Database Edition is available in two versions. Database Edition for DB2 consists of the following VERITAS products: • VERITAS Volume Manager v3.2 • VERITAS File System v3.4.2 with VERITAS Quick I/O and Cached Quick I/O • VERITAS Volume Manager Storage Administrator (Solaris) • VERITAS Volume Manager Storage Administrator (AIX) For high availability DB2 environments, VERITAS Database Edition/HA for DB2 includes one additional VERITAS product: • VERITAS Cluster Server v2.0 Note that the DB2 v7.2 agent for Cluster Server is included at no charge on the DB2 v7.2 CD. In addition, both versions include the Database Edition for DB2 administrator guide, provides information for DB2 administrators to optimally configure and manage DB2 databases running in the Database Edition environment. Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans 8 are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.
  9. 9. 32. Is the VERITAS Cluster Server Agent for DB2 available separately? The VERITAS Cluster Server Agent for DB2 is available separately from VERITAS. This agent is included at no charge on the DB2 v7.2 CD. Given that VERITAS has tested and supports this agent for use with the Database Edition/HA, VERITAS also will support configurations that use that agent, even if they are not in a Database Edition environment. For a full list of application agents available for use with Cluster Server, please refer to Cluster Server sales collateral. VERITAS Software Corporation For additional information about Corporate Headquarters VERITAS Software, its products, or the 350 Ellis Street location of an office near you, please call Mountain View, CA 94043 our corporate headquarters or visit our 650-527-8000 or 866-837-4827 Web site at www.veritas.com. Copyright 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans 9 are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. Specifications and product offerings subject to change without notice. June 2002.

×