[mythtv-commits] Ticket #13471: mythconverg_backup should skip recordedseek table to avoid breaking recordings.

[MythTV]

#13471: mythconverg_backup should skip recordedseek table to avoid breaking
recordings.
----------------------------------------+-----------------------------
 Reporter:  wispfrog                    |          Owner:  sphery
     Type:  Bug Report - General        |         Status:  closed
 Priority:  minor                       |      Milestone:  30.0
Component:  Contributed Scripts & Apps  |        Version:  Unspecified
 Severity:  medium                      |     Resolution:  Won't Fix
 Keywords:                              |  Ticket locked:  0
----------------------------------------+-----------------------------
Changes (by sphery):

 * owner:  (none) => sphery
 * resolution:   => Won't Fix
 * status:  new => closed
 * component:  MythTV - General => Contributed Scripts & Apps
 * milestone:  needs_triage => 30.0


Comment:

 The mythconverg_backup.pl script is meant to be used as a general-purpose
 backup script for the MythTV database.  It is often used to backup a
 database before transferring it to a newly-built system or before
 restoring it to a system that's upgraded to a new OS version, not just for
 last-ditch, "I lost everything but am prepared for days of rebuilding
 work" scenarios.  Therefore it is designed to get as much of the
 information as possible from the existing database.

 Note, too, that any backup of the MythTV system should be performed when
 the MythTV system is shut down (all backends, all frontends, and all other
 clients), and performing backups while anything is modifying the database
 are highly discouraged (and the end result is suspect).  Users performing
 backups while the system is running should, at minimum, do their best to
 schedule the backup when the MythTV system is as idle as possible (not
 recording and, as much as possible, not modifying anything in the
 database).

 If you want to skip the recordedseek table backup on your system's
 backups, you may do so by specifying the --ignore-table option in a MySQL
 Option File--ideally one that's only used for that backup run, but at
 most, in a user-specific options file.  See
 https://dev.mysql.com/doc/refman/5.7/en/mysqldump.html#mysqldump-option-
 summary and https://dev.mysql.com/doc/refman/5.7/en/option-files.html for
 more details.

-- 
Ticket URL: <https://code.mythtv.org/trac/ticket/13471#comment:1>
MythTV <http://www.mythtv.org>
MythTV Media Center