<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi everyone.</p>
<p>In doing some dev testing and by definition testing our disaster
recovery plan, I've run into a bit of a roadblock in how backups
are done for Freeside.</p>
<p>I need to be able to move the whole configuration of Freeside to
a dev server, while not moving any of the customer data - no
invoices, trouble tickets or the like. I want to do some testing
on single new customer as if it were all of our customers.</p>
<p>Such a backup procedure is also potentially useful in the case
where someone accidentally breaks some backend configuration - a
billing event definition for example - and needs it to be restored
from backups, while leaving the customer information alone. Nobody
wants to have to re-issue and re-send all the invoices that were
done this morning, and re-create the customer accounts from two
hours ago in a use case like this. <br>
<br>
What Postgres tables should I be dumping to save backups of
"everything but customer data"?<br>
</p>
</body>
</html>