vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can now create Red Hat CoreOS enabled Satellite locations in the Sao Paulo (sao, br-sao) region.
: To create a Red Hat CoreOS enabled location in the Sao Paulo region, see [Understanding Satellite locations](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfras-plan-os).





 23 August 2022 

New! You can now create Red Hat CoreOS enabled Satellite locations in the Osaka (osa, jp-osa) region.
: To create a Red Hat CoreOS enabled location in the Osaka region, see [Understanding Satellite locations](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfras-plan-os).





 18 August 2022 

New! You can now create Red Hat CoreOS enabled Satellite locations in the Sydney (syd, au-syd) region.
: To create a Red Hat CoreOS enabled location in the Sydney region, see [Understanding Satellite locations](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfras-plan-os).





 10 August 2022 

Added information about verifying your permissions
: Before you start a task, check that you have the appropriate permissions. See [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 5 August 2022 

CLI change log
: Updated the CLI plug-in change log page for the [release of version 1.0.433](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-changelog).





 3 August 2022 

RHEL 8 is now supported.
: You can now select RHEL8 as your operating system. For more information, see [Planning your operating system](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfras-plan-os).

New! Check out the Satellite Config tutorial.
Unzip the file prometheus-2.27.1.windows-amd64.tar.gz.
3. Edit the prometheus.yml file. For example, you can edit it with Notepad.
4. Configure the scrape_configs section of prometheus.yml configuration file as follows to have prometheus scrape the windows_exporter.

scrape_configs:
 The job name is added as a label job=<job_name> to any timeseries scraped from this configuration.
- job_name: 'windows_exporter'

static_configs:
- targets: ['localhost:9182']

labels:
region: "us-east"
instance: "<HOSTNAME>"
job: "<JOBNAME>"

Where

<HOSTNAME> is the name of the Windows system

<JOBNAME> is a custom attribute that you can set to identify the role of the node that you are scraping, and you can also use to scope the data in IBM Cloud Monitoring

Next, you will add the remote_write configuration to the end of the prometheus.yml file to configure the target monitoring instance that will receive the metrics.

remote_write:
- url: "<ENDPOINT>/prometheus/remote/write"

bearer_token_file: C:UsersAdministratorpromsysdig-apikey

write_relabel_configs:
 Drop forwarding the metrics generated by the exporter that are not supported
- source_labels: ["__name__"]
regex: "^windows_(.)"
action: keep

- regex: "(__name__)|(job)|(region)|(instance)|(status)|(core)|(name)|(start_mode)|(nic)|(volume)|(state)|(version)|(mode)|(branch)|(timezone)|(goversion)|(collector)|(revision)"
action: labelkeep

Where
u3c.2x4 4GB 1000Mbps 2 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD 







 lon 



Table 5. Worker node flavors for London.

 Name Memory Network speed Cores Type OS Primary storage Secondary storage 

 b3c.16x64 64GB 1000Mbps 16 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD 
 b3c.16x64.300gb 64GB 1000Mbps 16 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 300GB SSD 
 b3c.32x128 128GB 1000Mbps 32 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD 
 b3c.4x16 16GB 1000Mbps 4 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD 
 b3c.56x242 242GB 1000Mbps 56 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD 
 b3c.8x32 32GB 1000Mbps 8 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD 
 c3c.16x16 16GB 1000Mbps 16 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD 
 c3c.16x32 32GB 1000Mbps 16 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD 
 c3c.32x32 32GB 1000Mbps 32 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD
* Veeam Backup & Replication configuration database - The database that stores data about the backup infrastructure, jobs, and sessions.
* Veeam Backup & Replication console – The console that provides a user interface to the backup application functions for the Backup Administrator.
* Backup repository – A local entity that provides storage capacity to be used for backups.
* Scale-out backup repository – A logical entity that groups a number of backup repositories (known as extents) to create a scalable pool of storage.
* FLR Appliance - For Linux® File Level Recovery (FLR), Veeam Backup & Replication uses a special FLR helper, which is a small virtual appliance based on a stripped-down Linux kernel.



More information about Veeam software components is provided in section [Veeam solution components](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-bms-archi-components).

Veeam distributed software architecture allows these software packages to be installed on the same physical server or on their own servers. The initial all-in-one Veeam on bare metal server for VMware Solutions deployment provides all the roles that are installed on a single bare metal server per site. Optionally, the architecture can scale out for improved capacity and performance or to provide for VM DR replication functions by deploying more add-on proxies as needed.

The following image shows an overview of the all-in-one server. The all-in-one servers run all Veeam core components and they include local DAS storage for backups.

Zoom

![Veeam on bare metal server deployment model for all-in-one server](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/veeam-bms-deployment-models-all-in-one.svg)

Figure 2. Veeam on bare metal server deployment model for all-in-one server
Veeam backup proxy 

A backup proxy is a Veeam® component that sits between the backup server and other components of the backup infrastructure. While the backup server administers tasks, the proxy processes jobs and delivers backup traffic to the backup repository. Key design elements of backup proxies include the following details:



* By default, the role of the backup proxy is assigned to the backup server. It is recommended to deploy dedicated backup proxies.
* For scaling, backup proxies can be scaled-out or scaled-up.
* A backup proxy can be deployed on either a physical or virtual Windows®-based or Linux®-based server.
* In practice, performance differences don't exist between Windows and Linux proxies. Therefore, the OS decision can be based on such things as licensing.
* Backup proxies run the following components and services:



* The Veeam Installer Service is an auxiliary service that is installed only on the Windows-based server and is used to analyze, install, and upgrade the components.
* The Veeam Data Mover performs the data processing tasks that include retrieving virtual machine (VM) data from storage, compressing, de-duplicating, encrypting, and sending data to the backup repository.



* Ideally, plan for one physical core or one vCPU and 2 GB of RAM for each configured proxy task, where a proxy task processes one VM disk.
* For virtual backup proxy servers, it is recommended to configure proxies with maximum of 8 vCPUs to avoid scheduling issues.
* Typically, virtual backup proxy servers use 4, 6, or 8 vCPUs.
* For a physical backup proxy, consider a 20-core server with 48 GB RAM and dual 10 GB NICS.
* The traffic from the source to the backup proxy is not optimized, for example, compressed or de-duped. Therefore, 100% of the backup data is transferred over this connection.
* Between the backup proxy and backup repository, optimized data typically about 50% of the source data size is transferred over this connection.
* --clone-policy-max-snapshots following by the number of clones you want to keep.
* --clone-policy-zones followed by the list of zones, where you want to keep a copy of the backup snapshot.



The following example creates a backup plan for an existing policy that includes fast restore in two zones within the eu-de region. The plan includes keeping a maximum of two cached backups in each zone. The backup job starts creating backup snapshots at 7:15 PM every day.

ibmcloud is backup-policy-plan-create r138-8c494618-9e4f-4b67-9a08-ee3491404f3b --cron-spec '15 19 * * ' --active --name my-policy-plan --attach-tags my-daily-backup-plan --copy-tags true --delete-after 10 --delete-over-count 2 --clone-policy-max-snapshots 2 --clone-policy-zones eu-de-1,eu-de-3
Creating plan my-policy-plan of backup policy r138-8c494618-9e4f-4b67-9a08-ee3491404f3b under account Test Account as user ibm.user@ibm.com...

ID r138-7734be40-e2a5-4ee6-b4bd-75763639092b
Name my-policy-plan
Active true
Lifecycle state pending
Clone policy Max snapshots Zones
2 eu-de-1,eu-de-3

Deletion trigger Delete after Delete over count
10 2

Attached tags my-daily-backup-plan
Copy tags true
Cron specification 15 19 * * 
Created at 2023-02-21T19:21:28+00:00
Resource type backup_policy_plan
Configuring backup 



 Configuring backup for Citrix Hypervisor 

IBM Cloud® Backup can be configured for backing up hypervisors and virtual machines either on Windows or Linux® operating systems. The backup can be encrypted, compressed, and duplicated. For more details on backing up your system, see [Getting started with IBM Cloud Backup](https://cloud.ibm.com/docs/Backup?topic=Backup-getting-started).

All of the virtual machines are stored on NFS storage, and [thin provisioning](https://docs.citrix.com/en-us/tech-zone/design/reference-architectures/image-management.htmlchoosing-the-right-provisioning-model) can be used while creating the virtual machines by using machine catalogs. Snapshots can be manually created, or they can be scheduled at hourly, daily, or weekly intervals. For more information on scheduling snapshots and receiving notifications, see [Managing Snapshots](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managingSnapshots).





 Configuring backup for VMware ESXi 

When you add or delete a service or infrastructure component, you must wait until the modification is complete before you can add or delete another service or infrastructure component.

You can configure your virtual machine backups with Veeam.



1. Log in to the [IBM Cloud® console](https://cloud.ibm.com/login) by using your unique credentials.
2. Navigate to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/e9cda99c64ea1ee68cf0eda257d6a1de69ddbc4e/icons/icon_hamburger.svg) > VMware > Resources.
3. Select your vCenter instance.
4. Click the Services tab.
5. Click Add.
6. Click Veeam for backups.
7.
Veeam solution components 

Review the Veeam® software components.



 Backup server 

The Veaam Backup server (VBR) is a Windows®-based server on which Veeam Backup & Replication is installed. VBR is the core component in the backup infrastructure that coordinates and manages the configuration and interaction of the other components of the system. This component includes the backup infrastructure, connections to the hypervisors, and the agents that run on customer hosts. This infrastructure eliminates much of the configuration that is traditionally required to be done across several systems into one single pane of glass that streamlines deployment and management. The VBR is backed by the MS SQL 2016 database, which holds the metadata.

The VBR is accessed primarily by way of the Veeam console application, with authentication enabled PowerShell access and authentication enabled API access. Network traffic rules are defined on the VBR server to encrypt all network traffic between Veeam components required for VM backup jobs.

In this design, the all-in-one IBM Cloud bare metal server with Windows 2019 operating system is used to host the VBR server component.





 Enterprise Manager 

Enterprise Manager is a management and reporting component for managing multiple Veeam Backup & Replication installations from a single web console. Enterprise Manager is an optional component of this design.

Enterprise Manager runs as an application on Windows 2019 operating system. You can install Enterprise Manager on the all-in-one server, or alternatively to a server in another suitable backup location based on their design. The customers need to remember, that Enterprise Manager requires a configuration database, which needs to be considered when you deploy Enterprise Manager.





 Backup proxy 

The Veeam proxy is a component that sits between the backup server and the other components of the backup infrastructure, such as storage repository. While the VBR server administers the individual backup tasks, the proxy processes these jobs and delivers the backup traffic. The Veeam Proxy is the high-performance data mover in the Veeam system. The Veeam proxy connects to the customer ESXi™ hypervisor and transfers data between the hypervisor and the various Veeam components as needed.
Veeam backup for Office 365 

Veeam backup for Office 365 protects your Office 365 data by backing up your Exchange Online, SharePoint Online, and OneDrive for Business data. True data protection and RPO (recovery point objective) aren't included with Office 365. Veeam provides a software-defined solution that protects Office 365, performs granular restores, and recovers data to anywhere.



  Features 



*  Custom scheduling of backups
*  View backup and restore session-statistical information
*  Create and view data protection reports
*  Back up different types of Microsoft® objects such as Groups, Sites, Users, and Organizations



As you provision a server with a Microsoft image, you can select Veeam backup for Office 365 as an image add-on. For more information about Veeam backup for Office 365 and IBM Cloud, see [IBM Cloud Veeam backup support for Office 365](https://www.ibm.com/cloud/blog/ibm-cloud-announces-new-veeam-backup-support-for-microsoft-office-365).

For more information about Veeam and IBM, see [Veeam on IBM Cloud](https://www.ibm.com/cloud/veeam).

Veeam backup for Office 365 is available on bare metal and virtual servers on only a monthly basis.
You should design your tests to mimic the potential emergency conditions as closely as possible by simulating a so-called “rolling disaster condition”, where your IT service is impacted progressively by the emergency. This is the best way to test your solution and have a reasonable understanding if it is resilient and has the ability to resist stress conditions.

Testing is one of the most important activities in the disaster recovery process but often hard to complete in the proper manner on public cloud. Because of the standardized nature of the cloud, you can't take for granted the ability to run testing as you need when using on-demand resources, for example:



* The frequency and the moment for the test
* Test by application compared to test of the full environment
* Continue to mirror data to secondary site during the test



You should analyze in detail if the requirements for testing can be met in the selected cloud.
</ns2:SoftLayer_Network_StorageInitParameters>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:disasterRecoveryFailoverToReplicant>
<replicantId xsi:type="int">replica Volume ID</replicantId>
</ns1:disasterRecoveryFailoverToReplicant>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>









 Fail back to the original primary site in the UI 

After a disaster event, IBM Cloud® begins remediation work to return the impacted locations to normal operations. When the site is restored, you can initiate a Failback to the original site by clicking Storage, File Storage for Classic in the [IBM Cloud® console](https://cloud.ibm.com/cloud-storage/file).



1. Click your active volume ("target").
2. In the upper right, click Replica and click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/action-menu-icon.svg).
3. Select Failback. When the primary location is marked disabled, the option of Disaster Recovery Failback becomes active.

During the Disaster Recovery Failover, the system is forced to fail over to the replica site and the replication relationship is severed. To be able to fail back to the original site after the site is restored to normal operations, the system must reestablish the replication bond. This action can take considerable amount of time. Expect a message that shows the failover is in progress. Additionally, an icon appears next to your volume on the File Storage for Classic that indicates that an active transaction is occurring. Hovering over the icon produces a window that shows the transaction. The icon disappears when the transaction is complete. During the Failback process, configuration-related actions are read-only. You can't edit any snapshot schedule or change snapshot space.
For more information, see [Configuring streaming to an Activity Tracker instance](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-streaming-configure-l2l).





 Overview 

Disaster recovery is about surviving a catastrophic failure or loss of availability in a single location.

Activity Tracker is a regional service, there is no automatic cross-regional failover or cross-regional disaster recovery. If all of the availability zones in a region fail, Activity Tracker becomes unavailable in that location.



 Availability zones 

The following table lists the high-availability (HA) status for the regions (locations) where the IBM Cloud Activity Tracker hosted event search service is available:



Table 1. List of locations where the service is available

 Geography Region EU-Supported HA Status 

 Asia Pacific Tokyo (jp-tok) N/A MZR 
 Asia Pacific Osaka (jp-osa) N/A MZR 
 Asia Pacific Chennai (in-che) N/A SZR 
 Asia Pacific Sydney (au-syd) N/A MZR 
 Europe Frankfurt (eu-de) YES MZR 
 Europe London (eu-gb) NO MZR 
 North America Dallas (us-south) N/A MZR 
 North America Washington (us-east) N/A MZR 
 North America Toronto (ca-tor) N/A MZR 
 South America Sao Paulo (br-sao) N/A MZR 



Where



* A geography is a geographic area or larger political body that contains one or more regions.
* A region is a defined geographic territory.

A region could be a specific postal code area, a town, a city, a state, a group of states, or even a group of countries.

A region contains [multiple availability zones](https://www.ibm.com/cloud/data-centers/) to meet local access, low latency, and security requirements for the region.
* N/A means feature that is not applicable to that geography.
* MZR means multi-zone region.
Hybrid Power Disaster Recovery (DR) 

The client wants to use the IBM® Power® Systems Virtual Server as a DR destination for their on-premises environment.



  Client needs 



*  A first step into using infrastructure as a service (IaaS) environment before committing to end-to-end, mission-critical application hosting
*  A mission-critical IBM Power environment with a DR solution to raise the level of security and reliability of their on-premises data center
*  A DR solution in a different geography







  Examples 



*  Client is in need of reducing risk by adding a DR destination without acquiring or growing their data center and capital investment
*  Client has a long-term strategy for cloud migration and can use their DR environment to gain infrastructure as a service experience, and prepare for a production rollout
*  Remote to remote DR site







  Solution components 



*  Power Systems Virtual Server
*  PowerHA (Optional)
*  Direct Link Connect and Direct Link Dedicated (Optional)
*  Cloud Object Storage for custom image hosting
IBM Cloud Resiliency Orchestrator 

IBM® Cloud Resiliency Orchestration (CRO) offers a unified disaster recovery (DR) management approach that delivers real-time DR readiness validation and automated DR testing and recovery.

The Orchestration Server enables DR monitoring, reporting, testing, and workflow automation of complex IT infrastructure and applications. Built-in automation and analytics deliver faster, more cost-effective DR to help keep daily business operations running and to proactively avoid disruptions that lead to lost revenue, brand damage, and dissatisfied customers.

IBM CRO can reduce DR test times and DR failover by up to 80 percent, resulting in a more cost-effective DR experience that is smarter, tailored, and more agile than ever before. Additionally, IBM CRO provides DR process orchestration functions and drives other platform and function orchestrators at different layers.

Zoom

![Orchestrator functions diagram](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/overview/images/BCDR-Architecture-Diagram-image14.svg)

Figure 1. Orchestrator functions diagram



 How do we maintain the disaster recovery posture in IBM Cloud? 

IBM CRO handles the complete lifecycle of the DR process to ensure that the recovery of the application on the cloud can be done quickly and with confidence. This lifecycle is defined by the following.



 Discovery 

IBM CRO interfaces with the infrastructure and applications on the source – be it on premises data center, private cloud, or public cloud, and discovers and builds the full stack of the application including its dependencies and the recovery order. It performs this discovery by directly talking to the underlying infrastructure like the hypervisors, OS, databases, storage, and more, or by ingesting the data that is already available in other configuration management databases or discovery tools. These discovered application stacks form the building blocks on which IBM CRO operates.





 Provision 

After these application stacks are created in IBM CRO, it provisions storage, network, and in certain cases the server itself, and sets up the replication with the appropriate replication interval based on the required
High availability and disaster recovery for Direct Link 

The IBM Cloud® Direct Link global service is highly available within any IBM Cloud location. However, recovering from disasters that affect an entire location requires planning and preparation.

You are responsible for understanding your connection configuration, customization, and usage of the service. You are also responsible for being ready to re-create an instance of the service in a new location and restore your data there. For information on how to design Diversity to achieve HA with Direct Link, see [Models for diversity and redundancy in Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-models-for-diversity-and-redundancy-in-direct-link).



 High availability within the service 

IBM Cloud service supports high availability with no single point of failure. The service achieves high availability automatically and transparently by means of the Multi-Zone Region ([MZR](https://cloud.ibm.com/docs/overview?topic=overview-locationsmzr-table)) feature provided by IBM Cloud.





 High availability for customer Direct Link connections 

Your Direct Link connections are location specific. It is up to you to set up any High Availability or Disaster Recovery plans that are required. For information on how to design Diversity to achieve HA with Direct Link, see [Models for diversity and redundancy in Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-models-for-diversity-and-redundancy-in-direct-link).





 Disaster recovery 

In the event of a catastrophic failure impacting an entire region, and the Direct Link physical link between on-premises and IBM Cloud was in that region, you would experience an outage. If you require a highly available connection to IBM Cloud, it is imperative that you have a redundant connection in a second region. If you decide to rely on a single connection, it is recommended that you back up all configuration elements in case you would ever have to recreate your Direct Link gateway and virtual connections.