vania-janet/multiturn-rag-retrieval-data huggingface dataset:
These backups, and any on-demand backups you make, all count toward the above allocation.

In the above example, if your database contains 2 GB of data and you have not taken any on-demand backups, then your total backup size is 2 GB x 30 = 60 GB. Your backup costs are nil.

If your database contains 15 GB of data and you have not taken any on-demand backups, then your total backup size is 15 GB x 30 = 450 GB. In this scenario, your backup costs are (450 GB - 60 GB) * 0.03 = $11.7 per month.

Most deployments will not ever go over the allotted credit.





 Dedicated Cores Pricing 

With dedicated cores, your resource group is given a single-tenant host with a guaranteed minimum reserve of cpu shares. Your deployments are then allocated the number of CPUs you specify. The cost of dedicated cores is $100 per core per month, and each member gets the selected number of cores. For example, if you provision a deployment with 3 dedicated cores per member, that is a total of 9 cores, and billed at $900 per month.





 Scaling per Member 

Databases for EnterpriseDB deployments have minimum and maximum allocation for disk and RAM as shown. Scaling deployments through the API/CLI provides more granularity and also allows a user to scale a database instance up to 4 TB of disk per member.



Table 1. Per Member Scaling Limits

 Resource Minimum Maximum Scaling Granularity (API/CLI) 

 Disk 20 GB per member 4 TB per member 1024 MB per member 
 RAM 1 GB per member 112 GB per member 128 MB per member 
 CPU (if enabled) 3 CPUs per member 28 CPUs per member 1 CPU per member
These backups, and any on-demand backups you make, all count toward the above allocation.

In the above example, if your database contains 2 GB of data and you have not taken any on-demand backups, then your total backup size is 2 GB x 30 = 60 GB. Your backup costs are nil.

If your database contains 15 GB of data and you have not taken any on-demand backups, then your total backup size is 15 GB x 30 = 450 GB. In this scenario, your backup costs are (450 GB - 60 GB) * 0.03 = $11.7 per month.

Most deployments will not ever go over the allotted credit.





 Dedicated Cores Pricing 

You have the option of selecting the CPU allocation for your deployment. With dedicated cores, your resource group is given a single-tenant host with a guaranteed minimum reserve of cpu shares. Your deployments are then allocated the number of CPUs you specify. The cost of dedicated cores is $30 per core per month, and each member gets the selected number of cores. For example, if you provision a deployment with 3 dedicated cores per member, that is a total of 6 cores, and billed at $180 per month.

Dedicated cores are an optional feature. The default Shared CPU setting provisions your deployment on hosts with shared compute resources and incurs no additional charge.





 Scaling per Member 

Databases for Redis deployments have minimum and maximum allocation for disk and RAM. Scaling deployments through the API/CLI provides more granularity and also allows a user to scale a database instance up to 4 TB of disk per member.



Table 1. Per Member Scaling Limits

 Resource Minimum Maximum Scaling Granularity (API/CLI) 

 Disk 1 GB per member 4 TB per member 1024 MB per member 
 RAM 1 GB per member 112 GB per member 128 MB per member 
 CPU (if enabled) 3 CPUs per member 28 CPUs per member 1 CPU per member
: The IBM Cloud Network load balancer (NLB) for VPC is now generally available. Use the network load balancer to distribute traffic among multiple server instances within the same region of your VPC. For more information, see [About IBM Cloud Network Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-network-load-balancers).





 01 September 2020 

New region
: The Sydney region endpoint is now in service at https://au-syd.iaas.cloud.ibm.com. For more information, see [Creating a VPC in a different region](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region). See also [Endpoint URLs](https://cloud.ibm.com/apidocs/vpcendpoint-url) in the IBM Cloud VPC API.







 August 2020 



 27 August 2020 

Large profiles (GA):
: The following two 48-core profiles are now generally available:



* cx2-48x96
* mx2-48x384



For more information, see [Profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles).

UI enhancements
: New design for the VPC Overview page and generation switcher
: Updated load balancer page to include auto scale enablement





 24 August 2020 

Auto scale (GA)
: Auto scale is now generally available. Use auto scale to improve performance and costs by dynamically creating virtual server instances to meet the demands of your environment. For more information, see [Creating an instance group for auto scaling](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-group).





 12 August 2020 

New image support
: Red Hat® Enterprise Linux 8 is now available in all regions.





 07 August 2020 

Virtual private endpoints (Beta)
: Endpoint gateways for IBM Cloud VPC are now available in a limited, allow-listed beta.
C1.8x8 8 8 GB SAN 
 C1.16x16 16 16 GB SAN 
 C1.32x32 32 32 GB SAN 





 Storage notes 



