Jira DOC-703: Update Database backup to reflect start time and updated directions. #1548

lanceleonard · 2021-09-28T03:11:13Z

Initial draft

Merge branch 'master' into jira-doc-703

lanceleonard · 2021-09-28T03:26:03Z

A staged preview is available.

rrelledge

Looks good. I left some suggestions for possible typos.

rrelledge · 2021-09-28T14:01:18Z

content/rs/administering/import-export/database-backup.md

+Periodic backups provide a way to restore data with minimal data loss.  With Redis Enterprise Software, you can schedule periodic backups to occur every once a day (every 24 hours), twice a day (every twelve hours), every four hours, or every hour.
+
+As of v6.2.8, you can specify the start time for twenty four or twelve hour backups.


Suggested change

Periodic backups provide a way to restore data with minimal data loss. With Redis Enterprise Software, you can schedule periodic backups to occur every once a day (every 24 hours), twice a day (every twelve hours), every four hours, or every hour.

As of v6.2.8, you can specify the start time for twenty four or twelve hour backups.

Periodic backups provide a way to restore data with minimal data loss. With Redis Enterprise Software, you can schedule periodic backups to occur once a day (every 24 hours), twice a day (every 12 hours), every four hours, or every hour.

As of v6.2.8, you can specify the start time for 24- or 12-hour backups.

Fixed to match intention.

rrelledge · 2021-09-28T14:08:26Z

content/rs/administering/import-export/database-backup.md

