The config file gives the login details for Netapp appliances/SVMs and Postgres databases and a list of "targets",.Provide a config file - see example-config.yaml in the repo root for details on how this must be formatted and what.In a nutshell, we could not get it to work reliably.īut then, Netapp released OnTap 9.6 which brings with it a REST API.Postgres is a "community supported" plugin which uses shell script, embedded in Perl, called from Java, called from a server.you can't use Ansible, Salt or any other config management platform to deploy easily, you're meant to do it through their UI.extra firewall holes are required for the agent.the plugin installation and running has trouble with selinux.Unfortunately we have had a lot of problems: Individual databases are supported by plugins which sit in a Java agent that needs installing on the database box. Netapp offer a product which can do this process for a whole range of databases and present a nice UI along with it. This is a simple app to manage this process SnapCenter | Set db restore point | -> | Perform snapshot | -> | Tell database that backup is complete | (see the Postgres documentation for many, many, more details on this). When an instance is brought up from the snapshot it discards data from after the "restore point"Īs potentially corrupt and attempts to replay as much as possible from any source of write-ahead logs available prevented fromįortunately, Postgres is clever about this it does not need to be prevented from writing but it does need to create a for us toīe able to actually restart a b0rked system from the snapshot) the app in question must be "quiesced" i.e. Under normal circumstances for this to work (i.e. Of course, the problem is that the database is still writing. We can tell the Netapp to preserve the current storage blocks as a "snapshot" - no data is copied, only locked, so this In our Multimedia system the database is over 600G and this becomes so problematic as to make the backup almost useless.įortunately, Netapp has a much better solution - snapshotting. It takes ages, needs loads of disk, and takes even longer to replay.
Traditionally you run pg_dump (or equivalent) to make a huge SQL file that can be replayed,Īnd compress it. Backup app for Postgres databases using NetApp backed storage Why? What does it do?ĭatabase backups are a pain.
0 kommentar(er)
