vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The free memory of the virtual server instance in kibibytes (1024 bytes).



Table 14: Free memory metric metadata

 Metadata Description 

 Metric name ibm_is_instance_memory_free_kib 
 Metric type gauge 
 Value type byte 
 Segment by IBM IS Generation 2, resource name 







 Memory usage percentage 

The percent of used memory of the virtual server instance.



Table 15: Memory usage percentage metric metadata

 Metadata Description 

 Metric name ibm_is_instance_memory_usage_percentage 
 Metric type gauge 
 Value type percent 
 Segment by IBM IS Generation 2, resource name 









 Volume monitoring metrics 



 Number of bytes read for a volume 

The cumulative number of bytes read for a volume since virtual server instance start.



Table 16: Number of bytes read for a volume metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_read_bytes 
 Metric type gauge 
 Value type byte 
 Segment by IBM IS Generation 2, resource name, disk name of the volume, ID of the volume 







 Number of bytes written for a volume 

The cumulative number of bytes written for a volume since virtual server instance start.



Table 17: Number of bytes written for a volume metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_write_bytes 
 Metric type gauge 
 Value type byte 
 Segment by IBM IS Generation 2, resource name, disk name of the volume, ID of the volume 







 Number of read requests for a volume 

The cumulative number of read requests for a volume since virtual server instance start.



Table 18: Number of read requests for a volume metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_read_requests 
 Metric type gauge 
 Value type none 
 Segment by IBM IS Generation 2, resource name, disk name of the volume, ID of the volume 







 Number of write requests for a volume 

The cumulative number of write requests for a volume since virtual server instance start.



Table 19: Number of write requests for a volume metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_write_requests 
 Metric type gauge 
 Value type none 
 Segment by IBM IS Generation 2, resource name, disk name of the volume, ID of the volume
Kubernetes resource requirements 

The resource requirements for the IBM Cloud® Monitoring agent depend on the size and load of the monitored host. The greater the activity the greater the resource requirements.

Monitoring can consume between 5 KB to 20 KB of bandwidth. The following can affect the bandwidth required:



* The number of metrics
* The number of events
* The number of Kubernetes objects
* The enabled products and features



When data is collected you will see a spike in bandwidth usage while the file is being ingested.

You do not want to place bandwidth shaping or caps on the agent. Doing so can affect data sent to the collection service.

In general, in larger clusters, the agent requires more memory. In servers with a larger number of cores the agent requires more CPU cores to monitor system calls. CPU cores are used on the host and Kubernetes nodes visible to the agent as proxies.

Consider the following environment definitions.



Table 1. Example environment sizings

 Environment size Description 

 Small 8 or less CPU cores <br>10 or less Kubernetes nodes 
 Medium Between 9 and 32 CPU cores <br>Between 10 and 100 Kubernetes nodes 
 Large More than 32 CPU cores <br>More than 100 Kubernetes nodes 



The following recommendations can improve behavior instead of when you use default values. Your environment might require different resources depending on your requirements. The values should only be used for general information.



Table 2. Configuration considerations based on environment sizes

 Cluster configuration Small Medium Large 

 Kubernetes CPU request 1 3 5 
 Kubernetes CPU limit 1 3 5 
 Kubernetes Memory Request 1024 MB 3072 MB 6144 MB 
 Kubernetes Memory Limit 1024 MB 3072 MD 6144 MB 
 Dragent Memory Watchdog 512 MB 1024 MB 2048 MB 
 Cointerface Memory Watchdog 512 MB 2048 MB 4096 MB 



