You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,11 @@ It is not recommended to classify using a pre-existing node group in the PE Cons
48
48
49
49
### Backup Schedule
50
50
51
+
> WARNING: The backup functionality in this module has been deprecated and will be removed in a future release.
52
+
Please refer to the [PE Backup and Restore documentation](https://puppet.com/docs/pe/latest/backing_up_and_restoring_pe.html) for details on how to backup.
53
+
You should ensure the parameter `pe_databases::manage_database_backups` and any parameters from the `pe_databases::backup` class are removed from classification or hiera.
54
+
You should also clean up associated crontab entries.
55
+
51
56
Backups are not activated by default but can be enabled by setting the following parameter:
52
57
53
58
Hiera classification example
@@ -90,6 +95,11 @@ Those defaults change based on the `$all_in_one_pe` parameter.
90
95
91
96
## Backups
92
97
98
+
> WARNING: The backup functionality in this module has been deprecated and will be removed in a future release.
99
+
Please refer to the [PE Backup and Restore documentation](https://puppet.com/docs/pe/latest/backing_up_and_restoring_pe.html) for details on how to backup.
100
+
You should ensure the parameter `pe_databases::manage_database_backups` and any parameters from the `pe_databases::backup` class are removed from classification or hiera.
101
+
You should also clean up associated crontab entries.
102
+
93
103
This is the documentation for Pupet Enterprise backups:
0 commit comments