technical solutions document - wordwonktechnical_solutions_document).doc · web viewyes no tsm...

/tt/file_convert/5b1affcb7f8b9a41258e3fb4/document.doc

Technical Solutions DocumentFor:

IBM/CMS Managed Services

Client Name: E-mail this completed form to:[email protected]

Questions about completing this form? Please call 561-997-2900.

Extension: 139 ORExtension: 181

Address:

Contact Name: Title:

Phone #: - - E-mail:

IBM/Champion Client? Existing: New: Please Select Purpose(Check Box below)

Existing or New Hosting Opportunity? Existing: New: Indicative Price

Budget Approved? Yes No Budget and Planning

Best and Final

Industry: Example: Services — SMB

Work Order Number:

Primary Data Center: DR Required? DR Data Center:(Check Box below) (Check Box below) (Check Box below)

Atlanta BellSouth eBHC Yes Atlanta BellSouth eBHCChicago –eBHC No Chicago –eBHCPeak -10 Peak -10Other: Other:

Project TeamName Phone E-Mail

Prepared By: IBM SE: IBM CSE: IBM PM: IBM TSS Champion PSA:

Date CommentsOriginal Creation Date: Document Version: Revision Date: QA-1 Date Required: QA-1 Date Completed:

Confidential & Proprietary

mailto:[email protected]


Date: 5/9/2023 — 11:30 AM Technical Solutions Document

Opportunity Qualified Yes No

Date Sent To Champion: Acknowledged By:

About The Client.................................................................................................................................................. 3Opportunity Overview.......................................................................................................................................... 3Assumptions........................................................................................................................................................ 4Exceptions........................................................................................................................................................... 4Requirements...................................................................................................................................................... 5

Facilities........................................................................................................................................................... 5Security............................................................................................................................................................ 6Internet Connection.......................................................................................................................................... 7Network............................................................................................................................................................ 7Servers............................................................................................................................................................. 8Software Licenses............................................................................................................................................ 9SAN................................................................................................................................................................ 10Backups......................................................................................................................................................... 11Services Responsibility Matrix SRM...............................................................................................................12

Contract Term.................................................................................................................................................... 13Implementation Time Period.............................................................................................................................. 13Details Of The Environment............................................................................................................................... 14

General.......................................................................................................................................................... 14Facilities......................................................................................................................................................... 15Cross Connects............................................................................................................................................. 15Network Switches And Security..................................................................................................................... 15Connectivity For Staging Of Test Servers......................................................................................................15Network Connectivity..................................................................................................................................... 16Servers........................................................................................................................................................... 16SAN Fabric..................................................................................................................................................... 17SAN Storage.................................................................................................................................................. 17Transaction Monitoring (Special Order).........................................................................................................18Database Monitors (Special Order)................................................................................................................18Backups......................................................................................................................................................... 18Software Licenses.......................................................................................................................................... 19

IBM Provided Licenses And Media.............................................................................................................19Client Provided Licenses............................................................................................................................ 19

Appendix A — Backup Sizing Sheet.................................................................................................................. 20Appendix B — Transaction Monitoring (Special Order).....................................................................................22Appendix C — Database Monitors (Special Order)...........................................................................................23

Confidential & ProprietaryPage - 2



About The ClientINSTRUCTIONS: Please provide a brief (1 or 2 paragraphs), high-level description of the Client. Include information such as who the Client is, their location, and what they do within their industry.

Opportunity Overview

INSTRUCTIONS: Please provide a brief (1 or 2 paragraphs), high-level description of what the opportunity is, and discuss what the criticality of the solution is for the Client.




IMPORTANT NOTE:The standard implementation time period is ten (10) weeks from the day the customer agrees to and signs the contract.The CMS implementation team requires a minimum of two weeks of the ten weeks to complete the build and configuration as designed. The two weeks commences after All of the equipment is received and inventoried at the build site, unless otherwise agreed upon by IBM and CMS.

Assumptions

1.

2.

3.

4.

5.

6.

7.

8.

Exceptions INSTRUCTIONS: Describe what requirements may be outside of the standard offering, or are of extreme importance to the Client.