+    |--------------|-------------|
+    | **Interval** | Specifies the frequency of the backup; that is, the time between each backup snapshot.<br/><br/>Supported values include _Every 24 hours_, _Every 12 hours_, _Every 4 hours_, and _Every hour_. |
+    | **Set starting time** | _v6.2.8 or later:&nbsp;_ Specifies the start time for the backup; available when **Interval** is set to _Every 24 hours_ or _Every 12 hours_.<br/><br/>If not specified, defaults to a time selected by Redis Enterprise Software. |
+    | **Choose storage type** | Specifies the storage type for the backup.  Supported options vary and might require additional details.  To learn more, see [Supported storage types](#supported-storage-types).


Mismatched anchor

Suggested change

| **Choose storage type** | Specifies the storage type for the backup. Supported options vary and might require additional details. To learn more, see [Supported storage types](#supported-storage-types).

| **Choose storage type** | Specifies the storage type for the backup. Supported options vary and might require additional details. To learn more, see [Supported storage locations](#supported-storage-locations).

rrelledge · 2021-09-28T14:11:28Z

content/rs/administering/import-export/database-backup.md

+
+## Default backup start time
+
+If you do _not_ specify a start time for twenty four or twelve hour backups, Redis Enterprise Software chooses one for you, based on the time the backups are enabled.


Suggested change

If you do _not_ specify a start time for twenty four or twelve hour backups, Redis Enterprise Software chooses one for you, based on the time the backups are enabled.

If you do _not_ specify a start time for 24- or 12-hour backups, Redis Enterprise Software chooses one for you, based on the time the backups are enabled.

Fixed to intention

rrelledge · 2021-09-28T14:11:51Z

content/rs/administering/import-export/database-backup.md

+- You choose to back up your database every 12 hours.
+- Because you didn't set a start time, the cluster randomly chooses an offset of 4,320 seconds (or 72 minutes).
+
+This means your first periodic backup will run roughly around 5:12 pm (72 minutes after the time you enabled backups) and repeats every twelve hours at about that same time.


Suggested change

This means your first periodic backup will run roughly around 5:12 pm (72 minutes after the time you enabled backups) and repeats every twelve hours at about that same time.

This means your first periodic backup will run roughly around 5:12 pm (72 minutes after the time you enabled backups) and repeats every 12 hours at about that same time.

rrelledge · 2021-09-28T14:16:58Z

content/rs/administering/import-export/database-backup.md

+To backup to an SFTP server, enter the SFTP server location in the format:
+
+```sh
+sftp://user:password@host:<:custom_port>/path/


Suggested change

sftp://user:password@host:<:custom_port>/path/

sftp://user:password@host:<custom_port>/path/

Fixed-ish. (There should only be one colon).

rrelledge · 2021-09-28T14:21:02Z

content/rs/administering/import-export/database-backup.md

+
+1.  Use the Buckets list to locate and select your bucket.  When the settings appear, select the **Permissions** tab, locate the **Access control list (ACL)** section, and then select the **Edit** button.
+
+1.  When the **Edit access control list (ACL)** screen appears, locate the Access for other AWS accounts section and then select the **Add grantee** button.


Suggested change

1. When the **Edit access control list (ACL)** screen appears, locate the Access for other AWS accounts section and then select the **Add grantee** button.

1. When the **Edit access control list (ACL)** screen appears, locate the **Access for other AWS accounts** section and then select the **Add grantee** button.

rrelledge · 2021-09-28T14:26:54Z

content/rs/administering/import-export/database-backup.md

+
+1.  When the **Edit access control list (ACL)** screen appears, locate the Access for other AWS accounts section and then select the **Add grantee** button.
+
+    1.  In the **Grantee** field, enter:


Suggested change

1. In the **Grantee** field, enter:

1. In the **Grantee** field, enter the AWS account ID:

rrelledge · 2021-09-28T14:27:57Z

content/rs/administering/import-export/database-backup.md

+    1.  In the **Bucket ACL** list, enable **Read** and **Write**.
+    1.  When finished, select the **Save changes** button.
+
+Once the bucket is available and the permissions are set, use the name of your bucket as the **Backup destination** for your database's Remote backup settings. For example, suppose your bucket is named *backups-bucket*.  In that case, set **Backup destination** to `s3://backups-bucket`.


Suggested change

Once the bucket is available and the permissions are set, use the name of your bucket as the **Backup destination** for your database's Remote backup settings. For example, suppose your bucket is named *backups-bucket*. In that case, set **Backup destination** to `s3://backups-bucket`.

Once the bucket is available and the permissions are set, use the name of your bucket as the **Backup destination** for your database's **Remote backup settings**. For example, suppose your bucket is named *backups-bucket*. In that case, set **Backup destination** to `s3://backups-bucket`.

rrelledge · 2021-09-28T14:28:36Z

content/rs/administering/import-export/database-backup.md

+
+1. Sign in to Google Cloud Platform console.
+
+1. In the admin console menu, locate the _Storage_ section than select **Cloud Storage&nbsp;>&nbsp;Browser**.


Suggested change

1. In the admin console menu, locate the _Storage_ section than select **Cloud Storage > Browser**.

1. In the admin console menu, locate the _Storage_ section then select **Cloud Storage > Browser**.

rrelledge · 2021-09-28T14:34:27Z

content/rs/administering/import-export/database-backup.md

+
+The syntax for creating the backup varies according to your authorization mechanism.  For example:
+
+`abs://:storage_account_access_key@storage_account_name/container_name/[path/]`


Suggested change

`abs://:storage_account_access_key@storage_account_name/container_name/[path/]`

`abs://storage_account_access_key@storage_account_name/container_name/[path/]`

* Added more detail to rladmin verify commands (#1550) * Jira DOC-703: Update Database backup to reflect start time and updated directions. (#1548) * First steps; not yet ready for review. * Initial draft * Adding default start time discussion. * Minor tweaks and edits. * Moar fixes * Jira DOC-769: Update TLS support statement for TLS. (#1554) * Initial draft * Adding statement to Supported OS article. * Tweaks and fixes * Jira DOC-929: Add additional details about the upgrade policy to the upgrade doc. (#1599) * Initial draft * Promoting section. * Incoporating editorial feedback. * Jira DOC-939: RS - Align Export data article to Back up data article (#1598) * Initial draft * Editorial feedback. * Jira DOC-857: RS - v6.2.8 Release notes (#1628) * Added public read parameter to automated deployment of robots.txt (#1622) * Initial draft * Editorial fixes/tweaks * More fixes/tweaks * Jira DOC-564: RS - Clarify how to enable public/private IP support (#1611) * Initial draft. * Editorial feedback/tweaks. * Fixing typo. * More updates/tweaks. * Allow HTML encoding in table-children column names (#1629) * Jira DOC-196: Modules: document enterprise capability support (#1504) * Initial draft * Tweaks and fixes * Editorial feedback. * More editorial feedback. * More editorial changes. * More fixes/updates * Updating limitations. Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com>

lanceleonard added 3 commits September 22, 2021 12:59

First steps; not yet ready for review.

08c5f17

Updating to latest master

a5cbbfa

Merge branch 'master' into jira-doc-703

Initial draft

7480a32

lanceleonard requested review from adisht, kaitlynmichael and rrelledge September 28, 2021 03:11

lanceleonard self-assigned this Sep 28, 2021

lanceleonard added the p_Software label Sep 28, 2021

lanceleonard added 2 commits September 27, 2021 20:49

Adding default start time discussion.

d9dae27

Minor tweaks and edits.

5394ac2

rrelledge approved these changes Sep 28, 2021

View reviewed changes

Moar fixes

c152cf0

kaitlynmichael approved these changes Sep 29, 2021

View reviewed changes

lanceleonard merged commit ca81cdc into release-rs-6-2-8 Sep 30, 2021

lanceleonard deleted the jira-doc-703 branch September 30, 2021 22:10

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Jira DOC-703: Update Database backup to reflect start time and updated directions. #1548

Jira DOC-703: Update Database backup to reflect start time and updated directions. #1548

lanceleonard commented Sep 28, 2021

lanceleonard commented Sep 28, 2021

rrelledge left a comment

rrelledge Sep 28, 2021

lanceleonard Sep 28, 2021 •

edited

Loading

rrelledge Sep 28, 2021

lanceleonard Sep 28, 2021

rrelledge Sep 28, 2021

lanceleonard Sep 28, 2021

rrelledge Sep 28, 2021

lanceleonard Sep 28, 2021

rrelledge Sep 28, 2021

lanceleonard Sep 28, 2021

rrelledge Sep 28, 2021

lanceleonard Sep 28, 2021

rrelledge Sep 28, 2021

lanceleonard Sep 28, 2021

rrelledge Sep 28, 2021

lanceleonard Sep 28, 2021

rrelledge Sep 28, 2021

lanceleonard Sep 28, 2021

rrelledge Sep 28, 2021

lanceleonard Sep 28, 2021

		Periodic backups provide a way to restore data with minimal data loss. With Redis Enterprise Software, you can schedule periodic backups to occur every once a day (every 24 hours), twice a day (every twelve hours), every four hours, or every hour.

		As of v6.2.8, you can specify the start time for twenty four or twelve hour backups.

	\| Choose storage type \| Specifies the storage type for the backup. Supported options vary and might require additional details. To learn more, see [Supported storage types](#supported-storage-types).
	\| Choose storage type \| Specifies the storage type for the backup. Supported options vary and might require additional details. To learn more, see [Supported storage locations](#supported-storage-locations).


		## Default backup start time

		If you do _not_ specify a start time for twenty four or twelve hour backups, Redis Enterprise Software chooses one for you, based on the time the backups are enabled.

	This means your first periodic backup will run roughly around 5:12 pm (72 minutes after the time you enabled backups) and repeats every twelve hours at about that same time.
	This means your first periodic backup will run roughly around 5:12 pm (72 minutes after the time you enabled backups) and repeats every 12 hours at about that same time.

	sftp://user:password@host:<:custom_port>/path/
	sftp://user:password@host:<custom_port>/path/


		1. Use the Buckets list to locate and select your bucket. When the settings appear, select the Permissions tab, locate the Access control list (ACL) section, and then select the Edit button.

		1. When the Edit access control list (ACL) screen appears, locate the Access for other AWS accounts section and then select the Add grantee button.


		1. When the Edit access control list (ACL) screen appears, locate the Access for other AWS accounts section and then select the Add grantee button.

		1. In the Grantee field, enter:

	1. In the Grantee field, enter:
	1. In the Grantee field, enter the AWS account ID:

	Once the bucket is available and the permissions are set, use the name of your bucket as the Backup destination for your database's Remote backup settings. For example, suppose your bucket is named backups-bucket. In that case, set Backup destination to `s3://backups-bucket`.
	Once the bucket is available and the permissions are set, use the name of your bucket as the Backup destination for your database's Remote backup settings. For example, suppose your bucket is named backups-bucket. In that case, set Backup destination to `s3://backups-bucket`.


		1. Sign in to Google Cloud Platform console.

		1. In the admin console menu, locate the _Storage_ section than select Cloud Storage > Browser.


		The syntax for creating the backup varies according to your authorization mechanism. For example:

		`abs://:storage_account_access_key@storage_account_name/container_name/[path/]`

	`abs://:storage_account_access_key@storage_account_name/container_name/[path/]`
	`abs://storage_account_access_key@storage_account_name/container_name/[path/]`

Jira DOC-703: Update Database backup to reflect start time and updated directions. #1548

Jira DOC-703: Update Database backup to reflect start time and updated directions. #1548

Conversation

lanceleonard commented Sep 28, 2021

lanceleonard commented Sep 28, 2021

rrelledge left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

lanceleonard Sep 28, 2021 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

lanceleonard Sep 28, 2021 •

edited

Loading