Version Differences for Backups of AnthillPro

(Created backup schedule section)
(Added in Restoration Section)
Line 39:
  == Clean Restoration ==    == Clean Restoration == 
       
    + Restoring AnthillPro to a clean state requires overlaying the installation with backed-up data files. The directions outlined below are for backups of the embedded Derby database. If using another database type, you cannot use most of the concepts in this section. Typically, restoring AnthillPro to a backed-up version is an option of last resort, and should only be used if there is no other way to correct an issue.  
       
    + Note that restoration requires shutting down the server and agent(s).  
       
    + # Shutdown the server and the agent(s).  
    + # Go to the AnthillPro instance.  
    + # In the '''%SERVER_HOME%\var\db\''' directory, rename the data folder to '''data_old'''. In Item 7, a copy of the backed-up data folder will be added (renaming the existing data folder reduces the chances of corruption).  
    + # Go to the '''%SERVER_HOME%\var\db\backup\''' directory and open the appropriate backup folder. Every backup is identified in the format year-month-date_hour-minute-second (e.g., 2008-10-08_10-59-48).  
    + # Open the backup you want to restore AnthillPro to, and copy the data folder located within the directory (e.g., the data folder is located in the var\db\backup\2008-10-08_10-59-48\ directory of a backup that was performed on October 8, 2008 at 10:59:48 a.m.).  
    + # Go back to the '''%SERVER_HOME%\var\db\''' directory.  
    + # Paste the backup's data folder here. Do not delete the old (renamed) data folder until you have verified that the restoration was successful.  
    + # 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 ==