1.

2.

3.

4.

5.

6.

7.

8.




Requirements

The following sections provide detailed requirements for: Facilities () Servers (Page 8) Security (Page 6) Software Licenses (Page 9) Internet Connection (Page 7) SAN (Page 10) Network (Page 7) Backups (Page 11)

Services Responsibility Matrix SRM (Page 12)

Facilities

# COMMENTS

Cabinets1. Dedicated Cages Yes No Size: 2. Shared Space? Yes No3. Dedicated Cabinets

Please specify type

4. Shared Cabinets Enter U required

5. Other Cabinets

Cross-Connect1. Continuous cross-connect

to connect to the CMS infrastructure (not out to the demarc)

2. Noncontiguous cross- connect to connect to the demarc for WAN connections

Power1. PDUs

a. Front End b. Backend

2. 20A, 208 V Circuits 3. 30A, 208 V Circuits


Page 5



Patching Facility1. Patch Panels 2. Wire Management 3. 2 Post Cable Rack 4. Ladder Racks 5. 60A, 208 V Circuits

(3 Phase) 6. 20A, 110 V Circuits

(Standard)

Security

# COMMENTS

Firewall Model1. Cisco PIX 515

a. VPN Acceleration 2. Cisco PIX 525

a. VPN Acceleration 3. Other 4. Number IPSeC VPN

tunnels to be set up at the IBM data center (Customer to set up and manage the corresponding VPN tunnels at their sites)

5. Virtualized Internet facing firewall

6. Dedicated single Internet facing Firewall

7. Dedicated HA Internet facing firewall

8. Network Intrusion Detection Systems (NIDS)?

9. Private address range (requires NATing on the customer side if there is a conflict)

10. High Availability Configuration? Yes No

11. SSL Acceleration Yes No12. Load Balancing?

(Round Robin or by well ports only)




Internet Connection# COMMENTS

Internet Bandwidth1. Primary physical

Internet connection at 100 Mbps

2. Primary physical Internet connection at 10 Mbps

