On Wed, Oct 3, 2012 at 1:42 PM, Bill Meek <span dir="ltr"><<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 10/03/2012 10:12 AM, Jim Oltman wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm reading the Release Notes for 0.26, and while I will wait a while to<br>
upgrade, I am curious about the DB backup procedure. The notes say to run:<br>
<br>
/usr/share/mythtv/<a href="http://mythconverg_backup.pl" target="_blank">mythconverg_<u></u>backup.pl</a><br>
<br>
as the user that will be performing the upgrade.<br>
</blockquote></div>
...<br>
<br>
Hi;<br>
<br>
Truth be told, the original reason for adding that was my<br>
misunderstanding that the upgrade process would use the<br>
backuprc file of the user running mythbackend (probably<br>
mythtv) or mythtv-setup (probably $USER.)<br>
<br>
It turns out the configuration file is created 'on the fly' so my<br>
reason is wrong. The 1st choice for the backup directory is from<br>
the 'DB Backups' storage group (with 'Default' next followed by<br>
/tmp.)<br>
<br>
So, if the directory in 'DB Backups' matches the DBBackupDirectory<br>
entry in backuprc (mine does,) then the test is a good one, if only<br>
to test write permissions. I understand that writing to /tmp isn't<br>
likely to fail, but a backup there would be erased if someone<br>
boots before realizing they need the file.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Bill</font></span></blockquote><div><br></div><div>That's where my backups are dumping to. The DB Backups Storage Group. </div></div>