Skip to content

Commit

Permalink
Content updates for BlueXP repo renaming
Browse files Browse the repository at this point in the history
  • Loading branch information
netapp-bcammett committed May 11, 2023
1 parent 35b561f commit c0d6247
Show file tree
Hide file tree
Showing 34 changed files with 152 additions and 152 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1 +1 @@
# cloud-manager-backup-restore
# bluexp-backup-recovery
2 changes: 1 addition & 1 deletion api-backup-restore.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -174,4 +174,4 @@ curl --location --request GET 'https://api.bluexp.netapp.com/account/account-DpT

== API reference

Documentation for each BlueXP backup and recovery API is available from https://docs.netapp.com/us-en/cloud-manager-automation/cbs/overview.html.
Documentation for each BlueXP backup and recovery API is available from https://docs.netapp.com/us-en/bluexp-automation/cbs/overview.html.
2 changes: 1 addition & 1 deletion concept-backup-to-cloud.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,6 @@ The start time is based on the time zone set on each source ONTAP system. You ca

=== Backup copies are associated with your NetApp account

Backup copies are associated with the https://docs.netapp.com/us-en/cloud-manager-setup-admin/concept-netapp-accounts.html[NetApp account^] in which the BlueXP Connector resides.
Backup copies are associated with the https://docs.netapp.com/us-en/bluexp-setup-admin/concept-netapp-accounts.html[NetApp account^] in which the BlueXP Connector resides.

If you have multiple Connectors in the same NetApp account, each Connector displays the same list of backups. That includes the backups associated with Cloud Volumes ONTAP and on-premises ONTAP instances from other Connectors.
2 changes: 1 addition & 1 deletion concept-cloud-backup-policies.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -224,7 +224,7 @@ ifdef::aws[]
//+
//"s3:BypassGovernanceRetention" must be added only if you want your Admin users to be able to overwrite/delete backup files locked using Governance mode.
+
https://docs.netapp.com/us-en/cloud-manager-setup-admin/reference-permissions-aws.html[View the full JSON format for the policy where you can copy and paste required permissions^].
https://docs.netapp.com/us-en/bluexp-setup-admin/reference-permissions-aws.html[View the full JSON format for the policy where you can copy and paste required permissions^].
endif::aws[]
ifdef::azure[]
* For Azure:
Expand Down
2 changes: 1 addition & 1 deletion concept-kubernetes-backup-to-cloud.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ link:task-licensing-cloud-backup.html#use-a-bluexp-backup-and-recovery-paygo-sub

BYOL is term-based (12, 24, or 36 months) _and_ capacity-based in 1 TB increments. You pay NetApp to use the service for a period of time, say 1 year, and for a maximum amount capacity, say 10 TB.

You'll receive a serial number that you enter in the BlueXP digital wallet page to enable the service. When either limit is reached, you'll need to renew the license. The Backup BYOL license applies to all source systems associated with your https://docs.netapp.com/us-en/cloud-manager-setup-admin/concept-netapp-accounts.html[BlueXP account^].
You'll receive a serial number that you enter in the BlueXP digital wallet page to enable the service. When either limit is reached, you'll need to renew the license. The Backup BYOL license applies to all source systems associated with your https://docs.netapp.com/us-en/bluexp-setup-admin/concept-netapp-accounts.html[BlueXP account^].

link:task-licensing-cloud-backup.html#use-a-bluexp-backup-and-recovery-byol-license[Learn how to manage your BYOL licenses].

Expand Down
2 changes: 1 addition & 1 deletion concept-ontap-backup-to-cloud.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@ If you have an annual contract from a marketplace, all BlueXP backup and recover

BYOL is term-based (12, 24, or 36 months) _and_ capacity-based in 1 TiB increments. You pay NetApp to use the service for a period of time, say 1 year, and for a maximum amount capacity, say 10 TiB.

You'll receive a serial number that you enter in the BlueXP digital wallet page to enable the service. When either limit is reached, you'll need to renew the license. The Backup BYOL license applies to all source systems associated with your https://docs.netapp.com/us-en/cloud-manager-setup-admin/concept-netapp-accounts.html[BlueXP account^].
You'll receive a serial number that you enter in the BlueXP digital wallet page to enable the service. When either limit is reached, you'll need to renew the license. The Backup BYOL license applies to all source systems associated with your https://docs.netapp.com/us-en/bluexp-setup-admin/concept-netapp-accounts.html[BlueXP account^].

link:task-licensing-cloud-backup.html#use-a-bluexp-backup-and-recovery-byol-license[Learn how to manage your BYOL licenses].