3. Committed bandwidth for primary Internet connection. (Primary Internet connection (minimum 1 Mbps)

4. Internet connections burstable to 10 100

5. Number of registered IP addresses

Network# COMMENTS

CIsco Equipment1. Cisco 4500 2. Cisco 6500 3. Other 4. Number of ports per

switch 5. Redundant Switches?

(HA) 6. CIsco 4500 Modules

Used a. Load Balancers b. SUP Modules

7. CIsco 6500 Modules Used

a. Load Balancers b. SUP Modules

8. SSL 9. Ports on a shared

switch a. LB Number of Farms: Number of Servers per Farm:

Cables1. Fiber cables (SAN,

FW, GigE ports,




Servers)2. CAT 5/6 Ethernet

10/100 3. Other cross-connects 4. Lantronics

Load Balancing1. Round Robin or by

well ports only?

Servers# COMMENTS

Servers1. Total number fully

managed 2. Total number partially

managed 3. x335/6 4. x346 5. x365/6 6. x445/6 7. Blade Chassis

a. # Of Blades 8. Other xSeries 9. p510 10. p520 11. p550 12. p570

a. # Of LPARS Per Server

13. Other pSeries

14. Servers Purchased By: Customer IBM Other




Software Licenses# COMMENTS

Operating Systems1. Win2000 Standard 2. Win2000 Advanced 3. Win2003 4. Win2003 Enterprise 5. Total # of Windows

Servers 6. VMWare ESX

a. Total # of VMWare Instances

7. Linux a. Redhat

(Enter version) b. SuSe

(Enter version) c. Total # of Linux

Servers 8. AIX

a. AIX 5.2 b. AIX 5.3

9. Citrix a. # of Citrix Farms b. # of Citrix Users c. Type of Citrix

Load Balanced Farms

d. How will Citrix be accessed? Portal Program Neighborhood

e. Type of Data Store Needed Access SQL (Requires an SQL license)

f. Total # of Citrix Instances

10. OS Licenses Provided By: IBM Customer

VM GSX? No Yes

If YES, which OS? (Examples: Win2000 or Win2003)




Databases # COMMENTS

1. Replication Required? Yes No2. Oracle (Enter version) 3. SQL2000 4. DB2 5. Other

a. Clustered? Yes No6. DBA Support Provided By: Customer CMS Other7. DBA Transaction

Monitoring Required? Yes No If YES, please complete Database Monitors (Special Order), page 18.

8. Lotus Notes/Domino?? Yes No

a. # of Mailboxes 9. Mailboxes Managed By: Customer ASP-One IBM Other

SAN# COMMENTS

Data Requirements1. Total Solution SAN

Requirements(e.g. GB, TB, RAID)

(Complete details in Error: Reference source not found, page Error: Reference source not found)

2. # of OS Instances Connected to the SAN

(Enter Type)

3. # of OS Instances to be clustered

(Enter Type)

SAN Fabric1. McData 4300

(Up to 16 ports) 2. McData 4500

(Up to 24 ports) 3. DS 4800 4. DS 4100 5. Expansion Unit 710’s 6. Expansion 100 7. # of SPF Modules on

each base switch 8. # of 5m LCOLC

connections to host attachment to the switch

9. Total Ports Per Switch




Backups# COMMENTS

Tape Library1. Dedicated Tape

Solution Library (Please specify.)

2. Shared Tape Library

Backup Servers Dedicated Shared1. Dedicated Tape

Solution Library IBM Other

Backup Retention Requirements1. Offsite Storage

Frequency and Retention Requirements

2. Total Amount of Data for a Full Backup

3. Backup Schedule Provided? Yes No

4. Special Archiving Required?

(Please explain.)

LAN Free Backup Required? Yes No

TSM1. Mailboxes Managed By: IBM CMS Customer2. # of TSM Client

Processors 3. # of TSM Mail

Processors 4. # of Database

Processors

Are any of these Servers Clustered? Yes No1. # of OS Instances to

be Clustered 2. Clustering Software to

be used

Backup Sizing (Please be sure to complete Appendix A — Backup Sizing Sheet, page 20.)




Services Responsibility Matrix SRM

IBMChampion

Services Group CustomerServer sizing and configuration, including projections for growth

Perform

Procure all of the necessary equipment PerformProcure OS licenses PerformProcure database licenses PerformProcure licenses for tools and backups (TSM agents including database agent)

Perform

Provision space - half cabinet PerformProvision additional power circuits. PerformProvision Internet connection at the IBM data center PerformProvision VPNs at the IBM data center PerformProvision VPNs at the customer sites PerformProvision Internet bandwidth at the end user locations PerformProvide 16 public IP addresses PerformReceive the equipment and the software PerformRack and stack the equipment PerformCable the equipment PerformConfigure the firewall PerformConfigure the switch PerformConfigure remote IP KVM switch PerformInstall OS PerformConfigure IP addresses PerformSetup administrative ids PerformProvide temporary administrative access to the customer to install applications and data content

Perform

Install the applications PerformSetup end users PerformReset administrative ids PerformInstall tools on the servers PerformConfigure alerts - PFA, thresholds (CPU; memory; disk); event logs

Perform

Test alerts PerformManage OS patches PerformManage OS alerts PerformCall for service Assist PerformManage end users PerformFirewall management Perform




Application management PerformPerform backups PerformMonitor backup jobs and backup job completion PerformTake tapes offsite (use the IBM CSG account with Iron Mountain)

Perform

All ongoing physical and logical DBA tasks PerformProvide a Server and operations Help Desk PerformProvide a OS Help Desk PerformEnd User, Application Help Desk PerformIBM CMC for CSG to call for local support assistance Perform

Contract Term

Months (Enter the number of months. This is normally 60 months.)

Implementation Time Period

The standard implementation time period is ten (10) weeks from the day the customer agrees to and signs the contract.IMPORTANT NOTE:

The CMS implementation team requires a minimum of two weeks of the ten weeks to complete the build and configuration as designed. The two weeks commences after All Of The Equipment is received and inventoried at the build site, unless otherwise agreed upon by IBM and CMS.

The ten weeks also includes a technical discovery period of two weeks, which starts with the boarding call with the customer. This provides the necessary time for the IBM and CMS implementation teams to meet with the customer and determine exact networking, firewall, server, SAN, backup and monitoring installation, and configuration and management details and thresholds.

The SOA will be appended for any areas discovered during the technical discovery period that may be different from the SOA specifications.

Major deviations may result in a pricing adjustment via PCR(s).

Any delays in the schedule as a result of additional equipment or work items found during the technical discovery or any delays in the procurement of equipment will be reflected in the overall project plan and the new project plan will be complied by the IBM and CMS Project Managers and communicated to the customer in a timely fashion.




Details Of The EnvironmentINSTRUCTIONS: The content of the following sections is standard, and usually does not require any modifications. For example, the items appearing in GREEN are variables and may require modification.

General1. New customer — To be housed at the Bell South eBHC.2. The environment will consist of all new equipment, provisioned by IBM.3. Application support is part of the requirements for IBM.4. Database support is part of the requirements for IBM.5. Customer will be responsible for all aspects of data content and data migration.6. CMS must test all processes and procedures, including backups and restores, and all the monitoring tools,

prior to the SOR date. This should be part of the project plan and time should be allowed for it.7. No credit for hours not used.8. From an IBM delivery perspective, this is a collocation deal along with ordering the equipment and

receiving the equipment and providing local “smart hands” support and offsite storage support.9. A business partner, Champion Computer Services Group (CMS), is responsible for the configuration and

ongoing management and monitoring (events logs; thresholds; processes), providing a 24 x 7 x 365 help desk for operations related issues, and web portal for reporting and firewall and switch, SAN, Windows OS and OS management as well as OS patch management.

10. The use of a business partner has been approved by IBM management.11. IBM is responsible for the infrastructure (power, ping, pipe), operational events, receiving the equipment

and for offsite storage using Iron Mountain.12. IBM will assign a Transition Manager (TM) to procure the equipment and software licenses.13. The Director of eHBC (IBM) will assign a IBM Project Manager (PM) as well as a PE.14. IBM will purchase the licenses for all of the management tools and for backup agents (TSM and database

client for TSM).15. CMS will rack and stack the equipment. 16. CMS will be responsible for the physical and logical builds.17. System sizing has been provided by Gulf Bay.18. The customer has provided the server, internal and external storage and bandwidth configuration and

specifications.19. The specifications provided by the customer include their growth projections.20. The customer is responsible for migrating the applications, users and the data. 21. All alerts are logged in real time and can be viewed by the customer on the CMS provided web portal in

real time. Historical views are also available via the same web portal. Additional consoles will not be provided.

22. Alerts will not be forwarded to the customer.23. Customer will not be provided with a duplicate management console.24. The customer will call the CMS Help Desk for server and operations related issues only.25. CMS will call the IBM CMC to open a ticket if local support assistance is required.26. End user and application Help Desk provided by the customer.27. The customer and CMS will follow IBM Change Management procedures and processes, including

emergency change management procedures and processes for emergency changes.28. The customer will be responsible for providing all non SAP application and database skills.29. IBM will be responsible for providing all SAP application and database skills30. Facilities, infrastructure, hardware and software to be provided by IBM and managed by CMS.31. Up to 80 hours of OS, server and infrastructure (e.g. Firewall; switch; VLAN; NIDS; load balancing, etc.)

support per month will be provided between the SOR date and the customer’s environment going Live (General Availability or “GA” date). — 10 hours per server, cumulative. Apps & DB excluded.




Facilities1. Hosted at the Atlanta BellSouth eBHC.2. No requirement for a second site.3. One half of a Netfinity cabinet.4. The environment will require 8 x 30A, 208 V power circuits.5. x 30A PDUs and 4 universal PDUs

INSTRUCTIONS:Please modify as appropriate.

Cross Connects1. Two Gig cross connects (cat6) will be provided by IBM, linking the customer dedicated switches to the

CSG infrastructure switches. One is a primary link and the other will be used as a secondary link.2. IBM PM to verify that the distance to the CSG cage is less than 280 feet. 3. Includes $350 for Ethernet cables.

Network Switches And SecurityINSTRUCTIONS: Those items appearing in GREEN below are variables and may or may not be included in a particular TSD.

1. CSG responsible for physical and logical builds and cabling.2. CSG will configure firewall rules and VLANs.3. CSG to manage the firewalls and switches.4. Customer to provide firewall rules for their applications.5. Customer will not be granted access to the firewall rules or to the firewall logs or to the Firewall console or

the firewall administrative passwords.6. All requests for changes in firewall rules must be made following established change management

procedures.7. Emergency firewall requests for circumstances where the environment or an application becomes

inaccessible because of firewall settings may be submitted via the established emergency change management procedures.

8. No more than three emergency requests per month.9. All SLAs will be suspended during this period of change.10. There should, typically, be no reason for emergency changes to switch and VLAN settings other than

device outage.11. 24 x 7 support from Cisco is included for the Cisco equipment.12. High Availability (HA) configuration not used for the firewall and switch.13. Pix515 firewalls will include an additional 4 port E'net interface.

Connectivity For Staging Of Test ServersINSTRUCTIONS: The following represents the typical content for this section. Please modify it as appropriate.

The servers that are designated as staging or Test servers in the server section of this TSD document will have a management VLAN link to CSG but will not be monitored. These servers will be permitted to communicate with the production servers on a change request basis from the customer to upgrade applications, promote new code or apply application / database patches.

Staging or Test servers will be placed in their own VLAN that is isolated from the production servers to prevent infections or viruses or any changes from impacting the production servers. Connection to the production servers will be provided for the staging servers via a fire-walled connection for the customer to upgrade applications or apply application / database patches.




Network Connectivity1. No dynamic IPs.2. IBM will assign private IPs addresses in the range of 172.16.x.x for the customer’s servers at the IBM

data center. The customer is responsible for working with IBM during the technical discovery phase to ensure that these IPs addresses do not pose any conflicts with customer’s existing IP addressing schema. In case of a conflict, the customer will provide NATing for the IP addresses in conflict.

3. One VPN is to be set up for the customer to maintain their applications.4. CSG to set up and manage the VPN tunnel only at the IBM data center.5. Customer to set up and manage the VPN tunnel at their site.6. No requirement to provide a copy of the alerts for the customer via the VPN.7. No second management console at the customer site.8. The IPSec tunnel will be based on 3-DES Sha technology9. The IPSec connection will be from specified machines at the customer site to specified machines at the

IBM hosting center as defined by the customer.10. NIDS - Outside the firewall monitoring = Yes (IBM data center only)11. NIDS - Inside the firewall monitoring = No (IBM data center only).12. The customer will provision and manage all SSL certificates.

ServersINSTRUCTIONS: Those items appearing in GREEN below are variables and may or may not be included in a particular TSD.

1. No clustered servers.2. CSG responsible for physical and logical builds and cabling for the servers at the data center. 3. CSG will configure the servers at the data center.4. CSG will load and configure the OS at the data center.5. CSG to manage the servers and the OS at the data center.6. Customer to provide licenses for the database.7. The customer will be responsible for all application support above the operating system.8. Customer to perform all physical and logical DBA tasks.9. CSG retain administrative ids (root authority) for the fully managed servers.10. Customer will be granted local administrative access to initially install their applications and load their

data.11. Customer must request temporary administrative access through the CSG Help Desk thereafter.12. All SLAs are suspended while the customer has administrative authority.13. All requests for administrative authority must be made following established change management

procedures.14. Emergency requests for administrative authority to correct circumstances where the environment or an

application becomes inaccessible may be submitted via the established emergency change management procedures.

15. No more than three emergency requests per month.16. The customer has provided the server, internal and external storage and bandwidth configuration and

specifications. 17. CSG is not responsible for application performance.18. CSG will apply anti-virus updates for the servers.19. Customer will not have a duplicate management console nor will they have access to alerts.20. Upgrades to the OS or Citrix, other than patches, are excluded. (e.g. Win2000 to Win2004) 21. OS patch management is included.22. Citrix patch management is included.23. Customer to set up and manage end user ids and passwords.




24. Customer responsible for using Citrix shadowing of end user sessions, if required.25. Device only SLA of 99.5 % for fully managed servers, firewall and switches.26. Staging and test servers have the following services and restrictions:

a. Customer manages these servers.b. No offsite storage of backups.c. No alerts to be managed by CSG.d. Customer has administrative authority.e. Not included in any SLAs.f. Define the VMware disk as not automatically committing the changes so that changes can be

rolled back. (Applicable only if using VMware).g. VMs can be reloaded by the customer off of the SAN. (Applicable only if using VMware).h. CSG will reload VMware on a staging server if requested by the customer via the change

management process. No more than 2 requests for restoring VMs per month. (Applicable only if using VMware).

i. CSG is not responsible for data or application migration to production.j. All application migration and / or data migration activities must be planned following established

change management. procedures and processes.k. Administrative authority may be needed by the customer to complete the migration.l. All SLAs are inactive during the migration and until the customer re-certifies the application.m. CSG to make a copy of the new production environment and resume monitoring after the

customer re-certifies the application. An extended maintenance window will be required to make this copy.

n. Customer needs to be able to access the production servers to 1) required to make this copy.o. Placed in their isolated VLAN and connected to the production servers via a firewall on customer

