On Wed, Apr 9, 2014 at 11:27 AM, <[email protected]> wrote: > > Another project I need to work on is osTicket. This is an open source work order system which would be great for both my department and our maintenance department. The problem here is that their documentation is sketchy (and I think intentionally so to sell their support services). osTicket simply requires a LAMP setup to run and I somehow stumbled my way through that to give ourselves a sandbox for practice. Here are some questions I have. > > I set this up on a virtual server with VMware. My experience is limited here too. What's a good set of numbers for allocating hard drive space and RAM for this server? Also, what is thin provisioning and should I use it?
For a typical LAMP setup a half gig of RAM and 10GB of disk space should suffice. Since disk is cheap you might want to go to 20GB. > Backups are important. I see where VMware allows me to take a snapshot of the server and would think this would be the simplest way to run backups. We are using the free version of VMware so does that mean I do not have the ability to automate snapshots? > If I cannot automate snapshots how do you backup the mySQL database and then restore it if the need arises? Even if you can automate snapshots there's no guarantee that the on-disk database will be in a consistent state when the snapshot is taken, meaning that the database might be unusable after recovery. The best way to get around this is to do a database dump at a given time each day so that the database dump - which will be guaranteed recoverable as long as it finished - is backed up. mysqldump -uroot -pmysqlrootpassword databasename | gzip -9 >/path/to/dumps/databasename.dump.gz There are other incantations available, such as sticking the data in the filename and then using a variation of "find /path/to/dumps -type f -amin 10080 -delete..." to get rid of dumps older than a week, for instance. Another idea is to use something like duplicity to do a more concise backup of what needs to be backed up on your disk. You can cause duplicity to dump to a share mounted on another machine or something like that if you wish, or even do an offsite backup to amazon s3. The takeaway on this is that a low-level backup of the virtual drive might not provide a recoverable mysql instance, so make sure to do something else that will. Michael -- Michael Darrin Chaney, Sr. [email protected] http://www.michaelchaney.com/ -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