Expand Down
2 changes: 1 addition & 1 deletion legal-notices.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,6 @@ include::https://raw.githubusercontent.com/NetAppDocs/common/main/_include/commo
include::https://raw.githubusercontent.com/NetAppDocs/common/main/_include/open-source-notice-intro.adoc[]

// Add required link(s)
* https://docs.netapp.com/us-en/cloud-manager-setup-admin/media/notice.pdf[Notice for BlueXP^]
* https://docs.netapp.com/us-en/bluexp-setup-admin/media/notice.pdf[Notice for BlueXP^]
* link:media/notice_cloud_backup_service.pdf[Notice for the BlueXP backup and recovery^]
* link:media/notice_single_file_restore.pdf[Notice for Single File Restore^]
2 changes: 1 addition & 1 deletion project.yml
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,7 @@ sidebar:
url: /legal-notices.html
product-family:
name: BlueXP
repo: cloud-manager-family
repo: bluexp-family
sidebar_label: All BlueXP documentation
homepage:
tiles:
Expand Down
10 changes: 5 additions & 5 deletions reference-backup-cbs-db-in-dark-site.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -89,9 +89,9 @@ Once you verify that your system is back in a working order, we recommend that y

=== Install a new Connector on a new on-premises Linux host

When installing a new BlueXP Connector, make sure you download the same release of software as you had installed on the original Connector. Periodic changes to the BlueXP backup and recovery database structure may make newer software releases incompatible with the original database backups. You can https://docs.netapp.com/us-en/cloud-manager-setup-admin/task-managing-connectors.html#upgrade-the-connector-on-prem-without-internet-access[upgrade the Connector software to the most current version after restoring the Backup database^].
When installing a new BlueXP Connector, make sure you download the same release of software as you had installed on the original Connector. Periodic changes to the BlueXP backup and recovery database structure may make newer software releases incompatible with the original database backups. You can https://docs.netapp.com/us-en/bluexp-setup-admin/task-managing-connectors.html#upgrade-the-connector-on-prem-without-internet-access[upgrade the Connector software to the most current version after restoring the Backup database^].

. https://docs.netapp.com/us-en/cloud-manager-setup-admin/task-quick-start-private-mode.html[Install the BlueXP Connector on a new on-premises Linux host^]
. https://docs.netapp.com/us-en/bluexp-setup-admin/task-quick-start-private-mode.html[Install the BlueXP Connector on a new on-premises Linux host^]

. Log into BlueXP using the admin user credentials that you just created.

Expand Down Expand Up @@ -144,13 +144,13 @@ unzip catalogxxxxxx.zip

=== Discover your ONTAP clusters and StorageGRID systems

. https://docs.netapp.com/us-en/cloud-manager-ontap-onprem/task-discovering-ontap.html#discover-clusters-using-a-connector[Discover all the on-prem ONTAP working environments^] that were available in your previous environment.
. https://docs.netapp.com/us-en/bluexp-ontap-onprem/task-discovering-ontap.html#discover-clusters-using-a-connector[Discover all the on-prem ONTAP working environments^] that were available in your previous environment.

. https://docs.netapp.com/us-en/cloud-manager-storagegrid/task-discover-storagegrid.html[Discover your StorageGRID systems^].
. https://docs.netapp.com/us-en/bluexp-storagegrid/task-discover-storagegrid.html[Discover your StorageGRID systems^].

=== Set up the StorageGRID environment details

Add the details of the StorageGRID system associated with your ONTAP working environments as they were set up on the original Connector setup using the https://docs.netapp.com/us-en/cloud-manager-automation/index.html[BlueXP APIs^].
Add the details of the StorageGRID system associated with your ONTAP working environments as they were set up on the original Connector setup using the https://docs.netapp.com/us-en/bluexp-automation/index.html[BlueXP APIs^].

You'll need to perform these steps for each ONTAP system that is backing up data to StorageGRID.

Expand Down
2 changes: 1 addition & 1 deletion reference-backup-multi-account-azure.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ summary: BlueXP backup and recovery enables you to create backup files in an Azu
[.lead]
BlueXP backup and recovery enables you to create backup files in an Azure account that is different than where your source Cloud Volumes ONTAP volumes reside. And both of those accounts can be different than the account where the BlueXP Connector resides.

These steps are required only when you are https://docs.netapp.com/us-en/cloud-manager-backup-restore/task-backup-to-azure.html[backing up Cloud Volumes ONTAP data to Azure Blob storage^].
These steps are required only when you are https://docs.netapp.com/us-en/bluexp-backup-recovery/task-backup-to-azure.html[backing up Cloud Volumes ONTAP data to Azure Blob storage^].

Just follow the steps below to set up your configuration in this manner.

