vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block Storage for VPC snapshots.

You can go to the backup snapshots details page in other ways. For example, when you view a list of [backup jobs](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policy-jobs&interface=uibackup-view-jobs-ui), you can click the snapshots link for a backup job and go to the details page.
2. On the volume details page, select the Snapshots and Backups tab. A list of snapshots that were created by backup policies or manually is shown in the list. Cross-regional copies of snapshots are included in the list, too.
3. From the list, click the backup snapshot name to go to its details page.
4. From the Actions menu, click Create volume.
5. Define the new volume in the side panel. The information is the same as when you create a volume from the [list of snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restorebaas-vpc-restore-snaphot-list-ui). Table 1 describes the options on the side panel.
6. When you're finished, click Save. The new volume is created.







 Creating a volume from a backup snapshot when you provision an instance 

Follow these steps to create a boot and data volume from snapshots when you provision a new virtual server instance.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon !
[menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block Storage for VPC snapshots.

You can go to the backup snapshots details page in other ways. For example, when you view a list of [backup jobs](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policy-jobs&interface=uibackup-view-jobs-ui), you can click the snapshots link for a backup job and go to the details page.
2. On the volume details page, select the Snapshots and Backups tab. A list of snapshots that were created by backup policies or manually is shown in the list. Cross-regional copies of snapshots are included in the list, too.
3. From the list, click the backup snapshot name to go to its details page.
4. From the Actions menu, click Create volume.
5. Define the new volume in the side panel. The information is the same as when you create a volume from the [list of snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restore&interface=uibaas-vpc-restore-snaphot-list-ui). Table 1 describes the options on the side panel.
6. When you're finished, click Save. The new volume is created.







 Creating a volume from a backup snapshot when you provision an instance 

Follow these steps to create a boot and data volume from snapshots when you provision a new virtual server instance.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon !
For more information, see [terraform destroy](https://developer.hashicorp.com/terraform/cli/commands/destroy).





 Deleting snapshots in the UI 

You can delete any snapshot for a volume or all snapshots for a volume. To be able to delete a snapshot, it must meet to the following prerequisites:



* Be in a stable or pending state.
* Not be actively restoring a volume.



An easy way to determine whether you can delete a snapshot is to look in the [console](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-viewsnapshots-vpc-view-list-ui) for the list of snapshots and check its status. You can delete all snapshots for a volume. Deleting all snapshots requires further confirmation in the UI.



 Deleting a single snapshot in the UI 

You can delete a snapshot from the list of all snapshots by using the following steps.



1. Go to the list of all snapshots. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Snapshots.
2. Click the Actions menu (ellipsis) in the row of the snapshot that you want to delete.
3. Select Delete.
4. Confirm the deletion and click Delete.



You can also delete a snapshot from the details page of a Block Storage for VPC volume.



1. Go to the list of all Block Storage for VPC volumes. In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu !
[Enabling Auto scale for better capacity and resiliency](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-ha-auto-scale)Enabling Auto scale for better capacity and resiliency

This tutorial shows you how to set up compute (virtual server instance) Auto scale for horizontal scaling. You create an Auto scale instance template that defines the details of the virtual server instances that are created. After you define the template, you define instance groups to set the scaling policies that determine when and how many virtual server instances are added or removed. The instance group setup includes enabling the backend orchestration to add the newly created virtual server instances to the backend server pool for the cloud load balancer.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 10 minutes
* 2021-04-20



[Regional snapshots in 3-tier architecture](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-regional-snapshots-3-tier-arch)Regional snapshots in 3-tier architecture

Block storage snapshots can be created in IBM Cloud® VPC Gen2. You can use this feature for a backup and restore of a 3-tier application. Block storage snapshots can also be used to scale out a 3-tier system with minimal changes to your application.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 2021-06-25



[Deploying n-tier application with IBM Cloud single availability zone](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-deploy-n-tier-app-szr)Deploying n-tier application with IBM Cloud single availability zone

This tutorial walks you through setting up a resilient environment for an n-tier application in an IBM Cloud® for a single availability zone. The IBM Cloud VPC infrastructure that is created uses Intel Xeon CPUs and additional Intel technologies. In this tutorial, you create your own VPC, then create subnets in one zone of the region, then you provision the virtual server instances.
The interval for creating a backup and its retention period can be the same or they can be different.

Backups that are created by the backup plan inherit the parent volume resource group details. You can create up to four plans per backup policy and modify the backup schedule and retention policy anytime. Your four plans can have different frequencies. For example, one can be daily. Another one can be weekly, and so on. All plans apply to the volumes with tags that match the backup policy.

You can [view backup job status](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policy-jobs) while backups are being created, modified, or deleted.





 Tags for target resources 

Backup policies contain user tags for target resources that associate the policy with Block Storage for VPC volumes with the same user tag. To create backups, at least one user tag that is applied to a volume must match the tag for target resources in the backup policy. User tags are added by an authorized user in the account. Any user with the correct access role can list and can delete user tags in the account on the condition that the tags are not attached to any resource.

In addition to user tags, tags can be access management tags and service tags. Only user tags are applied to backup policies. [Access management tags](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=uistorage-add-access-mgt-tags) are used to manage access to resources; only the account administrator can create access management tags. Service tags are a privileged construct that only authorized services can manage. Users are not authorized to attach and detach service tags on a resource, even if they have access to manage tags on the resource. Service tags are helpful to distinguish which snapshots were created manually or automatically by a backup policy.

If a volume has multiple tags, only one tag needs to match a backup policy tag. Based on the schedule in the backup plan, a matching tag triggers a backup. If multiple volume tags match backup policy tags, only one backup is created at the scheduled interval.
Setting up snapshots with the Block Storage for VPC add-on 

Virtual Private Cloud

Block Storage for VPC volume snapshots provide you with a standardized way to copy a volume's contents at a particular point in time without creating an entirely new volume. For more information, see [How snapshots work](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-about).

If you want to see an example scenario using snapshots to back up a WordPress app, see [Point in time backup and restore of a stateful application](https://w3.ibm.com/w3publisher/isl-cloud-platform/blogs/5ef8f200-0e27-11ed-a874-c7aca9398345).

Deploy the snapshot validation webhook to validate user input. For more information, see [Deploying the snapshot validation webhook](https://github.com/kubernetes-sigs/ibm-vpc-block-csi-driver/tree/master/deploy/kubernetes/snapshot/validation-webhook).



 Creating an app deployment 

Create an example Persistent Volume Claim (PVC) and deploy a pod that references that claim.



1. [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)
2. Verify that the add-on state is normal and the status is Ready.

ibmcloud oc cluster addon ls --cluster CLUSTER-ID

Name Version Health State Health Status
vpc-block-csi-driver 5.0 normal Addon Ready. For more info: http://ibm.biz/addon-state (H1500)
3. Verify that the driver pods are deployed and the status is Running.

kubectl get pods -n kube-system | grep vpc-block-csi

Example output
Setting up snapshots with the Block Storage for VPC add-on 

Virtual Private Cloud

Block Storage for VPC volume snapshots provide you with a standardized way to copy a volume's contents at a particular point in time without creating an entirely new volume. For more information, see [How snapshots work](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-about).

If you want to see an example scenario using snapshots to back up a WordPress app, see [Point in time backup and restore of a stateful application](https://w3.ibm.com/w3publisher/isl-cloud-platform/blogs/5ef8f200-0e27-11ed-a874-c7aca9398345).

Deploy the snapshot validation webhook to validate user input. For more information, see [Deploying the snapshot validation webhook](https://github.com/kubernetes-sigs/ibm-vpc-block-csi-driver/tree/master/deploy/kubernetes/snapshot/validation-webhook).



 Creating an app deployment 

Create an example Persistent Volume Claim (PVC) and deploy a pod that references that claim.



1. [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)
2. Verify that the add-on state is normal and the status is Ready.

ibmcloud ks cluster addon ls --cluster CLUSTER-ID

Name Version Health State Health Status
vpc-block-csi-driver 5.0 normal Addon Ready. For more info: http://ibm.biz/addon-state (H1500)
3. Verify that the driver pods are deployed and the status is Running.

kubectl get pods -n kube-system | grep vpc-block-csi

Example output
* In the Log Level Detail list, select the level of detail for job logging.
* Select or clear the Use all available bandwidth option.



12. Click Run Restore. The Process Details dialog shows the restore progress and indicates when the restore is completed. Other recent job processes might also be listed in the dialog. To close the Process Details screen, click Close. Closing the window does not affect the restore process.







 Restoring databases in AlwaysOn Availability groups 

You must always restore an SQL Server database to the primary replica in an AlwaysOn Availability Group. If Windows® IBM Cloud Backup for Classic Agent and plug-in are not installed on the primary replica server, you must fail over to a server where the software is installed before you attempt the restore.

After you restored a database to the primary replica and added the database back into the AlwaysOn Availability Group, it can be replicated to the secondary replicas. To reduce the amount of replication traffic after a restore, you can run a “Restore from another computer” on any secondary replica server where the Windows® IBM Cloud Backup for Classic Agent and plug-in are installed.



 Restoring a primary database in an AlwaysOn Availability Group 



1. If the IBM Cloud Backup for Classic Agent and plug-in are not installed on the primary replica server, fail over to the secondary database instance where the IBM Cloud Backup for Classic Agent is installed. The formerly secondary replica where you backed up the database becomes the primary replica.
2. Remove the primary database from the AlwaysOn Availability Group.
3. Delete the database from all secondary replicas.
4. Restore the primary database to the original database name by using the Overwrite Existing Databases option.
5. Add the restored primary database to the AlwaysOn Availability Group by using the Full Synchronization option. After you restored an SQL Server database to the primary replica, you can restore the database to secondary replica servers to reduce the amount of required replication traffic.







 Restoring a secondary database in an AlwaysOn Availability Group 



1. If you didn't delete the database from all secondary replicas when you restored the primary database, remove the secondary database from the AlwaysOn Availability Group.
2.
What are the key differences between a snapshot and clone? 

The key differences are as follows:



 Context Snapshot Clone 

 Definion A snapshot is a thin-provisioned group of volumes that cannot be attached to a host or accessed/manipulated. A clone is created from a snapshot and results in independent volumes which surface in the GUI and can be attached to hosts. 
 Primary function Revert or restore the source disks to a desired state Create a complete volume clone 
 Ease of creation Easy and quick process Three-step process and takes long time 
 Pricing Charged 30% of the regular storage rate target volume storage plus the GRS costs 



See [Snapshots, cloning, and restoring](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-volume-snapshot-clonevolume-snapshot-clone) for more detailed information.





 Is there any UI to perform snapshot or clone operations? 

None. You should use the API and CLI to perform snapshot or clone operations. Using the Power Systems Virtual Server API and command line interface (CLI) you can create, restore, delete and attach the snap-shots and volume-clones.

APIs to create snapshot and clone



* [Create a new volumes clone request and initiates the Prepare action](https://cloud.ibm.com/apidocs/power-cloudpcloud-v2-volumesclone-post)
* [Create a PVM Instance snapshot](https://cloud.ibm.com/apidocs/power-cloudpcloud-pvminstances-snapshots-post)



CLIs to create snapshot and clone



* [Create a snapshot](https://cloud.ibm.com/docs/power-iaas-cli-plugin?topic=power-iaas-cli-plugin-power-iaas-cli-referencecreate-snapshot)
Ensure that the VM is configured to point to your AD/DNS servers and optionally add the VM to your DNS domain.
4. Create a nonroot backup user ID on this server and ensure that all the necessary services are configured and started for file transfers. For example, FTP or SSH.
5. Ensure that this VM is included in your Veeam management backup job.







 vCenter file-based backup 

VMware vCenter Server with embedded PSC provides an appliance management user interface and API to export the database and configuration to a file server that uses various protocols. For more information, see [File-Based Backup and Restore of vCenter Server Appliance](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-3EAED005-B0A3-40CF-B40D-85AD247D7EA4.html).

VMware documents an example of how you can configure the API to run periodically as a cron job directly on the vCenter Server Appliance and PSC.

If you have an external PSC, you must back up both the vCenter Server Appliance and the PSC separately by using this technique. If you have an embedded PSC, then the PSC backup is included in your vCenter backup. Familiarize yourself with and plan for the considerations and limitations that are documented by VMware. Also, plan for a regular rotation and expiration of the file backups on your file server.

VMware requires the backup location to be an empty folder, so plan for your backup rotation or automation to leave the location empty for each subsequent backup job.





 NSX file-based backup 

Proper backup of all NSX components is crucial to restoring the system to its working state if a failure occurs. The design requires you to configure NSX backup through the NSX Manager backup function. For this purpose, you can configure NSX Manager to regularly perform backups to your file server.
IBM Cloud classic bare metal to classic bare metal migration 

RackWare Management Module (RMM) solution simplifies the overall migration process of moving the operating system, applications, and data from one bare metal server to another in the IBM Cloud® classic environment. The migration can occur either over the public or private interface of the compute resource. The only requirement is that RMM must be able to access both source and target server over SSH.



 Objectives 



* Prepare the source and target servers
* Learn what is needed for the supported network topology
* Learn how to use the RMM solution







 Limitations 



1. Encrypted volumes are not supported.
2. Do not modify the target. If anything is modified out of control of RMM after the first migration, it can be wiped out and the result can be unexpected.
3. The RMM solution handles only the OS, application, and data movement, so anything else needs to be set up by you (for example, security groups, subnets, etc.).
4. For data migration, file performance and endurance storage are not supported. You can use third-party tools such as rsync for data migration on block and file.







 Supported operating systems 



* CentOS 7.8, 7.9
* RHEL 7.2, 7.3, 7.4, 8.1
* Ubuntu 18.04, 20.04
* Debian 9.x, 10.x
* Windows 2012, 2012R2, 2016, 2019







 Supported topology 

Migration can be done either over the public or the private interface. While RMM uses SSH to communicate with the servers, migrate by using the private address. In addition, you get to use IBM's network during migration over the private interface.

Because RMM is deployed in IBM Cloud VPC, it requires a transit gateway for the RMM to communicate with the source and the target server over the private interface. The source and target server also need to be able to communicate with one another.

If the source and target server do not have direct communication, then consider using pass-through with the RMM server. The RMM server acts as a proxy, and migration flows through the RMM server.
If you need to adjust the resources that are allocated to the new deployment, use the optional fields in the UI, CLI, or API to resize the new deployment. Be sure to allocate enough for your data and workload, if the deployment is not given enough resources the restore fails.

While storage and memory are restored to the same as the source deployment, specific instance configurations are not automatically set for the new instance. In this case, rerunning the configuration after a restore might be needed. Note any instance modifications before running the restore (parameters like shared_buffers, max_connections, deadlock_timeout, archive_timeout, and others) to ensure accurate setting for the instance after the restore is complete.

It is important that you do not delete the source deployment while the backup is restoring. You must wait until the new deployment is provisioned and the backup is restored before deleting the old deployment. Deleting a deployment also deletes its backups so not only does the restore fail, you might not be able to recover the backup either.



 Recovery in the UI 

To initiate a PITR, enter the time that you want to restore back to in Coordinated Universal Time. If you want to restore to the most recent available time, select that option. Clicking Restore brings up the options for your recovery. Enter a name, select the version, region, and allocated resources for the new deployment. Click Recover to start the process.

Zoom

![Recovery Options dialog](https://cloud.ibm.com/docs-content/v1/content/3505da55c475bf1edbe3eb3496324ba13941b783/databases-for-postgresql/images/pitr-dialog.png)

Recovery Options Dialog

If you use Key Protect and have a key, you must use the CLI to recover, and a command is provided for your convenience.





 Recovery in the CLI 

The Resource Controller supports provisioning of database deployments, and provisioning and restoring are the responsibility of the Resource Controller CLI.
The number of volumes is a link that takes you to a [list of volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policiesbackup-view-vol-backup-policies) that apply for the policy. 
 Tags for target resources Tags for target Block Storage for VPC volumes that you are backing up. 
 Last run time (local) The most recent time a job ran for the backup policy. If the field is blank, the volumes don't have matching tags for a job to run. 
 Created date (local) Date and time of when the backup was created. 
 Actions menu Click the Actions icon (...) for available actions, such as restore and delete. 







 Viewing details of a backup policy with the UI 

You can view details of a backup policy by using the UI.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Backup policies. By default, the Overview tab is selected.
2. Click a policy name. Table 2 describes the information about the selected backup policy.





Table 2. Backup policy details

 Field Value 

 Actions Actions on this policy: Add auditing and Delete. 
 Policy details 
 <br><br> * Name<br><br><br> Name of the backup policy. Click the pencil icon to edit. 
 <br><br> * Resource group<br><br><br> [Resource group](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-startedresources-and-resource-groups) for the Block Storage for VPC volume. 
 <br><br> * Location<br><br><br> Policies for the selected region. 
 <br><br> * Created date<br><br><br> Date the policy was created.