AWS sap documentation change
Summary
Updated documentation for AWS Backint agent installation and configuration, including formatting fixes, placeholder standardization, proxy configuration syntax correction, and notification subscription details for GovCloud regions.
Security assessment
Changes include typo corrections, placeholder standardization (e.g., KMS ARN regions), and proxy syntax fixes. While signature verification and KMS encryption are security features, the changes do not introduce new security documentation or address a specific vulnerability. Notification updates for GovCloud regions improve clarity but do not directly relate to security issues.
Diff
diff --git a/sap/latest/sap-hana/aws-backint-agent-s3-installing-configuring.md b/sap/latest/sap-hana/aws-backint-agent-s3-installing-configuring.md index 59f0d6209..016efb5db 100644 --- a//sap/latest/sap-hana/aws-backint-agent-s3-installing-configuring.md +++ b//sap/latest/sap-hana/aws-backint-agent-s3-installing-configuring.md @@ -5 +5 @@ -Install AWS Backint agent using the AWS Systems Manager documentInstall AWS Backint agent using AWS Backint installer — interactive modeInstall AWS Backint agent using AWS Backint installer — silent modeUse a proxy address with AWS Backint agentBackint-related SAP HANA parametersModify AWS Backint agent configuration parametersConfigure SAP HANA to use a different Amazon S3 bucket and folder for data and log backupConfigure SAP HANA to use a different Amazon S3 bucket and folder for catalog backupConfigure AWS Backint agent to use shorter Amazon S3 pathsView AWS Backint agent logsGet the currently installed AWS Backint agent versionUpdate or install previous versionPerformance tuningSubscribe to AWS Backint agent notifications +Install AWS Backint agent using the AWS Systems Manager documentInstall AWS Backint agent using AWS Backint installer — interactive modeInstall AWS Backint agent using AWS Backint installer — silent modeUse a proxy address with AWS Backint agentBackint-related SAP HANA parametersModify AWS Backint agent configuration parametersConfigure SAP HANA to use a different Amazon S3 bucket and folder for data and log backupConfigure SAP HANA to use a different Amazon S3 bucket and folder for catalog backupConfigure AWS Backint agent to use shorter Amazon S3 pathsView AWS Backint agent logsGet the currently installed AWS Backint agent versionUpdate to the newest version or install a previous version of AWS Backint agentPerformance tuningSubscribe to AWS Backint agent notifications @@ -84 +84 @@ Disable any existing backup processes (including scheduled log backups) before c - 1. “modify” — SSM will update the `global.ini` file directly. + 1. "modify" — SSM will update the `global.ini` file directly. @@ -86 +86 @@ Disable any existing backup processes (including scheduled log backups) before c - 2. “sql” — SSM will create a file called `modify_global_ini.sql` with SQL statements that you can run in your target SAP HANA system to set the required parameters. You can find the `modify_global_ini.sql` file in the ``<installation directory>`/aws-backint-agent/` folder. + 2. "sql" — SSM will create a file called `modify_global_ini.sql` with SQL statements that you can run in your target SAP HANA system to set the required parameters. You can find the `modify_global_ini.sql` file in the `<installation directory>/aws-backint-agent/` folder. @@ -88 +88 @@ Disable any existing backup processes (including scheduled log backups) before c - 3. “none” — No action will be taken by SSM to modify the `global.ini` file. You must manually update it to complete the setup. + 3. "none" — No action will be taken by SSM to modify the `global.ini` file. You must manually update it to complete the setup. @@ -100 +100 @@ Disable any existing backup processes (including scheduled log backups) before c - 12. **Important!** **Ensure No Backup In Process**. Choose **Yes** to confirm that you have disabled existing backups and are ready to proceed with the installation. **The SSM document will fail if you choose “No”**. + 12. **Important! Ensure No Backup In Process**. Choose **Yes** to confirm that you have disabled existing backups and are ready to proceed with the installation. **The SSM document will fail if you choose "No"**. @@ -102 +102 @@ Disable any existing backup processes (including scheduled log backups) before c - 6. Under **Targets** , select the method for your target instance to use to install the AWS Backint agent, and then choose the instance on which to install it. If you are not able to find your instance in the list, verify that you have followed all of the steps in the [prerequisites](./aws-backint-agent-Amazon-S3.html#aws-backint-agent-s3-prerequisites). + 6. Under **Targets** , select the method for your target instance to use to install the AWS Backint agent, and then choose the instance on which to install it. If you are not able to find your instance in the list, verify that you have followed all of the steps in the [prerequisites](./aws-backint-agent-amazon-s3.html#aws-backint-agent-s3-prerequisites). @@ -114 +114 @@ If you do not have the latest version of the SSM Agent installed (2.3.274.0 or l -The SSM document creates symbolic links (symlinks) in the SAP HANA global directory for the Backint configuration. Verify that the symlink for `hdbbackint` exists in the `/usr/sap/`<SID>`/SYS/global/hdb/opt` directory and the symlink for `aws-backint-agent-config.yaml` exists in the `/usr/sap/`<SID>`/SYS/global/hdb/opt/hdbconfig` directory. +The SSM document creates symbolic links (symlinks) in the SAP HANA global directory for the Backint configuration. Verify that the symlink for `hdbbackint` exists in the `/usr/sap/<SID>/SYS/global/hdb/opt` directory and the symlink for `aws-backint-agent-config.yaml` exists in the `/usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig` directory. @@ -159 +159 @@ or -If you encounter permission issues while downloading the AWS Backint installer using the AWS CLI, check your IAM policy and ensure that your policies allow for downloading objects from the `awssap-backint-agent` bucket. See the [Identity and Access Management](./aws-backint-agent-Amazon-S3.html#aws-backint-agent-iam) section of this documentation for details. +If you encounter permission issues while downloading the AWS Backint installer using the AWS CLI, check your IAM policy and ensure that your policies allow for downloading objects from the `awssap-backint-agent` bucket. See the [Identity and Access Management](./aws-backint-agent-amazon-s3.html#aws-backint-agent-iam) section of this documentation for details. @@ -183 +183 @@ or -Run the installer with the `-l` flag if you want the installer to get the AWS Backint agent binary file from your own file system or Amazon S3 bucket. Specify the location of the `aws-backint-agent.tar.gz` file. + Run the installer with the `-l` flag if you want the installer to get the {aws} Backint agent binary file from your own file system or Amazon S3 bucket. Specify the location of the [path]``aws-backint-agent.tar.gz`` file. @@ -187 +187 @@ Run the installer with the `-l` flag if you want the installer to get the AWS Ba - sudo python install-aws-backint-agent -l s3://amzn-s3-demo-bucket/aws-backint-agent.tar.gz + sudo python install-aws-backint-agent -l s3://<S3 bucket>/aws-backint-agent.tar.gz @@ -189 +189 @@ Run the installer with the `-l` flag if you want the installer to get the AWS Ba - sudo python install-aws-backint-agent -l https://amzn-s3-demo-bucket.s3.amazonaws.com/aws-backint-agent.tar.gz + sudo python install-aws-backint-agent -l https://<S3 bucket>.s3.amazonaws.com/aws-backint-agent.tar.gz @@ -215 +215 @@ If you leave this field empty, AWS Backint installer will prompt you to confirm - 1. “modify” — AWS Backint installer will update the `global.ini` file directly. + 1. "modify" — AWS Backint installer will update the `global.ini` file directly. @@ -217 +217 @@ If you leave this field empty, AWS Backint installer will prompt you to confirm - 2. “sql” — AWS Backint installer will create a file called `modify_global_ini.sql` with SQL statements that you can run in your target SAP HANA system to set the required parameters. You can find the `modify_global_ini.sql` file in the ``<installation directory>`/aws-backint-agent/` folder. + 2. "sql" — AWS Backint installer will create a file called `modify_global_ini.sql` with SQL statements that you can run in your target SAP HANA system to set the required parameters. You can find the `modify_global_ini.sql` file in the `<installation directory>/aws-backint-agent/` folder. @@ -219 +219 @@ If you leave this field empty, AWS Backint installer will prompt you to confirm - 3. “none” — No action will be taken by AWS Backint installer to modify the `global.ini` file. You must manually update them to complete the setup. + 3. "none" — No action will be taken by AWS Backint installer to modify the `global.ini` file. You must manually update them to complete the setup. @@ -223 +223 @@ If you leave this field empty, AWS Backint installer will prompt you to confirm - 11. **Verify signature of the agent binary`.tar` file ** — + 11. **Verify signature of the agent binary`–0—tar` file** — @@ -225 +225 @@ If you leave this field empty, AWS Backint installer will prompt you to confirm - * Choose `y` to verify the signature of the AWS Backint agent source file. If you choose `y`, enter the Amazon S3 bucket location of the signature file of the agent binary `.tar` file, for example, `https://s3.amazonaws.com/awssap-backint-agent/binary/latest/aws-backint-agent.sig`. Or, provide a local file that is stored on the instance. If you proceed without making a selection, the default location listed within brackets ([]) is used. + * Choose `y` to verify the signature of the AWS Backint agent source file. If you choose `y`, enter the Amazon S3 bucket location of the signature file of the agent binary `–0—tar` file, for example, ` [https://s3.amazonaws.com/awssap-backint-agent/binary/latest/aws-backint-agent.sig](https://s3.amazonaws.com/awssap-backint-agent/binary/latest/aws-backint-agent.sig) `. Or, provide a local file that is stored on the instance. If you proceed without making a selection, the default location listed within brackets ([]) is used. @@ -233 +233 @@ If you leave this field empty, AWS Backint installer will prompt you to confirm - 7. To verify the installation, log in to your instance and view the `/`<install directory>`/aws-backint-agent` directory. You should see the following files in the directory: the AWS Backint agent binary, the `THIRD_PARTY_LICENSES.txt` file, which contains licenses of libraries used by the agent, the launcher script, the YAML configuration file, and the optional `modify_global_ini.sql` file. In addition, a source file (`aws-backint-agent.tar.gz`) of AWS Backint agent is stored in the package directory. You can verify the signature of this file to ensure that the downloaded source file is original and unmodified. See the [Verifying the signature of AWS Backint agent and installer for SAP HANA](./aws-backint-agent-signature.html) section in this document for details. + 7. To verify the installation, log in to your instance and view the `/<install directory>/aws-backint-agent` directory. You should see the following files in the directory: the AWS Backint agent binary, the `THIRD_PARTY_LICENSES.txt` file, which contains licenses of libraries used by the agent, the launcher script, the YAML configuration file, and the optional `modify_global_ini.sql` file. In addition, a source file (`aws-backint-agent.tar.gz`) of AWS Backint agent is stored in the package directory. You can verify the signature of this file to ensure that the downloaded source file is original and unmodified. See the [Verifying the signature of AWS Backint agent and installer for SAP HANA](./aws-backint-agent-signature.html) section in this document for details. @@ -235 +235 @@ If you leave this field empty, AWS Backint installer will prompt you to confirm -In addition, the AWS Backint installer creates symbolic links (symlinks) in the SAP HANA global directory for the Backint configuration. Verify that the symlink for `hdbbackint` exists in the `/usr/sap/`<SID>`/SYS/global/hdb/opt` directory, and that the symlink for `aws-backint-agent-config.yaml` exists in the `/usr/sap/`<SID>`/SYS/global/hdb/opt/hdbconfig` directory. +In addition, the AWS Backint installer creates symbolic links (symlinks) in the SAP HANA global directory for the Backint configuration. Verify that the symlink for `hdbbackint` exists in the `/usr/sap/<SID>/SYS/global/hdb/opt` directory, and that the symlink for `aws-backint-agent-config.yaml` exists in the `/usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig` directory. @@ -256 +256 @@ The following is an example response file. - s3_bucket_name = amzn-s3-demo-bucket + s3_bucket_name = <S3 bucket> @@ -259,2 +259,2 @@ The following is an example response file. - s3_bucket_region = us-east-1 - s3_sse_kms_arn = arn:aws:kms:us-east-1:111122223333:key/1abcd9b9-ab12-1a2a-1abc-12345abc12a3 + s3_bucket_region = <us-east-1> + s3_sse_kms_arn = arn:aws:kms:<us-east-1>:111122223333:key/1abcd9b9-ab12-1a2a-1abc-12345abc12a3 @@ -268 +268 @@ If you want to generate the response file programmatically instead of using AWS - sudo python install-aws-backint-agent -g "s3_bucket_owner_account_id = 111122223333,s3_bucket_name = amzn-s3-demo-bucket,s3_bucket_region = us-east-1,hana_sid = TST,s3_sse_kms_arn = arn:aws:kms:us-east-1:111122223333:key/1abcd9b9-ab12-1a2a-1abc-12345abc12a3,s3_bucket_folder = myfolder,installation_directory = /hana/shared/,modify_global_ini = sql" -f myresponse.rsp + sudo python install-aws-backint-agent -g "s3_bucket_owner_account_id = 111122223333,s3_bucket_name = <S3 bucket>,s3_bucket_region = <us-east-1>,hana_sid = TST,s3_sse_kms_arn = arn:aws:kms:<us-east-1>:111122223333:key/1abcd9b9-ab12-1a2a-1abc-12345abc12a3,s3_bucket_folder = myfolder,installation_directory = /hana/shared/,modify_global_ini = sql" -f myresponse.rsp @@ -297 +297 @@ If you use a proxy address in your SAP HANA environment when you install the age - export HTTP_PROXY=<PROXY_ADDRESS>:<PROXY_PORT> + export HTTP_PROXY=<PROXY_ADDRESS:PROXY_PORT> @@ -316 +316 @@ Add `http_proxy`, `HTTP_PROXY`, `no_proxy`, and `NO_PROXY` variables to the `aws -To enable SAP HANA backups using AWS Backint agent, you must set the following SAP HANA parameters. If you chose the “modify” option for the `global.ini` file update, the SSM document or AWS Backint installer adds or updates the following backup related SAP HANA parameters in `global.ini` for the system database. If you chose “sql”, you can run the SQL statements specified in the `modify_global_ini.sql` file to update these parameters. For more details about these parameters, see [Backup Configuration Parameters](https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.03/en-US/c1eb6ff410f946318dae539cb3d33f9f.html) in the _SAP HANA Administration Guide_. +To enable SAP HANA backups using AWS Backint agent, you must set the following SAP HANA parameters. If you chose the "modify" option for the `global.ini` file update, the SSM document or AWS Backint installer adds or updates the following backup related SAP HANA parameters in `global.ini` for the system database. If you chose "sql", you can run the SQL statements specified in the `modify_global_ini.sql` file to update these parameters. For more details about these parameters, see [Backup Configuration Parameters](https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.03/en-US/c1eb6ff410f946318dae539cb3d33f9f.html) in the _SAP HANA Administration Guide_. @@ -343 +343 @@ Changing the `tcp_backlog` parameter requires a restart of SAP HANA to take effe -The AWS Backint agent configuration parameters are maintained in a YAML file in the `/``<installation directory>``/aws-backint-agent/` directory. The name of the configuration file is `aws-backint-agent-config.yaml`. The following tables summarize the configuration parameters added as part of the AWS Backint agent installation process, and additional parameters that you can add or change. +The AWS Backint agent configuration parameters are maintained in a YAML file in the `/<installation directory>/aws-backint-agent/` directory. The name of the configuration file is `aws-backint-agent-config.yaml`. The following tables summarize the configuration parameters added as part of the AWS Backint agent installation process, and additional parameters that you can add or change. @@ -354 +354 @@ Name of the parameter | Description | Default value -`S3SseKmsArn` | ARN of the kms-key that AWS Backint agent can use to encrypt the backup files stored in Amazon S3. For example, `arn:aws:kms:us-east-1: 111122223333:key/5bfbc9b9-ab12-ab12-a123-11111xxx22xx`. | Empty +`S3SseKmsArn` | ARN of the kms-key that AWS Backint agent can use to encrypt the backup files stored in Amazon S3. For example, `arn:aws:kms:<us-east-1>: 111122223333:key/5bfbc9b9-ab12-ab12-a123-11111xxx22xx`. | Empty @@ -389 +389 @@ To use a different Amazon S3 bucket and folder for the data and log backups, fol -Locate the `data_backup_parameter_file` and `log_backup_parameter_file` parameters. The default value of these parameters should be `/`<installation directory>`/aws-backint-agent/aws-backint-agent-config.yaml`. If you do not see this default value, check the configuration file to confirm that it is displaying the same Amazon S3 location. +Locate the `data_backup_parameter_file` and `log_backup_parameter_file` parameters. The default value of these parameters should be `/<installation directory>/aws-backint-agent/aws-backint-agent-config.yaml`. If you do not see this default value, check the configuration file to confirm that it is displaying the same Amazon S3 location. @@ -399 +399 @@ Move the previous logs backup with source type `volume` to the new Amazon S3 loc -The backup catalog is assigned a name in the following format: `log_backup_0_0_0_0.`<BackupID>``. This type of backup is managed by a different SAP HANA parameter, has a source type `catalog`, and should remain in the data backup location. This file contains the backup catalog file that stores the history of all backups. Only the log backups with source type `volume` should be moved to the new Amazon S3 location. To change the Amazon S3 location for catalog backup, see Configure SAP HANA to use a different Amazon S3 bucket and folder for catalog backup. +The backup catalog is assigned a name in the following format: `log_backup_0_0_0_0.<BackupID>`. This type of backup is managed by a different SAP HANA parameter, has a source type `catalog`, and should remain in the data backup location. This file contains the backup catalog file that stores the history of all backups. Only the log backups with source type `volume` should be moved to the new Amazon S3 location. To change the Amazon S3 location for catalog backup, see Configure SAP HANA to use a different Amazon S3 bucket and folder for catalog backup. @@ -408 +408 @@ log_backup_0_0_0_0/ | Log file with source type "catalog" -log_backup_1_0_`<backup ID>`_`<backup ID>` | Log file with source type "volume" +log_backup_1_0_<backup ID>_<backup ID> | Log file with source type "volume" @@ -418,2 +418,2 @@ log_backup_0_0_0_0/ | Log file with source type "catalog" -log_backup_2_0_`<backup ID>`_`<backup ID>` | Log file with source type "volume" -log_backup_3_0_`<backup ID>`_`<backup ID>` | Log file with source type "volume" +log_backup_2_0_<backup ID>_<backup ID> | Log file with source type "volume" +log_backup_3_0_<backup ID>_<backup ID> | Log file with source type "volume" @@ -430 +430 @@ Run the following commands to move the volume type of SYSTEM DB logs. In the exa - aws s3api put-object --bucket <S3 bucket> --key <S3 folder for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --region us-east-1 + aws s3api put-object --bucket <S3 bucket> --key <S3 folder for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --region <us-east-1> @@ -433 +433 @@ Run the following commands to move the volume type of SYSTEM DB logs. In the exa - aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ s3://<S3 bucket>/<S3 folder for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "*" --include "log_backup_1_0*" --recursive --dryrun --region us-east-1 + aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ s3://<S3 bucket>/<S3 folder for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "*" --include "log_backup_1_0*" --recursive --dryrun --region <us-east-1> @@ -436 +436 @@ Run the following commands to move the volume type of SYSTEM DB logs. In the exa - aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ s3://<S3 bucket>/<S3 folder for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "*" --include "log_backup_1_0*" --recursive --region us-east-1 + aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ s3://<S3 bucket>/<S3 folder for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "*" --include "log_backup_1_0*" --recursive --region <us-east-1> @@ -439 +439 @@ Run the following commands to move the volume type of SYSTEM DB logs. In the exa - aws s3 ls s3://<S3 bucket>/<S3 folder for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --region us-east-1 + aws s3 ls s3://<S3 bucket>/<S3 folder for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --region <us-east-1> @@ -446 +446 @@ Run the following commands to move the volume type TENANT DB logs. In the exampl - aws s3api put-object --bucket <S3 bucket> --key <S3 folder for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --region us-east-1 + aws s3api put-object --bucket <S3 bucket> --key <S3 folder for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --region <us-east-1> @@ -449 +449 @@ Run the following commands to move the volume type TENANT DB logs. In the exampl - aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ s3://<S3 bucket>/<S3 bucket for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include "log_backup_2_0" --include "log_backup_3_0" --recursive --dryrun --region us-east-1 + aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ s3://<S3 bucket>/<S3 bucket for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include "log_backup_2_0" --include "log_backup_3_0" --recursive --dryrun --region <us-east-1> @@ -452 +452 @@ Run the following commands to move the volume type TENANT DB logs. In the exampl - aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ s3://<S3 bucket>/<S3 bucket for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include "log_backup_2_0" --include "log_backup_3_0" --recursive --region us-east-1 + aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ s3://<S3 bucket>/<S3 bucket for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include "log_backup_2_0" --include "log_backup_3_0" --recursive --region <us-east-1> @@ -455 +455 @@ Run the following commands to move the volume type TENANT DB logs. In the exampl - aws s3 ls s3://<S3 bucket>/<S3 bucket for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --region us-east-1 + aws s3 ls s3://<S3 bucket>/<S3 bucket for logs>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --region <us-east-1> @@ -470 +470 @@ Run the following commands to move the volume type TENANT DB logs. In the exampl - 3. Create a `hdbbackint` soft link from `/usr/sap/`<SID>`/SYS/global/hdb/opt/hdbconfig/` to `/hana/shared/aws-backint-agent/`. + 3. Create a `hdbbackint` soft link from `/usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig/` to `/hana/shared/aws-backint-agent/`. @@ -495 +495 @@ After a successful validation, we recommend waiting for at least a week before d -When you're ready, delete the previous logs with the following commands. +When you’re ready, delete the previous logs with the following commands. @@ -498,2 +498,2 @@ When you're ready, delete the previous logs with the following commands. - aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "" --include "log_backup_1_0" --recursive --dryrun --region us-east-1 - aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "" --include "log_backup_1_0" --recursive --region us-east-1 + aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "" --include "log_backup_1_0" --recursive --dryrun --region <us-east-1> + aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "" --include "log_backup_1_0" --recursive --region <us-east-1> @@ -502,2 +502,2 @@ When you're ready, delete the previous logs with the following commands. - aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include --include "log_backup_2_0" --include "log_backup_3_0" --recursive --dryrun --region us-east-1 - aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include "log_backup_2_0" --include "log_backup_3_0" --recursive --region us-east-1 + aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include --include "log_backup_2_0" --include "log_backup_3_0" --recursive --dryrun --region <us-east-1> + aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include "log_backup_2_0" --include "log_backup_3_0" --recursive --region <us-east-1> @@ -521 +521 @@ To use a different Amazon S3 bucket and folder for catalog backup, follow these -Locate the `data_backup_parameter_file`, `log_backup_parameter_file`, and `catalog_backup_parameter_file` parameters. The default value of these parameters should be `/`<installation directory>`/aws-backint-agent/aws-backint-agent-config.yaml`. If you do not see this default value, check the configuration file to confirm that it is displaying the same Amazon S3 location. +Locate the `data_backup_parameter_file`, `log_backup_parameter_file`, and `catalog_backup_parameter_file` parameters. The default value of these parameters should be `/<installation directory>/aws-backint-agent/aws-backint-agent-config.yaml`. If you do not see this default value, check the configuration file to confirm that it is displaying the same Amazon S3 location. @@ -531 +531 @@ Move the previous catalog backup with source type `catalog` to the new Amazon S3 -The backup catalog is assigned a name in the following format: `log_backup_0_0_0_0.`<BackupID>``. This type of backup has a source type `catalog`. This file contains the backup catalog file that stores the history of all backups. Only the catalog backups with source type `catalog` should be moved to the new Amazon S3 location. To change the Amazon S3 location for log backup, see Configure SAP HANA to use a different Amazon S3 bucket and folder for data and log backup. +The backup catalog is assigned a name in the following format: `log_backup_0_0_0_0.<BackupID>`. This type of backup has a source type `catalog`. This file contains the backup catalog file that stores the history of all backups. Only the catalog backups with source type `catalog` should be moved to the new Amazon S3 location. To change the Amazon S3 location for log backup, see Configure SAP HANA to use a different Amazon S3 bucket and folder for data and log backup. @@ -540 +540 @@ log_backup_0_0_0_0/ | Log file with source type "catalog" -log_backup_1_0_`<backup ID>`_`<backup ID>` | Log file with source type "volume" +log_backup_1_0_<backup ID>_<backup ID> | Log file with source type "volume" @@ -550,2 +550,2 @@ log_backup_0_0_0_0/ | Log file with source type "catalog" -log_backup_2_0_`<backup ID>`_`<backup ID>` | Log file with source type "volume" -log_backup_3_0_`<backup ID>`_`<backup ID>` | Log file with source type "volume" +log_backup_2_0_<backup ID>_<backup ID> | Log file with source type "volume" +log_backup_3_0_<backup ID>_<backup ID> | Log file with source type "volume" @@ -562 +562 @@ Run the following commands to move the `catalog` type of SYSTEM DB logs. In the - aws s3api put-object --bucket <S3 bucket> --key <S3 folder for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --region us-east-1 + aws s3api put-object --bucket <S3 bucket> --key S3 folder for catalog/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --region <us-east-1> @@ -565 +565 @@ Run the following commands to move the `catalog` type of SYSTEM DB logs. In the - aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ s3://<S3 bucket>/<S3 folder for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "*" --include "log_backup_0_0_0_0*" --recursive --dryrun --region us-east-1 + aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ s3://<S3 bucket>/<S3 folder for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "*" --include "log_backup_0_0_0_0*" --recursive --dryrun --region <us-east-1> @@ -568 +568 @@ Run the following commands to move the `catalog` type of SYSTEM DB logs. In the - aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ s3://<S3 bucket>/<S3 folder for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "*" --include "log_backup_0_0_0_0*" --recursive --region us-east-1 + aws s3 cp s3://example-s3-bucket;/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ s3://<S3 bucket>/<S3 folder for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "*" --include "log_backup_0_0_0_0*" --recursive --region <us-east-1> @@ -571 +571 @@ Run the following commands to move the `catalog` type of SYSTEM DB logs. In the - aws s3 ls s3://<S3 bucket>/<S3 folder for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --region us-east-1 + aws s3 ls s3://<S3 bucket>/<S3 folder for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --region <us-east-1> @@ -578 +578 @@ Run the following commands to move the `catalog` type tenant database logs. In t - aws s3api put-object --bucket <S3 bucket> --key <S3 folder for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --region us-east-1 + aws s3api put-object --bucket <S3 bucket> --key S3 folder for catalog/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --region <us-east-1> @@ -581 +581 @@ Run the following commands to move the `catalog` type tenant database logs. In t - aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ s3://<S3 bucket>/<S3 bucket for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include "log_backup_0_0_0_0*" --recursive --dryrun --region us-east-1 + aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ s3://<S3 bucket>/<S3 bucket for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include "log_backup_0_0_0_0*" --recursive --dryrun --region <us-east-1> @@ -584 +584 @@ Run the following commands to move the `catalog` type tenant database logs. In t - aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ s3://<S3 bucket>/<S3 bucket for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include "log_backup_0_0_0_0*" --recursive --region us-east-1 + aws s3 cp s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ s3://<S3 bucket>/<S3 bucket for catalog>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/DB_<SID>/ --exclude "" --include "log_backup_0_0_0_0*" --recursive --region <us-east-1> @@ -588 +588 @@ Run the following commands to move the `catalog` type tenant database logs. In t - 3. **Create the`aws-backint-agent-config-catalog.yaml` parameter file** + 3. Create the ` **aws-backint-agent-config-catalog.yaml** ` parameter file @@ -597,2 +597,2 @@ Run the following commands to move the `catalog` type tenant database logs. In t - S3BucketName: "<Amazon S3 bucket for SAP HANA catalog>" - S3BucketFolder: "<Amazon S3 folder for SAP HANA catalog>" + S3BucketName: "Amazon S3 bucket for SAP HANA catalog" + S3BucketFolder: "Amazon S3 folder for SAP HANA catalog" @@ -601 +601 @@ Run the following commands to move the `catalog` type tenant database logs. In t - 3. Create a `hdbbackint` soft link from `/usr/sap/`<SID>`/SYS/global/hdb/opt/hdbconfig/` to `/hana/shared/aws-backint-agent/`. + 3. Create a `hdbbackint` soft link from `/usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig/` to `/hana/shared/aws-backint-agent/`. @@ -606 +606 @@ Run the following commands to move the `catalog` type tenant database logs. In t - 4. **Update the`global.ini` file** + 4. Update the ` **global.ini** ` file @@ -612 +612 @@ Update the `global.ini` file with the following configuration. - 5. **Run reconfiguration for the update** + 5. Run reconfiguration for the update @@ -616 +616 @@ Run `hdbnsutil -reconfig` for the update to take effect. - 6. **Validate to ensure that all steps have been processed correctly** + 6. Validate to ensure that all steps have been processed correctly @@ -622 +622 @@ Run `hdbnsutil -reconfig` for the update to take effect. - 7. **Delete previous backups** + 7. Delete previous backups @@ -626 +626 @@ After a successful validation, we recommend waiting for at least a week before d -When you're ready, delete the previous logs with the following commands. +When you’re ready, delete the previous logs with the following commands. @@ -629,2 +629,2 @@ When you're ready, delete the previous logs with the following commands. - aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "" --include "log_backup_0_0_0_0" --recursive --dryrun --region us-east-1 - aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "" --include "log_backup_0_0_0_0" --recursive --region us-east-1 + aws s3 rm s3://<S3 bucket>/<S3 folder>/<SID>/usr/sap/<SID>/SYS/global/hdb/backint/SYSTEMDB/ --exclude "" --include "log_backup_0_0_0_0" --recursive --dryrun --region <us-east-1>