-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathexample-config.yaml
More file actions
34 lines (30 loc) · 2.09 KB
/
Copy pathexample-config.yaml
File metadata and controls
34 lines (30 loc) · 2.09 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
#The Netapp section contains details of each netapp SVM that hosts a volume that you need to back up
netapp:
- host: netapp.company.int #the hostname of the netapp that is accessed. This must be OnTap 9.6+ and host the REST API over https.
user: snapshotuser #the username of a user that is allowed to create and list snapshots.
password: userpassword #password for the above user
svm: svm_nfs #svm that hosts the volumes
name: simulator-nfs #user-provided name label that is used to reference this in "targets" below
#The Databases section contains details of each Postgres database that uses the volumes to be backed up.
#These need to be put into a consistent state (aka 'quiesced') before the snapshot can take place
databases:
- name: databse1 #user-provided label that is used to reference this in "targets" below
host: localhost #hostname where the database can be accessed
port: 5432 #port where the database can be accessed on `hostname`
default_db: postgres #default db to log in to, this is needed even though we don;t actually do ops on it
user: replication-user #username to log in as. This must be a superuser or "replication" user in order to carry out pg_start_backup/pg_stop_backup
password: password #password for the user
ssl_mode: require #can be 'require', 'disable', 'verify-ca', 'verify-all'
targets:
- database: databse1 #The database to back up. This field must correspond to the Name: field of one entry in Databases
netapp: simulator-nfs #The Netapp SVM containing the volume that needs backing up. This field must correspond to the Name: field of one entry in Databases
volumeid: 26894980-70ca-47d3-a67f-fdc6a994e7c5 #UUID of the volume that needs to be snapshotted
smtp:
smtpserver: mx.mycompany.com:25
mailfrom: SmartBackup <smartbackup@gnm.int>
sendonsuccess: true
mailto:
- someadmin@mycompany.com
- someotheradmin@mycompany.com
pagerduty:
service_key: pagerduty-service-key