Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#59 Automated Backup Of FOG for Ubuntu users

Unstable (example)
closed
mastacontrola
5
2014-05-26
2011-12-03
geener1987
No

I have modified this tool that's included with FOG, and made it so users who have FOG on Ubuntu can backup FOG. I have tested this on the 64 bit versions of 10.04 LTS and 11.04 Ubuntu and works on both. This tool will backup your Configuration settings, your MySQL database, your Snapins, and all of your Images. Here are the minor changes made:

1. This will no longer backup the reports section, it will backup all the config files in /var/www/fog.
2. This will also backup the install folder as in the extracted fog_0.32 folder that's extracted. This will save time from having to download the new copy if you are migrating servers etc. However, in order to do this, you need the fog_0.32 folder located on the server and you will have to manually enter the file path within this file.

I have tested this on my private FOG server and verified that it works, I will be working on another file to be able to move everything back automatically as well.

To run this file, simply type ./FOGBackup.sh (destination directory) *Note the destination directory must exist.

Discussion

  • geener1987
    geener1987
    2011-12-03

     
    Attachments
  • mastacontrola
    mastacontrola
    2014-05-26

    • status: open --> closed
    • assigned_to: mastacontrola
    • Group: --> Unstable (example)
     
  • mastacontrola
    mastacontrola
    2014-05-26

    The backup code included with FOG should be sufficient enough and should be easily adjustable to needed specs. This comes with the caveat that we have now included a GUI backup option that can be used to save and restore the FOG Database. This does not backup the snapin's directory or the state of the config file. As the config.php file is now basically used for the service information which is typically unchanged and the database information on the fly, this shouldn't pose much of an issue.