Webmaster Forums - Webmaster forum for HTML, PHP, ASP, CSS and more - View Single Post

richard34 · 10-14-2009, 01:17 AM

Hello
REPLICATION SERVER. The most important characteristic of HAP is support for replication of the primary backup appliance. This lets the user copy all incoming blocks and meta-information to the replication server. Of course this happens without interrupting the backup process. The replication server is a Backup Appliance. Just like with every other our Backup Appliance, all HAP settings are placed on the primary server. The number of replicated appliances is unlimited It is possible to connect three, four or even more to each other as a backup for the backups of the backups. Each incoming block is sent to the replica server as soon as it is available. If the replica server is not available temporarily, the primary server keeps track of which blocks have not been replicated yet. The meta information is still replicated by the database engine that is in use and can also pick up everything after temporary non-availability of the replica server. The status of the replication can be seen in the console.

POWER LOSS. One of the most critical events for a backup server is power loss. 95% of all appliances are in a data centre. Although it should not happen, reality has taught: us that power loss in a data centre does actually occur. The problem here is that the OS for the appliance will check all storage before it is available for the new backup. This can last 12 hours on a 10TB system with a lot of information. To prevent this the 7D appliance and 14D appliance have two partitions This first partition contains 5% of the available storage and the second partition 95% of the storage. In the case of a power loss or other cause that forces the OS to check all of the available storage, the first partition is checked first. As soon as this is ready, probably within an hour, the primary server is ready for backups and restores. While the secondary partition is being checked, the incoming blocks for backups are stored on the first partition until it is 95% full. This functionality is available on single and replicated setups.

10-14-2009, 01:17 AM	#2 (permalink)
richard34 Junior Member Join Date: Oct 2009 Posts: 34	Re: IASO Online Backup Hello REPLICATION SERVER. The most important characteristic of HAP is support for replication of the primary backup appliance. This lets the user copy all incoming blocks and meta-information to the replication server. Of course this happens without interrupting the backup process. The replication server is a Backup Appliance. Just like with every other our Backup Appliance, all HAP settings are placed on the primary server. The number of replicated appliances is unlimited It is possible to connect three, four or even more to each other as a backup for the backups of the backups. Each incoming block is sent to the replica server as soon as it is available. If the replica server is not available temporarily, the primary server keeps track of which blocks have not been replicated yet. The meta information is still replicated by the database engine that is in use and can also pick up everything after temporary non-availability of the replica server. The status of the replication can be seen in the console. POWER LOSS. One of the most critical events for a backup server is power loss. 95% of all appliances are in a data centre. Although it should not happen, reality has taught: us that power loss in a data centre does actually occur. The problem here is that the OS for the appliance will check all storage before it is available for the new backup. This can last 12 hours on a 10TB system with a lot of information. To prevent this the 7D appliance and 14D appliance have two partitions This first partition contains 5% of the available storage and the second partition 95% of the storage. In the case of a power loss or other cause that forces the OS to check all of the available storage, the first partition is checked first. As soon as this is ready, probably within an hour, the primary server is ready for backups and restores. While the secondary partition is being checked, the incoming blocks for backups are stored on the first partition until it is 95% full. This functionality is available on single and replicated setups.