request.p. Placed in their own Windows domain or workgroup to ensure that the production environment

remains isolated.

SAN Fabric1. CSG will provide installation, configuration, ongoing system administration and management support for

the SAN Fabric components.2. CSG will zone the SAN switches as necessary for security. CSG retains sole root/administrative access

(privileged access with authority to perform system-level functions or security administration) in order to perform installation and ongoing management services for the SAN Fabric.

3. The servers will be connected to the SAN Storage via multiple connections to the SAN switches using two or more HBAs for redundancy in each server.

4. In the event that additional SAN switches or switch ports are required, Customer will sign a new PCR for the additional equipment. Downtime may be required to complete the upgrade.

SAN Storage1. CSG will provide installation and ongoing system administration and management support services for the

SAN storage device components.2. The raw disk drive capacity specified in Attachment A will be provided by IBM.3. CSG will allocate space on the disk drives as directed by Customer.4. Customer will be responsible for populating the files and databases and for all Content.5. IBM retains sole root/administrative access (privileged access with authority to perform system level

functions or security administration) in order to perform installation and ongoing management services for SAN Storage.However, following installation and setup and prior to IBM beginning ongoing management, Customer may request to be provided with root/administrative access for a limited period of time, only for the purpose of loading and configuring applications, databases, clusters and Content and for all database administration




