2. Click Next.• Click Reset. Returns the configuration to the following default settings:– Request Timeout: 01:30 (minutes and seconds)– Retry Count: 3 (attempts)Removing a Cloud accountYou can remove a Cloud account to, discontinue your cloud service, or stop using it for a particular Core.To remove a cloud account:1. On the Core Console, click the Tools tab.2. In the left menu, click Clouds.3. Next to the cloud account you want to edit, click the drop-down menu, and then click Remove.4. In the Delete Account window, click Yes to confirm that you want to remove the account.5. If the cloud account is currently in use, a second window asks you if you still want to remove it. ClickYes to confirm.NOTE: Removing an account that is currently in use causes all archive jobs scheduled for thisaccount to fail.Understanding replicationAbout protecting workstations and serversTo protect your data add the workstations and servers you want to protect in the Core Console; forexample, your Exchange server, SQL Server, or your Linux server.NOTE: In this section, generally the word machine also refers to the AppAssure Agent softwareinstalled on that machine.In the Core Console, you can identify the machine on which an AppAssure Agent software is installed andspecify which volumes to protect, define schedules for protection, add extra security measures such asencryption, and more. For more information on how to access the Core Console to protect workstationsand servers, see Protecting A Machine.About replicationReplication is the process of copying recovery points and transmitting them to a secondary location fordisaster recovery. The process requires a paired source-target relationship between two cores. Thesource core copies the recovery points of the protected machines and then asynchronously andcontinuously transmits them to a target core at a remote disaster recovery site. The off-site location canbe a company-owned data center (self-managed core) or a third-party managed service provider’s(MSP’s) location or cloud environment. When replicating to an MSP, you can use built-in work flows thatlet you request connections and receive automatic feedback notifications. Possible scenarios forreplication include:• Replication to a Local Location. The target core is located in a local data center or on-site location,and replication is maintained at all times. In this configuration, the loss of the Core does not prevent arecovery.• Replication to an Off-site Location. The target core is at an off-site disaster recovery facility forrecovery in the event of a loss.42