The Monitoring agent has its own memory watchdog to prevent runaway memory consumption on the host in case of memory leaks.
For a more condensed comparison, see [IBM Power Systems CPW performance data comparison](https://www.itechsol.com/wp-content/uploads/2018/07/IBM-Power-Systems-CPW-Performance-Data-Comparison-P7-vs-P8-vs-P9-rev3-July-2018.pdf).
* How do I migrate my VM from one data center to another (WDC04 to DAL13)?

To migrate your VM from one data center to another, you must capture and export your VM to Cloud Object Storage (COS). After you successfully capture and export your VM, copy it to the COS in the destination region, then perform an import followed by a deploy.
* What does VM pinning do?

You can choose to soft pin or hard pin a VM to the host where it is running. When you soft pin a VM for high availability, PowerVC automatically migrates the VM back to the original host once the host is back to its operating state. If the VM has a licensing restriction with the host, the hard pin option restricts the movement of the VM during remote restart, automated remote restart, DRO, and live partition migration. The default pinning policy is none.
* What does it mean to set an affinity or anti-affinity rule?

You can apply affinity and anti-affinity policies to both VMs and volumes.

VM affinity and anti-affinity policy allows you to spread a group of VMs across different hosts or keep them on a specific host.

Volume affinity and anti-affinity policy allow you to control the placement of a new volume based on an existing PVM instance (VM) or volume. When you set an affinity policy for a new storage volume, the volume is created within the same storage provider as an existing PVM instance or volume. With an anti-affinity policy, the new volume is created in a different storage provider other than the storage provider the existing PVM instance or volume is located in.

The use of volume affinity policy (affinity or anti-affinity) requires the availability of multiple storage providers. You might experience the following errors when you use a volume affinity policy:
Can BMR be used for regular backup? 

BMR backup isn't a disk image, but a system volume image backup system. The system isn't intended to be used for regular backups, but along with them.





 Can BMR be used for database backups? 

Database backups must be made separately with the normal IBM Cloud Backup for Classic methods. BMR doesn't replace the need for SQL or Oracle plug-ins. Though BMR uses the VSS technology to backup open files, it can't always be guaranteed that the backed-up files are transaction consistent. The recommendation for these types of specialized applications is that you create two backup jobs: one to back up OS and application binary files and another one for application data.





 What kind of restore jobs can be run with BMR? 

You can either do a whole system restore, or you can pick individual files from the backup to restore. The BMR backup job can replace your current files backup job. The restore process is done inside the OS, just like a traditional backup job.





 Does BMR have open file back up capabilities? 

BMR has open file back up capabilities. However, BMR doesn't replace the need for SQL or Oracle plug-ins. Click [here](https://cloud.ibm.com/docs/Backup?topic=Backup-MSSQLplugin) for the MSSQL plug-in installation instructions.





 How much disk space and time does a BMR restore take? 

A backup that is made from a default installation uses about 6 GB. Such a restore takes around 15 minutes on a 1-GB port. This process is also affected by private port speed. If you need faster backups and restore, a port speed increase might be needed.





 Is the 32-bit version of EVault for Windows® 8 still supported? 

No. The 32-bit version of the backup software agent was retired along with Windows® Server 2008 Standard and data center Editions in March 2017.





 Why does my backup agent show as offline in the WebCC?
Managing volume spike protection and costs 

Configure index rates alerts in your IBM® Log Analysis instance to monitor and be alerted of unexpected spikes in your data volumes. Use the index rate to analyze and predict costs associated with storage of searchable data.

Index rates are calculated based on data that is ingested over the last 30 days and collected in 5 minute intervals.

Data collection commences on January 31, 2022 for existing instances. For new instances, data collection starts from the day that the instance is provisioned.

The standard hourly index rate is used to identify spikes or deviations in data volumes. The standard deviation is calculated by comparing the average hourly index rate with the average of the same hour over a rolling 30 day period. The severity of a spike is measured in standard deviations.

The z-score represents the count of standard deviations. You can use it to predict costs associated with storage of searchable data.



 How are index rates calculated 

The number of log lines that are indexed, that is, the number of log lines that are available for search, are collected every 5 minutes.

A day is based on a 24 hour period that is based on UTC time zone.

To calculate the daily average index rate, the following formula is applied:



1. The total number of indexed lines for the past hour, that is, the number of log lines over 1 hour rolling period, is collected.
2. The total number of indexed lines per hour is then divided by 60 to get the average of log lines per minute.
3. The average log lines per minute is then divided by 60 to get the average of log lines per second.
4. The index rate is calculated as the average value of all index rates that are calculated over 24 hours.



To calculate the hourly average index rate, also known as the standard hourly index rate, the following formula is applied:



1. The total number of indexed lines for the past hour, that is, the number of log lines over 1 hour rolling period, is collected.
2. The total number of indexed lines per hour is then divided by 60 to get the average of log lines per minute.
3.
Segment by IBM IS Generation 2, resource name, disk name of the volume, ID of the volume 







 Number of write requests for a volume 

The cumulative number of write requests for a volume since virtual server instance start.



Table 19: Number of write requests for a volume metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_write_requests 
 Metric type gauge 
 Value type none 
 Segment by IBM IS Generation 2, resource name, disk name of the volume, ID of the volume 









 Virtual server instance monitoring metrics 



 Virtual server instance state 

The state of the virtual server instance. A value of 1 indicates that the virtual server instance is running. A value of -1 indicates that the virtual server instance is stopped. 0 indicates an unknown value.



Table 20: The state of the virtual server

 Metadata Description 

 Metric name ibm_is_instance_running_state 
 Metric type gauge 
 Value type none 
 Segment by IBM IS Generation 2, resource name 









 Attributes for segmentation 



 Global attributes 

These attributes are available for segmenting all of the previously listed metrics.



Table 21: Available attributes for segmenting

 Attribute Attribute Name Attribute Description 

 Cloud type ibm_ctype Coud type is a value of public, dedicated, or local 
 Location ibm_location Location of the monitored resource - this can be a region, data center, or global 
 Resource ibm_resource Resource being measured by the service - typically an identifying name or GUID 
 Resource type ibm_resource_type Type of resource measured by the service 
 Scope ibm_scope Scope of the account, organization, or space GUID that is associated with this metric 
 Service name ibm_service_name Name of the service generating this metric 







 Additional attributes 

These attributes are available to segment one or more attributes as described in the preceding table. See the individual metrics for segmentation options.



Table 22: Available attributes for segmenting one or more attributes

 Attribute Attribute name Attribute description 

 Disk name of the volume ibm_is_disk_name Disk name of the volume that is attached to the virtual server instance, corresponds to output of 'ls -l /dev/disk/by-id'
* Can BMR be used for regular backup?

BMR backup isn't a disk image, but a system volume image backup system. The system isn't intended to be used for regular backups, but along with them.
* Can BMR be used for database backups?

Database backups must be made separately with the normal IBM Cloud Backup for Classic methods. BMR doesn't replace the need for SQL or Oracle plug-ins. Though BMR uses the VSS technology to backup open files, it can't always be guaranteed that the backed-up files are transaction consistent. The recommendation for these types of specialized applications is that you create two backup jobs: one to back up OS and application binary files and another one for application data.
* What kind of restore jobs can be run with BMR?

You can either do a whole system restore, or you can pick individual files from the backup to restore. The BMR backup job can replace your current files backup job. The restore process is done inside the OS, just like a traditional backup job.
* Does BMR have open file back up capabilities?

BMR has open file back up capabilities. However, BMR doesn't replace the need for SQL or Oracle plug-ins. Click [here](https://cloud.ibm.com/docs/Backup?topic=Backup-MSSQLplugin) for the MSSQL plug-in installation instructions.
* How much disk space and time does a BMR restore take?

A backup that is made from a default installation uses about 6 GB. Such a restore takes around 15 minutes on a 1-GB port. This process is also affected by private port speed. If you need faster backups and restore, a port speed increase might be needed.
* Is the 32-bit version of EVault for Windows® 8 still supported?

No. The 32-bit version of the backup software agent was retired along with Windows® Server 2008 Standard and data center Editions in March 2017.
* Why does my backup agent show as offline in the WebCC?
* Specify the minute each hour that a snapshot is to be taken. The default is the current minute.
* Specify the number of hourly snapshots to be retained before the oldest is discarded.



* Daily



* Specify the hour and minute that a snapshot is to be taken. The default is the current hour and minute.
* Select the number of hourly snapshots to be retained before the oldest is discarded.



* Weekly



* Specify the day of the week, hour, and minute that a snapshot is to be taken. The default is the current day, hour, and minute.
* Select the number of weekly snapshots to be retained before the oldest is discarded.





3. Click Save. If the total number of scheduled snapshots is over 50, you receive a warning message and can't save.



The list of the snapshots is displayed as they're taken in the Snapshots section of the Detail page.





 Adding a Snapshot schedule from the SLCLI 

You decide how often and when you want to create a point in time reference of your storage volume with Snapshot schedules. You can have a maximum of 50 snapshots per storage volume. Schedules are managed through the Storage > File Storage for Classic tab of the [IBM Cloud® console](https://cloud.ibm.com/login).

Before you can set up your initial schedule, you must first purchase snapshot space if you didn't purchase it during the initial provisioning of the storage volume.

To create a snapshot schedule, use the following command.

 slcli file snapshot-enable --help
Usage: slcli file snapshot-enable [OPTIONS] VOLUME_ID

Enables snapshots for a given volume on the specified schedule

Options:
--schedule-type TEXT Snapshot schedule [INTERVAL|HOURLY|DAILY|WEEKLY]
[required]
--retention-count TEXT Number of snapshots to retain [required]
--minute INTEGER Minute of the day when snapshots should be taken
--hour INTEGER Hour of the day when snapshots should be taken
--day-of-week TEXT Day of the week when snapshots should be taken
For more information, see [Creating a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create&interface=ui).





 How does the backup service work? 

You add [user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about&interface=uibackup-service-about-tags) to your volumes and specify the same tags in a backup policy. When the tags match, a backup is triggered based on the backup plan schedule. You can [view backup jobs](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policy-jobs) to see the progress of the operation. The Snapshot for VPC service is used to create the backup. The entire contents of the volume are copied and retained for the number of days or total number of backups that are specified in the backup plan. When the retention period is reached, the older backups are deleted.





 What resources are backed up? 

Block Storage for VPC data and boot volumes with user tags that match the tags in a [backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about&interface=uibackup-service-policies) are backed up.





 How do enable my volumes to be backed up? 

Enabling your backups is two-part process. First, you [specify user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-use-policies) on the Block Storage for VPC volumes that you want to back up. You then [create a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create) and specify these tags, which identify the volumes that you're backing up. Within a policy, you create a [backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create&interface=uibackup-plan-ui) to schedule backups of these resources.
Restoring an AIX mksysb image onto an IBM Power Systems Virtual Server instance 

Learn how to restore an AIX mksysb image onto an IBM Power Systems Virtual Server instance

The IPv6 interface that is used for VM management might be affected when you restore an AIX mksysb image. Before proceeding onto the next section, review [Recommended Reliable Scalable Cluster Technology (RSCT) package levels for imported AIX images](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-recommended-rsct-package).



 Defining an AIX Helper VM 

You can use an existing AIX VM to copy an AIX mksysb archive. The alt_disk_mksysb command copies the mksysb archive onto a new volume. The alt_disk_mksysb command also gives you the option of rebooting from a specific disk image.

Before you can copy an AIX mksysb archive, determine the amount of space the helper VM needs to hold the mksysb image. In the following example, the mksysb image (gdrh10v1.sysb) is roughly 5.8 GB. Determining the space needed as follow:

:>ls -l gdrh10v1.sysb
-rw-r--r-- 1 root system 5806899200 Jul 18 2017 gdrh10v1.sysb

Next, you must identify a helper VM file system with enough space to hold the mksysb image. If such a file system does not exist, you can attach a data volume as a staging area. To display information about a volume group, use the lsvg command.

 lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 00f6db0a00004c000000016b94f02
VG STATE: active PP SIZE: 32 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 639 (20448 megabytes)
MAX LVs: 256 FREE PPs: 477 (15264 megabytes)
LVs: 12 USED PPs: 162 (5184 megabytes)
ODF creates three times the specified number. For example, if you enter 1, ODF creates 3 OSDs. 1 
 billingType Enter a billingType of either essentials or advanced for your OCS deployment. advanced 
 ocsUpgrade Enter a true or false to upgrade the major version of your ODF deployment. false 
 workerNodes Optional: Enter the names of the worker nodes that you want to use for your ODF deployment. Don't specify this parameter if you want to use all the worker nodes in your cluster. To retrieve your worker node name, run the oc get nodes command. N/A 
 clusterEncryption Enter true or false to enable encryption. 
 encryptionInTransit Enter true to enable in-transit encryption. Enabling in-transit encryption does not affect the existing mapped or mounted volumes. After a volume is mapped/mounted it retains the encryptioin settings that were used when it was initally mounted. To change the encryption settings for existing volumes, they must be remounted again one-by-one. false 
 hpcsServiceName Enter the name of your Hyper Protect Crypto Services or Key Protect instance. For example: Hyper-Protect-Crypto-Services-eugb. false 
 hpcsInstanceId Enter your Hyper Protect Crypto Services or Key Protect instance ID. For example: d11a1a43-aa0a-40a3-aaa9-5aaa63147aaa. false 
 hpcsSecretName Enter the name of the secret that you created by using your Hyper Protect Crypto Services or Key Protect credentials. For example: ibm-hpcs-secret. false 
 hpcsBaseUrl Enter the public or private endpoint of your Hyper Protect Crypto Services or Key Protect instance. For example: https://api.eu-gb.hs-crypto.cloud.ibm.com:8389. false 
 hpcsTokenUrl Enter https://iam.cloud.ibm.com/identity/token. false 
 ignore-noobaa Enter true if you do not want to deploy MultiCloud Object Gateway. false
Duplication creates a copy of your volume based on a snapshot in the same availability zone as the parent volume. The duplicate volume inherits the capacity and performance options of the original volume by default and has a copy of the data up to the point-in-time of a snapshot. The duplicate volume can be dependent or independent from the original volume, and it can be manually refreshed with data from the parent volume. You can adjust the IOPS or increase the volume size of the duplicate without any effect on the parent volume.



* A dependent duplicate volume does not go through the conversion of becoming independent, and can be refreshed at any time after it is created. It locks the original snapshot so that snapshot cannot be deleted while the dependent duplicate exists. The parent volume cannot be canceled while the dependent duplicate volume exists. If you want to cancel the parent volume, you must either cancel the dependent duplicate first or convert it to an independent duplicate.
* An independent duplicate is superior to the dependent duplicate in most regards, but it cannot be refreshed immediately after creation because of the lengthy conversion process. It can take up to several hours based on the size of the volume. For example, it might take up to a day for a 12-TB volume. However, after the separation process is complete, the data can be manually refreshed by using another snapshot of the original parent volume.



For more information about duplicates, see [Creating and managing duplicate volumes](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-duplicatevolume).



Table 1. Comparison of features between different types of volume copies.
This table has row and column headers. The row headers identify the capability. The column headers identify the type of volume copy.

 Feature Replica Dependent duplicate Independent duplicate 

 Created from a snapshot ![Checkmark icon.](https://cloud.ibm.com/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/icons/checkmark-icon.svg) ![Checkmark icon.]