2 SQL Sentry Quick Start 2 2 Table of Contents 1. Cover Page 1 2. Table of Contents Quick Start Guide 4 4. Important Concepts Installation Recommendations System Requirements Installation and Setup Steps Step 1: Install SQL Sentry Step 2: The Setup Wizard Step 3: Start Using the Client Additional Tasks Add Users and Groups Monitor Additional Connections Introduction to Actions and Settings How to Configure Actions How to Configure Settings Security Overview Monitoring Service Security Client Security Watching Servers Across Domains Pass-through Authentication Least Privilege General Performance Monitoring Non-Windows Network Environment Security Appendix SQL Sentry Performance Advisor Performance Advisor Security Requirements Performance Advisor Required Ports Performance Advisor Data Capacity Planning SMTP Settings Uninstalling SQL Sentry 39-40
3 SQL Sentry Quick Start Object Removal Script for Watched 2000 Servers Object Removal Script for Watched Servers Watched Server Objects Standard Vs Enterprise Editions The SQL Sentry User Guide Contact Information Index 55-56
4 SQL Sentry Quick Start 4 3 Quick Start Guide PURPOSE OF THIS GUIDE This Quick Start Guide will quickly walk you through the basic Installation and Setup Steps for SQL Sentry. Following this guide you should be able to install SQL Sentry, complete basic configuration, start managing schedules, monitoring performance, and generating notifications across your enterprise within 10 to 30 minutes. Please note, this guide is focused on initial installation and configuration steps only, and does not cover such topics as using the visual job calendar, performance monitoring, chaining, queuing, etc. Please refer to the SQL Sentry User Guide for more information on these and other topics related to everyday use. The User Guide can be accessed at any time from the SQL Sentry Client Help menu.
5 SQL Sentry Quick Start 5 4 Important Concepts SQL SENTRY COMPONENTS SQL Sentry consists of the Client (a thin client application), the Monitoring Service (a Windows service), and a SQL Server Database. The SQL Sentry Database stores event metadata and history information collected by the SQL Sentry Monitoring Service and the SQL Sentry Client provides a thin client interface for viewing and managing this information. One SQL Sentry Monitoring Service is typically required for every 50 to 100 monitored SQL Servers, Analysis Services connections, SharePoint Servers, Oracle Databases or Windows Task Schedulers. Multiple Monitoring Services can be installed for scalability, redundancy, or to collect information from remote sites. Normally a SQL Sentry Client will be installed on each DBA's workstation. All SQL Sentry Monitoring Services and Clients connect to the same database. It's important to note that SQL Sentry does not attempt to replace SQL Server Agent, Oracle Scheduler, Windows Task Scheduler or any other scheduling agents. Instead, SQL Sentry communicates with these schedulers to ascertain event status, and collect history and performance information using a lightweight polling architecture. Thus SQL Sentry does not require agents installed on each monitored server, dramatically reducing associated setup and maintenance overhead of agent-based systems. SQL Sentry also does not install a database on every monitored SQL Server. ALERTING AND RESPONSE SYSTEM As part of its Alerting and Response system, SQL Sentry uses the concept of Conditions and Actions. Conditions describe the various states of monitored objects in your environment. You configure Actions to take place when a Condition is met. All Actions work on the principle of inheritance. This means that if you configure an Action in response to a Condition being met at the global level (Shared Groups node in the Navigator pane), it will be automatically passed down to all applicable objects below it. This allows you to define global Actions for the most common issues across your environment once, and have those passed down to every monitored server automatically. You can further refine Actions at each level as needed. This gives you the ability to determine exactly what happens in response to events occurring in your server environment. Each Connection type supports multiple Conditions and Actions. Configuring Actions globally provides a powerful way to significantly reduce the setup and configuration time required to implement notifications. For example, by enabling the Send Action for the global SQL Server Agent Job: Failure Condition, you will automatically receive alerts for any SQL Agent job failures across your enterprise. The only requirement is that the SQL Server connection and its jobs be "watched" by SQL Sentry. For a more detailed explanation of how Conditions and Actions work see the Alerting and Response System topic in the SQL Sentry User Guide. WATCHING CONNECTIONS AND OBJECTS Throughout this document you'll also see the term "watch" used frequently, in the context of
6 SQL Sentry Quick Start 6 watching connections or objects. When you have SQL Sentry watch a connection or object via the context menu this simply means that SQL Sentry will begin monitoring it. Please consider these rules regarding watched connections and objects: 1. When a connection is watched, SQL Sentry will monitor the connection and fire any applicable conditions for the connection based on its type. 2. When an object is watched, SQL Sentry will monitor the object and fire conditions for the object based on its type. 3. A connection can be watched without watching any of its objects. 4. If any object on a connection is set to watched, the connection will also be automatically set to watched. 5. An object and its connection must be watched to utilize SQL Sentry's queuing, chaining, and performance monitoring features
7 SQL Sentry Quick Start 7 5 Installation Recommendations WHERE TO INSTALL THE SQL SENTRY COMPONENTS The SQL Sentry Client, Monitoring Service, and SQL Sentry Database are typically installed as follows: The SQL Sentry Client is installed on your workstation computer(s) The SQL Sentry Database is installed on a SQL Server instance on your local area network The Monitoring Service is installed on the same computer as the SQL Sentry Database, or any other non-production server in the same LAN. The SQL Sentry Clients and Monitoring Services are each configured to connect to the same SQL Sentry Database during setup. NOTE: The SQL Sentry Database must be installed on a SQL Server 2005 (Service Pack 2) or higher instance. SQL Server Express Edition is not supported. Please see the System Requirements section for more information. INSTALL ALL COMPONENTS ON THE SAME LOCAL AREA NETWORK For performance reasons, it is recommended that the SQL Sentry Client, Monitoring Service and database be installed on the same LAN. For example, you would not want to connect the SQL Sentry Client or Monitoring Service to a SQL Sentry Database over a slow WAN link, as performance will suffer. WHERE TO INSTALL THE MONITORING SERVICE(S) It is not recommended that the Monitoring Service be installed on a production server, as it does incur some memory and CPU overhead. Exactly how much depends on the number of connections and objects being monitored. INSTALLING THE SQL SENTRY MONITORING SERVICE AND DATABASE ON THE SAME COMPUTER Depending on your environment, you may want to install the Monitoring Service on the same SQL Server machine where the SQL Sentry Database is located, to minimize network overhead for communications between the Monitoring Service and the database. Because both Microsoft SQL Server and the SQL Sentry Monitoring Service are multi-threaded, to ensure adequate performance when running both on the same computer it is very important that the computer have at least two CPUs. See System Requirements for more information. INSTALLING MULTIPLE SQL SENTRY CLIENTS AND MONITORING SERVICES Depending on the size of your SQL Server environment, you may need to install multiple SQL Sentry Clients and Monitoring Services. Typically each DBA will have the SQL Sentry Client installed on their workstation, and one Monitoring Service will be installed for every 50 to 100 SQL Server, Oracle, or Windows Task Scheduler instances being monitored.
8 SQL Sentry Quick Start 8 CLUSTERING SQL SENTRY MONITORING SERVICES Multiple Monitoring Services can be installed to handle more than 100 connections, and/or to provide automatic redundancy and load balancing. There is no configuration required to implement a basic SQL Sentry cluster. Simply install more than one Monitoring Service and connect each to the same SQL Sentry Database during setup, and they will automatically distribute the monitoring load evenly between themselves. If one Monitoring Service fails, the remaining Monitoring Service(s) will pickup the load automatically. See the Load Balancing and Fault Tolerance topic in the SQL Sentry User Guide for more details. INCREASED FAULT TOLERANCE FOR THE SQL SENTRY DATABASE If increased fault tolerance is required for the SQL Sentry Database, we recommend installing the database on a clustered SQL Server instance. Log shipping can also be used with the SQL Sentry Database, however a separate SQL Sentry license is required for the standby server. Customers can obtain this standby license by visiting our Customer Portal and modifying the Server name of their current license key to the name of the standby server and applying this license key to the SQL Sentry Database on the standby server.
9 SQL Sentry Quick Start 9 6 System Requirements SQL SENTRY COMPONENTS SQL Sentry Client computer Windows version from supported list below Microsoft.NET 4.5 (included in the setup package) Minimum Single 1.6 GHz CPU, 1 GB RAM SQL Sentry Monitoring Service computer Windows version from supported list below Microsoft.NET 4.5 (included in the setup package) Minimum Dual 1.6 GHz CPUs, or 1.6 GHz multi-core CPU, 1 GB RAM SQL Sentry Database SQL Server 2005 (Service Pack 2), Standard and Enterprise SQL Server 2008, Standard and Enterprise SQL Server 2008 R2, Standard and Enterprise SQL Server 2012, Standard, BI, and Enterprise SQL Server 2014 RTM Minimum Dual 1.6 GHz CPUs, or 1.6 GHz multi-core CPU, 2 GB RAM (4 GB RAM when running both Event Manager and Performance Advisor) Disk Space: 3GB (8GB when running both Event Manager and Performance Advisor) IMPORTANT: These system requirements are the minimum recommended requirements for a standard 5-server installation. When monitoring more than 5 servers with SQL Sentry, additional RAM and disk space may be needed for the database server. See the SQL Sentry Overhead Analysis document and the Performance Advisor Data Capacity Planning topic for more details. NOTE: For performance reasons, it is not recommended that the SQL Sentry Client, Monitoring Service, or SQL Server (including the instance housing the SQL Sentry Database) be run simultaneously on the same single CPU computer. However, the Monitoring Service may perform satisfactorily on one CPU if there are no other CPU intensive programs or services operating on the same system, such as SQL Server. Additional factors include the number of instances being monitored and the number of objects on those instances. SUPPORTED OPERATING SYSTEMS Supported Operating Systems (x86) Windows Server 2008 Windows Vista Windows 7
10 SQL Sentry Quick Start 10 Windows 8 Supported Operating Systems (x64) Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Windows Vista Windows 7 Windows 8 WATCHED CONNECTIONS Watched (monitored) SQL Server instances SQL Server 2000, both 32-bit and 64-bit (Windows Server 2003 or higher) SQL Server 2005, both 32-bit and 64-bit SQL Server 2008, both 32-bit and 64-bit SQL Server 2008 R2 SQL Server 2012 SQL Server 2014 RTM NOTE: SQL Sentry does not support monitoring any version of SQL Server Express Edition. Watched (monitored) SharePoint instances SharePoint Server 2010 All Editions Watched (monitored) Windows connections Windows Server 2003 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Windows XP Windows Vista Windows 7 Windows 8 Note: You may monitor the individual Windows machines which are part of a Windows Cluster, but neither Performance Advisor for Windows or Event Manager for Windows is cluster aware. FEATURES WITH ADDITIONAL REQUIREMENTS Deadlock tab and associated data in Performance Advisor for SQL Server is available on SQL 2005 and higher Execution plan collection requires SQL 2005 SP2 or higher
11 SQL Sentry Quick Start 11 Monitoring Analysis Services with Performance Advisor requires SQL Server 2005 or higher Indexes tab and Fragmentation Manager require SQL Server 2005 or higher Monitoring the Windows Event Log with Event Manager for Windows is only supported for Windows Vista or higher Watched (monitored) Windows instances Windows Server 2003 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows XP Windows Vista Windows 7 Windows 8 NOTE: Windows Vista introduced Task Scheduler 2.0. Task Scheduler 2.0 is backwards compatible with Task Scheduler 1.0, however, Task Scheduler 1.0 is not forwards compatible with Task Scheduler 2.0. For this reason, in order to Watch or Synchronize Task Scheduler 2.0 connections, you must have a SQL Sentry Monitoring Service and SQL Sentry Client running Windows Vista or higher. Windows 8 and Windows 2012 also introduced changes to Task Scheduler. In order to Watch or Synchronize Windows 8 and Windows Server 2012 connections, you must have a SQL Sentry Monitoring Service and SQL Sentry Client running Windows 8 or Windows Watched (monitored) Oracle instances Oracle 9i Oracle 10g Oracle 11g NOTE: SQL Sentry's Oracle support requires the Oracle client connection software to be installed on each SQL Sentry Client machine and on each SQL Sentry Server machine. The full Oracle client, including the Oracle Data Access Components (ODAC) and Oracle Data Provider (ODP) components, is required.
12 SQL Sentry Quick Start 12 7 Installation and Setup Steps Once you receive your license and setup file download information, copy the setup executable to the server on which you want to install the SQL Sentry Monitoring Service and then run it. If you are upgrading SQL Sentry from a previous version, it is strongly recommended that you backup your SQL Sentry Database prior to beginning the process. Follow these steps: 1. Install SQL Sentry 2. Complete the Setup Wizard 3. Start Using the Client 7.1 Step 1: Install SQL Sentry A Welcome dialog will be displayed when the SQL Sentry Setup program is first started, click Next to continue or Cancel to exit. The License Agreement dialog is displayed next, select the checkbox and click Next to continue. For future reference, a copy of the license file is located in the "Client" folder of the installation. If the setup program detects that SQL Sentry is already installed it will prompt for removal. The installation process enables you to easily upgrade from previous versions and maintain all of your existing configuration settings, including any Users and Groups, notification settings, etc. Any time SQL Sentry is upgraded or another component is installed, the existing software is first uninstalled. This is to ensure that all components are of the latest version, and therefore compatible. This only applies to the Client and Server files; the SQL Sentry Database, where all of your settings and history are kept, is not removed. NOTE:.NET Framework 4.5 is required for all installations. A reboot may be required if the.net Framework files are in use. Temporarily stopping any applications that make use of the.net Framework can help to avoid a reboot. A. CHOOSE THE COMPONENTS DETERMINE THE MONITORING SERVICE COMPUTER For the initial installation it is recommended that you first determine which computer the Monitoring Service will be installed on and then install both the SQL Sentry Monitoring Service and Client together on that computer. This is analogous to installing the native client tool and SQL Server on the same computer. Even if you don't plan on using the SQL Sentry Client regularly from this machine, the SQL Sentry Client is used to enter your license key and will enable you to complete the licensing process during the initial installation. You will be prompted to launch the SQL Sentry Client and enter your license key at the end of the install. DBA WORKSTATION COMPUTERS
13 SQL Sentry Quick Start 13 Only one Monitoring Service is required for your SQL Sentry Enterprise. Unless desired, there is no need to install a Monitoring Service on any DBA workstation machines. To install just the SQL Sentry Client do the following: On the Custom Setup screen, select the drop down arrow next to the Monitoring Service component and choose the Entire feature will be unavailable option. For more information about where components are typically installed see the Installation Recommendations topic. B. CHOOSE THE INSTALL LOCATION Setup will show the default install location; click Next to use the default location. To install to a different location, click Browse... then select the appropriate location. C. SQL SENTRY DATABASE ACCOUNT INFORMATION On the Database Account Information screen you will chose a location and name for the SQL Sentry Database. In the SQL Server Name field enter the the server instance where you would like to install the SQL Sentry Database. In the Database Name field enter a name for the SQL Sentry Database. The SQL Sentry Database will be created as part of the installation process. If the Windows user account you are using for the installation does not have SysAdmin privileges on the selected SQL Server, deselect the "Windows Authentication" and enter a SQL Server login and password for an account with SysAdmin privileges. If you are upgrading, specify the existing SQL Sentry Database. All the necessary schema changes will be applied to the existing database.
14 SQL Sentry Quick Start 14 Click the Test button to validate the chosen credentials. After a successful test, click the Next button to continue the setup. Note: If an existing database has been selected, clicking test will ask you to confirm that you want to upgrade the database. D. SERVICE ACCOUNT INFORMATION At the Service Account Information screen you will enter the Windows account under which the SQL Sentry Monitoring Service will run. This account must have SysAdmin privileges on each watched SQL Server. The account must also have Windows Administrator privileges on any computer with a watched Windows Task Scheduler connection, or to collect system level performance metrics with SQL Sentry Performance Advisor. Note: It is not necessary for this account to be a Domain administrator account. Instead, it is recommended that the service account be a standard user Domain account that has been added to the local Administrators group of each monitored target. For more information please see the Performance Advisor Security Requirements topic.
15 SQL Sentry Quick Start 15 For information on SQL Sentry Monitoring Service security settings see the SQL Sentry Security topics. Click the Test button to validate the chosen credentials. After a successful test, click the Next button to continue the setup. Note: You can change the service account any time after the initial installation by runningtrue the Service Configuration Utility found in the SQL Sentry program group. E. INSTALL On the Ready to install SQL Sentry screen, click Install to begin installation. F. COMPLETE SETUP Click Finish to complete setup and launch SQL Sentry. Note: If you have not installed the SQL Sentry Client, you will not see the Launch option. You will need to install the SQL Sentry Client on another machine and run it in order to enter your license key and complete the licensing process. If you have upgraded an existing installation of SQL Sentry, running the Setup Wizard is not required. All previous settings have been retained.
16 SQL Sentry Quick Start 16 Click below to proceed: Step 2: Complete the Setup Wizard 7.2 Step 2: The Setup Wizard LAUNCH THE SQL SENTRY CLIENT The first time you launch the SQL Sentry Client, you will see the License Not Found message box. Click OK and you will be prompted to enter your license key. At the License Entry screen, you can either paste your license key or drag-and-drop the license file into the large text box. Click Save to continue. Once the license has been validated the SQL Sentry Client will launch. RUN THE SETUP WIZARD With a new install, the first time the Client is started, the Setup Wizard is automatically launched. The wizard will quickly walk you through the initial configuration steps. You can run the wizard again at any time from the Help menu of the Client to add new users or adjust certain global settings. 1. ALERTING SETTINGS In the SMTP Server field enter the domain name or IP address of the SMTP server to be used for routing SQL Sentry notifications. If using localhost, keep in mind this will be the local SMTP server on the machine where the SQL Sentry Monitoring Service is installed since it is responsible for sending all notifications. The SQL Sentry Client does not send any notifications. Note: This step can be skipped and configured later by unchecking the Enable Alerts box.
17 SQL Sentry Quick Start 17 Note: You may need to contact your network administrator first to ensure that the IP address of the Monitoring Service computer has been granted both Connect and Relay permissions for the specified SMTP server. Next, enter the From Address. This is the address which will appear on the From line of all notifications sent by SQL Sentry. You can also specify a Username and Password if authentication is required by your SMTP server. This is not usually required in most environments. Click the Test button to generate a test to a specific address. Important: For the most accurate SMTP test, you should use the Client installed on the SQL Sentry Monitoring Service computer to send the test message. If you use a Client on a different computer, such as your local workstation, the results may be different. For example, your SMTP server may allow relay from your workstation but not from the SQL Sentry Monitoring Service computer, in which case the test from your workstation would succeed but the SQL Sentry Monitoring Service would be unable to deliver notifications. At least one user is required for SQL Sentry to be able to send notifications. Enter the user's address and name and then click Next to continue. Note: Tokens are disabled by default in SQL Server 2005 and higher. They must be enabled in
18 SQL Sentry Quick Start 18 order to monitor SQL Server Agent Alerts with SQL Sentry. See SQL Server Books Online for more information on tokens and security. 2. SELECT CONNECTIONS TO WATCH On the Select Connections to Watch screen the Add Connection dialogue will be displayed. Use the Connection Type drop-down box to choose your connection type. Enter the server name or the server name\instance name and click the Connect button to add the connection. To add additional connections that you would like to monitor use the Add button. After you have added all the connections that you want SQL Sentry to watch, click Next to continue. Note: For each connection type you can select up to the number of connections allowed by your license. 3. CONFIRM SETTINGS Click Execute to confirm settings and continue 4. SETUP PROGRESS The Setup Progress dialog will show the status as the wizard settings are applied and watched connections are synchronized for the first time. If any errors occur, click the button for that step to access the error details. At least one connection must be synchronized successfully in order to complete the wizard, at which time the Next button will be enabled. Important: FINISHED If errors occur while synchronizing with one or more connections, it may be due to problems with security, network connectivity, and/or name resolution. See the topic Security and the SQL Sentry Server for more details. You can click Back to return to the "Select Connections" dialog, either resolve the problems or deselect the problem connections, then click Next to retry the process again. If there is an error during the SMTP Connectivity test you will be able to complete the wizard, however, SQL Sentry will not be able to deliver or pager alerts until the problem is resolved. If you need to adjust the SMTP settings, you can click Back a few times to return to the "SMTP Settings" dialog and make the necessary changes and test them, then proceed back through the wizard. You have successfully configured SQL Sentry when the final confirmation dialog displays. Please refer to Additional Tasks for additional configuration options. Click Finish to start using the Client. Click below to proceed: Step 3: Start Using the Client!
19 SQL Sentry Quick Start Step 3: Start Using the Client Congratulations, you have successfully installed SQL Sentry, configured global notification settings, and are now ready to start using the SQL Sentry Client for managing events across your enterprise. Use the different options on the Get Started screen to start exploring the features in SQL Sentry. Please refer to the SQL Sentry User Guide available online and through the Client Help menu, for additional information about available features. MAINTENANCE Just as with any other SQL Server database, it is important that regular maintenance activities be performed on the SQL Sentry database to ensure optimal performance. Please see the SQL Sentry Database Maintenance topic in the SQL Sentry User Guide for more details and recommendations.
20 SQL Sentry Quick Start 20 8 Additional Tasks Overview ADDITIONAL TASKS Refer to these topics for additional information on configuring SQL Sentry. Add Additional Users and Groups Monitor Additional Connections Customize Global Settings 8.1 Add Users and Groups The Contacts node in the Navigator contains the Users and Groups sub-nodes. This is where you create and maintain Users and Groups for notification purposes. At least one user is required for SQL Sentry to be able to send notifications. Click the Users node to add a new user. Enter the user's name, address, optional pager address (SMTP-based), and an optional description. You can add as many users and groups as you want at this point - groups are optional. Click Save when you are finished adding each user. For more information about Users and Groups see the Contact Management topic in the SQL Sentry User Guide. 8.2 Monitor Additional Connections ADDING CONNECTIONS You can easily add additional monitored Connections to your SQL Sentry environment. This is accomplished by right-clicking either the Shared Groups node, a Site node, a Computer Group node, or an existing Computer node in the Navigator pane and using the Add Connection command. You can also add a Connection through the File menu. In the Add Connection dialog you may choose the desired Connection Type from the drop-down menu (Analysis Services Connection, SharePoint Server Connection, SQL Server Connection, Windows Connection, Oracle Database Connection). WATCHING CONNECTIONS When you add a new Connection to your environment the Watch With Event Manager / Performance Advisor options are checked by default. Before SQL Sentry will start monitoring a Connection or object, its status must be set to watched. Connections or objects that are not being watched will be displayed with a grayed-out icon next to their name in the Navigator tree view. Unwatched Connections or objects can have their status set to watched through their respective context menus with the Watch command. Once you have watched a new Connection the SQL Sentry Monitoring Service will start actively monitoring the Connection and its objects, and begin honoring
21 SQL Sentry Quick Start 21 any associated configured Conditions and Actions. Note: Immediately after adding a Connection or setting a Connection to watched status, SQL Sentry will begin to synchronize with that Connection. Exactly how long the synchronization process takes depends on the number of objects associated with the Connection, the amount of historical data available, and how many Connections are being watched at the same time. The Watch Status Window will keep you informed of the process and alert you about any errors. 8.3 Introduction to Actions and Settings When you run the Setup Wizard a number of global Settings are configured for your installation. If you entered your SMTP Settings and added a User, a number of default Conditions and Actions were also added to help you get up and running quickly. As a reminder, the Wizard can be accessed through the Help menu at any time. Before proceeding you should introduce yourself with these basic SQL Sentry Alerting and Response System concepts. Conditions Conditions describe the various states of any monitored objects. Actions Settings Actions determine what happens when a Condition is met. Settings define criteria for when a Condition is considered to be met. Certain Settings known as Source Settings are used to define what events are collected by SQL Sentry. There are a couple of ways to see how Settings and Conditions/Actions are configured for your SQL Sentry installation. You can use the Reports menu to run the Active Settings List and the Configured Actions List reports. (Reports menu > General) Or you can view configured Actions and Settings directly in the Actions and Settings Pane. By default the Actions and Settings pane is displayed on the right side of the SQL Sentry Client. If you do not see the Actions and Settings pane, it can be restored with the View menu. If you would like to configure global Actions or Settings, be sure that the Shared Groups node is selected in the Navigator pane. The Shared Groups node is the global or root node of your SQL Sentry installation. The SQL Sentry Alerting and Response System uses the principle of inheritance, so any Action or Setting you configure at the Shared Groups node will be passed down to all applicable objects below it. For example, if you configure a Send Action for the SQL Server Agent Job: Failure Condition at the global level (Shared Groups), you will receive an anytime a SQL Server Agent job fails across your entire monitored enterprise. You can further refine Actions or Settings at each level, as needed. For instance, if you have a development server in your environment that you don't wish to be alerted about, you can easily
Dell Archive Manager 5.1.1 2014 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license
Software used by portions of this application require the following license statement: [The BSD License] Copyright (c) 2004-2011 Jaroslaw Kowalski firstname.lastname@example.org All rights reserved. Redistribution
Concentsus Online Backup User Manual Concentsus Small Business 5252 Edgewood Drive, Suite 250 Provo, UT 84604 888-889-9949 www.concentsus.com 2008 Concentsus, a service of efilecabinet, LC All Rights Reserved.
Installation and Upgrade Guide Copyright Statement Copyright Acronis International GmbH, 2002-2014. All rights reserved. Acronis and Acronis Secure Zone are registered trademarks of Acronis International
NovaBACKUP User Manual NovaStor / May 2014 2014 NovaStor, all rights reserved. All trademarks are the property of their respective owners. Features and specifications are subject to change without notice.
LogMeIn Backup User Guide Contents About LogMeIn Backup...4 Getting Started with LogMeIn Backup...5 How does LogMeIn Backup Work, at-a-glance?...5 About Security in LogMeIn Backup...5 LogMeIn Backup System
Table of contents General 2 First steps 4 Installation 11 G Data ManagementServer 13 G Data Administrator 18 G Data AntiVirus Client 83 G Data WebAdministrator 88 G Data Firewall 90 Attachment 100 1 General
Getting Started Guide StarTeam Borland Software Corporation 100 Enterprise Way Scotts Valley, California 95066-3249 www.borland.com Borland Software Corporation may have patents and/or pending patent applications
Journyx Technical Document System Administration and Disaster Recovery Guide For Journyx Timesheet version 8.7m5 Document Version: 3.0.9 (January 2012) for version 8.7m5 For product versions prior to 8.7m5
Allworx OfficeSafe Operations Guide Release 6.0 No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopy,
NVR 3.0 System Administrator s Manual For V3.0.02 Version 2013/03/21 About This Manual Target Audience This manual is intended for System Administrators who are responsible for installing and setting up
Richmond SupportDesk Web Reports Module For Richmond SupportDesk v6.72 User Guide Contents 1 Introduction... 4 2 Requirements... 5 3 Important Note for Customers Upgrading... 5 4 Installing the Web Reports
Managed Workplace 2012 Setup Guide On Premise See All. Manage All. Service All. www.levelplatforms.com TABLE OF CONTENTS Welcome... vii About this Document... viii Where To Get More Help... viii Contact
Yosemite Server Backup User s Guide Part number: First edition: October 2010 Legal and notice information Copyright 2004, 2012 Barracuda Networks, Inc. Under copyright laws, the contents of this document
Installation and Upgrade Guide for Primavera Portfolio Management 8.0 Copyright 1999-2010, Oracle and/or its affiliates. The Programs (which include both the software and documentation) contain proprietary
Page 1 of 78 Features - NAS NDMP Client TABLE OF CONTENTS OVERVIEW SYSTEM REQUIREMENTS - NAS NDMP IDATAAGENT INSTALLATION Install the MediaAgent - Windows Install the MediaAgent - Windows -Clustered Environment
SYMANTEC ServiceDesk Customization Guide 7.0 Symantec ServiceDesk 7 The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement.
Page 1 of 86 Features - NAS NDMP Client Table of Contents Overview System Requirements - NAS NDMP idataagent Installation Install the MediaAgent - Windows Install the MediaAgent - Windows -Clustered Environment
Dell KACE K1000 Management Appliance Service Desk Administrator Guide Release 5.3 Revision Date: May 13, 2011 2004-2011 Dell, Inc. All rights reserved. Information concerning third-party copyrights and
Basic System Administration ESX Server 3.0 and VirtualCenter 2.0 Basic System Administration Revision: 20090213 Item: VI-ENG-Q206-219 You can find the most up-to-date technical documentation at: http://www.vmware.com/support/pubs
Canto Cumulus 5.5 Workgroup Edition Administrator Guide An administrator s guide to the Canto Cumulus Digital Asset Management System. 290 Division Street, Suite 400 San Francisco, CA 94103 U.S.A. Voice: