Notices Carbonite Availability for Windows User's Guide Version 8.1.0, February 27, 2018 If you need technical assistance, you can contact CustomerCare. All basic configurations outlined in the online documentation will be supported through CustomerCare. Assistance and support for advanced configurations may be referred to a Pre-Sales Systems Engineer or to Professional Services. Man pages are installed and available on Carbonite Availability and Carbonite Move Linux servers. These documents are bound by the same Carbonite license agreement as the software installation. This documentation is subject to the following: (1) Change without notice; (2) Furnished pursuant to a license agreement; (3) Proprietary to the respective owner; (4) Not to be copied or reproduced unless authorized pursuant to the license agreement; (5) Provided without any expressed or implied warranties, (6) Does not entitle Licensee, End User or any other party to the source code or source code documentation of anything within the documentation or otherwise provided that is proprietary to Carbonite, Inc.; and (7) All Open Source and Third-Party Components (“OSTPC”) are provided “AS IS” pursuant to that OSTPC’s license agreement and disclaimers of warranties and liability. Carbonite, Inc. and/or its affiliates and subsidiaries in the United States and/or other countries own/hold rights to certain trademarks, registered trademarks, and logos. Hyper-V and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries. Linux is a registered trademark of Linus Torvalds. vSphere is a registered trademark of VMware. All other trademarks are the property of their respective companies. For a complete list of trademarks registered to other companies, please visit that company’s website. © 2018 Carbonite, Inc. All rights reserved. Contents Chapter 1 Carbonite Availability overview 6 Core operations 7 Carbonite Availability workloads 10 Supported configurations 13 Chapter 2 Core Carbonite Availability requirements 20 Mirroring and replication capabilities 25 Chapter 3 Carbonite Replication Console 31 Carbonite Replication Console requirements 33 Console options 34 Chapter 4 Managing servers 37 Adding servers 47 Providing server credentials 50 Viewing server details 51 Editing server properties 53 General server properties 54 Server licensing 55 Server setup properties 57 Carbonite Availability queue 60 Source server properties 64 Target server properties 66 E-mail notification configuration 68 Script credentials 70 Log file properties 71 Verification log 73 Viewing server events 75 Viewing server logs 76 Managing VMware servers 78 Managing snapshots 79 Snapshot states 80 Chapter 5 Files and folders protection 83 Files and folders requirements 84 Creating a files and folders job 86 Managing and controlling files and folders jobs 116 Viewing files and folders job details 126 Validating a files and folders job 130 Editing a files and folders job 131 Viewing a files and folders job log 133 Failing over files and folders jobs 135 Failback and restoration for files and folders jobs 136 Restoring then failing back files and folders jobs 137 Failing back then restoring files and folders jobs 139 Chapter 6 Full server protection 141 Full server requirements 142 Creating a full server job 148 Contents 3 Managing and controlling full server jobs 174 Viewing full server job details 184 Validating a full server job 188 Editing a full server job 189 Viewing a full server job log 191 Failing over full server jobs 193 Reversing full server jobs 196 Reversing full server jobs manually 198 Chapter 7 SQL protection 201 SQL requirements 202 Creating a SQL job 205 Managing and controlling SQL jobs 229 Viewing SQL job details 239 Validating a SQL job 243 Editing a SQL job 244 Viewing a SQL job log 246 Failing over SQL jobs 248 Restoring then failing back SQL jobs 250 Chapter 8 Full server to Hyper-V protection 251 Full server to Hyper-V requirements 252 Creating a full server to Hyper-V job 255 Managing and controlling full server to Hyper-V jobs 282 Viewing full server to Hyper-V job details 292 Validating a full server to Hyper-V job 296 Editing a full server to Hyper-V job 297 Viewing a full server to Hyper-V job log 299 Failing over full server to Hyper-V jobs 301 Reversing protection after failover for full server to Hyper-V jobs 304 Chapter 9 Full server to ESX protection 305 Full server to ESX requirements 306 Creating a full server to ESX job 309 Managing and controlling full server to ESX jobs 335 Viewing full server to ESX job details 345 Validating a full server to ESX job 349 Editing a full server to ESX job 350 Viewing a full server to ESX job log 352 Failing over full server to ESX jobs 354 Reversing protection after failover for full server to ESX jobs 357 Chapter 10 Simulating protection 358 Chapter 11 Special network configurations 359 Firewalls 360 IP and port forwarding 361 Domain controllers 364 NetBIOS 365 WINS 366 DNS 368 Non-Microsoft DNS 376 Contents 4 Macintosh shares 378 NFS Shares 379 Chapter 12 Recommended optimizations 380 Planning 381 Installation optimizations 382 General optimizations 383 Full server optimizations 387 Application optimizations 388 Chapter 13 Security 389 Adding users to the security groups 390 Changing the account used to run the Double-Take service on Windows servers 391 Contents 5 Chapter 1 Carbonite Availability overview Carbonite Availability ensures the availability of critical workloads. Using real-time replication and failover, you can protect data, entire servers, individual applications, virtual servers, or clusters. You identify what you want to protect on your production server, known as the source, and replicate that to a backup server, known as the target. The target server, on a local network or at a remote site, stores a replica copy of the data from the source. Carbonite Availability monitors any changes to the source and sends the changes to the replica copy stored on the target server. By replicating only the file changes rather than copying an entire file, Carbonite Availability allows you to more efficiently use resources. Chapter 1 Carbonite Availability overview 6 Core operations Carbonite Availability performs three basic types of operations. l Mirroring on page 7—The initial copy or subsequent resynchronization of selected data l Replication on page 8—The on-going capture of byte-level file changes l Failover on page 9—The ability to stand-in for a server, in the event of a failure Mirroring Mirroring is the process of transmitting user-specified data from the source to the target so that an identical copy of data exists on the target. When Carbonite Availability initially performs mirroring, it copies all of the selected data, including file attributes and permissions. Mirroring creates a foundation upon which Carbonite Availability can efficiently update the target server by replicating only file changes. If subsequent mirroring operations are necessary, Carbonite Availability can mirror specific files or blocks of changed data within files. By mirroring only files that have changed, network administrators can expedite the mirroring of data on the source and target servers. Mirroring has a defined end point when all of the selected files from the source have been transmitted to the target. When a mirror is complete, the target contains a copy of the source files at that point in time. 1. Identical files are not mirrored. 2. New files are mirrored. 3. Different files can be mirrored. 4. Checksums can calculate blocks of data to be mirrored. Chapter 1 Carbonite Availability overview 7 Replication Replication is the real-time transmission of file changes. Unlike other related technologies, which are based on a disk driver or a specific application, the Carbonite Availability replication process operates at the file system level and is able to track file changes independently from the file’s related application. In terms of network resources and time, replicating changes is a more efficient method of maintaining a real-time copy of data than copying an entire file that has changed. After a source and target have been connected through Carbonite Availability, file system changes from the user-defined data set are tracked. Carbonite Availability immediately transmits these file changes to the target server. This real-time replication keeps the data on the target up-to-date with the source and provides high availability and disaster recovery with minimal data loss. Unlike mirroring which is complete when all of the files have been transmitted to the target, replication continuously captures the changes as they are written to the source. Replication keeps the target up-to-date and synchronized with the source. 1. A user or application updates part of a file. 2. Only the changed portion of the file is replicated to the target. 3. An up-to-date copy of the file is maintained on the target. Chapter 1 Carbonite Availability overview 8 Failover Failover is the process in which a target stands in for a failed source. As a result, user and application requests that are directed to the failed source are routed to the target. Carbonite Availability monitors the source status by tracking requests and responses exchanged between the source and target. When a monitored source does not respond to the target's requests, Carbonite Availability assumes that the server has failed. Carbonite Availability then prompts the network administrator to initiate failover, or, if configured, it occurs automatically. The failover target assumes the identity of the failed source, and user and application requests destined for the source server or its IP address(es) are routed to the target. When partnered with the Carbonite Availability data replication capabilities, failover routes user and application requests with minimal disruption and little or no data loss. 1. User and application requests are sent to the source name or IP address.