tasks. Ongoing management services will not begin until Customer turns sole root/administrative access back to IBM.

6. If additional disk is required, Customer will sign a new PCR for the additional equipment. Downtime may be required to complete the upgrade.

Transaction Monitoring (Special Order)INSTRUCTIONS: This section will be included for special, non-standard scenarios.Please refer to Appendix B — Transaction Monitoring (Special Order) for a sample of suggested content.

Database Monitors (Special Order)INSTRUCTIONS: This section will be included for special, non-standard scenarios.Please refer to Appendix C — Database Monitors (Special Order) for a sample of suggested content.

Backups1. CSG performs backups at the IBM Data center.2. Customer has no administrative access to the backup environment at the data center.3. Uses the shared, virtualized 3584 tape library. .4. Backups made over the backup VLAN segment. (This is a Gig VLAN.)5. Up to 800 GB of data backed up during full backups.6. Daily incremental backups. Kept in the library for 7 days. 7. Weekly full backup. Kept in the library for 7 days.8. Weekly offsite. Retained offsite for 90 days.9. 120 tapes to be ordered with the hardware. Specific label must also be ordered.10. Customer to provide any special hardware or software that may be required for the migration of data.11. Customer is responsible for ensuring that they have an adequate data migration window.




Software Licenses

IBM Provided Licenses And MediaINSTRUCTIONS: Those items appearing in GREEN below are variables, which may be modified as appropriate.

