Skip to content

Commit 29b1ced

Browse files
authored
Merge pull request #1735 from dehawkins512/dan_1102
Remove scheduling of database backups from documentation
2 parents d246320 + 5a9ffa5 commit 29b1ced

File tree

1 file changed

+1
-92
lines changed

1 file changed

+1
-92
lines changed

general_configuration/_topics/configuration.md

Lines changed: 1 addition & 92 deletions
Original file line numberDiff line numberDiff line change
@@ -1469,7 +1469,7 @@ Table: workers
14691469

14701470
#### Schedules
14711471

1472-
##### Scheduling SmartState Analyses and Backups
1472+
##### Scheduling SmartState Analyses
14731473

14741474
From the **Schedules** area in **Settings**, you can schedule the
14751475
analyses of virtual machines, hosts, clusters, and datastores to keep
@@ -1537,8 +1537,6 @@ To schedule a SmartState Analysis or Compliance Check:
15371537
**All Hosts for Cluster**, **A single Host**, or **Global Filters**.
15381538

15391539
- **Database Backup**: Under **Type**, displays **Network File System**, **Samba**, **Amazon AWS S3** and **OpenStack Swift**..
1540-
See [Scheduling a Database Backup](#database_backup) for details
1541-
on scheduling a database backup.
15421540

15431541
7. By applying **Global Filters** within any of the above items, you
15441542
can designate which virtual machines or hosts to analyze.
@@ -1568,93 +1566,6 @@ To schedule a SmartState Analysis or Compliance Check:
15681566

15691567
12. Click **Add**.
15701568

1571-
##### Scheduling a Database Backup
1572-
1573-
**Note:**
1574-
1575-
Set `wal_keep_segments` parameter to a value that ensures
1576-
{{ site.data.product.title_short }} scheduled backups finish. Create a test backup
1577-
using a value based on the calculation:
1578-
1579-
**(\<pg-volume-free-space\>MB/4)/16MB**.
1580-
1581-
Measure free space in MB and ensure the denominator matches in units.
1582-
1583-
Setting `wal_keep_segments` to this value will cause the transaction log
1584-
to occupy, at a minimum, one quarter of the current free space. Adjust
1585-
your calculation accordingly upon successful testing.
1586-
1587-
To set the `wal_keep_segments` value:
1588-
1589-
1. SSH to the database appliance
1590-
1591-
2. Access the database
1592-
1593-
# psql DBNAME USERNAME
1594-
1595-
3. Set the `wal_keep_segments` value
1596-
1597-
postgres=# ALTER SYSTEM SET wal_keep_segments = <value>;
1598-
1599-
4. Reload `wal_keep_segments`
1600-
1601-
postgres=# SELECT pg_reload_conf();
1602-
1603-
On successful backup, revise the value for `wal_keep_segments` to save
1604-
space based on transaction log size.
1605-
1606-
To schedule a database backup:
1607-
1608-
1. Browse to **Settings** > **Application Settings**.
1609-
1610-
2. Click on the **Settings** accordion, then click **Schedules**.
1611-
1612-
3. Click ![1847](../images/1847.png) (**Configuration**), and ![plus
1613-
green](../images/plus_green.png)(**Add a new Schedule**).
1614-
1615-
4. In the **Basic Information** area, type in a **Name** and
1616-
**Description** for the schedule. ![2082](../images/2082.png)
1617-
1618-
5. Select **Active** to enable this backup schedule.
1619-
1620-
6. From the **Action** list, select **Database backup**.
1621-
1622-
7. In the **Database Backup Settings** area, select a type of server to
1623-
put the backups. You can either use **Network File System** or
1624-
**Samba**.
1625-
1626-
- If selecting **Samba**, enter the **Depot Name**, **URI**,
1627-
**User ID**, and a valid **Password**. Then, click **Validate**
1628-
to check the settings.
1629-
1630-
- If you choose **Network File System**, enter the **Depot Name**
1631-
and **URI**.
1632-
1633-
8. In **Run**, set the frequency of the analysis to run. There are
1634-
further options based on which **Run** option you choose.
1635-
1636-
- Click **Once** to have the backup run only one time.
1637-
1638-
- Click **Daily** to run the backup on a daily basis. You will be
1639-
prompted to select the number of days between each backup.
1640-
1641-
- Click **Hourly** to run the backup hourly. You will be prompted
1642-
to select the number of hours between each backup.
1643-
1644-
9. Select a **Time Zone**.
1645-
1646-
**Note:**
1647-
1648-
If you change the **Time Zone**, you will need to reset the stating
1649-
date and time.
1650-
1651-
10. Type or select a date to begin the schedule in **Starting Date**.
1652-
1653-
11. Select a **Starting Time** (UTC) based on a 24 hour clock in the
1654-
selected time zone.
1655-
1656-
12. Click **Add**.
1657-
16581569
###### Modifying a Schedule
16591570

16601571
To modify a schedule:
@@ -1709,8 +1620,6 @@ schedules, including:
17091620

17101621
- SmartState Analysis
17111622

1712-
- Database Backup
1713-
17141623
- Automation Task
17151624

17161625
- Service Template

0 commit comments

Comments
 (0)