Expand Down
4 changes: 2 additions & 2 deletions reference-configure-azure-netapp-files.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,12 +17,12 @@ Using BlueXP you should create a Azure NetApp Files working environment to add a

== Create Azure NetApp Files working environment

You should create Azure NetApp Files working environments where your databases are hosted. For more information, refer to link:https://docs.netapp.com/us-en/cloud-manager-azure-netapp-files/concept-azure-netapp-files.html[Learn about Azure NetApp Files] and link:https://docs.netapp.com/us-en/cloud-manager-azure-netapp-files/task-create-working-env.html[Create an Azure NetApp Files working environment].
You should create Azure NetApp Files working environments where your databases are hosted. For more information, refer to link:https://docs.netapp.com/us-en/bluexp-azure-netapp-files/concept-azure-netapp-files.html[Learn about Azure NetApp Files] and link:https://docs.netapp.com/us-en/bluexp-azure-netapp-files/task-create-working-env.html[Create an Azure NetApp Files working environment].

== Create a connector
A BlueXP account admin should deploy a Connector in Azure that enables BlueXP to manage resources and processes within your public cloud environment.

For information, refer to link:https://docs.netapp.com/us-en/cloud-manager-setup-admin/task-creating-connectors-azure.html[Create a Connector in Azure from BlueXP].
For information, refer to link:https://docs.netapp.com/us-en/bluexp-setup-admin/task-creating-connectors-azure.html[Create a Connector in Azure from BlueXP].

* Ensure that there is connectivity from the connector to the database hosts.
* If you have the Azure NetApp Files working environment and databases in the same Virtual Network (VNet), you can deploy the connector in the same VNet.
Expand Down
8 changes: 4 additions & 4 deletions reference-configure-cloud-volumes-ontap.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,15 @@ Using BlueXP you should create a Cloud Volumes ONTAP working environment to add

== Create Cloud Volumes ONTAP working environment

You can discover and add existing Cloud Volumes ONTAP systems to BlueXP. For information, refer to link:https://docs.netapp.com/us-en/cloud-manager-cloud-volumes-ontap/task-adding-systems.html[Adding existing Cloud Volumes ONTAP systems to BlueXP].
You can discover and add existing Cloud Volumes ONTAP systems to BlueXP. For information, refer to link:https://docs.netapp.com/us-en/bluexp-cloud-volumes-ontap/task-adding-systems.html[Adding existing Cloud Volumes ONTAP systems to BlueXP].

== Create a Connector

You can get started with Cloud Volumes ONTAP for your cloud environment in a few steps. For more information, refer one of the following:

* link:https://docs.netapp.com/us-en/cloud-manager-cloud-volumes-ontap/task-getting-started-aws.html[Quick start for Cloud Volumes ONTAP in AWS]
* link:https://docs.netapp.com/us-en/cloud-manager-cloud-volumes-ontap/task-getting-started-azure.html[Quick start for Cloud Volumes ONTAP in Azure]
* link:https://docs.netapp.com/us-en/cloud-manager-cloud-volumes-ontap/task-getting-started-gcp.html[Quick start for Cloud Volumes ONTAP in Google Cloud]
* link:https://docs.netapp.com/us-en/bluexp-cloud-volumes-ontap/task-getting-started-aws.html[Quick start for Cloud Volumes ONTAP in AWS]
* link:https://docs.netapp.com/us-en/bluexp-cloud-volumes-ontap/task-getting-started-azure.html[Quick start for Cloud Volumes ONTAP in Azure]
* link:https://docs.netapp.com/us-en/bluexp-cloud-volumes-ontap/task-getting-started-gcp.html[Quick start for Cloud Volumes ONTAP in Google Cloud]

You should use the same connector to manage both Cloud Volumes ONTAP working environment and databases.

Expand Down
4 changes: 2 additions & 2 deletions reference-configure-fsx-for-ontap.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,15 @@ Using BlueXP you should create an FSx for ONTAP working environment to add and m

== Create FSx for ONTAP working environment

You should create the FSx for ONTAP working environments where your databases are hosted. For information, refer to link:https://docs.netapp.com/us-en/cloud-manager-fsx-ontap/start/task-getting-started-fsx.html[Get started with Amazon FSx for ONTAP] and link:https://docs.netapp.com/us-en/cloud-manager-fsx-ontap/use/task-creating-fsx-working-environment.html[Create and manage an Amazon FSx for ONTAP working environment].
You should create the FSx for ONTAP working environments where your databases are hosted. For information, refer to link:https://docs.netapp.com/us-en/bluexp-fsx-ontap/start/task-getting-started-fsx.html[Get started with Amazon FSx for ONTAP] and link:https://docs.netapp.com/us-en/bluexp-fsx-ontap/use/task-creating-fsx-working-environment.html[Create and manage an Amazon FSx for ONTAP working environment].

