In Part I of the series, we introduced PostgreSQL as a viable Enterprise Geodatabase alternative. When we left off, we had a connection to an ArcGIS 10.2.1 database, and were able to create a feature class. In Part II, we continued to discuss the use of PostgreSQL for ArcGIS by adding a schema owner to receive and own feature datasets (plus contents). And lastly, we created permission roles and assign users to those roles. In this Post, we address a backup/restoration procedure.