1. Windows server as specified in the server section. (17)2. Windows Advanced as specified in the server section. (3)3. RedHat Linux ES as specified in the server section. (0) 4. RedHat Linux AS as specified in the server section. (0)5. TSM agents for the servers as shown in the server section. (42 CPUs)6. TSM database agents for the database servers as shown in the server section. (2 CPUs)7. TSM e-mail agents. (0)8. Symantec AntiVirus (purchased by CSG and paid for by IBM). (20)9. Patch management software agents (purchased by CSG and paid for by IBM). (20)

Client Provided LicensesINSTRUCTIONS: The following represents the typical content for this section. Please modify it as appropriate.




Appendix A — Backup Sizing Sheet

COMPANY INFORMATIONCompany NameContact PersonState / ZipPhone # / Fax#Email Address

SIZING INFORMATION To be filled in on the attached sizing chart worksheetServer Name Individual name of client/node to be backed up. This could be a

workstation, file application or data server.

O/S & Version Client operating system/platform including version and service/release levels. Be specific.

Number of Processors Required to determine the license of each node (tiers)

Network Type Type of network this server is connected to including specifics like speed, switched or non-switched, and subnet or location.( Example : FDDI or 100BT ethernet )

Server Storage used (GB) Total amount of data on the client/node to be backed up.(GB)

