Intended for use as an "add-on" service for Webserve accounts
Connections to/from the MySQL service are restricted to Webserve and direct logins to the MySQL servers. As such, you are unable to use desktop MySQL clients to manage your databases or connect to your databases from servers other than Webserve.
All MySQL accounts come with a test account to provide you with a completely separate environment in which to test your applications before moving into production or to test the impact of MySQL version upgrades prior to the roll out.
This service is intended for those with modest disk usage requirements, as such there is no charge for the first 1GB of use.
Guidelines & Responsibilities
Appropriate Use
You will have complete control and the associated responsibility for your own MySQL database server running as your account name on the port number that is assigned to you with your account. The appropriate use of the account and its associated MySQL server is to provide a database service only for use by web applications in your Webserve account.
Test databases must be located on the test server (mysql-test.iu.edu) and not on the production server (mysql.iu.edu). Likewise, production databases must not be placed on the test server but need to be located on mysql.iu.edu. If you need help or have questions about moving test MySQL databases into production, contact IU Webmaster for assistance.
Backups and File Restores
You are responsible for performing and maintaining your own backups on mysql.iu.edu and mysql-test.iu.edu.
All accounts are pre-enabled for cron to permit you to run automated database checkpoint and backups. We strongly recommend doing a DB-level checkpoint mysqldump to ensure your data is backed up sufficiently should you need to restore data. While UITS performs standard system backups, because of the relationship between data elements within the data files needing to be in complete synchronization, a file restore done by UITS may not be sufficient to restore your database.
For additional information see Backup and Recovery in the MySQL Reference Manual and the IU Webmaster document on MySQL backups.
Data Collection
IMPORTANT
Please note that you cannot use this service for storing of critical data .
If you plan on collecting and storing personal information, you should contact the data manager for guidance and regulations that govern the use of that data. The list of data managers can be found at http://datamgmt.iu.edu/dm.shtml .
Use of the MySQL Service requires adherence to policies outlined by both the University Information Policy Office and the IU Webmaster. Please see Important Security Information for MySQL Accounts for policies and guidelines.
Entry of personal data on a web site should be done within the wwws directory.
Critical data may not be stored using this MySQL service. Please see Classifications of Institutional Data for a list of examples.
You are encouraged to avoid collecting unnecessary data and to make use of existing official data sources, such as HRMS or SIS, when possible. Please see What is the HRMS/SIS project?
Passwords that are used as part of a web application that are stored in a MySQL database must be
(i) transmitted in a secure manner, meaning that the communications between the www browser and the server (Webserve) should encrypted by putting the web application in the secure WWW server;
--and--
(ii) stored in a MySQL table encrypted using MySQL data types/functions which encrypt and decrypt the value of the variable as it is read and written to the table.
You may not run more than one MySQL database server process (mysqld) within a single account using the same or additional port numbers. If you need additional database server processes for a special set of circumstances, you should apply for another MySQL database service account.
Posts
No comments:
Post a Comment