how does one disable the backing up of Log Records during the backup process? In the code I traced the items to be backed up to a single class object but I am not sure which one is responsible for the Log Records.
{
MT->model('config') => 1,
MT->model('session') => 1,
MT->model('ts_job') => 1,
MT->model('ts_error') => 1,
MT->model('ts_exitstatus') => 1,
MT->model('ts_funcmap') => 1,
},
{
MT->model('placement') => 1,
MT->model('ping') => 1,
MT->model('objecttag') => 1,
MT->model('objectasset') => 1,
MT->model('objectscore') => 1,
So I am migrating blogs around using the archived packages the backup system creates but am forced to wait 30 minutes to over 3 hours in one case for the blog to backup. Each time they are hanging on the Log Records.
This blog here has 1 post in it.
Backing up MT::Log records: 136500 records backed up...
136500 for one post blog... How do I stop this portion of the backup from occurring? I have truncated the mt_log table down to just this month's traffic.
Any advice will be greatly appreciated!
Reported on Movable Type 4.1x
On further inspection the backup process is backing up the entire mt_log table... So for moving blogs around that table will move every time... This will need to be disabled.
I've checked, and the latest version (5.13) backup only the relevant log files.
Movable Type 4.1x is very old...
Anyway, for the list that you found in the code, the above list looks like things that it should not backup, (sessions, ts_jos, config) and the below looks like things to backup (placements, objectassets)
So I suggest to try adding 'log' type under the 'config' type line, like that:
MT->model('config') => 1,
MT->model('log') => 1,
MT->model('session') => 1,
Right on I will give that a shot during the next backup. By truncating out the mt_log table I was able to bypass that speedbump. Is there anyway without rewriting the backup engine to have it only backup items that pertain to the blog_id you are backing up?
Backing up MT::Placement records: 142189 records backed up.
Backing up MT::ObjectAsset records: 41778 records backed up.
Backing up MT::ObjectScore records: There were no MT::ObjectScore records to be backed up.
Backing up MT::Trackback records: 150416 records backed up.
Backing up MT::Association records: 14168 records backed up.
Backing up MT::ObjectTag records: 67677 records backed up.
Backing up MT::TBPing records: 30052 records backed up.
Backing up MT::Comment records: 819500 records backed up...
This particular blog has 6 posts, 0 comments. Yet 2 hours after starting it, we are still cranking away. I can't tell it to not download comments, those need to be migrated ( even though this site has none ).
Yes there is - upgrade.
But carefully - this is a very old version, and as always in upgrading, the wider the version gap the riskier the upgrade process.