vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Multiple instance storage disks 

When there are multiple instance disks on your virtual server instance, each disk is provisioned from a separate underlying physical device. This allows for better independent performance as well as software high-availability solutions to be implemented like software-based RAID.





 Billing 

You are billed for instance storage only while the virtual server instance is running.





 Restrictions 

Using instance storage comes with some restrictions. Keep the following in mind when you are considering instance storage:



* You cannot attach or detach the instance storage disk from an existing virtual server instance.
* The instance storage disk cannot be used as a boot disk.
* Bring your own key (BYOK) is not supported for instance storage.



To prevent loss of critical data, review the data retention policy and ensure that critical data is stored on persistent storage. For more information, see [Lifecycle of instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storageinstance-storage-lifecycle).

For information about provisioning a virtual server instance with instance storage, see [Managing instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage-provisioning).
Workload Placement for bare metal 

Many events can cause server outages. Some are planned and within your control and others are unforeseen events such as hardware failures, software bugs, network issues, and even maintenance that didn’t go as planned. Multiple application servers should be implemented to avoid and eliminate these potential outages. Spinning up multiple applications is not enough. Where the application server is deployed needs to be considered so that you avoid a single fault domain.

For bare metal servers, you want to spread the server application across multiple data centers. By placing the application servers across PODs, availability is improved.

While each POD supports multiple VLANs, you can order extra VLANs at the POD level rather than the data center level. As you order the bare metal server, you can assign the bare metal server to the VLANs to dictate server deployment across PODs within a data center.

Zoom

![Compute resources deployed in different zones/data centers.](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/HA-Compute-different-zones.svg)

Figure 3. Compute resources deployed in different zones/data centers.





 Workload Placement for virtual servers 

The default behavior for the IBM scheduler is to place the virtual servers in available hypervisors first, which can result in virtual servers being placed within the same hypervisor. This can be catastrophic if any or all of the virtual servers are deployed on the same hypervisor. A hardware (HW) or software (SW) failure can cause a disruption.

IBM Cloud provides two solutions to help avoid the virtual servers being deployed on the same hypervisor.