You can create the FSx for ONTAP working environment either using BlueXP or AWS. If you have created using AWS, then you should discover the FSx for ONTAP systems in BlueXP.

== Create a Connector

An Account Admin needs to create a Connector in AWS that enables BlueXP to manage resources and processes within your public cloud environment.

For information, refer to link:https://docs.netapp.com/us-en/cloud-manager-setup-admin/task-quick-start-connector-aws.html[Creating a Connector in AWS from BlueXP].
For information, refer to link:https://docs.netapp.com/us-en/bluexp-setup-admin/task-quick-start-connector-aws.html[Creating a Connector in AWS from BlueXP].

* You should use the same connector to manage both FSx for ONTAP working environment and databases.
* If you have the FSx for ONTAP working environment and databases in the same virtual private cloud (VPC), you can deploy the connector in the same VPC.
Expand Down
2 changes: 1 addition & 1 deletion reference-restart-backup.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ BlueXP backup and recovery functionality is built into the BlueXP Connector. You
| Connector location
| Procedure

| Cloud deployment | Follow the instructions for https://docs.netapp.com/us-en/cloud-manager-setup-admin/task-managing-connectors.html#connect-to-the-linux-vm[connecting to the Connector Linux virtual machine^] depending on the cloud provider you're using.
| Cloud deployment | Follow the instructions for https://docs.netapp.com/us-en/bluexp-setup-admin/task-managing-connectors.html#connect-to-the-linux-vm[connecting to the Connector Linux virtual machine^] depending on the cloud provider you're using.
| Manual installation | Log in to the Linux system.

|===
Expand Down
6 changes: 3 additions & 3 deletions task-backup-kubernetes-to-azure.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -62,8 +62,8 @@ image:diagram_cloud_backup_k8s_cvo_azure.png[A diagram showing how BlueXP backup
Note that the Private Endpoint is optional.

Kubernetes cluster requirements::
* You have discovered the Kubernetes cluster as a BlueXP working environment. https://docs.netapp.com/us-en/cloud-manager-kubernetes/task/task-kubernetes-discover-azure.html[See how to discover the Kubernetes cluster^].
* Trident must be installed on the cluster, and the Trident version must be a minimum of 21.1. See https://docs.netapp.com/us-en/cloud-manager-kubernetes/task/task-k8s-manage-trident.html[how to install Trident^] or https://docs.netapp.com/us-en/trident/trident-managing-k8s/upgrade-trident.html[how to upgrade the Trident version^].
* You have discovered the Kubernetes cluster as a BlueXP working environment. https://docs.netapp.com/us-en/bluexp-kubernetes/task/task-kubernetes-discover-azure.html[See how to discover the Kubernetes cluster^].
* Trident must be installed on the cluster, and the Trident version must be a minimum of 21.1. See https://docs.netapp.com/us-en/bluexp-kubernetes/task/task-k8s-manage-trident.html[how to install Trident^] or https://docs.netapp.com/us-en/trident/trident-managing-k8s/upgrade-trident.html[how to upgrade the Trident version^].
* The cluster must be using Cloud Volumes ONTAP on Azure for its' backend storage.
* The Cloud Volumes ONTAP system must be in the same Azure region as the Kubernetes cluster, and it must be running ONTAP 9.7P5 or later (ONTAP 9.8P11 and later is recommended).
+
Expand Down Expand Up @@ -116,7 +116,7 @@ spec:
```

License requirements::
For BlueXP backup and recovery PAYGO licensing, a subscription through the Azure Marketplace is required before you enable BlueXP backup and recovery. Billing for BlueXP backup and recovery is done through this subscription. https://docs.netapp.com/us-en/cloud-manager-cloud-volumes-ontap/task-deploying-otc-azure.html[You can subscribe from the Details & Credentials page of the working environment wizard^].
For BlueXP backup and recovery PAYGO licensing, a subscription through the Azure Marketplace is required before you enable BlueXP backup and recovery. Billing for BlueXP backup and recovery is done through this subscription. https://docs.netapp.com/us-en/bluexp-cloud-volumes-ontap/task-deploying-otc-azure.html[You can subscribe from the Details & Credentials page of the working environment wizard^].
+
For BlueXP backup and recovery BYOL licensing, you need the serial number from NetApp that enables you to use the service for the duration and capacity of the license. link:task-licensing-cloud-backup.html#use-a-bluexp-backup-and-recovery-byol-license[Learn how to manage your BYOL licenses].
+
Expand Down
Loading

0 comments on commit c0d6247

Please sign in to comment.