DOCSLIB.ORG

Zz-Cryptoprevent-Do

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Zz-Cryptoprevent-Do REPLAY 4 ADMINISTRATOR’S GUIDE Copyright 2009/2010 by AppAssure Software , Inc. ALL RIGHTS RESERVED. No part of this work covered by the copyright hereon may be reproduced or used in any form or by any means — graphic, electronic, or mechanical, including photocopying, recording, taping, Web distribution or information storage and retrieval systems — without the written permission of the publisher. For permission to use material from this publication, contact AppAssure Software, Inc. 1925 Isaac Newton Square, Suite 440 Reston, VA 20190 +1 703-547-8686 [email protected] Replay 4 Administrator’s Guide ii Contents Chapter One: Introduction ............................................................. 1 REPLAY 4 .......................................................................................................................................................... 1 Chapter One: Introduction ........................................................................................................................ 1 What Is In This Guide ......................................................... 1 About Replay 4 ................................................................... 1 What you get with Replay 4 .............................................. 2 What's New in Replay 4? ................................................... 2 Replication for Off-site Backup and Disaster Recovery .............................................. 2 New Enterprise Console ............................................................................................................ 3 Added Support for Hyper-V R2, Windows 7 and Windows Server R2 Platforms and VMware vSphere ............................................................................................ 4 Expanded Flexibility for Single-server and Enterprise implementations ............ 4 Replay for Windows Servers ............................................. 5 Features ............................................................................................................................................ 5 Replay for Exchange........................................................... 6 Features ............................................................................................................................................ 6 Replay for SQL .................................................................... 7 Features ............................................................................................................................................ 8 Replay for Hyper-V ............................................................ 9 Features: ........................................................................................................................................... 9 Replay for SharePoint ...................................................... 10 Replay for Desktops ......................................................... 11 Restore to Dissimilar Hardware Option ......................... 12 Replay Replication ............................................................ 12 Features & Benefits .................................................................................................................. 13 Replay Replication Topologies ........................................................................................... 13 Replay 4 Administrator’s Guide iii Contents 1 : 1 Configuration .............................................................................................................. 13 Many : 1 Configuration ..................................................................................................... 14 Many: Many Configuration ............................................................................................. 14 Chapter Two: System Overview & Requirements ...................................................................... 15 Architecture ....................................................................... 15 Planning a Replay Deployment ....................................... 16 Single Protected Server Deployment ............................................................................... 16 Technical Considerations ................................................................................................. 16 Exchange Cluster Deployment ............................................................................................ 17 Distributed Server Deployment .......................................................................................... 17 Repository Storage Recommendations..................................................................... 18 Calculate Space Requirements .................................................................................... 18 Sample Environment ..................................................................................................... 19 Pre-Installation Requirements ........................................ 20 Software Requirements .......................................................................................................... 20 Security Requirements ............................................................................................................ 21 Network Requirements........................................................................................................... 22 Distributed Cores Running on Physical Hardware ..................................................... 22 Single Message Recovery Requirements ....................................................................... 24 Exchange Cluster Deployment Requirements .............................................................. 24 Exchange 2010 Deployment Requirements .................................................................. 24 Using Replay on Exchange Mailbox Role Servers ................................................. 25 Using Replay on Database Availability Group Members................................... 25 Necessary updated firmware and drivers ...................................................................... 26 SAN .................................................................................................................................................. 26 Obtaining Assistance or Support .................................... 27 Contacting the AppAssure Support Center by Telephone ..................................... 27 E-mail Support ........................................................................................................................... 27 Phone Support ........................................................................................................................... 27 Chapter Three: Installing Replay.......................................................................................................... 28 Preparing for Installation ................................................ 28 Creating the Replay Service Account ............................................................................... 28 Adding the Replay service account to local administrators group .................... 33 Replay 4 Administrator’s Guide iv Contents Assigning Local Server Rights to the Replay Core Service Account .................. 34 Delegating Administrative Permissions to the Replay Service Account’s ReplayAdmin Role in MS Exchange 2003 ...................................................................... 34 Granting Server Level Permissions for MS Exchange 2003 Servers ................... 35 Granting Permissions to Exchange 2003 Mailbox Store(s) .................................... 35 Assigning the Exchange Administrator Role in MS Exchange 2007 .................. 36 Installing REPLAY 4 .......................................................... 37 Install the Replay Core ............................................................................................................ 38 Install the Replay Agent Using the Installer .................................................................. 43 Install the Replay Agent from the Replay Core ........................................................... 52 If both computers are in the same domain: ............................................................ 52 User permissions ............................................................................................................ 52 Firewall settings .............................................................................................................. 52 UAC ...................................................................................................................................... 52 If one machine is in a workgroup and the other machine is in a domain: 52 User permissions: ........................................................................................................... 52 Firewall settings: ............................................................................................................. 52 UAC: ..................................................................................................................................... 52 How to enable “Remote Administration” ................................................................. 53 Windows 2008/Vista ......................................................................................................... 53 Windows 2008 R2/Windows 7 ..................................................................................... 53 Local Policy ......................................................................................................................
Load more

