|
(Added in Restoration Section)
|
(Working on 'Filesystem' section)
|
| Line 52: | |||
| # Restart the server and agent(s). Ensure that the restoration was successful. If there is a problem, contact the [http://support.urbancode.com AnthillPro support team] with [http://wiki.urbancode.com/AnthillPro/What_to_Consider_When_Submitting_a_Support_Ticket details]. | # Restart the server and agent(s). Ensure that the restoration was successful. If there is a problem, contact the [http://support.urbancode.com AnthillPro support team] with [http://wiki.urbancode.com/AnthillPro/What_to_Consider_When_Submitting_a_Support_Ticket details]. | ||
| == Filesystem == | == Filesystem == | ||
| + | '''KEEP IN MIND THAT ALL THE STEPS LISTED ABOVE ARE ONLY FOR CHANGING THE DATABASE STATES'''. In actuality, no other files are backed up, which leaves your previous build artifacts, codestation artifacts, job logs, test results, etc. at risk. To negate this, it is recommended to backup the entire anthillpro directory filesystem as well so that the filesystem can be restored to the same timeframe as the server. | ||
| + | Unfortunately, there are some cases that warrant a server not being able to have its entire filesystem backed up. THe order of precedence on how to continue is thus: | ||
| + | # Attempt to make a backup of the entire server filesystem. If this is not an option, see #2. | ||
| + | # Attempt to backup any customized files (such as custom startup scripts in the '''bin''' directory, changed libraries in the '''lib''' directory, etc.) in addition to the '''var''' directory. If this is not an option, see #3. | ||
| + | # Attempt to back up the entire '''var''' directory. If this is not an option, see #4. | ||
| + | # Attempt to back up the most important parts of the '''var''' directory. This includes the following: | ||
| + | ## '''artifacts''' - Where your build artifacts live for each buildlife. | ||
| + | ## '''codestation''' - Where your codestation project artifacts live for each codestation buildlife. | ||
