Didn't find any forum that is specifically for this so figured this might be the appropriate place to ask. Senario: virtualized environment (VMware) [virt backups and restores not tested/trusted] ... no NAS nor 'shared folder' on other server and single site for multiple campuses of a medium size school district that uses Moodle as flipped and as blended (always traffic - almost truely 24/7). Always wise to do a full site backup when upgrading to a higher version ... easy enough to do on Linux (tar ball of code directory, data directory, and an sql dump in a script) that saves to the largest partition of the drive. Last night, didn't think it trough before hand and did tar balls and dump via command line via single script while connected via ssh remotely, but waited about 2 hours for the tar ball of the data directory! (Yeah, I know, stupid me! Sure could have used some zzzzz's (instead of watching the screen and checking for 'space' via df via watch) ... yawn!
Aside from running cron previous to full site backup (hopefully the trashdir will be emptied), are their directories inside moodledata which one could skip ... to reduce the size and therefore time of a full site backup? Obvious one is moodledata/temp (?) and moodledata/sesssions if not using DB. But how about moodledata/cache? or others one wouldn't need to do a complete site restore should an upgrade fail whale for some reason?
Come to think of it, that would be a desired admin add-on tool. Is there one?
Thanks in advance for any suggestions/thoughts.
'spirit of sharing', Ken