* SAN primary boot disk (25 or 100 GB) with extra disks available, up to 2 TB each (five total disks allowed).
* Pricing for public virtual servers that use SAN storage includes virtual CPU, memory, and minimum primary boot disk. Extra disk prices depend on the disk size and quantity that you select.



All supported operating systems (such as RHEL, CentOS, Windows, Ubuntu, and others), databases that are supported, and software add-ons are also available with this offering.







 Memory 

Memory profiles are best for memory intensive workloads, such as large caching workloads, intensive database applications, or in-memory analytics workloads.

The offering is available in the following profiles:



Table 13. Memory profiles

 Profile vCPU RAM Storage Type 

 M1.1x8 1 8 GB SAN 
 M1.2x16 2 16 GB SAN 
 M1.4x32 4 32 GB SAN 
 M1.8x64 8 64 GB SAN 
 M1.16x128 16 128 GB SAN 
 M1.30x240 30 240 GB SAN 
 M1.48x384 48 384 GB SAN 
 M1.56x448 56 448 GB SAN 
 M1.64x512 64 512 GB SAN 





 Storage notes 



* SAN primary boot disk (25 or 100 GB) with extra disks available, up to 2 TB each (five total disks allowed).
* Pricing for public virtual servers that use SAN storage includes virtual CPU, memory, and minimum primary boot disk. Extra disk prices depend on the disk size and quantity that you select.



All supported operating systems (such as RHEL, CentOS, Windows, Ubuntu, and others), databases that are supported, and software add-ons are also available with this offering.







 GPU 

GPU profiles are best for high-performance workloads that require more compute density to reduce resource management and costs. The GPU profiles are ideal for artificial intelligence processes, intense graphic and data applications, or developing new applications that require fast performance.
Securing your application with Guard 

Guard is a runtime-security solution that IBM Cloud® Code Engine you can use to govern the incoming requests and outgoing responses of your application. Guard uses a per-application auto learned set of micro-rules to govern the application incoming requests and outgoing responses. As a result, you can use Guard to identify application anomalies and support Situational Awareness. Guard can also block requests or responses that are not in line with expected patterns.

In this tutorial, deploy a Hello World application and protect it with Guard.

Before you begin:



