ZettaMirror Install Guide March 2014
Table of Contents Planning Your ZettaMirror Deployment...3 Where to install ZettaMirror?...3 Do I need extra retention policies?...3 How to Download & Install ZettaMirror...4 How to Configure ZettaMirror...5 System Settings...5 Add New Task...6 Task Preferences...6 Backup Files...7 Backup Windows System State...8 Backup SQL Server...9 Backup NetApp Volume...10 Pre and Post Job Scripting...11 Backup Exchange Database...11 Backup Hyper-V...12 Setting Your Run-As User; Per System (Windows)...13 Snapshots and Retention...13 How Our Snapshot Retention Works...13 How to Configure Snapshots...14 How to Recover Data...15 Browser Based Recovery...15 Appendix... i Appendix A: Exclusions... i
Planning Your ZettaMirror Deployment Where to Install ZettaMirror? ZettaMirror agents can be used to backup data from both local and network sources giving you the option to install ZettaMirror directly on each system that needs to be backed up or on a central system that can read data across the network. The recommendation is to install ZettaMirror directly on each system that needs to be backed up because this helps spread the computer resource load as well as enables full use of VSS on Windows systems. Do I Need Extra Retention Policies? Zetta stores your data in personal storage volumes and each volume designates one possible retention plan. By default you are assigned one volume and therefore one retention policy for all of your data to be stored on. If needed, additional storage volumes can be added to your organization to allow multiple retention policies at no additional charge through contacting support. A common example of needing multiple retention policies would be a user with a SQL server and a file server. Due to the different nature of the data being stored it is common to store the data on different retention policies, such as a 7 day retention for the SQL server and a 30 day retention for the file server. Organization Volume 1 Volume 2 System 1 System 2 System 3 System 4 System 5 System 6 3
How to Download & Install ZettaMirror 1. If you have just completed your initial enrollment to Zetta, you will be automatically logged into the Zetta System Management Portal (SMP); if not, log into the SMP at admin.zetta.net using your full email address and the strong password you created when you enrolled. 2. Once logged in to the SMP, navigate to the ZettaMirror tab, scroll down to the bottom of the page and click the orange download client button to be browse a list of the different versions of ZettaMirror. 3. Determine what Operating System your server is running and download the appropriate agent. Be sure to take consideration for 32 bit vs. 64 bit OS. 4. Download and save the correct version of the ZettaMirror program then run the installer. 5. Once the installation completes you will be prompted to enter your SMP login credentials to register the new ZettaMirror. 6. Once the ZettaMirror agent is authenticated and registered it will open a web page that brings you to the system s configuration page in the SMP. 4
How to Configure ZettaMirror To configure the ZettaMirror agent on a system, log into the SMP through admin.zetta.net and click on the system you want to configure as listed on the ZettaMirror tab. The first time you configure a system you will be presented with the following workflow. System Settings The first window you will be presented with is the systems settings window which is where you configure the job level preferences for the backup. The primary configuration options here are the job schedule and the network throttle. The schedule is where you specify what time and what days you want the sync to run. The Network Throttle section is where you specify the rate, day of the week and time of the day you wish to throttle the backup job to. From this window you can also configure a job level Local Backup which will enable a local backup of every task setup in the backup job. This means every item backed up to Zetta s cloud will also be backed up to the specified location in your environment. The destination for the Local Backup can be attached storage or a network path. 5
Add New Task After configuring your sync schedule you will be presented with the task management wizard where you select and configure the backup tasks you would like to be included in the system s backup job. Task Preferences For every task there is a set of general task level preferences that can optionally be configured. This task syncs to: The target storage volume the data is being backed up to at Zetta. This option allows different tasks to be backed up to different volumes for the purpose of managing different retention policies for different data sets within a backup job. Archive deleted items: Enable archive of deleted items by prohibiting Zetta from deleting items on the Zetta storage end when files are deleted locally. Deleted data will remain on the Zetta end until manually deleted or the option is disabled. Create a local Backup: Enable a local backup of the specific backup task to be sent somewhere in your environment in addition to the copy sent to Zetta. The destination for the Local Backup can be attached storage or a network path. Zetta Transfer Optimization cache location: Zetta utilizes two caches stored locally to optimize transfer performance, combined the two caches generally total about 1% of the size of the data set. If free disk space is a concern you can specify an alternate location for the caches here. 6
Backup Files The Backup Files task is where you add any data sources you would like to backup on your system. The value for the backup file or path field can be a local path to a directory or file as well as a UNC path for a network location. Exclude: o File or Directory type: Both the File and Directory type excludes match a value of a specific file (name or type) or directory (name) and exclude anything that matches within the entire data source. File Examples: *.mp3,.jpeg, VacationPhoto_01.jpg Directory Examples: My Documents, Program Files, Users o Path Type: The Path type exclude matches a path to a specific file or directory within the data source and excludes the match from the backup task. Path Examples: C:\Windows\System32\drivers, *\Windows\System32\drivers, Windows\System32\drivers o A full list of exclude types and examples can be located in Appendix A at the end of this document. 7
Backup Windows System State The Backup Windows System State task is used to create a Windows System State backup on Windows Server machines running server 2003, 2008 or 2012. The Windows System State backup captures the state of the active directory database as well as system registry information and other items deemed critical by the operating system. This backup is recommended to be performed primarily on domain controllers although it can be run on any Windows server. The full list of items included in a system state backup can be found here: http://technet.microsoft.com/en-us/library/cc816584%28ws.10%29.aspx. To run the plug-in the system must have Windows Server Backup Features installed as well as be running Powershell 2.0 or greater. Windows Server Backup Features can be added by going to Server Manager > Add features. You can verify your version of Powershell by opening a command prompt and entering: Powershell get-host. If the result comes back as console host 1.0 or invalid argument you will need to download the.net management framework update that includes Powershell 2.0 and reboot the server post installation. To configure the plug-in you must specify a local storage location for the backup to be written out to where it will reside while being backed up to the Zetta cloud. This is done through the Staging drive field. 8
Backup SQL Server The Backup SQL Server task enables Zetta s integration with MS SQL to create a full backup of databases and sync the backup to the Zetta cloud. By utilizing our sub-file change detection algorithm we are able to detect the incremental changes day on day from the full backup of SQL.. Requirements: Powershell 2.0 or greater. Enough local disk space available to write out a full backup. The server must have the SQL management framework. To configure the plug-in you must first specify if the instance(s) you want to back up is a default instance or a named instance. You can find this information by opening services.msc, scrolling down to SQL Server and check the value in parenthesis. (MSSQLSERVER) is the default instance name; if this is the value for your service then you can check the backup default SQL server option. Any other value will have to be specified in the backup named SQL server instance(s) field. Next you will have to specify the staging drive or path which is the location that the full backup is written out to. This location must be a local disk and will need space to write out every database in the instance prior to backing up to Zetta. The Validate SQL backup option triggers the verify backup functionality of SQL and will check to ensure the files in the backup are readable and restorable. This is an optional function and will increase the time the backup process runs. 9
Backup NetApp Volume ZettaMirror has the ability to backup a NetApp filer through integration with the NetApp administrative tools and built in snapshot functionality. The configuration for the NetApp plugin is done through a text file that is saved locally on the machine that ZettaMirror is installed on and the backups will run through. The configuration file can by located by clicking the (sample) link at the end of the configuration file line. There a full guide explaining the configuration and how the plugin works located on the ZettaMirror knowledgebase. https://admin.zetta.net/ng/knowledgebase/showpage?id=34013617&title=zettamirror+netap p+installation+guide Task Preferences: Excludes: The same exclude types & syntax as the Backup Files task. The full listing of types, syntax and examples is located in Appendix A at the end of this document. 10
Pre and Post Job Scripting Through the Pre and Post job script tasks a user can add their own custom scripts to be run in conjunction with ZettaMirror for backup purposes. The location for the script must be specified in the Run script: field. The Pre job script will run prior to the sync and the post job script will run afterwards, allowing users to script operations such as database dumps and cleanups. Backup Exchange Database The Backup Exchange Database task allows users to have ZettaMirror trigger an application aware backup of an exchange server. The backup utilizes the exchange specific VSS writers and in doing so triggers the backup flag within exchange which allows the database to automatically truncate log files post backup. The primary configuration options for this plugin are automatically detected so by clicking Add Task the exchange backup will be set to run. 11
Backup Hyper-V The Backup Hyper-V task allows users to schedule a backup of their Hyper-V environment and capture the state of their Hyper-V.VHD files. The only configuration option needed for this plugin is selecting the location of the Hyper-V image store. Task Preferences: Exclude VMs: Allows a user to specify a VM by name to exclude from the backup task. 12
Setting Your Run-As User; Per System (Windows) Setting the run as user on Windows is a very important step if you are syncing data from network sources. This step ensures that the user account the ZettaMirror service is running as will have access to the network sources. 1. Right click the ZettaMirror icon in your system tray. 2. Select Local Settings. 3. Click This Account and enter the Username and Password for a Domain admin account. 4. Check your services to verify that the ZettaMirror Service has accepted the correct Log-On-As that you provided. Snapshots and Retention How Our Snapshot Retention Works Our snapshots function as a solution to both version history and data retention policies. Through the use of pointers, the changes in your data are saved on a day on day basis as a snapshot point. Each snapshot reflects what your data looked like at that point in time and is similar to what is commonly known as an incremental in that each snapshot only reflects the changes that occurred since the last snapshot. The difference between our snapshots and your typical incremental is that you never have to restore each snapshot to a full backup to access your data, allowing users to utilize the incremental forever methodology. By doing this your snapshots function as both your version history and your retention policies. Example: 1. You have 30 daily snapshots, you need to recover a file that has become corrupted and is realized to have been corrupted for the past 10 days. 2. You access your snapshot from 11 days ago and recover the file as it was at that point in time, before the corruption occurred and without having to rebuild anything on your end. The snapshots utilize the grandfather-father-son roll of methodology where a given daily snapshot will be promoted to a monthly and a given monthly will be promoted to an annual. 13
Example: 1. You have a two year retention policy; two years from now: a. You will have 30 daily snapshots, one for each of the most recent 30 days. b. You will have 11 monthly snapshots, one for the most recent 11 months after the 30 dailies. c. You will have 2 annual snapshots, one for each of the 2 previous years. How to Configure Snapshots 1. From admin.zetta.net, go to the storage tab and then click on the retention tab. 2. This will bring up the retention policies page. 3. This brings up your snapshot settings configuration page where you can view your current retention policies as well as request additional retention policies to be added. 14
How to Recover Data Recovery is performed by accessing the per system recovery page and navigating through the file browser to the file or directory you wish to restore. Browser Based Recovery 1. Log into admin.zetta.net. 2. Select the system from the dashboard that the data you wish to recover was backed up from. 3. Select the Recovery tab. 4. Select the volume that the data you wish to recover resides on and then click the Browse Recovery Data button. 5. Navigate to the file or directory you wish to recover. 6. If you wish to restore from a previous version select the snapshot data from the version drop down in the embedded navigation bar. 7. Once you have the file or directory you wish to recover right click on the item and select Restore using ZettaMirror which will bring you back to the recovery page in the main management portal. 8. Select the system you wish to restore the data to. 9. Specify the path you wish to recover to. For single file restores this path must specify the file name and extension you wish to restore to. The path value can be a network path for directory restores. 10. Enter your password and click the Start Recovery button. NOTE: after performing this recovery, you must re-enable your sync schedule as it is suspended to prevent a sync running while recovering data. 15
Appendix Appendix A: Exclusions You can specify one or more Excludes to prevent syncing certain directories or files. ZettaMirror will skip syncing all files or directories that match any of the following types. Note: For Excludes that support wildcards, the following expressions are supported: * Matches any sequence of characters? Matches a single character ^* Matches a single '*' character ^? Matches a single '?' character File Exclude all files whose name matches Value, which may be an exact name or a wildcard expression. Value is matched against only the base name of each file (and not any parent directories). Value: Creek.jpg Matches:...\Pictures\Sample Pictures\Creek.jpg Value: *.jpg Matches:...\Pictures\Sample Pictures\Autumn Leaves.jpg and...\pictures\sample Pictures\Creek.jpg Common Mistakes: File excludes must match a file name and not a path to a file for a value. Use the path type exclude if you want to enter in a path to the file for a value. Directory Exclude all directories whose name matches Value, which may be an exact name or a wildcard expression. Value is matched against only the inner-most name of each directory (and not any parent directories). Value: Pictures i
Matches:...\Pictures Value: Sample* Matches:...\Music\Sample Music and...\pictures\sample Pictures Common Mistakes: Directory excludes must match a directory name and not have a path for a value. Use the path type exclude if you want to enter in a path for a value. Path Exclude directories or files whose path matches the entire Value to the item being excluded. Value: C:\Users\Pictures\Sample Pictures Matches: C:\Users\Pictures\Sample Pictures\ Value: *\Pictures\Sample* Matches: C:\Users\Pictures\Sample Pictures and C:\Program Files\Adobe\Pictures\Sample Artists\ Common Mistakes: A trailing slash on the exclude path value will cause the exclude not to work. (C:\Users\Pictures\Sample Pictures\) Other Max Size, Min Size: Exclude files larger than the Max Size or smaller than the Min Size. Newer Than, Older Than: Exclude files newer than or older than a date (in YYYYMMDD format) or a number of days (between 0 and 1899). Ignore Errors: If any errors occur while syncing files or directories that match these values, ZettaMirror will ignore them and continue syncing. Value may be an exact name or a wildcard expression. ii