app_store_connect:back_up_and_restore
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
app_store_connect:back_up_and_restore [2017/08/22 10:34] – su | app_store_connect:back_up_and_restore [2023/08/30 12:50] (current) – [Safely Removing Snapshots / Purge Command] su | ||
---|---|---|---|
Line 8: | Line 8: | ||
===== Virtual Machine Snapshot ===== | ===== Virtual Machine Snapshot ===== | ||
- | If App Store Connect is installed on a Virtual Machine, snapshot is a reliable way to back-up an entire server. Refer to VM documentation for information on how to create, schedule and restore snapshots. | + | If App Store Connect is installed on a Virtual Machine, snapshot is a reliable way to back-up an entire server. |
===== Manual Backup ===== | ===== Manual Backup ===== | ||
- | If server | + | If snapshot is not an option, configuration and data files can be manually backed up and restored. Instructions |
- | **1. Take a Big Data Snapshot | + | **1. Back Up App Store Connect Configuration** |
+ | |||
+ | To protect against hardware failure, the contents of the App Store Connect program-data folder should be copied to an alternative location. | ||
+ | |||
+ | * C: | ||
+ | |||
+ | |||
+ | **2. Back Up Big Data** | ||
+ | |||
+ | 2.1. Take a database Snapshot | ||
Execute the BackupUtility batch file " | Execute the BackupUtility batch file " | ||
Line 21: | Line 30: | ||
* BackupUtility: | * BackupUtility: | ||
- | {{ : | + | {{ : |
This creates a database restore point protecting against data corruption or accidental loss. | This creates a database restore point protecting against data corruption or accidental loss. | ||
Line 27: | Line 36: | ||
The console window automatically closes after 10 seconds. | The console window automatically closes after 10 seconds. | ||
- | //If BackupUtility is not present, upgrade to the latest App Store Connection// | ||
- | * Download App Store Connect: [https:// | + | 2.2 Archive back-up files |
+ | To protect against hardware failure, the contents of the back-up folder should be copied to an alternative location. | ||
- | ** 2. Archive configuration and data snapshot files ** | + | |
- | + | ||
- | To protect against hardware failure, the contents of the following folders should be copied to an alternative location. | + | |
- | + | ||
- | * Data BackUp Folder: C:\Program Files\Intelligent Plant\Big Data\es\backup | + | |
- | * App Store Connect Configuration: | + | |
===== Manual Restore ===== | ===== Manual Restore ===== | ||
- | ** 1. To recover App Store Connect configuration | + | **1. To recover App Store Connect configuration** |
1.1 Stop Intelligent Plant Data Core windows service | 1.1 Stop Intelligent Plant Data Core windows service | ||
Line 51: | Line 55: | ||
- | ** 2. Revert Big Data to a snapshot | + | **2. Revert Big Data to a snapshot** |
For advanced Snapshot management (create/ | For advanced Snapshot management (create/ | ||
- | {{ : | + | {{ : |
List returns all available snapshots. Note the snapshot id is actually a time-stamp (format: YYYYMMddHHmmss). | List returns all available snapshots. Note the snapshot id is actually a time-stamp (format: YYYYMMddHHmmss). | ||
Line 63: | Line 67: | ||
+ | ===== Scheduled Backup ===== | ||
+ | |||
+ | To configure a regular scheduled backup, create a Windows Scheduled Task to execute one of following batch files: | ||
+ | |||
+ | * **Snapshot.bat** - Execute a snapshot | ||
+ | |||
+ | * **SnapshotWithPurge.bat** - Execute a snapshot with purge (purge is explained in the Data Retention Policy section below). | ||
+ | |||
+ | Below is a sample configuration. | ||
+ | |||
+ | NB. Remember to specify a valid account and adjust schedule to your own preference. | ||
+ | |||
+ | <file xml BigDataBackup.xml> | ||
+ | |||
+ | <?xml version=" | ||
+ | <Task version=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | <Actions Context=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | </ | ||
+ | |||
+ | |||
+ | ===== Data Retention Policy ===== | ||
+ | |||
+ | Snapshot takes an incremental backup of the Big Data state. Incremental means each snapshot is dependent on the others that have gone before it, and thus may become inefficient if too many snapshots are maintained. Therefore, it is advised to have an archiving and data retention policy in place. | ||
+ | |||
+ | ===== Archiving Snapshots ===== | ||
+ | |||
+ | Snapshots are saved to a backup folder. For a typical App Store Connect installation, | ||
+ | |||
+ | < | ||
+ | |||
+ | //For custom configuration, | ||
+ | |||
+ | Providing a Snapshot is not actively being taken, it is safe to **copy** the entire " | ||
+ | |||
+ | **Do not cut or delete files from Snapshots** as this will break the incremental integrity of the files contained. | ||
+ | |||
+ | |||
+ | ===== Safely Removing Snapshots / Purge Command ===== | ||
+ | |||
+ | Snapshots can be removed using the Backup Utility and executing the **Purge** command. This will delete old snapshots according to the retention policy defined in the config file. | ||
+ | |||
+ | The default snapshot retention is 14 days. | ||
+ | |||
+ | To modify the retention policy: | ||
+ | |||
+ | |||
+ | 1. Open the BackUp Utility config file. \\ For a default installation, | ||
+ | |||
+ | < | ||
- | ===== Special Cases ===== | + | 2. Refer to **AppSettings** section and modify **DayRetentionPolicy** setting. |
- | If App Store Connect is processing Alarms & Events, please contact Intelligent Plant for further advice on how to reliably back-up App Store Connect with minimal interruption. | + | < |
+ | < | ||
+ | <add key=" | ||
+ | <add key=" | ||
+ | <add key=" | ||
+ | </ | ||
+ | </ | ||
+ | 3. Save file \\ The new setting will take effect the next time the BackupUtility is started. |
app_store_connect/back_up_and_restore.1503398041.txt.gz · Last modified: 2017/08/22 10:34 by su