1. Use a dedicated virtual server. This option allows you to own the entire hypervisor and control the placement of the virtual servers.
2. Use Placement Groups. Placement Groups is an anti-affinity feature. If virtual servers are marked in the same placement group, then these virtual servers are instantiated across different hypervisors.
For IBM Cloud® Hyper Protect Virtual Server for IBM Cloud® Virtual Private Cloud instances and z/OS virtual server instances, see [s390x instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-vs-profiles).<br><br>Some profiles might not be available because the amount network interfaces in the virtual server exceed profile limits. You can remove network interfaces to select from more profiles. For more information, see [Resizing a virtual server](https://cloud.ibm.com/docs/vpc?topic=vpc-resizing-an-instance). 
 Operating system Determine what operating system [image](https://cloud.ibm.com/docs/vpc?topic=vpc-about-images) to select for your instance. You can choose a stock image, a custom image from your account, or a custom image that was shared with your account from a private catalog. For more information about custom images, see [Getting started with custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images). <br>If you plan to use Windows operating systems with SQL Server, see the [About Microsoft SQL on VPC](https://cloud.ibm.com/docs/microsoft?topic=microsoft-mssql-about). 
 Naming Make sure that you have a unique name for the instance. The instance name must be unique within an account and region. If you have a method to naming virtual server instances, it's much easier to filter and search on them later. 
 Auxillary storage Determine the amount of auxiliary storage [volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-aboutsecondary-data-volumes) that you need.
Overview of Parallels Server 4 bare metal server 

Parallels Server Bare Metal is a virtualization solution that provides hardware virtualization along side the software virtualization of Virtuozzo, providing technology for both virtual machines and containers*.

Command line interface

Along with the usual Virtuozzo commands, other commands are available: pctl, pmigrate, pstat, and prl_disk_tool.

Migration

You can now migrate Virtuozzo Containers to virtual machines, physical servers to Virtuozzo Containers, and physical servers to virtual machines to allow for consolidation of services. This functionality also allows for one to migrate containers or VMs between bare metal servers, convert VMs that were created on different virtualized environments (V2V), and change Windows SIDs when you clone or deploy a Windows VM from a template.

IP address usage and VLANs

You can assign VMs to an IP from the physical server by using Parallels Tools that are in the VM. Additionally, PSBM allows for virtual switches and VLANs to be created within the VMs to better secure intra-VM network traffic.

Executing commands

You can run raw commands from the physical server directly within the Virtuozzo Containers and now within VMs (when parallels tools are installed within the VM), including user password resets.

Process accounting

You use Parallels Server Bare Metal to increase and reduce the priority of resources that are allocated (CPU, Disk I/O Priority) to a VM quickly.

Backup

Parallels Server Bare Metal provides the functionality to back up and restore VMs and containers on either the local bare metal server or a remote bare metal server to include full, and incremental backups.

Network accounting

You use Parallels Server Bare Metal to easily view and locate VMs or Containers based on current and historical network throughput.

Network

Parallels Server Bare Metal uses Portable IP addresses, while Virtuozzo uses either Portable or Static IP addresses (depending on the configuration).

* IBM Cloud® licenses only hardware virtual machines on Parallels Server 4 Bare Metal, unless otherwise indicated on the order form. VM = virtual machine. V = VPS or Container.
See [Architecture and concepts in serverless instances](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-serverless-architecture-concepts) for a description of the provisioning parameters in the payload.

Note that both Spark 3.1 and Spark 3.3 are supported. If you don't specify a default Spark runtime version when you create a service instance, Spark 3.1 is taken by default.

{
"default_runtime": {
"spark_version": "3.1"
},
"instance_home": {
"region": "us-south",
"endpoint": "https://s3.direct.us-south.cloud-object-storage.appdomain.cloud",
"hmac_access_key": "<your-hmac-access-key",
"hmac_secret_key": "<your-hmac-secret-key"
},
"default_config": {
"key1": "value1",
"key2": "value2"
}
}

The IBM Cloud® response to the create instance command:

Creating service instance MyServiceInstance in resource group Default of account <your account name> as <your user name>...
OK
Service instance MyServiceInstance was created.

Name: MyServiceInstance
ID: crn:v1:staging:public:ibmanalyticsengine:us-south:a/d628eae2cc7e4373bb0c9d2229f2ece5:1e32e-afd9-483a-b1-724ba5cf4::
GUID: 1e32e-afd9-483a-b1-724ba5cf4
Location: us-south
State: provisioning
Type: service_instance
Sub Type:
Service Endpoints: public
Allow Cleanup: false
Locked: false
Created at: 2021-11-29T07:20:40Z
For example, SQL Server on Linux supports Pacemaker. Availability groups on Linux clusters require at least two synchronous replicas to guarantee HA, but at least three replicas for automatic recovery, so it is recommend that an availability group is setup on at least three nodes.
* None - Known as clusterless availability groups or was initially referred to as a read-scale availability group. However, this option provides only a subset of availability groups features, and does not include automatic failover. The features do include manual planned and forced failover and both synchronous and asynchronous replication modes, readable secondary nodes, and secondary replica backups. Availability groups without a WSFC cluster can still provide readable secondary nodes, read-only routing, and load balancing. Failover can be automated with external tools. A new feature of SQL Server 2019 helps mitigate this with automatic traffic redirection, which provides for routing of read/write traffic back to the primary node and does not require a Listener.



The following terminology is used to describe availability group concepts:



* Availability group - supports a replicated environment for a discrete set of user databases.
* HA availability group - a group of databases that fail over together.
* Read-scale availability group - a group of databases that are copied to other instances of SQL Server for read-only workload.
* Primary replica - makes the primary databases available for read-write connections from clients and sends transaction log records of each primary database to every secondary database.
* Secondary replica - up to eight secondary replicas, each of which hosts a set of secondary databases and serves as a potential failover targets for the HA availability group.





 Synchronization modes 

Availability group secondary replicas can be configured with one of the following synchronization modes:



* Synchronous - The log is hardened (the transactions are committed to the transaction log) on every secondary replica before the transaction is committed on the primary replica. This guarantees zero data loss, with a potential performance impact on a highly transactional workload if network latency is high. You can have two synchronous-commit replicas per AG. This mode is best suited for instances in the same AZ or MZR.
Building a custom bare metal server 

Use the following steps to build a custom IBM Cloud® Bare Metal Servers.



 Before you begin 

Make sure that you review the [Getting started tutorial](https://test.cloud.ibm.com/docs/bare-metal?topic=bare-metal-getting-started) before you begin the provisioning process.





 Provisioning through the IBM Cloud catalog 

Use the following steps to provision your Bare Metal Servers through the IBM Cloud.



1. Open the [IBM Cloud catalog](https://cloud.ibm.com/catalog/).
2. Select Bare Metal Servers under Compute.
3. Click Continue. If you do not see a Continue button, you might need to log in.
4. In the Bare Metal Servers section, select the following information:



Table 1: Custom bare metal server selections

 Field Value 

 Quantity Enter the Quantity of identical servers to provision. The default quantity is 1. If you want to provision multiple servers with different specifications, you need to provision the servers separately. 
 Hostname Permanent or temporary name for your servers, for example, baremetal01. Click Information for formatting specifics. 
 Domain Identification string that defines administrative control within the internet, for example, Customer-123456.cloud. Click Information for formatting specifics. 
 Billing Select either Hourly, Monthly, 1-year term, or a 3-year term. 
 Location Region and data center where your server is to be located. 
 Select your server Select the server that best meets your workload. 
 RAM For some servers, RAM defaults are based on the CPU model and can't be changed. Keep in mind that for SAP certified servers, RAM, and operating system default is based on your server selection. Your local storage option also defaults based on your server selection. 
 SSH keys Enter an optional public key of your SSH key that you can use to log in to your server after it is provisioned. 
 Image (operating system) Select an image for your server. Your options are based on your selected server. 
 Add-ons Expand the Add-ons section to select the appropriate options or use the default values.
Veeam on bare metal server introduction 

The Veeam® on bare metal server for IBM Cloud® for VMware Solutions service can be used as a dedicated and all-in-one backup solution for VMware vCenter Server® instances or VMware Regulated Workloads.

The Veeam on bare metal server solution is built on standard IBM Cloud bare metal servers. The servers have a dedicated compute and a local dedicated storage. This solution provides a backup infrastructure that is physically isolated from other IBM Cloud Storage services.

The solution uses Direct Attached Storage (DAS), that is, local SATA disks with RAID 6 attached to the bare metal server, as the Storage Repository for backups. For scaling up, customers can add more proxy servers to the solution to add backup capacity and performance. They can also use IBM Cloud Object Storage together with Veeam's scale-out backup repository functions for redundancy (copying backups) or long-term retention (offload backups).



  Related links 



*  [Veeam Backup & Replication](https://www.veeam.com/vm-backup-recovery-replication-software.html?ad=menu-products)
*  [Veeam Help Center technical documentation](https://www.veeam.com/documentation-guides-datasheets.html?ad=menu-resources)
* INSTANCE: ID or name of the instance.
* INSTANCE_DISK: ID or name of the instance disk.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is instance-disk-update 

Update a virtual server instance disk.

ibmcloud is instance-disk-update INSTANCE INSTANCE_DISK --name NEW_NAME [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* INSTANCE_DISK: ID or name of the instance disk.
* --name: New name of instance disk.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is instance-disks 

List all disks of a virtual server instance.

ibmcloud is instance-disks INSTANCE [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is instance-network-interface 

View details of a network interface of a virtual server instance.

ibmcloud is instance-network-interface INSTANCE NIC [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* NIC: ID or name of the network interface.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.
(https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/HA-bmDeploymentTypes2x.svg)

Figure 1. Two different types of bare metal deployment. Option B with LACP nic bonding is recommended for higher availability.

Note: For VMware, LACP is not available, but other NIC teaming mode is allowed.





 Virtual server 

In the case of virtual server, you do not control which host and hypervisor the virtual server is instantiated on. It is controlled by the IBM Cloud scheduler. You also do not need to worry about the redundant link to the host/hypervisor. Redundancy is already configured to remove the link failure as a SPOF.

It is also best practice to deploy the boot volume on SAN over a local disk. If the host is experiencing a hard shutdown, IBM hypervisor manager evacuates and migrates the virtual server to a different host. This action is only available when the boot volume is on SAN.

Zoom

![The hypervisor with a redundant link connection with NIC bonding configured](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/HA-Hyper-with-redundancy075x.svg)

Figure 2. The hypervisor with a redundant link connection with NIC bonding configured.







 Workload Placement for bare metal 

Many events can cause server outages. Some are planned and within your control and others are unforeseen events such as hardware failures, software bugs, network issues, and even maintenance that didn’t go as planned. Multiple application servers should be implemented to avoid and eliminate these potential outages. Spinning up multiple applications is not enough. Where the application server is deployed needs to be considered so that you avoid a single fault domain.
* [List all reserved IPs bound to a network interface](https://cloud.ibm.com/apidocs/vpc/latestlist-instance-network-interface-ips) for a bare metal server
* [Retrieve bound reserved IP](https://cloud.ibm.com/apidocs/vpc/latestget-instance-network-interface-ip) for a bare metal server









 23 August 2022 



 For all version dates 

Additional user tag support for boot and data volumes. You can now add user tags to boot and data volumes when provisioning a virtual server instance or adding a volume attachment. You can specify the user_tags property when you [create an instance](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance), [create an instance template](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance-template), and [create a volume attachment](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance-volume-attachment). For more information, see [Create and attach a block storage volume when you create a new instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=api) and [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag&interface=api).







 16 August 2022 



 For all version dates 

Improved VLAN support for bare metal servers. The restriction limiting a VLAN ID in the allowed_vlans property to a single PCI [network interface on a bare metal server](https://cloud.ibm.com/apidocs/vpc/latestget-bare-metal-server-network-interface) has been removed. As a result, you can now move VLAN interfaces between PCI interfaces on the same bare metal server.







 26 July 2022 



 For all version dates 

Resource suspension for virtual server instances.
[External link icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/launch-glyph.svg)](https://cloud.ibm.com/login), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Bare metal servers.
2. From the Bare metal servers for VPC page, click Create.
3. On the New bare metal server for VPC page, you can view and select profiles under Profile.







 Using the CLI to view profiles 

Use the following command to list all the bare metal server profiles that are available in a region:

ibmcloud is bare-metal-server-profiles [--output JSON] [-q, --quiet]





 Using the API to view profiles 

List all bare metal server profiles that are available in a region by running the following API request:

curl -X GET 
"$vpc_api_endpoint/v1/bare_metal_server/profiles?version=2021-03-09&generation=2" 
-H "Authorization: $iam_token"





 Next Steps 

After you choose a profile, you can [create bare metal servers on VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-bare-metal-servers).
[Serverless web app and eventing for data retrieval and analytics](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-serverless-github-traffic-analytics)





 Subscription tutorials 

[Subscribing to cron events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cron-tutorialsubscribe-cron-tutorial)



* [Determine your cron interval](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cron-tutorialdetermine-cron-interval)
* [Create your app (or job)](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cron-tutorialcreate-app)
* [Create a subscription](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cron-tutorialcreate-subscription)
* [Testing your subscription](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cron-tutorialtest-subscription)
* [Update your subscription](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cron-tutorialupdate-subscription)
* [Clean up for cron subscription tutorial](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cron-tutorialclean-subscription)



[Subscribing to Object Storage events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialsubscribe-cos-tutorial)



* [Determine your Object Storage bucket and region](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialdetermine-cos-bucket-and-region)
The optional vCenter server instance services, such as Veeam or Zerto are linked to your vCenter server instance. By deleting the source vCenter Server instance, these services are deleted, and so are your historical backups. Additional work effort is required to reconfigure the services or migrate configurations post the automated deployment. This action is done to match your needs and requirements in the new target NSX-T based vCenter Server instance.

This is not a key parameter. However, it gives guidance on where additional project tasks and skills are required. Or also you must take a different approach to these additional services.





 Related links 



* [vCenter Server single site](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverview)
* [vCenter Server multisite](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_multisite)
* [Regulated workloads - single site](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-overview)
* [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices)
To provision a dedicated instance, you must have a dedicated host available or [create one](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances). A dedicated host is required if you use a Windows custom image and [your own license](https://cloud.ibm.com/docs/vpc?topic=vpc-byol-vpc-aboutbyol-vpc-windows). z/OS virtual server instances do not support the dedicated type. 
 Location Locations are composed of regions (specific geographic areas) and zones (fault-tolerant data centers within a region). Select the location where you want to create your virtual server instance. 
 Name A name is required for your virtual server instance. 
 Resource group Select a resource group for the instance. 
 Tags You can assign a user tag to the instance so that you can easily filter instance resources in your resource list. For more information, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag&interface=ui). 
 Access management tags Access management tags help you apply flexible access policies on specific resources. For more information, see the [Controlling access to resources by using tags](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorial) UI tutorial. 



3. Select an operating system for the instance. You can select an image, a snapshot of a boot volume, or an existing boot volume. Table 2 describes these options.



Table 2. Instance provisioning operating system selections

 Field Value 

 Image Select a stock image, Custom image, or Catalog image for the operating system.<br><br><br><br> * For more information about available stock images, see [x86 virtual server images](https://cloud.ibm.com/docs/vpc?topic=vpc-about-images) and [s390x virtual server images](https://cloud.ibm.com/docs/vpc?topic=vpc-vsabout-images).