...
NOTE: If you currently use the shared server from CIT (known as lampdbprod.cit.cornell.edu or mustang01.serverfarm.cornell.edu), customers are requested to move your database info from the shared server to your own MySQL instance (either on a Cornell Stack VM or a customer-provided MySQL server).
Using Cornell Stack for MySQL server only (no web server/instance installed).
Some customers may only want to use the Cornell Stack for hosting a MySQL server with no Apache/web server initiated. This is possible, but there are caveats to this:
- With no Instance created (with Apache) on the VM, customer will not have phpMyAdmin available to use for Administration. You will need to work with webservices@cornell.edu to allow access from another system/server with firewall rule changes.
- You will also need to notify them which applications/websites will be connecting to it for database services.
- The VM status page will not show any services nor will it have the "Database Admin Page" link. You will need to go directly to the database page with a url that looks like:
https://dashboard.hosting.cornell.edu/db/webhost###.serverfarm.cornell.edu - where webhost### equates to the VM name given to you when you received your Cornell Stack information from Webservices
- The above page should allow you to create databases and users as it would have if you linked to it from the status page.
- Contact webservices@cornell.edu if you need root level mysql access or additional grants added to users.
Database backups
The MySQL database server performs a nightly mysqldump for backup purposes. These dump files are then backed up to tape by the TSM Backup that runs on each VM. If you find you need to go back to a previous MySQL backup dump file, please contact webservices@cornell.edu and provide the following info:
...