DOCSLIB.ORG

HP Data Protector 9.00 Integration Guide for Microsoft Volume Shadow Copy Service

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
HP Data Protector 9.00 Integration Guide for Microsoft Volume Shadow Copy Service HP Data Protector Software Version: 9.00 Integration guide for Microsoft Volume Shadow Copy Service Document Release Date: June 2014 Software Release Date: June 2014 Integration guide for Microsoft Volume Shadow Copy Service Legal Notices Warranty The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Restricted Rights Legend Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notice © Copyright 2014 Hewlett-Packard Development Company, L.P. Trademark Notices Adobe® is a trademark of Adobe Systems Incorporated. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation. UNIX® is a registered trademark of The Open Group. Documentation Updates The title page of this document contains the following identifying information: l Software Version number, which indicates the software version. l Document Release Date, which changes each time the document is updated. l Software Release Date, which indicates the release date of this version of the software. To check for recent updates or to verify that you are using the most recent edition of a document, go to: http://h20230.www2.hp.com/selfsolve/manuals This site requires that you register for an HP Passport and sign in. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html Or click the New users - please register link on the HP Passport login page. You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details. Support Visit the HP Software Support Online web site at: http://www.hp.com/go/hpsoftwaresupport This web site provides contact information and details about the products, services, and support that HP Software offers. HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to: l Search for knowledge documents of interest l Submit and track support cases and enhancement requests l Download software patches l Manage support contracts l Look up HP support contacts l Review information about available services l Enter into discussions with other software customers l Research and register for software training Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html To find more information about access levels, go to: http://h20230.www2.hp.com/new_access_levels.jsp HP Software Solutions Now accesses the HPSW Solution and Integration Portal Web site. This site enables you to explore HP Product Solutions to meet your business needs, includes a full list of Integrations between HP Products, as well as a listing of ITIL Processes. The URL for this Web site is http://h20230.www2.hp.com/sc/solutions/index.jsp HP Data Protector (9.00) Page 2 of 181 Integration guide for Microsoft Volume Shadow Copy Service Contents Contents Contents 3 Chapter 1: Introduction 9 Chapter 2: Integration concepts 10 Volume Shadow Copy Service 10 Virtual Disk Service 12 VSSBAR agent 12 Backup types 13 VSS database 15 Querying the VSSDB 16 Deleting backup sessions 16 Enabling and disabling replicas 17 Changes in the environment 17 Chapter 3: Configuration 18 Prerequisites and limitations 18 Prerequisites 18 Transportable backup prerequisites 18 Limitations 19 ZDB and instant recovery limitations 19 HP P6000 EVA Disk Array Family hardware provider limitations 20 HP P9000 XP Disk Array Family hardware provider limitations 20 Configuring the application system for instant recovery-enabled backup sessions 21 Configuring HP P4000 SAN Solutions 22 Prerequisites 22 Configuring the integration 23 Configuring the VSS hardware provider 23 Configuring HP P6000 EVA Disk Array Family 24 Prerequisites 24 Configuring the integration 25 Considerations 25 HP Data Protector (9.00) Page 3 of 181 Integration guide for Microsoft Volume Shadow Copy Service Contents Configuring the VSS hardware provider 25 Configuring HP P9000 XP Disk Array Family 26 Prerequisites 26 Configuring the VSS hardware provider 27 Configuring the user authentication data 27 Configuring HP 3PAR StoreServ Storage 28 Prerequisites 28 Configuring the Data Protector HP 3PAR StoreServ Storage integration 28 Configuring the HP 3PAR VSS hardware provider 29 Chapter 4: Backup 30 Backup types 30 Backup flow 30 Zero downtime backup with the Data Protector VSS integration 31 HP P4000 SAN Solutions 31 HP P6000 EVA Disk Array Family 32 HP P9000 XP Disk Array Family 32 HP 3PAR StoreServ Storage 33 Considerations 33 Microsoft Cluster environments and transportable backups 33 HP P4000 SAN Solutions 34 HP P6000 EVA Disk Array Family 34 Replica creation and reuse 35 HP P9000 XP Disk Array Family 35 HP 3PAR StoreServ Storage 36 Configuration check 36 Creating backup specifications 37 Backup options 42 ZDB options 42 Scheduling backup sessions 45 Starting backup sessions 47 Chapter 5: Restore 49 HP Data Protector (9.00) Page 4 of 181 Integration guide for Microsoft Volume Shadow Copy Service Contents Standard restore 49 Restore modes 49 Component restore 49 File restore 50 Restoring using the GUI 50 Restore options 52 Restoring using the CLI 52 Instant recovery 53 Instant recovery methods 55 Switch of disks 55 Copy of replica data 56 Copy of replica data with the source volume retained 56 Copy of replica data with the source volume not retained 56 Restore snapshot data to the source volume 57 Restore snapshot data to the source volume with the source volume retained 57 Restore snapshot data to the source location with the source volume not retained 58 Resync of volumes 58 Limitations 59 HP P4000 SAN Solutions considerations 59 HP P6000 EVA Array considerations 60 HP P9000 XP Array considerations 61 HP 3PAR StoreServ Storage considerations 63 Instant recovery procedure 63 Limitations 63 Procedure 63 Chapter 6: Writer specifics 70 Microsoft Data Protection Manager writer specifics 74 Backup 74 Restore 75 Restore the DPM server first 76 Restore the DPM clients directly 77 HP Data Protector (9.00) Page 5 of 181 Integration guide for Microsoft Volume Shadow Copy Service Contents Microsoft Exchange Server 2003 writer specifics 78 Backup 78 Restore 80 Rollforward recovery from the loss of one or more databases 80 Point-in-time restore after loss of a log file 81 Limitations 82 Instant recovery 82 Prerequisites 83 Post-instant recovery steps 83 Database recovery 83 User scenario for Microsoft Exchange Server 2003 backup and restore 84 Example - VSS transportable backup 84 Example restore scenario for Microsoft Exchange Server 2003 86 Microsoft Exchange Server 2007 writer specifics 87 Concepts 87 Continuous replication 87 Restore to original or another location 87 Backup 88 LCR and CCR environments 89 Restore 92 Standard restore 92 Rollforward recovery from the loss of one or more databases 92 Point-in-time restore after loss of a log file 93 Restoring individual mailboxes 94 Restoring a LCR or CCR copy to the original location 97 Instant recovery 99 Prerequisites 100 Limitations 101 Restoring an LCR or CCR copy to the original location 102 Post–instant recovery steps 102 Troubleshooting 103 HP Data Protector (9.00) Page 6 of 181 Integration guide for Microsoft Volume Shadow Copy Service Contents Microsoft Exchange Server 2010 writer specifics 103 Introduction 103 Microsoft Exchange Server 2010 concepts 104 Integrating Data Protector Microsoft Volume Shadow Copy Service integration with Exchange Server 2010 104 Configuration 104 Prerequisites 104 Licensing 105 Configuring 105 Backup 105 Limitations 105 Creating a backup specification 106 Restore 106 Restore scenarios 106 Restoring a passive copy 106 Restoring an active copy 109 Point-in-time restore 110 Instant recovery 111 Limitations 111 Instant recovery of a P6000 EVA Array snapclone to a different client using the CLI 112 Troubleshooting 113 Microsoft Hyper-V writer specifics 113 Concepts 113 Prerequisites 113 Backup 113 Prerequisites 115 Limitations 115 Backup from a physical cluster node 116 Restore 116 Restore from a physical cluster node 116 Troubleshooting 117 HP Data Protector (9.00) Page 7 of 181 Integration guide for Microsoft Volume Shadow Copy Service Contents Microsoft SharePoint Services writer specifics 117 Concepts 117 Backup 119 Restore 120 MSDE writer specifics 122 Restore 122 Chapter 7: Troubleshooting 123 Before you begin 123 Checks and verifications 123 Problems 123 ZDB related problems 128 Glossary 135 Index 176 We appreciate your feedback! 180 HP Data Protector (9.00) Page 8 of 181 Chapter 1: Introduction A traditional backup process is based on the direct communication between the backup application and the application whose data is backed up. This backup method requires from the backup application an individual interface for each application it backs up. To address the growing number of applications and their specific interfaces, a new coordinator between the actors of the backup and restore process was introduced on Microsoft Windows systems — the Microsoft Volume Shadow Copy Service. Data Protector integrates with the Volume Shadow Copy service through the Data Protector Microsoft Volume Shadow Copy Service integration (VSS integration). The Data Protector integration with the Microsoft Volume Shadow Copy Service can serve in two functions: l It provides support for certified VSS writers .
Load more

