vania-janet/multiturn-rag-retrieval-data huggingface dataset:
FAQs for VPC+ Cloud Migration 

FAQs for VPC+ Cloud Migration includes questions about IBM Cloud® migration. To find all FAQs for IBM Cloud, see our [FAQ library](https://cloud.ibm.com/docs/faqs).



  Will there be any business disruption during the migration process? 

Because your virtual server instances are restarted when VPC+ Cloud Migration takes a snapshot of your image, you might have a business disruption if you do not plan for it. You should have a dedicated migration window set to complete your migration.





  What precautions should I take during the migration process? 

Do not delete any resources from your IBM Cloud environment during the migration process, such as IBM Cloud Object Storage and image templates.





  Will migrating IBM Cloud classic environment to IBM Cloud VPC incur more charges? 

Pricing might change depending upon your environment, and you are billed according to the IBM Cloud VPC pricing plan. Also, your VPC environment is charged separately from your classic environment. Migration will not automatically de-provision your existing environment. If you do not want to maintain both accounts, you can de-provision it from IBM Cloud.





  Can I access my current IBM Cloud classic environment if I migrate to VPC? 

Yes, you can establish a link to your existing IBM Cloud classic infrastructure when you migrate to VPC. The migration will not disrupt anything from your existing environment.





  Why is my migration process taking so long? 

Migration can take a significant amount of time depending on the number of instances you are migrating, the size of your images, network performance, and the source location (data center) and the destination region (MZR). Wait until the process is complete and keep the VPC+ Cloud Migration tab open. When the migration process is complete, you will see a success message.
FAQs for Block Storage for VPC 

The following questions often arise about the Block Storage for VPC service. If you have other questions you'd like to see answered here, provide feedback by using the Open doc issue or Edit topic links.



 Offering questions 



 How does Block Storage for VPC prevent a single point of failure? What mechanism assures data durability? 

Block Storage for VPC volume data is stored redundantly across multiple physical disks in an Availability Zone to prevent data loss due to failure of any single component.





 How are volumes created and attached to an instance? 

When you create a virtual server instance, you can [create a Block Storage for VPC volume](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-from-vsi) that is attached to that instance. You can also [create stand-alone volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-standalone-vol) and later attach them to your instances.





 How many instances can share a provisioned Block Storage for VPC volume? 

A Block Storage for VPC volume can be attached to only one instance at a time. Instances cannot share a volume.





 How many Block Storage for VPC secondary data volumes can be attached to an instance? 

You can create 12 Block Storage for VPC data volumes per instance, plus the boot volume.





 How am I charged for usage? 

Cost for Block Storage for VPC is calculated based on GB capacity that is stored per month, unless the duration is less than one month. The volume exists on the account until you delete the volume or you reach the end of a billing cycle, whichever comes first.

Pricing is also affected when you [expand volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes) or [adjust IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-volume-iops) by specifying a different IOPS profile.
[If IHS was setup] HTTP Server URL:
Other details:
VPC name:
Subnet name:
VSIs and their IP addresses:
Notes:
1. For more configuration information, see /etc/virtualimage.properties on your VSI.
2. Refer to IBM Cloud Billing (https://cloud.ibm.com/billing) for the charges incurred for these resources.

For information about the log and correcting errors, see [FAQs](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-faq), [Known issues](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-known-issues), and [Troubleshooting](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-troubleshoot).
8. Access the administrative console or IBM HTTP Server console with the vsi_websphere_admin_name and vsi_websphere_admin_password values to verify the installation. You can also SSH as root user with the SSH key that you set up.







 Next steps 

You can [migrate your WebSphere Application Server applications](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-migrating) to your WebSphere Application Server environment.

To get IBM software support updates, [subscribe to My Notifications and other communications](https://www.ibm.com/support/pages/node/718119).

Join the [IBM WebSphere, Liberty & DevOps Community](https://community.ibm.com/community/user/wasdevops/communities/websphere-home) or [other communities](https://community.ibm.com/community/user/sitemap) to collaborate and share knowledge in forums and blogs.
Dynamic provisioning automatically creates the matching persistent volume (PV) and orders the file share in your account.



1. Create a configuration file to define your persistent volume claim (PVC) and save the configuration as a .yaml file. The following example creates a claim that is named mypvc by using the ibmc-vpc-file-5iops-tier storage class, billed monthly, with a gigabyte size of 10Gi.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: my-pvc
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 10Gi
storageClassName: ibmc-vpc-file-5iops-tier

name
: Enter the name of the PVC.

accessMode
: Specify one of the following options.



* ReadWriteMany: The PVC can be mounted by multiple pods. All pods can read from and write to the volume.
* ReadOnlyMany: The PVC can be mounted by multiple pods. All pods have read-only access.
* ReadWriteOnce: The PVC can be mounted by one pod only. This pod can read from and write to the volume.



storage
: Enter the size of the File Storage for VPC, in gigabytes (Gi). After your storage is provisioned, you can't change the size of your File Storage for VPC. Make sure to specify a size that matches the amount of data that you want to store.

storageClassName
: The name of the storage class that you want to use to provision File Storage for VPC. You can choose to use one of the [IBM-provided storage classes](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-file-vpc-sc-ref) or [create your own storage class](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockcustom-sc-vpc-block).
* [VPN for VPC](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsvpn-for-vpc)
* [VPN Server for VPC](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsvpn-server-for-vpc)







 Compute IAM roles and actions 



* [Auto Scale for VPC](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsauto-scale-for-vpc)
* [Bare Metal Server for VPC](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsbare-metal-server-for-vpc)
* [Dedicated Host for VPC](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsdedicated-host-for-vpc)
* [Image Service for VPC](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsimage-service-for-vpc)
* [Placement Groups for VPC](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsplacement-groups-for-vpc)
* [SSH Key for VPC](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsssh-key-for-vpc)
* [Virtual Server for VPC](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsvirtual-server-for-vpc)







 Storage IAM roles and actions 



* [Block Storage for VPC](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsblock-storage-for-vpc)
<br>To create an instance from a snapshot of a boot volume, use a snapshot in the same region. 
 Billing Think about the number of snapshots that you want to take. Consider whether you want to create fast-restore clones in other zones of your region. Evaluate if you need cross-regional copies. You're charged for the storage consumption and the data transfer separately. Billing for the fast restore feature is set at a flat rate based on instance hours. For more information, see the [FAQs](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-faqs&interface=apifaq-snapshot-pricing). 
 Performance Review the [performance impacts](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restoresnapshots-performance-considerations) for restoring a volume from a snapshot. 







 Next Steps 

After you planned your snapshots, you can [create snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-createsnapshots-vpc-create) of your volumes.
An average of the two would be 12 GB.
* Number of backups per volume per month. You can take a maximum of 750 backup snapshots per volume.
* Percent of incremental change after the initial backup. For example, 15 percent increase in size for each subsequent backup.



3. When you're finished, click Calculate cost.



The cost estimate summary shows how the costs are calculated and breaks down the storage cost, providing a monthly estimate. Click Save to see the details on the cost estimator panel.







 Creating backup policies and plans from the CLI 

You can create a backup policy from the command-line interface (CLI). The following examples show how to create a policy with no plan, a policy and a plan together, and a separate backup plan for an existing policy. They also show how to create multiple plans for an existing policy and how to create a plan with fast restore for backups.

For more information about available command options, see [ibmcloud is backup-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referencebackup-policy-create).



 Before you begin 

Before you can use the CLI, you must install the IBM Cloud CLI and the VPC CLI plug-in. For more information, see the [CLI prerequisites](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup).



1. Log in to IBM Cloud®.

ibmcloud login --sso -a cloud.ibm.com

This command returns a URL and prompts for a passcode. Go to that URL in your browser and log in. If successful, you get a one-time passcode. Copy this passcode and paste it as a response on the prompt. After successful authentication, you are prompted to choose your account. If you have access to multiple accounts, select the account that you want to log in as. Respond to any remaining prompts to finish logging in.
2. Select the current generation of VPC.
Because your virtual server instances are restarted when VPC+ Cloud Migration takes a snapshot of your image, you might have a business disruption if you do not plan for it. You should have a dedicated migration window set to complete your migration.
* What precautions should I take during the migration process?

Do not delete any resources from your IBM Cloud environment during the migration process, such as IBM Cloud Object Storage and image templates.
* Will migrating IBM Cloud classic environment to IBM Cloud VPC incur more charges?

Pricing might change depending upon your environment, and you are billed according to the IBM Cloud VPC pricing plan. Also, your VPC environment is charged separately from your classic environment. Migration will not automatically de-provision your existing environment. If you do not want to maintain both accounts, you can de-provision it from IBM Cloud.
* Can I access my current IBM Cloud classic environment if I migrate to VPC?

Yes, you can establish a link to your existing IBM Cloud classic infrastructure when you migrate to VPC. The migration will not disrupt anything from your existing environment.
* Why is my migration process taking so long?

Migration can take a significant amount of time depending on the number of instances you are migrating, the size of your images, network performance, and the source location (data center) and the destination region (MZR). Wait until the process is complete and keep the VPC+ Cloud Migration tab open. When the migration process is complete, you will see a success message.



Networking Bandwidth Metering for Classic



* How is bandwidth metering priced?



* Public bandwidth egress (or bandwidth allocation) pricing depends on regions. To learn more, visit [Bandwidth packages from IBM Cloud](https://www.ibm.com/cloud/bandwidth) and contact a specialist.
* Public bandwidth usage over GB allocation is charged per GB.



* What IMS permissions do I need to view and change bandwidth allocations (or add and remove devices to and from bandwidth pools)?

The BANDWIDTH_MANAGE IMS infrastructure classic permission is the only required permission for bandwidth metering. After you allow this permission, you can complete the following actions:



* Create a bandwidth pool
* Move a device into or out of a pool
* [Understand IAM Concepts in the IBM Cloud](https://cloud.ibm.com/docs/account?topic=account-iamoverview)
* [Getting Start with IAM and VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-started)
* [Walk-Through Scenarios for Setting VPC Permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resourcesteam-access-scenario)
* [List of IAM Permissions Needed to Perform an Action on a VPC Resource](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls)



![Architecture](https://cloud.ibm.com/docs-content/v1/content/d50364af907081c3c38f99c11f35dd9cab4b2510/vpc-journey/images/prepare-account/vpc-iam.png)





 Understand VPC Quota and limitations: 

IBM Cloud limits the VPC resources provisioned per account per region per vpc by default. Default quotas are set and can be increased by support ticket.



* [VPC quotas and limits](https://https//cloud.ibm.com/docs/vpc?topic=vpc-quotas)







 Next Steps 

The next step on the deployment journey is:



* [Provision VPC](https://cloud.ibm.com/docs/vpc-journey?topic=vpc-journey-vpc-provisioning)
See the Event Notifications catalog page for current pricing.



* As of 31 July, you create a pre-production destination and does not register any devices or send messages, the charges for July will be $15.
* As of 1 August, you register 500 devices and 5001 messages sent. The charges for August will be $30 (This is due to the message threshold exceeds the permitted limit.)
* As of 5 August, you change from pre-production destination to production destination. Then, the charges for August will be $30 plus pro-rata charges of consumption price, which will be equal to

Amount charged = $30 + $ (50/31) x (remaining number of days in the month) = $30 + [(50/31) x 26] = $71.86.
* If you create a pre-production destination on 1 August and do not register any devices and do not sent any message, but on 5th August change from pre-production destination to a production destination, then the charges will be:

Amount charged = $15 + $ (50/31) x (remaining number of days in the month) = $15 + [(50/31) x 26] = $56.86.
In addition:



* Check for user permissions. Be sure that your user account has sufficient permissions to create and manage VPC resources, create a IBM Cloud® Transit Gateway and create a IBM Cloud® Transit Gateway services. See the list of [required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources) for VPC. You will also need the ability to create resource groups and IAM resources like access groups, policies, service IDs, ...
* You need an SSH key to connect to the virtual servers. If you don't have an SSH key, see [the instructions](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys) for creating a key for VPC.







 Plan the Identity and Access Management Environment 

The admin team will enable the other teams to administer their resources as much as possible. The admin team will manage users and control access but will not create and destroy the resources shown in the architecture diagram.

Editor, Operator, Viewer and Manager are [IAM access roles](https://cloud.ibm.com/docs/account?topic=account-userrolesiamusermanrol). Each service defines the exact meaning of the roles and the associated actions. For VPC see the [Required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls) section.

Teams:



* Admin - define the account structure such as resource groups, access groups, users, roles.
* Network - create network resources such as DNS Services, Transit Gateway service, VPC and subnets.
* Shared - create VSI and block devices in the shared VPC. Create DNS records for shared services.
* Application1 - create VSI and block devices in the application1 VPC
* Application2 - create VSI and block devices in the application2 VPC.





 IAM Conceptual 



 Network Team 

A conceptual team ownership model was implemented.
For more information, see [Getting started with Terraform](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started).

VPC infrastructure services use a regional specific based endpoint, which targets to us-south by default. If your VPC is created in another region, make sure to target the right region in the provider block in the provider.tf file.

See the following example of targeting a region other than the default us-south.

provider "ibm" {
region = "eu-de"
}



 View all file shares with Terraform 

Import the list of file shares that belong to an account as a read-only data source. You can filter by share name or resource group ID.

data "ibm_is_shares" "example" {
}

The attributes that are exported include the total count of shares and the list of shares. The nested attributes include share ID, name, creation date, size, IOPS, CRN, access tags, encryption type and key, lifecycle state, replication role and status, mount target, and other attributes.

For more information, see [ibm_is_shares](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_shares).





 View file share information with Terraform 

Import the details of a file share as a read-only data source. You must identify the share by ID or name.

data "ibm_is_share" "example" {
share = ibm_is_share.example.id
}

data "ibm_is_share" "example1" {
name = ibm_is_share.example.name
}

The attributes that are exported include ID, name, creation date, size, IOPS, CRN, access tags, encryption type, encryption key, lifecycle state, replication role and status, mount target, and other attributes.
Be sure that your user account has sufficient permissions to create and manage VPC resources, create a IBM Cloud® Transit Gateway and create a IBM Cloud® Transit Gateway services. See the list of [required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources) for VPC. You will also need the ability to create resource groups and IAM resources like access groups, policies, service IDs, ...
* You need an SSH key to connect to the virtual servers. If you don't have an SSH key, see [the instructions](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys) for creating a key for VPC.







 Plan the Identity and Access Management Environment 

The admin team will enable the other teams to administer their resources as much as possible. The admin team will manage users and control access but will not create and destroy the resources shown in the architecture diagram.

Editor, Operator, Viewer and Manager are [IAM access roles](https://cloud.ibm.com/docs/account?topic=account-userrolesiamusermanrol). Each service defines the exact meaning of the roles and the associated actions. For VPC see the [Required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls) section.

Teams:



* Admin - define the account structure such as resource groups, access groups, users, roles.
* Network - create network resources such as DNS Services, Transit Gateway service, VPC and subnets.
* Shared - create VSI and block devices in the shared VPC. Create DNS records for shared services.
* Application1 - create VSI and block devices in the application1 VPC
* Application2 - create VSI and block devices in the application2 VPC.





 IAM Conceptual 



 Network Team 

A conceptual team ownership model was implemented. The network team administers all the network resources and hence most of what is shown in the diagram.
* How do I view my invoices?

To view your account invoices, follow these steps.



1. Go to the [IBM Cloud console ![External link icon](https://cloud.ibm.com/icons/launch-glyph.svg)](https://%7BDomainName%7D),
2. Then, click Manage > Billing and Usage.



Each account receives a single bill. If you need separate billing for different sets of resources, then you need to create multiple accounts.

For more information about invoices, see [Viewing your invoices](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-managing-invoices).
* How does Block Storage for VPC prevent a single point of failure? What mechanism assures data durability?

 How does Block Storage for VPC prevent a single point of failure? What mechanism assures data durability? 

Block Storage for VPC volume data is stored redundantly across multiple physical disks in an Availability Zone to prevent data loss due to failure of any single component.
* How are volumes created and attached to an instance?

 How are volumes created and attached to an instance? 

When you create a virtual server instance, you can [create a Block Storage for VPC volume](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-from-vsi) that is attached to that instance. You can also [create stand-alone volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-standalone-vol) and later attach them to your instances.
* How many instances can share a provisioned Block Storage for VPC volume?

 How many instances can share a provisioned Block Storage for VPC volume? 

A Block Storage for VPC volume can be attached to only one instance at a time. Instances cannot share a volume.
* How many Block Storage for VPC secondary data volumes can be attached to an instance?
Why am I still seeing charges for block storage devices after deleting my cluster? 

Virtual Private Cloud

Classic infrastructure

  What’s happening 

You have already deleted your cluster but your account is still charged for the storage volumes associated with the cluster.

  Why it’s happening 

When you delete your cluster, you have the option to delete the storage volumes used by the cluster. If you select no, the storage volumes remain in your account, and continue incurring charges until they are deleted.

  How to fix it 

Delete the storage volumes from your account.



1.  Find the cluster ID of the deleted cluster. This ID will be used to remove associated block storage volumes. If you don't have the cluster ID of the deleted cluster, run ibmcloud oc cluster ls and a make a note of the cluster IDs whose block storage volumes you want to keep.

ibmcloud oc cluster ls
2.  Find the remaining volumes that are associated with the deleted cluster.

Classic clusters:

ibmcloud oc storage volume ls --provider classic | awk '{print $1 " " $8}'

Example output for Classic Block Storage volumes. Note the volume ID and the cluster ID.

102413596 blntvemw0j6snjt04jr0

VPC clusters:

ibmcloud oc storage volume ls --provider vpc-gen2 | awk '{print $1 " " $8}'
3.  Remove the volumes.

Classic clusters:

ibmcloud sl block volume-cancel VOLUME_ID

VPC clusters:

ibmcloud is vold VOLUME_NAME_OR_ID
4.  Optional: Verify there are no more volumes associated with the deleted cluster.

Classic clusters:

ibmcloud oc storage volume ls --provider classic | awk '{print $1 " " $8}'

VPC clusters:

ibmcloud oc storage volume ls --provider vpc-gen2 | awk '{print $1 " " $8}'