Missing MySQL files?

RT Users
1

RT 3.2.2
MySQL 4.1.8
Red Hat Enterprise Linux 3.0

I’ve setup RT3 and the application seems to run fine ( I can access, login,
and use it via the web interface.) When I try to backup my database the
backup software complains “Failed to get 3 table files for table: ACL” I’ve
confirmed that my /var/lib/mysql/rt3 directory does only contain ACL.frm and
NOT ( ACL.MYI and ACL.MYD ) This is true for all the tables except
"sessions" which contains all three files.

My question is, have my RT tables been setup incorrectly? Other databases
on my system have .frm, .MYI, and .MYD files for every table, but my
instance of RT3 does not. What did I screw up?

Thanks,

-jeff

2

Jeff Holst wrote:

RT 3.2.2
MySQL 4.1.8
Red Hat Enterprise Linux 3.0

I’ve setup RT3 and the application seems to run fine ( I can access,
login, and use it via the web interface.) When I try to backup my
database the backup software complains “Failed to get 3 table files for
table: ACL” I’ve confirmed that my /var/lib/mysql/rt3 directory does
only contain ACL.frm and NOT ( ACL.MYI and ACL.MYD ) This is true for
all the tables except “sessions” which contains all three files.

My question is, have my RT tables been setup incorrectly? Other
databases on my system have .frm, .MYI, and .MYD files for every table,
but my instance of RT3 does not. What did I screw up?
You use backup software for MyISAM mysql tables, RT uses InnoDB for all
tables except sessions.
http://dev.mysql.com/doc/mysql/en/Backing_up.html
http://www.google.ru/search?q=site%3Adev.mysql.com+backup+InnoDB

3

Ruslan U. Zakirov wrote:

You use backup software for MyISAM mysql tables, RT uses InnoDB for all
tables except sessions.

Well… yes. We use NetVault software along with a Dell jukebox for
corporate wide backups. NetVault has an APM for MySQL backups, so I would
like our existing backup strategy to be able to include RT.

Apparently, standard MySQL database files have 3 versions ( .frm, .MYI, and
.MYD ) because that is what the NetVault software is looking for. when it
does the backups. The backups are failing, however, because my RT database
only contains the “.frm” files.

Can anyone tell me if what I’m seeing below is correct or if something is
setup incorrectly???

[root@zeus mysql]# cd /var/lib/mysql/rt3
[root@zeus rt3]# ls -ltr
total 256
-rw-rw---- 1 mysql mysql 65 Jan 18 08:38 db.opt
-rw-rw---- 1 mysql mysql 9948 Jan 18 08:38 Users.frm
-rw-rw---- 1 mysql mysql 8922 Jan 18 08:38 Transactions.frm
-rw-rw---- 1 mysql mysql 9538 Jan 18 08:38 Tickets.frm
-rw-rw---- 1 mysql mysql 8834 Jan 18 08:38
TicketCustomFieldValues.frm
-rw-rw---- 1 mysql mysql 8978 Jan 18 08:38 Templates.frm
-rw-rw---- 1 mysql mysql 8640 Jan 18 08:38 sessions.frm
-rw-rw---- 1 mysql mysql 9230 Jan 18 08:38 Scrips.frm
-rw-rw---- 1 mysql mysql 8936 Jan 18 08:38 ScripConditions.frm
-rw-rw---- 1 mysql mysql 8874 Jan 18 08:38 ScripActions.frm
-rw-rw---- 1 mysql mysql 9084 Jan 18 08:38 Queues.frm
-rw-rw---- 1 mysql mysql 8680 Jan 18 08:38 Principals.frm
-rw-rw---- 1 mysql mysql 8898 Jan 18 08:38 Links.frm
-rw-rw---- 1 mysql mysql 8732 Jan 18 08:38 Groups.frm
-rw-rw---- 1 mysql mysql 8630 Jan 18 08:38 GroupMembers.frm
-rw-rw---- 1 mysql mysql 8878 Jan 18 08:38
CustomFieldValues.frm
-rw-rw---- 1 mysql mysql 8934 Jan 18 08:38 CustomFields.frm
-rw-rw---- 1 mysql mysql 8752 Jan 18 08:38
CachedGroupMembers.frm
-rw-rw---- 1 mysql mysql 8954 Jan 18 08:38 Attributes.frm
-rw-rw---- 1 mysql mysql 8992 Jan 18 08:38 Attachments.frm
-rw-rw---- 1 mysql mysql 8860 Jan 18 08:38 ACL.frm
-rw-rw---- 1 mysql mysql 2048 Jan 20 13:18 sessions.MYI
-rw-rw---- 1 mysql mysql 5308 Jan 20 13:18 sessions.MYD

4

Jeff Holst wrote:

Ruslan U. Zakirov wrote:

You use backup software for MyISAM mysql tables, RT uses InnoDB for
all tables except sessions.

Well… yes. We use NetVault software along with a Dell jukebox for
corporate wide backups. NetVault has an APM for MySQL backups, so I
would like our existing backup strategy to be able to include RT.
http://www.google.ru/search?q=cache:WfNt0TGnE0oJ:www.bakbone.com/docs/APM_for_MySQL_Users_Guide.pdf+NetVault+APM+MySQL+InnoDB&hl=ru
Read word by word “2. The “InnoDB” format is not supported.”

Apparently, standard MySQL database files have 3 versions ( .frm, .MYI,
and .MYD ) because that is what the NetVault software is looking for.
Read this
http://dev.mysql.com/doc/mysql/en/Storage_engines.html
What did you say about standards?

when it does the backups. The backups are failing, however, because my
RT database only contains the “.frm” files.

Can anyone tell me if what I’m seeing below is correct or if something
is setup incorrectly???
it’s incorrect.

5

Thanks Ruslan, I think I understand what is going on now. It appears
getting NetVault to support the InnoDB format is my first hurdle if I want
to include RT in our regular backup processes.

Regarding my rt3 MySQL tables being setup incorrectly; any idea how to fix?
I have a brand new installtion of rt3 so I can start from scratch, but I’ve
done so at least a couple of times and end up with the same results.

-jeff

6

Jeff Holst wrote:

Thanks Ruslan, I think I understand what is going on now. It appears
getting NetVault to support the InnoDB format is my first hurdle if I
want to include RT in our regular backup processes.

Regarding my rt3 MySQL tables being setup incorrectly; any idea how to
fix? I have a brand new installtion of rt3 so I can start from scratch,
but I’ve done so at least a couple of times and end up with the same
results.
Why do you think that it’s incorrect?