Recommended publications
  • What Is a Service? a Windows Service Is an Application That Usually
    What is a service? A Windows service is an application that usually provides a basic Windows function such as manage system memory, make and monitor network connections, play sound, provide a file system, control security and authentication, interact with the user and many more. They run in the background and have has no user interface. Services are always running, whether they are needed or not. Think about setting these to Manual • Bluetooth Services (2): If you don't connect Bluetooth devices to your computer • Connected End User Experience and Telemetry: Microsoft Keyboard Logger • Diagnostic Policy Service: If you don't depend on Windows diagnostics • Distributed Link Tracking Client: When was the last time you created a symbolic link to a shared file? • dmwappushsvc: Transmits keyboard logger data to Microsoft. • Downloaded Maps Manager: If you use any other map service than the Maps app. • Fax: Not needed for printer fax machines, or if you don't have a fax. • IP Helper: IPV6 to IPV4 tools • Print Spooler: If you don't have a printer • Remote Access Connection Manager: If you don't use a VPN or access your home system remotely • TCP/IP NetBIOS Helper: If you are not in a workgroup network • Touch Keyboard and Handwriting Panel Service: If you don't need the screen touch keyboard or the handwriting features • Windows Media Player Network Sharing Service: Shares music across the home network • Windows Defender (4): If you use another antivirus program • Windows Image Acquisition: If you don't have a scanner • Windows Update: If you want to control the update process.
    [Show full text]
  • Implementing IBM DB2 9.7 Enterprise Server Edition with Microsoft
    Implementing IBM® DB2® 9.7 Enterprise Server Edition with Microsoft Failover Clustering March 2012 Jeremy Brumer Michelle Chiu Aslam Nomani Lui Tang This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this document should not be interpreted as such. © Copyright International Business Machines Corporation 2012. All rights reserved. U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 2 Notices, trademarks, service marks, and disclaimers IBM, the IBM logo, DB2, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product or service names may be the trademarks or service marks of others. The furnishing of this document does not imply giving license to any IBM patents. References in this document to IBM products, Programs, or Services do not imply that IBM intends to make these available in all countries in which IBM operates. 3 Contents Abstract 5 Introduction
    [Show full text]
  • Attacker Antics Illustrations of Ingenuity
    ATTACKER ANTICS ILLUSTRATIONS OF INGENUITY Bart Inglot and Vincent Wong FIRST CONFERENCE 2018 2 Bart Inglot ◆ Principal Consultant at Mandiant ◆ Incident Responder ◆ Rock Climber ◆ Globetrotter ▶ From Poland but live in Singapore ▶ Spent 1 year in Brazil and 8 years in the UK ▶ Learning French… poor effort! ◆ Twitter: @bartinglot ©2018 FireEye | Private & Confidential 3 Vincent Wong ◆ Principal Consultant at Mandiant ◆ Incident Responder ◆ Baby Sitter ◆ 3 years in Singapore ◆ Grew up in Australia ©2018 FireEye | Private & Confidential 4 Disclosure Statement “ Case studies and examples are drawn from our experiences and activities working for a variety of customers, and do not represent our work for any one customer or set of customers. In many cases, facts have been changed to obscure the identity of our customers and individuals associated with our customers. ” ©2018 FireEye | Private & Confidential 5 Today’s Tales 1. AV Server Gone Bad 2. Stealing Secrets From An Air-Gapped Network 3. A Backdoor That Uses DNS for C2 4. Hidden Comment That Can Haunt You 5. A Little Known Persistence Technique 6. Securing Corporate Email is Tricky 7. Hiding in Plain Sight 8. Rewriting Import Table 9. Dastardly Diabolical Evil (aka DDE) ©2018 FireEye | Private & Confidential 6 AV SERVER GONE BAD Cobalt Strike, PowerShell & McAfee ePO (1/9) 7 AV Server Gone Bad – Background ◆ Attackers used Cobalt Strike (along with other malware) ◆ Easily recognisable IOCs when recorded by Windows Event Logs ▶ Random service name – also seen with Metasploit ▶ Base64-encoded script, “%COMSPEC%” and “powershell.exe” ▶ Decoding the script yields additional PowerShell script with a base64-encoded GZIP stream that in turn contained a base64-encoded Cobalt Strike “Beacon” payload.
    [Show full text]
  • Guide to Hardening Windows 10 Technical Guide
    NOVEMBER 2020 Guide to Hardening Windows 10 For Administrators, Developers and Office Workers TABLE OF CONTENTS Introduction .......................................................................................................................... 4 Prerequisites ............................................................................................................................ 4 User roles ................................................................................................................................. 4 EFI (BIOS) Configuration ...................................................................................................... 5 To be enabled: ......................................................................................................................... 5 To be disabled: ......................................................................................................................... 5 Windows Defender Firewall .................................................................................................. 6 Enable logging of dropped packets ............................................................................................. 6 Disable enforcement of local rules and disable notifications .......................................................... 7 Block outbound connections by default ....................................................................................... 8 Secure potentially vulnerable protocols ......................................................................................
    [Show full text]
  • Creating a Windows Service That Uses Microsoft Dynamics Gp Econnect to Integrate Data
    INNOVATE Microsoft Dynamics™ GP Creating a Windows® service that uses Microsoft Dynamics GP eConnect to integrate data Article Create a Windows Service that uses the .NET FileSystemWatcher class to monitor a directory for file operations Date: April, 2008 Table of Contents Introduction ................................................................................................ 3 Overview ..................................................................................................... 3 Start a new application in Visual Basic .NET ................................................ 3 Add References needed by the new application .......................................... 3 Add code to the project ............................................................................... 4 Add Imports statements and set the Service Name .................................................................. 4 Declare a FileSystemWatcher object and add code to the OnStart event ..................................... 4 Add code to the OnStop event .............................................................................................. 5 Add a handler for the xmlWatcher.Created event ..................................................................... 5 Add and configure an installer for the service ............................................. 5 Build, install and test the service ................................................................ 6 2 CREATING A WINDOWS SERVICE THAT USES MICROSOFT DYNAMICS GP ECONNECT TO INTEGRATE DATA Introduction
    [Show full text]
  • Docker Windows Task Scheduler
    Docker Windows Task Scheduler Genealogical Scarface glissading, his karyotype outgone inflicts overflowingly. Rudolph is accessorial and suckers languorously as sociologistic Engelbart bridled sonorously and systematises sigmoidally. Which Cecil merchandises so unbelievably that Cole comedowns her suavity? Simple task runner that runs pending tasks in Redis when Docker container. With Docker Content Trust, see will soon. Windows Tip Run applications in extra background using Task. Cronicle is a multi-server task scheduler and runner with a web based front-end UI It handles both scheduled repeating and on-demand jobs targeting any. Django project that you would only fetch of windows task directory and how we may seem. Docker schedulers and docker compose utility program by learning service on a scheduled time, operators and manage your already interact with. You get a byte array elements followed by the target system privileges, manage such data that? Machine learning service Creatio Academy. JSON list containing all my the jobs. As you note have noticed, development, thank deity for this magazine article. Docker-crontab A docker job scheduler aka crontab for. Careful with your terminology. Sometimes you and docker schedulers for task failed job gets silently redirected to get our task. Here you do want to docker swarm, task scheduler or scheduled background tasks in that. Url into this script in one easy to this was already existing cluster created, it retry a little effort. Works pretty stark deviation from your code is followed by searching for a process so how to be executed automatically set. Now docker for windows service container in most amateur players play to pass as.
    [Show full text]
  • Automated Malware Analysis Report for Spoolsv.Exe
    ID: 160124 Sample Name: spoolsv.exe Cookbook: default.jbs Time: 10:37:44 Date: 05/08/2019 Version: 26.0.0 Aquamarine Table of Contents Table of Contents 2 Analysis Report spoolsv.exe 4 Overview 4 General Information 4 Detection 4 Confidence 4 Classification 5 Analysis Advice 5 Mitre Att&ck Matrix 6 Signature Overview 6 Spreading: 6 System Summary: 6 Data Obfuscation: 7 Boot Survival: 7 Hooking and other Techniques for Hiding and Protection: 7 Malware Analysis System Evasion: 7 Anti Debugging: 7 HIPS / PFW / Operating System Protection Evasion: 7 Language, Device and Operating System Detection: 7 Remote Access Functionality: 7 Behavior Graph 7 Simulations 8 Behavior and APIs 8 Antivirus and Machine Learning Detection 8 Initial Sample 8 Dropped Files 8 Unpacked PE Files 8 Domains 8 URLs 9 Yara Overview 9 Initial Sample 9 PCAP (Network Traffic) 9 Dropped Files 9 Memory Dumps 9 Unpacked PEs 9 Joe Sandbox View / Context 9 IPs 9 Domains 9 ASN 9 JA3 Fingerprints 9 Dropped Files 9 Screenshots 9 Thumbnails 9 Startup 10 Created / dropped Files 10 Domains and IPs 11 Contacted Domains 11 Contacted IPs 11 Static File Info 11 General 11 File Icon 11 Static PE Info 12 General 12 Entrypoint Preview 12 Rich Headers 13 Data Directories 13 Sections 13 Resources 14 Imports 14 Copyright Joe Security LLC 2019 Page 2 of 22 Exports 15 Version Infos 18 Possible Origin 18 Network Behavior 19 Code Manipulations 19 Statistics 19 Behavior 19 System Behavior 19 Analysis Process: cmd.exe PID: 2748 Parent PID: 480 19 General 19 File Activities 20 File Created 20 Analysis
    [Show full text]
  • How to Restart Premisys Services
    PremiSys Services Troubleshooting Introduction There are two services which comprise the PremiSys application server components. These services are: • IDenticard Windows Service • IDenticard Scheduling Service Under normal conditions, both of these services are configured to start automatically when the server starts. Both are also dependent on connection to the PremiSys databases which are hosted by a Microsoft SQL Server. The instance of SQL Server may or may not reside on the same server as the PremiSys application server, depending on the way the system has been designed. IDenticard Windows Service The IDenticard Windows Service is the primary server component of the PremiSys software. It handles the server side code for client logins, licensing, panel communications, transaction processing, etc. When this service is stopped, any running instance of the PremiSys client will receive a message box that indicates “The connection to the {server name} license server has been lost”. When the user acknowledges this message box, the client application will close. If a user attempts to restart the client application while the IDenticard Windows Service is stopped on the Application Server, they will receive a message box which indicates “AddIn Architecture Failed to start – Services unavailable…”. IDenticard Scheduling Service The IDenticard Scheduling Service runs various tasks within a PremiSys system. This includes, but is not limited to user- scheduled tasks for things like backups, transaction archives, reports and door schedules. When this service is stopped, any scheduled tasks will not run on their scheduled execution time. Starting Services Step-By-Step 1. Click on the “Windows Start Menu” Button on the lower-right corner of the Windows Desktop 2.
    [Show full text]
  • Windows Intruder Detection Checklist
    Windows Intruder Detection Checklist http://www.cert.org/tech_tips/test.html CERT® Coordination Center and AusCERT Windows Intruder Detection Checklist This document is being published jointly by the CERT Coordination Center and AusCERT (Australian Computer Emergency Response Team). printable version A. Introduction B. General Advice Pertaining to Intrusion Detection C. Look for Signs that Your System may have been Compromised 1. A Word on Rootkits 2. Examine Log Files 3. Check for Odd User Accounts and Groups 4. Check All Groups for Unexpected User Membership 5. Look for Unauthorized User Rights 6. Check for Unauthorized Applications Starting Automatically 7. Check Your System Binaries for Alterations 8. Check Your Network Configurations for Unauthorized Entries 9. Check for Unauthorized Shares 10. Check for Any Jobs Scheduled to Run 11. Check for Unauthorized Processes 12. Look Throughout the System for Unusual or Hidden Files 13. Check for Altered Permissions on Files or Registry Keys 14. Check for Changes in User or Computer Policies 15. Ensure the System has not been Joined to a Different Domain 16. Audit for Intrusion Detection 17. Additional Information D. Consider Running Intrusion Detection Systems If Possible 1. Freeware/shareware Intrusion Detection Systems 2. Commercial Intrusion Detection Systems E. Review Other AusCERT and CERT Documents 1. Steps for Recovering from a Windows NT Compromise 2. Windows NT Configuration Guidelines 3. NIST Checklists F. Document Revision History A. Introduction This document outlines suggested steps for determining whether your Windows system has been compromised. System administrators can use this information to look for several types of break-ins. We also encourage you to review all sections of this document and modify your systems to address potential weaknesses.
    [Show full text]
  • Security and Compliance
    Security and Compliance Robert Nottoli | Principal Technology Specialist | Microsoft Corporation [email protected] DISCLAIMER FOR DOCUMENTATION REGARDING PRE-RELEASED SOFTWARE This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, including URL and other Internet Web sites referenced, and is the confidential and proprietary information of Microsoft Corporation. The entire risk of the use or the results from the use of this document remains with the user. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Therefore, MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
    [Show full text]
  • Installation and Setup Guide for Server
    FUJITSU Software Symfoware Server V12.1.0 Installation and Setup Guide for Server Windows B1WS-1136-03ENZ0(00) December 2014 Preface Purpose of This Document The Symfoware Server database system extends the PostgreSQL features and runs on the Windows platform. This document describes how to install and setup "Symfoware Server". Intended Readers This document is intended for those who install and operate Symfoware Server. Readers of this document are assumed to have general knowledge of: - PostgreSQL - SQL - Windows Structure of This Document This document is structured as follows: Chapter 1 Overview of Installation Describes the installation types and procedures Chapter 2 Operating Environment Describes the operating environment required to use Symfoware Server Chapter 3 Installation Describes how to perform an new installation of Symfoware Server Chapter 4 Setup Describes the setup to be performed after installation Chapter 5 Uninstallation Describes how to uninstall Symfoware Server Appendix A Installation in Silent Mode Provides specifications for installation in silent mode Appendix B Symfoware Server Migration Procedures Describes how to migrate Symfoware Server from an old version/level. Appendix C Using WebAdmin After an Upgrade Describes the required operations for using WebAdmin after an upgrade. Appendix D Recommended WebAdmin Environments Describes the recommended WebAdmin environment. Appendix E Setting Up and Removing WebAdmin Describes how to set up and remove WebAdmin Appendix F Configuring Parameters Describes Symfoware
    [Show full text]
  • Microsoft Windows Server 2003. Server Clusters: Architecture
    Server Clusters : Architecture Overview For Windows Server 2003 Microsoft Corporation Published: March 2003 Abstract Server clusters are one of two Microsoft® Windows® clustering technologies available for the Microsoft Windows Server family of products. Windows Server 2003 clusters provide failover support for back-end applications and services that require high availability and data integrity. These back-end applications include enterprise applications such as database, file server, enterprise resource planning (ERP), and messaging systems. This white paper focuses on the architecture and features of the cluster service and describes its terminology, concepts, design goals, key components, and planned future directions. Microsoft® Windows® Server 2003 Technical Article The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.
    [Show full text]