Book Image

Plone 3.3 Site Administration

Book Image

Plone 3.3 Site Administration

Overview of this book

In the past few years, we have seen some dramatic changes in the way Plone sites are being developed, deployed, and maintained. As a result, developing and deploying sites, changing their default settings, and performing day to day maintenance tasks can be a challenge. This book covers site administration tasks, from setting up a development instance, to optimizing a deployed production site, and more. It demonstrates how-to perform these tasks in a comprehensive way, and walks the user through the necessary steps to achieve results.We have divided the subject of Plone site administration into three categories: development, deployment, and maintenance. We begin by explaining how a Plone site is built, and how to start using it through the web. Next, we add features by installing add-on products, focusing on themes, blogging, and other common enhancements. After the basics of developing and deploying a Plone site are covered, the book covers the basics of maintaining it.Further, throughout the book we preview some new technologies related to Plone site administration, available now as add-ons to the current Plone release. Finally, we will cover a variety of techniques to help you optimize your site's performance.
Table of Contents (15 chapters)
Plone 3.3 Site Administration
Credits
Foreword
About the Author
About the Reviewer
Preface
Index

Restoring your database from a backup


If you want to restore your database from the latest backup, you can stop your site (including ZEO) and run:

$ bin/restore

In the event that you would like to know more about the process, or you would like to restore from a date prior to the last backup, you can always use the repozo command.

Assuming you have the backups, you can restore the data from any date by using the -D option:

% bin/repozo -R -D 2009-10-26-00-06-33 -r var/backups -o var/filestorage/Data.fs

You must give -D a date string that matches one of your backups. It can be an incremental backup (that is, a file ending in .deltafs); repozo will figure out what to do with it.