Excellent point. The MySQL TEMP folder was moved, but not the operating system 
ones. I'll see if I can move the OS temp locations to the larger drive today & 
see what that gets me. I've just gotten the last 30 lines of the "attachments" 
table .sql file so I'm checking that to see if maybe there's anything in the 
text that might cause a stop. Still looking into this one guys. Thank you for 
all who have answered so far! Will update as soon as I know more.

Stephen Cena
Senior Systems Administrator 
Quality Vision International, Inc.
Phone: (585) 544-0450 x300
To notify helpdesk: http://helpdesk.ogp.qvii.com or email: hd-gene...@qvii.com
To report email issues: postmas...@qvii.com

-----Original Message-----
From: Jeffrey Pilant [mailto:jeffrey.pilant....@bayer.com] 
Sent: Monday, January 23, 2017 5:59 PM
To: Cena, Stephen (ext. 300) <s...@qvii.com>
Subject: RE: MySQL backups of RT 4.4.1 truncated

There are temp files and temp files.  The files you moved may not be the ones 
you need to move.  You might try observing the free space as the backup 
proceeds and see what it is filling with.  That might give you a clue of which 
set of temp files need moved.  I.e. rt vs. web vs. MySQL vs. System vs. 
whatever.  Each may define temp files in a different way.  Config file vs. 
registry variable vs. environment variable vs. different environment variable 
vs. command line parameter vs. whatever.  We programmers can get creative.

As to the question you asked about indexing, I don't know.  That should be 
asked to the list at large.


Freundliche Grüße / Best regards,

Jeffrey Pilant


Reply via email to