Database (db) type, Application database (Oracle, Sybase, MS-SQL, Informix, Exchange, Notes )

Version & Size (GB) Version, & Size (GB)

Daily Change (%) Estimate of the percent of total file system disk space that changes daily. This number is usually in the 3-10 % range. Use an integer (.03 )

Daily Change (GB) Total amount of new or changed data on the client/node to be backed up daily (GB)

# of file Versions kept The number of file space backup versions (copies) to be retained.

# of db Versions kept The number of full database backup versions (copies) to be retained.

Archived per month (GB) Total amount of data Archived from client/node per Month.(GB)( including of months of data to keep in library )

Backup Window for server (Time) Times of day between which The backup software must start and complete it's backup cycle.

Approx number of files to be backed-up

Number of files backed up are needed to size the backup software's relational database.

Retention period How long the data will reside in the library




Server NameMachine Model

O/S, version

Approx # of files on

server to be backed up.

# of file Versions (copies)

kept

Database (db) type, Version & Size

(GB)

# of db Versions (copies)

kept

Archived per

month (GB)

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

20




Appendix B — Transaction Monitoring (Special Order)

1. CSG will enable monitors to perform multiple transaction tests, analyze responses and generate alerts. 2. Monitors will run every fifteen (15) minutes and create an alert if they do not complete successfully. 3. Customer defined sequence of actions will be taken for the alerts, including restarting a server and

notifying Customer or the agent for Customer's designated application support provider.

Confidential & Proprietary



Appendix C — Database Monitors (Special Order)

1. The database instances will be monitored using Proactive monitors based on ActiveX Data Objects. The Monitors for the database instances will monitor the ability to log into to an external database or application server, and then issue a SQL Statement to perform a query and retrieve results for analysis. Microsoft SQL2000 Server is supported.

2. The database Monitor ensures that there are enough "connection handles" available and that the specified account can log into the database and that the database server can process the query requests and that the server can distribute the correct result set.

3. The number of rows to be returned when the Monitor executes can be controlled in order to minimize impact on the server being monitored.

4. Success can be determined by examining either row count or analyzing row content. When content analysis is performed, a column number is specified and content may be analyzed as a string or a number.

5. Customer must define the parameters and expected results for the SQL statements that will return the result set.

6. Changes to the application may require that these monitors be modified. Customer must:a. determine if a monitor needs to be changed, b. submit all requests for changes in writing using the Amendment process specified in Section 12.3

of the Agreement, c. engage the appropriate application vendor support re-sources required for IBM to make these

changes, d. approve all changes, e. approve test results, f. approve putting the changes into production. and g. define the sequence of actions to be taken for any alerts. There may be additional charges

associated with such changes which will be determined as part of a PCR.


technical solutions document - wordwonktechnical_solutions_document).doc · web viewyes no tsm...

Documents