* [Set up your Code Engine CLI environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli).
* [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* Be familiar with [deploying applications using CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-app-tutorial).



All Code Engine users are required to have a Pay-as-you-Go account. Tutorials might incur costs. Use the Cost Estimator to generate a cost estimate based on your projected usage. For more information, see [Code Engine pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricing).



 Step 1: Deploy a guard-learner application as a per-project service 

Guard-Learner is a service that learns the necessary micro-rules for each Guard-protected application in a project. To deploy a Guard-Learner application, create it in your project. Note that you create the Guard-Learner application only one time per Code Engine project.



* Protect your application and avoid exposing it to potential offenders by setting the visibility for the app to the project level with the --v project option. For more information, see [Options for visibility for a Code Engine application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloadsoptionsvisibility).
* For more information about the credentials that are used by IBM automation and IBM Support, see [IBM user IDs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-audit_user_ids). By leaving these credentials active, you are granting IBM permission to access the environment for satisfying provisioning requests or providing support as outlined here. You can revoke these credentials to prevent IBM access to the environment. If IBM later needs to satisfy a provisioning request or provide support, you are required to provide updated credentials to IBM Support.
* If credentials such as passwords are changed at any time, IBM Support may no longer be able to help you recover lost or forgotten credentials or even troubleshoot your environments.
* For more information about this issue and related concerns, see [Considerations when changing passwords for NSX components](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_networkingonvcenterservervc_networkingonvcenterserver-change-nsx-component-password-considerations) and [Considerations about changing vCenter Server artifacts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcenter_chg_impact).





 Communication and troubleshooting 



* IBM does not warrant that our products are defect free, however we do endeavor to fix them to work as designed. Clients play a large role in this effort.
* While IBM Support is available to provide assistance throughout the lifecycle of the product, support might be limited by the information and access provided by the client.
* The client is responsible for providing in–depth documentation at the time of a failure and responding timely to IBM Support when further clarification is needed.
* Clients are also responsible for following the guidelines in this document to grant consent to proactive support.
* By declining consent or failing to abide by the guidelines provided, the client assumes the responsibility of possible lag in problem resolution that is caused by communication delays between the client and support team.
* The client must be prepared to perform more technical troubleshooting that would otherwise be done by IBM Support.
* For more information about the credentials that are used by IBM automation and IBM Support, see [IBM user IDs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-audit_user_ids). By leaving these credentials active, you are granting IBM permission to access the environment for satisfying provisioning requests or providing support as outlined here. You can revoke these credentials to prevent IBM access to the environment. If IBM later needs to satisfy a provisioning request or provide support, you are required to provide updated credentials to IBM Support.
* If credentials such as passwords are changed at any time, IBM Support may no longer be able to help you recover lost or forgotten credentials or even troubleshoot your environments.
* For more information about this issue and related concerns, see [Considerations when changing passwords for NSX components](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_networkingonvcenterservervc_networkingonvcenterserver-change-nsx-component-password-considerations) and [Considerations about changing vCenter Server artifacts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcenter_chg_impact).





 Communication and troubleshooting 



* IBM does not warrant that our products are defect free, however we do endeavor to fix them to work as designed. Clients play a large role in this effort.
* While IBM Support is available to assist throughout the lifecycle of the product, support might be limited by the information and access provided by the client.
* The client is responsible for providing in–depth documentation at the time of a failure and responding timely to IBM Support when further clarification is needed.
* Clients are also responsible for following the guidelines set forth in this document to grant consent to proactive support.
* By declining consent or failing to abide by the guidelines provided, the client assumes the responsibility of possible lag in problem resolution, which might be caused by communication delays between the client and support team.
* The client should be prepared to perform more technical troubleshooting that would otherwise be done by IBM Support.
* MAS MS customers are required to have two (2) environments provisioned by default: (1) PROD and (1) NON-PROD
* All clients will be provisioned in their own application instance using dedicated namespace(s)
* IT Administration for the PROD and NON-PROD environments is solely managed by IBM's MAS-Dedicated operations team
* Clients can access PROD and NON-PROD systems via browser based URL
* MAS-Dedicated is an internet based offering that runs over HTTPS. There is no private cloud or direct connect option for MAS-Dedicated
* Clients are provided application administrator access for all applications ordered
* All servers are Red Hat Linux O/S
* Maximo Manage databases are IBM DB2. Oracle and MS SQLServer are not supported.







 MAS-Dedicated Integrations 

IBM Maximo Application Suite Dedicated Service supports integration to / from external systems. There are different options available to provide secure integration connections such as SSL, VPN, and Cloud Object Storage integration. HTTPS (SSL) is the standard encryption method and is supported for XML based interfaces using HTTP Post and Web Service endpoints. In addition, the REST API is available over HTTPS. All these integration methods can also be implemented with authentication. Cloud Object Storage is available for integrations that require file based transfers. A Site-to-Site IPsec VPN Tunnel can also be established between the client network and the IBM or AWS cloud environment using IBM's firewall in order to support other integration transport methods.

Integration options include, but are not limited to:



* Support for synchronous and asynchronous exchange of data with applications within the Suite
* Use of common protocols and format such as Web Services, HTTP, JMS, REST, OSLC, XML, JSON, XML and .csv files, DB tables
* Support of Create, Replace, Update, Delete and Query operation
* Support for customizing integration processing using Processing Rules and Scripting



For the MS-Manage Application:



* Maximo integration message generation and delivery based on application object events
* Support for implementation (batch) data loading
* Pre-defined (75+) interface components provided along with applications to configure new interfaces
There can be up to 4 VSIs in the placement group.



Zoom

![Placement Groups.](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/placement_groups.svg)

Figure 6. Placement group algorithms





 Auto scale 

You can use [Auto scale](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-group&interface=ui) to help optimize your compute costs. Auto scale adds and removes the virtual server instances dynamically to ensure you have the right amount of capacity for the current demand. You pay for what you need when you need it. The additional resources are removed when they are no longer needed.

Zoom

![Autoscale.](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/autoscale-compute.svg)

Figure 7. Auto scale Compute adds virtual servers based on load







 Using LBaaS to help increase resiliency 

IBM Cloud load balancer as a service (LBaaS) is a network offering that you can use to increase resiliency within a region. IBM Cloud provides multiple network devices and connections to ensure that your servers and data storage components are always in contact with each other. When you spread your workload across multiple machines, consider using a load balancer. A load balancer provides a well-known destination to your application. It also provides redundancy and scaling.

For more information about the different types of LBaaS and capabilities, see [Load balancers for VPC overview](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vs-elb).
[High Memory](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-power-vshmemory) Very High Memory profiles are best for server OLAP databases, such as SAP NetWeaver. 







 Custom 

IBM Power Virtual Servers are available with fully adjustable CPU Cores and Memory (RAM GiB). When you create a virtual server instance, you can define a custom size of the IBM Power Virtual Server profile to use for nonproduction SAP HANA instances, in accordance with existing SAP HANA for IBM Power Systems best practices and guidance from SAP.

Custom profiles are for nonproduct development for testing or development use only. These profiles aren't intended for production deployments and aren't supported or certified for SAP production. You cannot use this profile to go from a nonproduction environment to a production environment.

Each profile must have at least two dedicated cores. You can choose between Tier 1 (NVMe-based flash storage) and Tier 3 (SSD flash storage) storage. The Tier 1 storage type is best for customers who require higher throughput. Customers who don't require exceptionally high throughput and are looking to minimize costs want to select Tier 3. For more information, see the [What is a Power Systems Virtual Server?](https://cloud.ibm.com/power-iaas?topic=power-iaas-about-virtual-serverstorage-tiers) storage tiers section.





 Small 



Table 1. SAP HANA servers Small profile family

 Profile CPU Cores CPU Threads (also known as vCPU that uses SMT-8) GiB RAM Minimum Storage (GiB) SAPS SAP HANA Processing Type 

 ush1-4x128 4 32 128 500 24,000 OLAP/OLTP 
 ush1-4x256 4 32 256 910 24,000 OLAP/OLTP 
 ush1-4x384 4 32 384 1,240 24,000 OLAP/OLTP 
 ush1-4x512 4 32 512 1,650 24,000 OLAP/OLTP 
 ush1-4x768 4 32 768 2,140 24,000 OLAP/OLTP 







 Balanced
* [Microsoft SharePoint On Prem](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-sharepoint-onprem-cloud)
* [Salesforce](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-salesforce-cloud)
* [Web crawl](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-web-cloud)



Your data source isn't listed? Check whether IBM® App Connect has a connector to the data source. You can use a default connector that is built for App Connect to send data from a data source to Discovery. For a list of the data sources supported by App Connect default connectors, see [Connectors A-Z](https://www.ibm.com/cloud/app-connect/connectors/). For more information about integrating App Connect with Discovery, see [How to use IBM App Connect with IBM Watson® Discovery](https://www.ibm.com/support/knowledgecenter/SS6KM6/com.ibm.appconnect.dev.doc/how-to-guides-for-apps/watson-discovery.html).

To use an App Connect connector, you must create a separate App Connect instance. Costs that are incurred from a paid App Connect instance are not included with the cost of using Discovery. Except for indexing, Discovery does not support any integration with App Connect that you perform on your own.



 Data source requirements 

The following requirements and limitations are specific to Discovery on IBM Cloud:



* A collection can connect to only one data source.
* For more information about size limits, which can differ per plan, see the following topics:



* [Collection limits](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collectionscollections-limits)
* [Document limits](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collectionscollections-doc-limits)









 Installing IBM Secure Gateway for on-premises data
[Obtain the required information about your virtual data center](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vmware-as-a-service-tfvmware-as-a-service-tf-vdcinfo)
3. [Configure Terraform template variables](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vmware-as-a-service-tfvmware-as-a-service-tf-tfvars)
4. [Init, plan and apply](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vmware-as-a-service-tfvmware-as-a-service-tf-apply)
5. [Connect to the VMware Cloud Director Console](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vmware-as-a-service-tfvmware-as-a-service-tf-connect-to-console)
6. [Connect to the virtual machines through the Internet and validate connectivity](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vmware-as-a-service-tfvmware-as-a-service-tf-connect-to-vm)



An [alternative tutorial](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vmware-as-a-service-tf) using VMware Cloud Director Console is also available.





 Before you begin 

This tutorial requires:



* An IBM Cloud [billable account](https://cloud.ibm.com/docs/account?topic=account-accounts),
* Check for user permissions.
What VPN options are included with each firewall product? 

Not all firewalls offer VPN and not all VPN options are the same. The general options for VPN are:



* Each customer receives unlimited SSL VPN connections to our private network. These connections can be established by clicking the VPN link at the top of the page while logged into the IBM Cloud console.
* IBM Cloud also offers a basic multi-tenant IPsecVPN service.
* The FortiGate Security Appliance 1G provides SSL and IPsecVPN options with Public network access only (no access to the IBM Cloud private network). FSA 10G provides SSL and IPsecVPN options with Public or Private network access.
* The Network Gateway provides SSL, IPsecand OpenVPN capabilities on the public or private network
* The NetScaler products can provide SSL and IPsecVPN on the public or private network.
* Customers can also deploy a VPN solution on to a server within their IBM Cloud environment.







 Which firewall products support public-to-private NAT and/or private VLAN segmentation? 

Fortigate Security Appliance 10G supports NAT and private VLAN segmentation. The other firewall offerings only support public traffic.