Recommended publications
  • SQL Server Protection Whitepaper
    SQL Server Protection Whitepaper Contents 1. Introduction ..................................................................................................................................... 2 Documentation .................................................................................................................................................................. 2 Licensing ............................................................................................................................................................................... 2 The benefits of using the SQL Server Add-on ....................................................................................................... 2 Requirements ...................................................................................................................................................................... 2 2. SQL Protection overview ................................................................................................................ 3 User databases ................................................................................................................................................................... 3 System databases .............................................................................................................................................................. 4 Transaction logs ................................................................................................................................................................
    [Show full text]
  • How to Conduct Transaction Log Analysis for Web Searching And
    Search Log Analysis: What is it; what’s been done; how to do it Bernard J. Jansen School of Information Sciences and Technology The Pennsylvania State University 329F IST Building University Park, Pennsylvania 16802 Email: [email protected] Abstract The use of data stored in transaction logs of Web search engines, Intranets, and Web sites can provide valuable insight into understanding the information-searching process of online searchers. This understanding can enlighten information system design, interface development, and devising the information architecture for content collections. This article presents a review and foundation for conducting Web search transaction log analysis. A methodology is outlined consisting of three stages, which are collection, preparation, and analysis. The three stages of the methodology are presented in detail with discussions of goals, metrics, and processes at each stage. Critical terms in transaction log analysis for Web searching are defined. The strengths and limitations of transaction log analysis as a research method are presented. An application to log client-side interactions that supplements transaction logs is reported on, and the application is made available for use by the research community. Suggestions are provided on ways to leverage the strengths of, while addressing the limitations of, transaction log analysis for Web searching research. Finally, a complete flat text transaction log from a commercial search engine is available as supplementary material with this manuscript. Introduction Researchers have used transaction logs for analyzing a variety of Web systems (Croft, Cook, & Wilder, 1995; Jansen, Spink, & Saracevic, 2000; Jones, Cunningham, & McNab, 1998; Wang, 1 of 42 Berry, & Yang, 2003). Web search engine companies use transaction logs (also referred to as search logs) to research searching trends and effects of system improvements (c.f., Google at http://www.google.com/press/zeitgeist.html or Yahoo! at http://buzz.yahoo.com/buzz_log/?fr=fp- buzz-morebuzz).
    [Show full text]
  • How to Cheat at Windows System Administration Using Command Line Scripts
    www.dbebooks.com - Free Books & magazines 405_Script_FM.qxd 9/5/06 11:37 AM Page i How to Cheat at Windows System Administration Using Command Line Scripts Pawan K. Bhardwaj 405_Script_FM.qxd 9/5/06 11:37 AM Page ii Syngress Publishing, Inc., the author(s), and any person or firm involved in the writing, editing, or produc- tion (collectively “Makers”) of this book (“the Work”) do not guarantee or warrant the results to be obtained from the Work. There is no guarantee of any kind, expressed or implied, regarding the Work or its contents.The Work is sold AS IS and WITHOUT WARRANTY.You may have other legal rights, which vary from state to state. In no event will Makers be liable to you for damages, including any loss of profits, lost savings, or other incidental or consequential damages arising out from the Work or its contents. Because some states do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you. You should always use reasonable care, including backup and other appropriate precautions, when working with computers, networks, data, and files. Syngress Media®, Syngress®,“Career Advancement Through Skill Enhancement®,”“Ask the Author UPDATE®,” and “Hack Proofing®,” are registered trademarks of Syngress Publishing, Inc.“Syngress:The Definition of a Serious Security Library”™,“Mission Critical™,” and “The Only Way to Stop a Hacker is to Think Like One™” are trademarks of Syngress Publishing, Inc. Brands and product names mentioned in this book are trademarks or service marks of their respective companies.
    [Show full text]
  • Copyrighted Material
    2986IDX.qxd 9/6/01 12:12 AM Page 425 Index Note to the reader: Throughout this index boldfaced page numbers indicate pri- mary discussions of a topic. Italicized page numbers indicate illustrations. A for Local Users and Groups, 171 in Shared Folders, 333 abstracts, from Indexing Service, 140 Active Directory, 7–8 Accessibility, 2–6 for adding programs, 12 Internet Explorer options, 157 ActiveX controls, security settings for, 158 Magnifier, 176–177 Add Counters dialog, 257, 257–258 Narrator, 195–196 Add Excluded Files dialog On-Screen Keyboard, 234, 234–235 (Backup), 35 Options window, 2, 2–3 Add Hardware Wizard, 8–10, 350–351 Utility Manager, 385–386, 386 Add or Remove Programs, 10–13 Accessibility Options dialog, Keyboard address bar tab, 3, 3–4 in Explorer, 101–102, 102 Accessories, 6 in Internet Explorer, 149 Calculator, 37–38 Address Book, 13–25 Command Prompt, 46, 46–47 contact template, 20 Communications, 47 creating contacts, 16–17 Entertainment program group, 92 folders, 22–23 Program Compatibility Wizard, 288, 288–289 groups, 20–22 System Tools, 366. See also Backup identities for, 24–25 Character Map, 40 menus, 15–16 Disk Cleanup, 69–71, 71 retrieving e-mail addresses from, 241 Disk Defragmenter, 71–75 searching for people in, 325–326 File and Settings Transfer toolbar, 14, 15 Wizard, 112 window, 14 Scheduled Tasks, 316, 316–322 Address toolbar, 367 System Information, 361–363COPYRIGHTEDAdministrative Tools, MATERIAL 25–26. See also System Restore, 364, 364–365 Microsoft Management Console (MMC) snap-ins Windows Explorer, 97, 97–106 Active Directory, 7–8 Windows Movie Maker, 406–414, 407 for adding programs, 12 Action menu COM+ (Component Services), 45 for Device Manager, 59–63 Data Sources (ODBC), 51–55 425 2986IDX.qxd 9/6/01 12:12 AM Page 426 ADMINISTRATOR ACCOUNT Event Viewer, 93, 93–96, 94 attrib command, 291 Local Security Policy, 168, 168–170, AU files, 396 168–170 audio.
    [Show full text]
  • Destiny® System Backups
    Destiny® system backups Establishing a backup and restore plan for Destiny Overview It is important to establish a backup and restore plan for your Destiny installation. The plan must be validated and monitored to ensure that your data is sufficiently backed up and can be recovered in the event of hardware failure or other disaster. IMPORTANT Follett recommends deploying a comprehensive backup solution and testing and monitoring all backup processes. There are tradeoff decisions to be made in the backup strategy that will be shaped by your organization’s risk tolerance, technology constraints, and ability to absorb data loss or downtime. This document provides an overview of standard backup and restore for the Destiny system. IMPORTANT This content does not cover high-availability configurations such as clustered servers or log shipping. Please contact Follett School Solutions, Inc. Technical Support should you have any questions about backing up your Destiny installation. For details, see Destiny® system backups. Backing up Destiny: an overview SQL database The heart of the Destiny data resides in the SQL database. These are the main components of SQL data to be backed up: The Destiny SQL database. This database contains the main Destiny data. Proper SQL backup configuration of this database is essential. NOTE If your installation is a consortium, you will have to ensure a proper backup of multiple SQL databases (one per member). The Destiny SQL transaction log. The Master SQL database. This system database is useful when restoring to a replacement server. It is not necessary to back up the tempdb database. This is a SQL Server work area and is recreated automatically.
    [Show full text]
  • Infosphere MDM Collaboration Server: Installation Guide
    IBM InfoSphere Master Data Management Collaboration Server Version 11.6 Fix Pack 15 Installation Guide IBM Note Before using this information and the product that it supports, read the information in “Notices” on page 159. Edition Notice This edition applies to version 11.6 of IBM® InfoSphere® Master Data Management and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2000, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Planning to install.................................................................................1 Installation scenarios.................................................................................................................................. 1 Installation and configuration worksheets................................................................................................. 3 Installation directory worksheet............................................................................................................3 IBM Db2 data source worksheet............................................................................................................4 Oracle data source worksheet............................................................................................................... 5 WebSphere Application Server installation worksheet.........................................................................6
    [Show full text]
  • The Recovery Console Content
    The Recovery Console Content 1. Common .....................................................................................................................3 2. Invoke the Recovery Console......................................................................................3 2.1. Start from Media...................................................................................................3 2.2. Start using RIS .....................................................................................................4 2.3. Installation ............................................................................................................5 2.3.1. Attended ........................................................................................................5 2.3.2. Un-attended...................................................................................................6 2.4. Un-installation.......................................................................................................6 2.5. Windows NT 4.0 ...................................................................................................6 2.6. 64-bits ..................................................................................................................7 3. Commands..................................................................................................................7 3.1. Commands In-depth ...........................................................................................10 3.1.1. BOOTCFG...................................................................................................10
    [Show full text]
  • Database Management Systems Introduction Transaction ACID
    Introduction What is Concurrent Process (CP)? • Multiple users access databases and use computer Database Management systems simultaneously. • Example: Airline reservation system. Systems œ An airline reservation system is used by hundreds of travel agents and reservation clerks concurrently. Transaction, Concurrency and Why Concurrent Process? Recovery • Better transaction throughput and response time • Better utilization of resource Adapted from Lecture notes by Goldberg @ Berkeley Transaction ACID Properties of transaction • What is Transaction? • Atomicity: Transaction is either performed in its entirety or not performed at all, this should be DBMS‘ • A sequence of many actions which are responsibility considered to be one atomic unit of work. • Consistency: Transaction must take the database • Basic operations a transaction can include from one consistent state to another if it is executed in —actions“: isolation. It is user‘s responsibility to insure consistency œ Reads, writes • Isolation: Transaction should appear as though it is œ Special actions: commit, abort being executed in isolation from other transactions • Durability: Changes applied to the database by a committed transaction must persist, even if the system fail before all changes reflected on disk Concurrent Transactions Schedules • What is Schedules œ A schedule S of n transactions T1,T2,…Tn is an ordering of the B B operations of the transactions subject to the constraint that, for each transaction Ti that participates in S, the operations of Ti in Smust CPU2 A appear in the same order in which they occur in Ti. CPU A 1 œ Example: Sa: r1(A),r2(A),w1(A),w2(A), a1,c2; CPU1 T1 T2 time Read(A) Read(A) t1 t2 t1 t2 Write(A) interleaved processing parallel processing Write(A) Abort T1 Commit T2 1 Oops, something‘s wrong Another example • Reserving a seat for a flight • Problems can occur when concurrent transactions execute in an uncontrolled manner.
    [Show full text]
  • Data Definition Language (Ddl)
    DATA DEFINITION LANGUAGE (DDL) CREATE CREATE SCHEMA AUTHORISATION Authentication: process the DBMS uses to verify that only registered users access the database - If using an enterprise RDBMS, you must be authenticated by the RDBMS - To be authenticated, you must log on to the RDBMS using an ID and password created by the database administrator - Every user ID is associated with a database schema Schema: a logical group of database objects that are related to each other - A schema belongs to a single user or application - A single database can hold multiple schemas that belong to different users or applications - Enforce a level of security by allowing each user to only see the tables that belong to them Syntax: CREATE SCHEMA AUTHORIZATION {creator}; - Command must be issued by the user who owns the schema o Eg. If you log on as JONES, you can only use CREATE SCHEMA AUTHORIZATION JONES; CREATE TABLE Syntax: CREATE TABLE table_name ( column1 data type [constraint], column2 data type [constraint], PRIMARY KEY(column1, column2), FOREIGN KEY(column2) REFERENCES table_name2; ); CREATE TABLE AS You can create a new table based on selected columns and rows of an existing table. The new table will copy the attribute names, data characteristics and rows of the original table. Example of creating a new table from components of another table: CREATE TABLE project AS SELECT emp_proj_code AS proj_code emp_proj_name AS proj_name emp_proj_desc AS proj_description emp_proj_date AS proj_start_date emp_proj_man AS proj_manager FROM employee; 3 CONSTRAINTS There are 2 types of constraints: - Column constraint – created with the column definition o Applies to a single column o Syntactically clearer and more meaningful o Can be expressed as a table constraint - Table constraint – created when you use the CONTRAINT keyword o Can apply to multiple columns in a table o Can be given a meaningful name and therefore modified by referencing its name o Cannot be expressed as a column constraint NOT NULL This constraint can only be a column constraint and cannot be named.
    [Show full text]
  • Transaction Processing System
    Transaction processing system From Wikipedia, the free encyclopedia (Redirected from Transaction processing systems) It has been suggested that this article or section be merged into Transaction processing. (Discuss) Proposed since November 2012. Transaction processing is a style of computing that divides work into individual, indivisible operations, called transactions.[1] Atransaction processing system (TPS) or transaction server is a software system, or software/hardware combination, that supports transaction processing. Contents [hide] 1 History 2 List of transaction processing systems 3 Processing types o 3.1 Batch processing o 3.2 Real-time processing o 3.3 Time-sharing o 3.4 Transaction processing 4 Transaction processing system features o 4.1 Performance o 4.2 Continuous availability o 4.3 Data integrity o 4.4 Ease of use o 4.5 Modular growth 5 Databases and files o 5.1 Data warehouse o 5.2 Backup procedures . 5.2.1 Recovery process . 5.2.2 Types of back-up procedures . 5.2.2.1 Grandfather- father-son . 5.2.2.2 Partial backups . 5.2.3 Updating in a batch . 5.2.4 Updating in real-time 6 See also 7 References 8 Further reading [edit]History One of the first transaction processing systems was American Airline SABRE system, which became operational in 1960. Designed to process up to 83,000 transactions a day, the system ran on two IBM 7090 computers. SABRE was migrated to IBM System/360computers in 1972, and became an IBM product first as Airline control Program (ACP) and later as Transaction Processing Facility (TPF). In addition to airlines TPF is used by large banks, credit card companies, and hotel chains.
    [Show full text]
  • System Administration Guide: Volume 1
    System Administration Guide: Volume 1 SAP® Adaptive Server® Enterprise 16.0 DOCUMENT ID: DC31654-01-1600-01 LAST REVISED: May 2014 Copyright © 2014 by SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/ index.epx#trademark for additional trademark information and notices. Contents CHAPTER 1: Overview of System Administration .......1 Roles Required for System Administration Tasks ..............1 Database Owner .............................................................3
    [Show full text]
  • Transactions – Recovery ACID Properties and Recovery
    Transactions – Recovery CS 317/387 1 ACID Properties and Recovery The Recovery Manager is responsible for ensuring Atomicity and Durability . Atomicity is guaranteed by undoing the actions of the transactions that did not commit (aborted). Durability is guaranteed by making sure that all actions of committed transactions survive crashes and failures. 2 1 Types of Failures System crashes due to hardware or software errors main memory content is lost Transaction failures overflow, interrupt, data not available, explicit rollback, concurrency enforcement, programming errors no memory loss. Media failures problems with disk head, unreadable media surface (parts of ) information on secondary storage may be lost Natural disasters fire, flood, earthquakes, theft, etc. physical loss of all information on all media 3 Strategy If a transaction Ti is aborted (e.g., for concurrency control reasons), all its actions have to be undone . Active transactions at the time of the crash have to be aborted, i.e., their effects have to be undone when the system comes back. DBMS has to maintain enough information to undo actions of transactions (the LOG File) 4 2 Desired Behavior after system restarts: T1, T2 & T3should be durable.– T4 & T5 should be rolled back, i.e., effects undone. 5 Log Sequence of records (sequential file) Modified by appending (no updating) Contains information from which database can be restored Log and database stored on different mass storage devices Often replicated to survive single media failure Contains
    [Show full text]