Professional Documents
Culture Documents
Connecteddata Center Deployment 82
Connecteddata Center Deployment 82
Document information
Connected Backup Data Center Deployment
Connected Backup Version 8.2
Printed: May 7, 2007
Printed in USA
Copyright
Copyright 2007 Iron Mountain Incorporated. All rights reserved.
Trademarks
Iron Mountain, the design of the mountain, Iron Mountain, the design of the mountain, Connected, Connected DataProtector,
Connected EmailOptimizer, DataBundler, MyRoam, Delta Block, and SendOnce are trademarks or registered trademarks of Iron
Mountain Incorporated. All other trademarks and registered trademarks are the property of their respective owners. All other
trademarks and registered trademarks are the property of their respective owners.
Confidentiality
CONFIDENTIAL AND PROPRIETARY INFORMATION OF IRON MOUNTAIN. The information set forth herein represents
the confidential and proprietary information of Iron Mountain. Such information shall only be used for the express purpose authorized
by Iron Mountain and shall not be published, communicated, disclosed or divulged to any person, firm, corporation or legal entity,
directly or indirectly, or to any third person without the prior written consent of Iron Mountain.
Disclaimer
While Iron Mountain has made every effort to ensure the accuracy and completeness of this document, it assumes no responsibility
for the consequences to users of any errors that may be contained herein. The information in this document is subject to change without
notice and should not be considered a commitment by Iron Mountain Incorporated. Some software products marketed by Iron
Mountain Incorporated and its distributors contain proprietary software components of other software vendors.
TABLE
OF
C ONTENTS
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Other Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Typographical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Graphical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Iron Mountain Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Part I: About the Data Center
Chapter 1: Data Center Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Services overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
BackupServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
IndexServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
ReplicationServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
PoolServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
HSMServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Compactor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
DCAlerter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Chapter 2: Hierarchical Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
About HSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Migration and purge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Tape Groups and Tape Account Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Tape Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Multiple tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Permanent expansion library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Chapter 3: Compactor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Compactor and Data Center configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
How Compactor operates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
File expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Part II: Data Center Installation
Chapter 4: Sizing Your Data Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Sizing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Sizing estimates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Network bandwidth requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Table of Contents
Table of Contents
PREFACE
About this manual
The Connected Backup solution is a proven solution that automatically protects and restores user or server data files,
operating systems, and applications using a single central Data Center while reducing Information Technology costs and
email storage demands.
This manual is written for system administrators and Data Center technicians. Readers of this manual should be familiar with
the Windows operating system and the operations of their Data Centers.
This manual is organized into the following sections:
Section
Description
Chapter 3: Compactor
Chapter 7: Integrating the Data Center with Enterprise Describes how to use an Enterprise Directory with the Data
Directory
Center.
Chapter 8: Managing the Data Center with DCMC
Chapter 11: Introduction to Data Center Maintenance Introduces the daily, weekly, and monthly maintenance tasks for
the Connected Backup application.
Section
Description
Related documentation
Related manuals
The following manuals provide additional information about the Connected Backup product:
Manual
Description
Connected Backup Upgrading from Pre-8.0 Versions This manual describes how to upgrade a legacy Data Center and
Agent to version 8.2. The manual also describes new and changed
features in version 8.2.
Connected Backup Agent Deployment
Other Resources
The following resources provide additional information about the Connected Backup family of products:
Online help All applications provide procedural and conceptual information in an online help system. Click the Help
link, Help button, or ? button to open the online Help.
The Resource Center The Resource Center is a knowledge base of information that all Connected Backup customers
can access. It includes procedures and information not contained in the product manuals or online help systems. The
Resource Center is located at https://resourcecenter.connected.com/
Conventions
Typographical conventions
This manual uses the following typographical conventions:
Convention
Description
Bold text
Italic text
Monospaced text
A registry key
Important information
New terminology
file name
folder name
code examples
system messages
Graphical conventions
This manual uses the following graphical conventions:
Convention
Description
Indicates additional information that may be of interest to the
reader.
Indicates cautions that, if ignored, can result in damage to
software or hardware.
10
Contact Information
Technical support
Use the following to contact technical support:
Email: corporatesupport@ironmountain.com
Telephone: 800.675.5971
U.S. +1 508.808.7629
E.U. +49 6102 8828855
11
1
DATA CENTER SERVICES
About this chapter
This chapter describes the types of services the Data Center uses in the following topics:
To learn about...
Refer to:
BackupServer, on page 17
IndexServer, on page 18
ReplicationServer, on page 19
PoolServer, on page 20
HSMServer, on page 21
Compactor, on page 22
DCAlerter, on page 23
15
Services overview
Services overview
Types of services
The Data Center uses the following services to perform the necessary tasks of running the Data Center server:
16
PoolServer used to maintain the shared pool that the SendOnce technology uses.
HSMServer used to copy archive sets to archive storage devices and purge migrated sets from disk when needed.
BackupServer
BackupServer
How BackupServer works
BackupServer is the Data Center service that processes requests from the Agent for data backup and retrieval. BackupServer
gathers together all of the backed-up data into an archive set. The archive set is a file stored on the Data Center servers disk
in a folder called Customers. It contains file backup data transmitted from a client during a single backup session.
If the backup data from a single backup session is large, the BackupServer service saves information to more than one archive
set, each representing a portion of the backup session. Using multiple archive sets helps to optimize data recovery
performance.
When the Agent requests BackupServer to retrieve a file to a client, BackupServer must find the first backup of the file (called
the baseline) and all of that files changes (called deltas) necessary to recreate the specific version of the file that the user has
requested.
For example, if the user has requested to retrieve the third backed-up version of a file, BackupServer must retrieve the
baseline (version 1), the delta that represents the differences between version 1 and version 2, and the delta that represents
the differences between version 2 and version 3. Since the baseline and the deltas were backed up in different backup
sessions, they are in different archive sets. Therefore, BackupServer typically uses multiple archive sets to retrieve a file.
In addition to processing requests for data backup and retrieval, the BackupServer service manages the list of authorized user
accounts and registers new accounts. There is one user account for each client that is being backed up.
CAUTION
The Data Center servers store backed-up archive sets in a folder called Customers. The Data
Center server saves archive sets as files with the extension .arc.
Under no circumstances should you ever delete an .arc file from the Customers directory.
Doing so would mean deleting end users data and rendering it unrecoverable.
Management
BackupServer starts automatically with Windows Server. Status and statistics for BackupServer are found in the Data Center
Management Console (DCMC). To view the service in the DCMC, expand the Data Center server name and click
BackupServer.
17
IndexServer
IndexServer
IndexServer is the Data Center service that indexes file and archive set information to database tables.
Management
IndexServer starts automatically with Windows Server. Status and statistics for IndexServer are found in DCMC. To view
the service in the DCMC, expand the Data Center server name and click IndexServer.
18
ReplicationServer
ReplicationServer
How ReplicationServer works
The ReplicationServer service replicates the following content between the servers in a mirrored pair:
Archive sets
Agent configurations
Management
ReplicationServer starts automatically with Windows Server. Archive sets and database entries are replicated continuously
when ReplicationServer is running. If it becomes necessary to pause or stop replication, you can pause or stop the service in
the DCMC. You can view the status and progress of the replication service in the DCMC by expanding the Data Center server
name and clicking ReplicationServer.
19
PoolServer
PoolServer
PoolServer is the Data Center service that maintains the shared file pool used to implement SendOnce technology. The
SendOnce technology provides a method for identical files from multiple Agents to be backed up once. This method
reduces the storage needed on the Data Center server since multiple copies of the same file are not stored on the server.
Management
PoolServer starts automatically with Windows Server. Use the DCMC to view the status and statistics of the PoolServer. In
the DCMC, expand the Data Center server name and click PoolServer.
20
HSMServer
HSMServer
How HSMServer works
HSMServer is the Data Center service that processes the copying of archive sets between the local servers disk and the
archive storage device. The HSMServer contains the following components:
HSMClient
BackupHSM
HSMPurge
HSMClient is invoked by BackupServer to pass archive set copy requests to the BackupHSM service. The HSMClient
monitors the processing of the requests and mediates between BackupServer (the Windows service) and BackupHSM.
BackupHSM handles the operations for archive storage devices. HSMServer supports tape libraries and EMC Centera
archive storage devices.
It is not recommended that you pause the BackupHSM service. When BackupHSM is paused you cannot cancel requests or
view the status in DCMC. You can unmount a tape manually from a tape library while BackupHSM is paused.
The library audits its contents and then BackupHSM audits the library. If it is necessary to stop HSM activities, stopping
BackupHSM alerts the service to complete the current request and then stop.
It is the job of HSMPurge to migrate (copy) archive sets from disk to the archive storage device and, when necessary, purge
(delete) archive sets from disk in order to create free disk space.
When the end user wants to retrieve files, BackupServer sends a request to HSMClient to retrieve the appropriate archive
sets. BackupHSM copies the archive sets from the archive storage device back onto the servers disk where BackupServer
can process them.
Additional information
Refer to Chapter 2: Hierarchical Storage Manager, beginning on page 25, for more information about HSM.
21
Compactor
Compactor
The Compactor service works to clean old data off the Data Center. Compactor checks for synchronization between mirrored
servers, applies expiration rules to backed up data, and deletes data that is deemed expired. The goal of Compactor is to speed
up the Retrieve process and to reduce the amount of data stored long term on the Data Center.
Additional information
Refer to Chapter 3: Compactor, beginning on page 35, for additional details about the Compactor process.
22
DCAlerter
DCAlerter
DCAlerter notifies designated individuals when specific events occur on the Data Center. DCAlerter monitors the Data
Center event logs for specific event IDs configured for notification. When an event ID is logged that has been configured for
notification, DCAlerter sends an email message to the designated individuals.
Refer to Chapter 10: Event Logging, beginning on page 111 for additional information about Data Center event logs.
23
2
HIERARCHICAL STORAGE MANAGER
About this chapter
This chapter contains the following topics:
To learn about...
Refer to:
Tape sets
25
About HSM
About HSM
Description
Over time, the Agents on many computers perform many backups and the number of archive sets on the Data Center servers
disk grows. When free space on the disk drops below a preconfigured threshold, BackupServer requests Hierarchical Storage
Manager (HSM) to migrate archive sets from disk to the archive storage device, if one is installed. If no archive storage
device is installed, archive sets are kept only on the Data Center servers disks.
The Compactor service, discussed in Chapter 3: Compactor, beginning on page 35, removes old data and recycles disk space
as needed.
EMC Centera.
Visit the Resource Center for an updated list of hardware solutions that are currently supported.
26
Purge
As archive sets are continually backed up to the server and occupy more disk space, free disk space continues to drop. When
free disk space drops to a second specified percentage, HSMPurge starts purging migrated archive sets from disk. The
purging continues until free disk space grows to a third specified percentage. You can specify the disk space percentages for
the migration and purge processes in the DCMC.
Archive sets are not immediately purged from disk after migration to the archive storage device. The reason for this is to keep
as many archive sets as possible available on disk for possible file retrieval requests.
27
Tape Group 0
Tape Group 0 (zero) is the default Tape Group created by Data Center Setup. The default community is assigned to Tape
Group 0. Unless specified in Support Center, all new communities are also assigned to Tape Group 0.
28
Tape Sets
Tape Sets
Overview
Whether you are running a standalone or a mirrored Data Center configuration, there is a risk of losing backed-up data due
to various failures, such as:
Disk failure on a standalone Data Center or on one of the servers of a mirrored pair.
The amount of risk decreases in a mirrored server environment, where all backed-up data is stored redundantly on two
identical Data Centers, so that if one Data Center of a mirrored pair experiences technical problems, data is still available on
its mirror.
Unlike a mirrored pair, a standalone Data Center only stores a single copy of data on disk or archive storage device (if
applicable). In the event of hardware or software malfunction, service outage, a fire, or similar disaster, backed-up data, both
on disk and on the archive storage device, will be completely lost if no extra protective measures have been taken. To take
such protective measures, you can configure your Data Center to use one or more additional tape sets (refer to Chapter 6:
Installing the Data Center Software, beginning on page 73 for installation information). During the migration process, HSM
copies data from disk to tapes that belong to the tape sets. These tape sets are referred to as the Primary and Secondary Tape
Sets.
The Primary and Secondary Tape Sets serve different functions within the Data Center. Therefore, the methods by which you
create them differ as well.
Use DCMC to configure your Data Center to use Tape Sets. Refer to the DCMC Help for configuration procedures
29
Tape Sets
The SendOnce account tape set stores a backup of the SendOnce account (you can create only one copy of a SendOnce
account tape set). This tape set usually remains on-site and is especially helpful in a standalone Data Center
configuration, enabling fast recovery of backed up data, lost due to a bad tape or a disk failure. When the SendOnce
account tape set tape becomes full, you can remove it from the library and store it on the shelf at the same location.
Off-site Secondary Tape Sets contain a complete copy of archive sets (with the exception of the SendOnce account) and
are intended for off-site storage. Depending on your organizations needs, you can configure the system to create one or
more off-site Secondary Tape Sets. For maximum data protection, tapes in these tape sets are filled and removed from
the library as often as possible. After the tapes are removed from the library, they must be stored in a safe location,
preferably in a different building. Therefore, in the event of full-system crash, the most recent users data would still be
available on the off-site Secondary Tape Set tapes.
The advantages and disadvantages of this setup and how it can affect your Data Center operations.
The primary advantage of having Secondary Tape Sets is in having an ultimate degree of protection against loss or
damage of backup data. It is particularly valuable in a standalone server environment, where the risk of losing data due
to a disk or tape failure is especially high. In the event of an entire system crash, the off-site tapes from the Secondary
Tape Set remain the only source of end-user data, which would otherwise be lost forever.
30
Tape Sets
Although a mirrored server configuration provides an extra degree of data protection against all possible failures by storing
data redundantly at the two identical Data Centers, Secondary Tape Sets are still very helpful in the following situations:
You must quickly restore archive sets that are lost or damaged due to a tape failure.
One of the servers in a mirrored pair is completely destroyed, and you must quickly move backed-up data to a new
mirror.
The primary disadvantage of using Secondary Tape Sets is the increasing cost of media (you must provide additional tapes
to maintain this setup) and operation maintenance. Your decision is therefore a trade-off of cost against the level of risk you
are ready to accept.
Migration schedule
Frequency of data migration to the Secondary Tape Set is determined by the migration schedule. In a single server
environment, the risk of losing data due to disk failure is much higher than in a mirrored server configuration. To reduce this
risk, data must be migrated to the Secondary Tape Set as frequently as possible. Instead of being demand driven, migration
is scheduled to run daily or several times per day using the daily automatic procedure. The greater the frequency of migration,
the less the data loss if the disk were to fail. Migration to the Secondary Tape Set can also be performed with the DCMC.
To ensure data safety in case of fire or other disaster that might result in loss of the entire Data Center, Secondary Tape Set
tapes must be removed from the library and taken off-site as often as possible. The extraction schedule defines how often the
Secondary Tape Set tapes are removed from the library.
Extraction schedule
The frequency of tape extraction is determined by the following factors:
The amount of data that the Data Center receives daily (if the Data Center has a large user community, tape removal
should be performed more frequently)
The number of blank tapes that the user provides to support the Secondary Tape Set configuration
You can set the extraction interval to less than, equal to, or greater than a day. You should remove Secondary Tape Set tapes
from the library every other day or as soon as the tape gets full (waiting until the tape gets full reduces the cost of media, but
increases the risk of losing backed-up data due to complete disk loss). After the tapes are removed, they should be stored in
a safe location, preferably in a different building. Then, in the event of a full system crash, the most recent data can still be
retrieved from the off-site Secondary Tape Sets.
31
You have an existing tape library and would like to replace it by transitioning to a new tape library (for example, if you
are replacing an older tape library with one that uses newer technology).
You want to keep your existing tape library, but you must use an additional reliever library temporarily until you can
free up tape space on the original library.
You want to permanently use multiple tape libraries to expand your total available tape capacity.
Each of these situations poses its own unique considerations and procedures. For information on installing two tape libraries
on your Data Center or adding a second tape library, visit the Resource Center.
32
33
If you use libraries of different tape and barcode technologies, you must prepare in advance of setting up the new tapes. When
you order barcode labels for new tapes, order labels with the same barcode labels as your other libraries. For example, if one
library uses ABK001-ABK200, order labels with ABK001-ABK200 for the additional library. That way you can attach the
barcodes, alternating numbers for each library. For example, use the ABK001 label for the first library, the ABK002 label
for the second library, the ABK003 label for the first library, the ABK004 label for the second library, and so forth. Then
HSM alternates libraries when migrating data to a new tape.
34
3
COMPACTOR
About this chapter
This chapter contains a description on the Compactor service. This chapter contains the following topics:
To learn about...
Refer to:
35
Chapter 3/Compactor
Compactor configurations
Compactor runs on all Data Center configurations but runs differently on a mirrored configuration than it does on a
standalone Data Center server. It also works differently with HSM as opposed to a disk-only configuration.
Administration of Compactor
For assistance in administering Compactor, use DCMC to:
You can access DCMC Help from DCMC for more information on these topics.
36
Chapter 3/Compactor
2.
3.
4.
5.
6.
7.
8.
37
Chapter 3/Compactor
38
Chapter 3/Compactor
39
Chapter 3/Compactor
File expiration
File expiration
File expiration process
To reuse disk and archive storage space, the Data Center deletes old data using a process during the Compactor process called
expiration.
During setup, you are asked to establish parameters that define when data is old and can be deleted. The file expiration
rules are set to reasonable defaults by Data Center Setup, so you can safely accept the defaults if you are not sure of the
parameters you need. Entering -1 for any of the values turns off the expiration rule.
On a disk-only configuration, file expiration rules are used to keep from running out of disk storage. On a server using HSM,
file expiration rules are only used to minimize growth of data in storage; the disk is kept at an acceptable free space level by
data migration. Consequently, you should monitor a disk-only configuration closely in the weeks after startup, and decrease
the file expiration rules if disk space is being filled too quickly. On both disk-only and HSM configurations, if space is tightly
limited, more aggressive file expiration rules are necessary. File expiration rules are changed using DCMC.
Canceled specifies the minimum number of days after an account is canceled until its backed-up data is deleted. The
default number of days until deletion is 60.
Deleted specifies the minimum number of days that a file is retained after it has been deleted from the Agent that backed
it up. If a file is backed up and later deleted, it is normally retrievable via the Agent. However, if the file has been expired
and compacted from the Data Center, it cannot be retrieved. The default value is 90 days for disk-only configurations
and 180 days for HSM configurations.
Excluded specifies the number of days that a file is retained after the end-user has excluded it from the backup list on
the Agent. If a file is backed up and then later excluded from the Agent backup list, it is expired and deleted the next
time Compactor runs on the account. The default value is zero days for disk-only and HSM configurations.
RecentVersions and OldVersions are used together to specify the number of versions of a file that are retained. For
example, if RecentVersions = 9 (versions) and OldVersions = 30 (days), then old versions of a file are deleted if they are
more than 30 days old or there are 9 more recent versions. The most recent backed-up version of a file is not expired
using these parameters. The default value for RecentVersions is 10 versions for disk-only configurations and 20 versions
for HSM configurations. The default value for OldVersions is 45 days for disk-only configurations and 90 days for HSM
configurations.
Rule exceptions
It is possible for data to be on the Data Center longer than the expiration rules imply. For example, on January 1st an end user
deletes a file from their computer that has been backed up to the Data Center, and then performs a subsequent backup.
Compactor is set to process accounts no more than every 90 days, the next time Compactor processes this account is on April
15th. In this example, the expiration rule for deleted files is 90 days. As Compactor is processing this account it marks the
file for deletion from the Data Center. The file lived on the Data Center for more than 90 days after its deletion from the
end-user computer. This is because the expiration rule values and the number of days between Compactor runs for an account
or Tape Account Group are minimum values. Data could remain on the Data Center longer than these values indicate.
40
4
SIZING YOUR DATA CENTER
About this chapter
This chapter provides information that you can use as a guide to determine the hardware requirements for your Data Center.
Precise determination of these requirements is contingent upon a number of variables, most of which are dependant on the
specifics of the end user population, number of servers, and Agent configuration choices. Even if you are licensed for 5,000
users or 500 servers, you still might want to deploy hardware that would serve 10,000 users or 1,000 servers so you can easily
scale the Data Center to handle more users if needed in the future.
This chapter contains the following topics:
To learn about...
Refer to:
43
Sizing overview
Sizing overview
Planning your deployment
When sizing your Data Center hardware, plan for your total number of users or servers when completely deployed as opposed
to only the number you plan to initially deploy. If your goal is to have more than 10,000 users or 100 servers backing up to
the Data Center, then you should contact Iron Mountain Digital for assistance in sizing your Data Center hardware.
The information in this chapter provides guidelines for different hardware configurations including disk-only, disk with an
attached tape library, and disk with an attached EMC Centera. Disk-only Data Centers represent configurations using
Network Attached Storage (NAS), Storage Area Network (SAN) and directly attached disk storage. If you are configuring a
mirrored Data Center, each server must conform to the same guidelines.
First backup of each account is 1 GB compressed data, on average. This number does not include common files taking
advantage of SendOnce technology.
Size per month of compressed backup data per end user is 125 MB.
44
First backup of each server account is 10 GB compressed, on average. This number does not include common files
taking advantage of SendOnce technology.
Size per month of compressed backup data per end server account is 1GB.
Sizing overview
Additional resources
If your Data Center has variables not accounted for in this chapter, contact Iron Mountain Digital for an individualized sizing
estimation.
Visit the Resource Center for a table that compares each configuration type against each end user range overall.
45
Sizing estimates
Sizing estimates
You can estimate the sizing for a Data Center based on the number of accounts.
Note
If you are configuring a mirrored Data Center, each server must conform to the same minimum
guidelines.
PC Account
Server Account
Archive set
Database
Centera
Requirement
8 GB
46
Sizing estimates
Hardware requirements
The following table provides minimum hardware requirements for sizing a Data Center.
Hardware
Requirement
Processors
Memory
4 GB parity or ECC
Ethernet Adapter
1 GB per second
47
Network requirements
Network bandwidth between the client and each Data Center 1 megabit/second based on 5 to 6 MB of compressed data per
user per day.
48
IP address
5
PREPARING FOR INSTALLATION
Configure your servers
Before you can install the Data Center, make sure your servers are prepared and configured correctly for the installation. This
chapter explains how to prepare your server for a Data Center installation.
Refer to:
Tasks you need to complete before installing the Data Center Preinstallation tasks, on page 50
software
Information about configurations and licensing options
49
Preinstallation tasks
Preinstallation tasks
Preparing for installation
To prepare your Data Center for installation, you should do the following:
Prepare the Support Center and Account Management Website server(s) for installation.
Note
The Data Center supports the use of the Account Management Website with MyRoam application for
Connected Backup Agents. If you are using Legacy Agents only, you can ignore all references to the
MyRoam application.
The specific tasks within each of these steps depend on your Data Center configuration. For example, a standalone Data
Center has a different configuration from a mirrored Data Center, and a disk-only Data Center has a different configuration
from a Data Center with Hierarchical Storage Manager (HSM) installed.
Use the Data Center Installation Worksheets in Appendix B to organize your Data Center information. Having this
information available can make the Data Center installation easier.
50
Whether you will have a standalone Data Center or one configured with mirrored pair(s).
Licensing
Every Data Center must be licensed. You can purchase licenses for PC accounts only, server accounts only, or both. You
should obtain a permanent license before installing the Data Center software. However, if you do not have a license at the
time of installation, the Setup program creates a temporary license that expires in thirty days.
Your Data Center's license enables optional features your organization has chosen to implement. It also tracks the number of
active users and servers on the Data Center and warns you when the license use is nearing the contracted number.
If at any time you would like to change the features in use at your Data Center or increase the number of end users serviced,
you can contact Support to obtain a new license. For further information about obtaining a new Data Center license, refer to
Chapter 14: Monthly Maintenance.
51
Software requirements
To install the Data Center software, your servers must have the following software installed
Component
Requirement
Operating system
Windows 2003 Standard and Enterprise Editions with Service Pack 2, and
ODBC version 3.0 or later.
Windows 2003 Server Standard and Enterprise Editions R2, and ODBC
version 3.0 or later.
Windows 2000 Server with Service Pack (SP) 4 and all security hotfixes,
and ODBC version 3.0 or later.
Network
52
Note
For the purposes of this document, references to Windows or Windows Server refer to both Windows
Server 2000 and Windows Server 2003. Information that is pertinent to one specific operating system
is called out as such.
Refer to Installing and configuring Microsoft software, on page 61 for information on installing Microsoft software. Also,
refer to Web server preparation, on page 70 for Support Center and Account Management Website software requirements.
Note
If your Data Center supports more than 10,000 accounts, you should not run Support Center and the
Account Management Website on the same server.
VMware Support
You can install the Data Center on VMware configured to meet the existing system requirements, and open a browser
(Internet Explorer version 6.0 or later) and run the application. Supported versions are VMware ESX 2.5.1, 2.5.2, 2.5.3, and
3.0.1.
Note
If you set up a tape device for database backups, and you test it using a Windows Server backup, SQL
Server is not able to use the same media as used for the Windows Server backup.
53
54
Disk-based
HSM-based
Disk-based solutions
The Connected Backup application supports the following disk-based solutions for secondary storage:
Disk solutions interface with the Data Center directly rather than through HSM. The following sections include information
to help you prepare your disk solutions for use with the Data Center.
55
HSM-based solutions
If you are installing HSM, you also must have an archive storage device. Visit the Resource Center for a current list of
supported devices. In general, the Connected Backup solution supports tape libraries, EMC Centera, and Distributed AML
Server (DAS). This section contains information about preparing each device for HSM.
EMC Centera
If the Data Center uses EMC Centera as an archive storage device, you should follow the instructions that came with Centera
for proper installation and connection to the Data Center servers. Visit the Resource Center to view a list of supported Centera
software and hardware.
During Data Center Setup, you must enter the following information. For details, see the Data Center Setup online help.
Centera Addresses IP address(es) of the Centera. You can record the IP address(es) on the Data Center Installation
Worksheets in Appendix B.
Handler count Number of threads between Centera and the Data Center. The recommended number is 10 threads
for 100 megabit of network connectivity between Centera and the Data Center. If you use a gigabit connection between
Centera and the Data Center, use 20 threads.
Main Profile BackupHSM uses the Main profile to write data to and read data from the Centera. The default path
and name for the Main profile is: C:\CenteraProfiles\connected_main.pea, but may be edited. You can
record the Main profile path and name on the Data Center Installation Worksheets in Appendix B. For information about
how to set up a profile before running Data Center Setup, refer to the Resource Center procedure Using Centera Access
Profiles with the Data Center (document number 1657).
Purge Profile BackupHSM uses the Purge profile to purge data from the Centera. If Centera does not have purge
capability, BackupHSM deletes the data from Centera. The default path and name for the Purge profile is:
C:\CenteraProfiles\connected_purge.pea, but may be edited. You can record the Purge profile path and
name on the Data Center Installation Worksheets in Appendix B. For information about how to set up a profile before
running Data Center Setup, refer to the Resource Center procedure Using Centera Access Profiles with the Data Center
(document 1657).
Data Center Setup automatically configures HSM to work with Centera with the following settings. If you need to modify
any of these settings, contact Support.
MaxArchiveSize Determines the maximum size of an archive set for optimal performance. The default value is 90
megabytes.
CenteraPurgeInterval Determines how often the Data Center monitors for expired archive sets. The default value
is 1 day.
Tape libraries
If the Data Center will be using a tape library, you will need to have numeric barcode tape labels, and a differential SCSI host
adapter and cable available before installing HSM.
CAUTION
The host adapter to be connected to the library and its tape drives should have SCSI parity enabled.
Otherwise, you could experience problems with unreadable tapes and data loss.
The number of tape drives you have depends on your particular tape library. The tape drives in the tape library are numbered
in the order determined by the physical location of the drive in the library. For example, Drive 0 might be at the top of the
library, followed by Drive 1, Drive 2, Drive 3, and so forth, as you move from the top to the bottom of the library. The specific
numbering sequence varies according to manufacturer. You should refer to the documentation supplied with your tape library
to determine the correct numbering sequence.
56
Connect Drive 1 to a SCSI port with an ID number greater than the ID number of the port for tape Drive 0.
The SCSI port ID number for tape Drive 2 must be higher than the ID number for tape Drive 1, etc. The higher the drive
number-the higher the ID number, as shown in the table.
SCSI
Drive 0
Drive 1
Drive 2
Drive 3
Connect tape drives to busses in consecutive order. For example, connect Drive 0 and Drive 1 to Bus 0; connect Drive
2, Drive 3, and Drive 4 to Bus 1, etc.
Do not connect drives to busses out of sequence. In other words, do not connect Drives 0, 2 and 4 to Bus 0 while
connecting Drives 1, 3, and 5 to Bus 1.
Higher drive numbers must be connected to higher Bus ID numbers, as shown in the table.
The Bus IDs, and the SCSI IDs for each bus, do not have to be consecutive.
SCSI ID Number
Drive 0
Bus 0
Drive 1
Bus 0
Drive 2
Bus 1
Drive 3
Bus 1
Drive 4
Bus 1
With Microsoft Windows registry editor, you can verify and edit the SCSI mapping in the following registry key:
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SCSI
CAUTION
Editing the Windows registry is a procedure that can render your server inoperable. Exercise extreme
caution when editing the registry. For assistance in editing the Windows registry safely, contact Support.
57
2.
3.
Click the Physical Locations folder. A list of tape libraries and drives appears in the right pane.
4.
In the right pane, right-click a listed tape library or drive listed that HSM will use and select Properties.
5.
In the General tab, clear the Enable library check box to deselect it.
6.
Click OK.
7.
Repeat steps 4 through 6 for each tape library and/or drive to be used by HSM.
58
Network requirements
Network requirements
Determining server configuration
The Agent must be able to communicate with the Data Center. Also, if running a mirrored configuration, the Data Center
servers must be able to communicate with each other. For information on network bandwidth requirements, refer to Network
bandwidth requirements, on page 48.
When setting up a mirrored pair, you must assign a unique IP address, or optionally a DNS name, to each server. You must
also establish connectivity between the pair of servers before installing the Data Center software.
Ports
If a firewall or router is restricting communications between mirrored servers, each server must be able to access the
following ports on its mirror:
TCP ports 16400 - 16406 (RPC connections for Data Center services).
If a firewall or router is restricting communications between the Agent and the Data Center servers, each server must permit
TCP access on port 16384.
59
Security requirements
Security requirements
Setting up security
The Data Center uses Windows authentication and logons to run its services and to connect to SQL Server. The Data Center
installation software creates three domain accounts, each with very limited permission. The Data Center uses these accounts
to run the Data Center services and components.
During installation, Setup creates these accounts using the names and passwords that you specify. If you choose to change
the names of these accounts, make sure you record the new name and password of each account for later use. Choose account
names that accurately reflect the purpose of the account. Alternatively, you can opt to accept the default account names
created during installation.
Domain accounts
The Data Center installation creates the following domain accounts:
Default Account Name
Purpose
CNTD_DCServices
CNTD_WebServices
CNTD_DataBundler
You must log on to the server using an account with administrative privileges and the permission to create domain accounts
to run Data Center Setup, otherwise, the accounts created will not have the necessary permissions to start services,
authenticate Support Center and Account Management Website application logon attempts, or run DataBundler.
You can opt to create these accounts manually prior to running Data Center Setup. If you create the accounts prior to Setup,
the accounts must all be in the same domain. This is particularly important in a mirrored configuration where servers must
communicate with each other.
Whether you create these accounts manually or not, during installation, you are prompted to provide a password for each
account.
CAUTION
The domain accounts created by Setup to run the Data Center have limited permissions. Do not use these
accounts to log on to the Data Center server.
60
The vendors for all hardware, software, and firmware in your Data Center support Microsoft Windows 2000 Server or
Windows 2003 Server and SQL Server 2000.
All device drivers are at the appropriate revision level according to vendor recommendations.
When installing the required software, be sure to follow the guidelines in the remainder of this section to prepare your server
for a Data Center installation.
For specific Data Center software requirements, refer to Data Center server requirements, on page 52.
Delete any existing disk partitions, even if you are removing a system partition. However, do not delete any
proprietary computer vendor partitions created for configuration purposes (for example, an EISA partition).
Create an 8 GB, or larger if desired, boot partition (RAID or other redundant storage is best for the boot partition,
but is not essential).
Next, create a page file that is equal to the amount of installed RAM times two.
Install Windows in the new partition. Specify NTFS formatting for the system or boot partition.
When asked about licensing modes, select an option that represents per user licensing (depending on the Windows
version, this might be Per Seat Licensing or Per Device or Per User licensing).
When asked about server type, select standalone server rather than either of the domain controller options, provided
there are existing domain controllers in the network.
When asked about the network configuration for Windows 2000 Server, accept the following default selections:
Typical settings
If installing Windows 2000 Server, be sure to include IIS as part of the installation on the server that will host Support
Center and the MyRoam application (you can use the MyRoam application with Connected Backup Agents only).
Accept all default setup options for IIS except FTP and Gopher, which you should not select. Verify that World Wide
Web Service is selected.
61
If installing Windows 2003 Server, IIS is installed separately after the initial installation. Refer to Install IIS on Windows
2003 server, on page 63 for steps to install IIS after the initial Windows 2003 Server installation.
Refer to Web server preparation, on page 70 for information on setting up IIS on your Web server.
When asked for network protocols, install the TCP/IP protocol. The Data Center software does not use IPX/SPX, though
you can install it if you need it for administrative purposes.
If installing Windows 2000 Server, select the workgroup option (instead of domain) with the default workgroup name
WORKGROUP. Refer to Assign the server to an existing domain on Windows 2000, on page 64 for steps to perform
this task after the initial Windows installation.
If installing Windows 2003 Server, add the server to the appropriate domain during the initial Windows 2003 Server
installation.
62
Grant the IUSER_servername account Full Control permissions to the following folders: DataCenter,
InetPub\wwwroot\SupportCenter, InetPub\wwwroot\MyRoam, and the Temp folder (depending on your
operating system, either WINNT\Temp. or Windows\Temp).
Change the default account (IUSER_servername) to the Web Services logon account (CNTD_WebServices) created
during Data Center Setup and give this account Full Control permissions to the Temp folder (depedong on your
operating system, either WINNT\Temp or Windows\Temp).
In the Add or Remove Programs Control Panel window, select Add/Remove Windows Components.
2.
In Windows Components Wizard, select Application Server from the Components section and click Details.
3.
In the Application Server window, select Internet Information Services (IIS) and click Details.
4.
In the Internet Information Services (IIS) window, select Common Files, Internet Information Services Manager,
and World Wide Web Service.
5.
Click OK.
2.
3.
4.
Click New.
5.
6.
Click OK.
7.
8.
Use Control Panel Services to start World Wide Web Publishing Service.
The CNTD_DCServices account must have change permission, the CNTD_CDMaker account must have read
permission and the account used to log on to the Data Center must have administrator privileges that grant full rights to
these shares.
Any accounts used to access the customer archives, such as those used by CD Maker must be in the same domain.
63
2.
In the System Properties window, click the Network Identification tab and then click Properties.
3.
In the Member of section, type an appropriate domain name in Domain. All servers in the Data Center configuration
must be in the same domain.
4.
In the Domain Username and Password pop-up window, provide a username and password for an account that has
administrator privileges in the domain. Refer to Security requirements, on page 60 for more information.
Note
Using the Data Center servers as domain controllers places an additional performance load on them
and is not typically recommended.
5.
When you restart the server, log on with an account that has administrator privileges in the domain that you specified in
this procedure. You will use this account to set up the Data Centers.
64
1.
2.
3.
4.
5.
6.
a.
b.
c.
d.
Click Next on the first window of the Upgrade Device Driver Wizard.
e.
Select Display a list of the known drivers for this device so that I can choose a specific driver, and click Next.
f.
For non-DAS tape libraries: Click Have Disk. From the Connected Backup CD, select the DLT8000.INF file
for a DLT tape drive or the SW2AIT.INF file for an AIT tape drive. Install the tape device driver from the CD.
g.
For DAS libraries: Click Have Disk and install the drivers that came with the drivers installed in the DAS or
download the latest version from the vendors Web site.
Reboot the server so that Windows reassigns tape device numbers to the tape library.
Note
Numerous time-synchronization tools are available that run as a service under Windows to
synchronize the time between the two servers.
65
Select the Windows Backup utility from the Windows Accessories \ System Tools menu in the Start menu.
2.
3.
In the Backup utility, click the Tools menu and select Create an Emergency Repair Disk.
4.
Follow the online instructions. When prompted, be sure to select to back up the registry.
5.
When the repair disk is created, remove and label the floppy disk.
Select the Windows Backup utility from the Accessories \ System Tools menu in the Start menu.
2.
3.
4.
5.
Follow the online instructions. When prompted, be sure to select to back up the registry.
6.
When the repair disk is created, remove and label the floppy disk.
SQL server
Microsoft has implemented a processor-based licensing model to simplify SQL Server licensing. Under this new model, you
acquire a Processor License for each processor running the SQL Server software. If you have made a processor inaccessible
to all operating system copies on which the SQL Server software is set up to run, you do not need a software license for that
processor.
A Processor license includes access for an unlimited number of devices to connect from either inside the corporate LAN or
WAN or outside the firewall. You do not need to purchase additional Server licenses or Client Access Licenses (CALs). The
Processor license is all you need.
If you are installing SQL Server on the Web server or the DataBundler computer, it is only necessary to install the Client
Networking Utility. A full installation of SQL Server is not needed.
Installing SQL Server on a SQL Server farm for use with the Data Center is not a supported configuration. SQL Server must
be installed locally for use with the Data Center.
66
1.
The Data Center server supports the installation of the default instance of the SQL Server only.
2.
When prompted, select Install SQL Server Components, and then Database Server, Standard Edition.
3.
When prompted to specify the disk drive for the SQL Server installation path, specify the SQL database partition you
created in the section Create data partitions, on page 63.
4.
Ensure that SQL Server is set to allow Windows authentication. Create a domain account with local administrator
privileges for SQL Server to run. You should use the same logon account for all SQL Servers in your Data Center.
5.
6.
When installation is complete, apply the appropriate SQL Server service packs to the server.
Visit the Resource Center to obtain any additional software upgrades or hotfixes and install them.
From the Enterprise Manager console's Action menu, click New SQL Server Registration to register the current server.
When prompted, type in the name of the server and select Use Windows Authentication. You must use a domain
account to login into the SQL databases on the Data Center servers.
67
System requirements
Because of the added workload associated with Support Center and Account Management Website activities and because of
security considerations with a Web server, you should install Support Center and Account Management Website on a server
that is separate from the Data Center server.
Hardware requirements
Your Web server must meet the following minimum hardware requirements to run Support Center or the Account
Management Website:
Hardware
Support Center
Processor
500 MHz
1 GHz
RAM
1 GB
1 GB
4 GB
4 GB
20 GB
10 GB
Computers accessing Support Center or Account Management Websitemust meet the following hardware requirements:
68
Component
Requirement
Processor
RAM
64 MB or higher.
Software requirements
To install the Support Center and Account Management Website software, your Web server must have the following software
installed:
Component
Requirement
Operating system
Database
Internet
Refer to Windows server installation guidelines, on page 61 for information on installing this software.
Component
Requirement
Operating system
Web browser
69
Windows 2003 Server or Windows 2000 Server, Service Pack 4. Refer to Windows server installation guidelines, on
page 61 for installation information. Verify that Internet Explorer version 6.0 or higher is included in the installation.
Microsoft SQL 2000 Client Tools, Service Pack 4. Refer to SQL server, on page 66 for installation information.
Microsoft Internet Information Server version 5.0 or higher. Refer to the section below for installation information.
Note
If you are using the Microsoft IIS Lockdown tool to secure IIS, be aware that this tool is known to
cause problems in both applications in some circumstances. The URLScan filter in particular is
known to cause problems and should not be installed on the Web server, if possible. If you must use
the IIS Lockdown tool, back up your IIS state prior to using the tool so as to be able to recover should
IIS Lockdown cause problems with Support Center or Account Management Website.
After all supporting software is installed and configured, you can install Support Center and Account Management Website.
Regional settings
Make sure that both the default locale and the current locale of the Web server is set to English (United States). Use the
following steps to locate and verify this setting:
70
1.
2.
3.
4.
Click Set Default to verify that the default locale is also English (United States).
If you are hosting your own Data Center, you must have a license for the MyRoam feature installed on the Data Center
server. If your current license file does not include the MyRoam feature, contact Support to purchase this license.
To enable the MyRoam feature in a community, you must have the technician permission, Allocate Licenses to SubCommunities enabled.
To enable the MyRoam feature for specific Agent configurations, you must have the technician permission, Modify
Agent Configurations enabled.
MyRoam installation
To install the MyRoam software, run Data Center Setup and select the Install Website with MyRoam option. Refer to
Installing Support Center and Account Management Website, on page 81 for procedures that explain how to install software
on the Data Center server.
Note
In this release, only PC Agents support the use of the MyRoam feature.
Log on to Support Center using a technician ID that has the Allocate Licenses to Sub-Communities and Modify Agent
Configurations permissions enabled.
2.
Select the community where you want to enable the MyRoam feature.
3.
4.
On the Manage Features page, locate the row for the MyRoam feature and select Enabled in the PC Agents column.
5.
Click Save.
6.
7.
Expand the Website Settings node and select the configuration for which you want to enable the MyRoam feature.
71
8.
Select Options.
9.
In the Account Management Options section, select the option, Allow end users to retrieve files using the
MyRoamfeature.
72
6
INSTALLING THE DATA CENTER SOFTWARE
About this chapter
This chapter explains how to install and configure the Data Center software on servers that do not have a previous Data
Center installation. If your server has Data Center version 6.2, 7.0, or 7.1, or 7.5., or 8.x, visit the Resource Center for
instructions about upgrading your server(s) to version 8.2.
This chapter contains the following topics:
To learn about...
Refer to:
73
CAUTION
You must write down the Master Encryption Key (MEK) created during Data Center Setup. Store the
written information in a safe place. The MEK is required for reinstalling Data Center software in the
event that reinstallation is necessary.
Note
For the Setup application online Help to work correctly, we recommend running the setup
application locally. If you run the setup program remotely, the security settings in Microsoft will
prevent access to the Help system.
2.
Ensure that the Regional Options setting in Windows Control Panel is set to English, United States. This setting is
necessary on all Data Center servers.
3.
Run the Data Center Setup executable to install a standalone Data Center or a mirrored Data Center (either one pair of
mirrored servers or an entire cluster). You can include or omit HSM, as required. You can also install Support Center
and optionally, the MyRoam application, on the Web server using Data Center Setup.
When you begin the installation process, the program performs an initial check to see whether or not the configuration
prerequisites have been met. If there are problems, you are prompted to correct them.
74
4.
If all prerequisites are met, you can continue to follow the installation step by step. If questions arise as to how to proceed
with any step, click the Help button on the window for specific information on that stage of the process.
5.
After you install the software on each of the servers in your Data Center, refer to Verifying successful installation, on
page 76 for a list of items to check to verify that installation was successful.
Reinstallation
If, under the guidance of Support, you find it necessary to reinstall the Data Center software, it is important to understand
what it can and cannot accomplish. When reinstalling the Data Center software be aware of the following:
The same version of the software that is currently running on the Data Center must be used.
Privileges given for Windows registry keys, file shares, file directories, and databases are only added to, no privileges
are taken away.
You must have the MEK created during the initial Data Center installation to complete a reinstallation of the Data Center
software.
You should not reinstall the Data Center software without the guidance of Support. There are a limited number of reasons to
perform this task, therefore Support needs to be consulted to be sure that reinstalling is the best solution.
75
Mirror site replication (if using a mirrored or cluster configuration) is operating correctly.
Log on under the same account in which you installed the Data Center software.
2.
Using the Services Control Panel, verify that the following services are on the list and are started:
Backup Server
DC Alerter (if used). If you did not configure SMTP settings during installation, this service is disabled.
Index Server
Pool Server
Compactor
IIS Admin Service (running on the Support Center and Account Management Website servers)
MSSQL Server
World Wide Web Publishing Service (running on the Support Center and Account Management Website servers)
3.
If the services are not started, reboot the server and check again. They should start automatically when you reboot.
4.
From the Data Center Start menu, open Data Center Management Console (DCMC). If necessary, refer to DCMC Help
for instructions on adding a Data Center to DCMC. Verify that the services for your Data Center are running.
5.
In DCMC, expand the Events node and click Application. Look at the events for notification that BackupServer,
DCAlerter, PoolServer, ReplicationServer (if mirrored or clustered), IndexServer, Compactor, HSMPurge, and Backup
HSM (if used) have started.
6.
Verify that there are no warning or error events in the event log. If you have installed a mirrored pair of Data Centers,
you can see warnings from the first Data Center that it could not find its mirror. These are normal as long as they only
occurred before and during the time the mirror was installed.
76
The following procedure describes how to install a sample user account onto a client and then backup and retrieve data.
1.
2.
Using Support Center, create an Agent Setup file. The Agent configuration should include rules that select a small
number of files to back up. Refer to Support Center Help for instructions that explain how to create an Agent
configuration and distribute it to clients.
3.
Use the Agent Setup file on a client computer to install the Agent and register a new account on the Data Center.
CAUTION
Do not install the Agent software on the Data Center or MyRoam servers. Doing so produces problems.
4.
If using a Server Agent, select the Backup Set tab, select a few small files to back up, and click Backup Now. You
should see that the Agent initiates a backup and that the backup completes successfully.
5.
6.
a.
Proceed through the installation sequence until prompted to select files for backup. Select Let me select which files
and/or directories to back up.
b.
Continue until you are asked to begin the scan, and then do so. When the scan completes, you are presented with
the Explore to pick files view in the Backup View. Select a few small files to back up, and then click Backup
Now. You should see that the Agent initiates backup and that the backup completes successfully.
If using a Server Agent, select the Retrieve tab, select a file to retrieve and click Retrieve. When prompted to do
so, select Save all files in folder and enter a folder name in the Retrieve Options window. Then click Retrieve
again. You should see that a file retrieve is initiated and completes successfully.
b.
If using a PC Agent, select Retrieve View, pick one file to retrieve, and click Retrieve Now. Select Retrieve all
files to a different directory, specify a new folder, and click OK. You should see that a file retrieve is initiated and
completes successfully.
7.
If you are testing a standalone Data Center, uninstall the Agent from the test client using the Windows Add/Remove
Programs utility.
8.
If you are testing a mirrored Data Center do not uninstall the Agent. You can use it for other verification tasks.
77
Start DCMC. Refer to DCMC Help for instructions about adding a Data Center to DCMC.
2.
If using a tape library, be sure that tapes are inserted and labeled.
3.
In DCMC, force a migration. Refer to DCMC Help for a procedure to complete this task.
4.
Use DCMC to view the Application and DCMaint event logs. A blue event indicates that a migration has been
successful. There should be no BackupHSM warning or error events in the event log.
Normally, migrations happen automatically, so it is not necessary for you to perform this manually in a production
environment.
78
1.
Use DCMC to stop the BackupServer service on the first Data Center server. Refer to DCMC Help for specific
instructions.
2.
Using the Agent you created to verify the BackupServer operation, click Retrieve View. Select a file to retrieve, and
then click Retrieve Now (refer to the Agent Help for specific instructions). You should see that a file retrieve is initiated
and completes successfully using the mirror Data Center server.
3.
4.
Use DCMC to shut down BackupServer on the second Data Center server.
5.
Use the Agent to retrieve a file as you did in step 3. When you click Retrieve Now, you should see that a file retrieve is
initiated and completes successfully, using the mirror Data Center server. This operation confirms that the account
registration information and the data that was backed up were properly replicated between the two Data Centers.
6.
7.
Uninstall the Agent using the Windows Add/Remove Programs utility. The program you should remove is Connected
Backup or Connected DataProtector Agent.
8.
Delete the temporary folder and the files you used for the verifications.
Verify the test computer can ping the Data Center server(s).
Verify all firewalls are properly configured to allow access to port 16384 on the Data Center server(s) from the test
computer to all IP ports.
Verify that you placed the correct IP address(es) into the test Agent configuration. If using a PC Agent, check the Agent
settings. If using a Server Agent, use the Agent Settings node in Support Center to check the Agent settings.
Check the Application and DCMaint event logs for the Data Center to see if there are any messages.
Another possible problem is that the Agent might report an Internal Server Error. Review the Data Center's Application
event log (for mirrored sites, make sure you look at the correct server).
2.
In the details pane, right-click BackupServer and click Properties from the pop-up menu.
3.
In the Log On tab, verify the account name in the This Account box is an account as described in Security requirements,
on page 60.
Check that the tape library is supported. For a list of tape libraries and tape drives supported by the Data Center software,
visit the Resource Center and refer to Supported Archive Storage Devices.
79
80
Ensure the operating system can detect the tape library, has a medium changer, and has at least one tape drive listed in
the Device Manager.
Ensure that Removable Storage Manager (RSM), a Windows Server component, is disabled for both the tape library and
for all tape drives associated with it. Refer to the Removable Storage Manager, on page 58 for instructions about
disabling RSM for tape libraries and tape drives.
Check that all tape devices start at Logical Unit Number (LUN) 0; the Data Center does not recognize tape devices on
any other LUN.
Note
If your Data Center supports more than 10,000 accounts, you should not run Support Center and the
Account Management Website on the same server.
81
Configuration tasks
Configuration tasks
Changing the location of the MyRoam scratch folder
When the MyRoam application receives a request to retrieve files, it sends the request to the Data Center server. The Data
Center server creates a folder for each requested download in a Scratch folder located on the Data Center server, and uses
the Scratch folder to temporarily store the rebased files required to satisfy the retrieve request.
By default, the Scratch folder is located in the Data Center installation folder (typically, C:\Data Center). You may
want to change the location of this folder to a drive that has a significant amount of available disk space, if you expect to
have a large number of MyRoam requests or you expect the requests to be large requests.
Create a new Scratch folder in the location of your choice. The name of this folder must be Scratch.
2.
3.
Open the registry editor and change the value of the following registry key to refer to the new location:
HKEY_LOCAL_MACHINE\SOFTWARE\Connected\BackupDataCenter
4.
Configuring DCAlerter
Note
When you configure the DCAlerter service, verify that the anti-virus software on the server is not
blocking the alerts that DCAlerter sends.
DCAlerter uses email to notify designated individuals when specific events occur on the Data Center. Data Center Setup
activates this feature if you specify your SMTP mail host and an administrator email address during installation.
If you did not enter the SMTP mail host information during Data Center Setup, the DCAlerter feature is not activated. Data
Center Setup installs a default set of events for notifications.
To modify the installed settings, use DCMC. Refer to DCMC Help for a procedure to modify the installed settings.
82
7
INTEGRATING THE DATA CENTER WITH
ENTERPRISE DIRECTORY
About this chapter
This chapter contains the following topics:
To learn about
Refer to
The steps required to integrate a Data Center with enterprise Integration process, on page 86
directory.
The tasks required before you start the integration.
Configuring the firewall for enterprise directory integration. Configuring your firewall, on page 89
Enabling Support Center access for enterprise directory
integration.
83
You can map your entire Data Center to enterprise directory, or you can map only specific communities. If you map a
community to enterprise directory all of its subcommunities will use enterprise directory as well. It is important to map a
community to enterprise directory before allowing PC Agents to register to the community.
Enables Support Center technicians to use their enterprise directory passwords for authentication.
Prevents Support Center technicians from having access to Support Center after reassignment or termination.
Allows PC Agent accounts to be authenticated with the current enterprise directory user account and password. This
means PC Agent users can use their enterprise directory credentials to register PC Agents and retrieve data.
You cannot use enterprise directory to authenticate Server Agent accounts.
Facilitates PC Account Lifecycle Management, since your PC accounts are based on your existing enterprise directory
accounts.
Enables automatic population and updating of PC accounts. This is very useful for account management, reporting, and
troubleshooting.
84
If your organization uses Lotus Domino, please contact Connected Support for more information and assistance.
Support for Lotus Domino requires modifications to the databases that reside in the Data Center.
85
Integration process
Integration process
Integration phases
Before you start the integration, you should understand the following phases that must occur to ensure a successful
integration with enterprise directory:
1.
Preparing your IT infrastructure for integration and gathering the information you need to complete the procedures in
this document.
2.
Configuring your firewall to permit Support Center access to your enterprise directory.
3.
4.
Defining the Enterprise Directory Setup Properties in Support Center, which includes mapping Support Center data
fields to corresponding enterprise directory data fields.
Complete each of the requirements and steps in one phase before continuing on to the next phase.
CAUTION
Read this entire procedure before you plan to integrate, and make sure you understand all of the
requirements and steps.
86
Note
An LDAP browser helps you identify and locate all of your enterprise directory accounts and
servers. During the preparation state, is it useful to use the LDAP browser to gather information and
identify the server(s) that you want to permit Support Center to access. Check to see if your
enterprise directory software includes a browser. If it does not, you can obtain a free LDAP browser
from the Internet.
Do the following to prepare for integration with enterprise directory:
1.
Install or upgrade your Data Center to the current version. For more information about installing your Data Center for
the first time refer to Chapter 6: Installing the Data Center Software, beginning on page 73. For more information about
upgrading your Data Center, visit the Resource Center.
2.
Confirm that your organizations enterprise directory is one of following supported directory services:
3.
Verify that enterprise directory accounts exist for all users to whom you are deploying PC Agents. This also includes
users who are responsible for accessing Support Center to manage your Connected Backup user accounts. (These users
are commonly referred to as Support Center technicians.) If you plan to use enterprise directory to authenticate PC Agent
registration, this is critical. Users without enterprise directory accounts are not able to authenticate, and therefore the
Agent fails to register.
4.
Locate the enterprise directory source server that has access to all the user accounts to which you are planning to deploy
Connected Connected Backup Agents. For best results, this server should be as high up as possible in the enterprise
directory architecture. Make note of the URL for the source server; you will need it later to grant Support Center access
to your enterprise directory.
5.
Install Secure Socket Layer (SSL) certificates on each enterprise directory server that the Data Center servers and the
Support Center server will read. Using SSL is strongly recommended to prevent unauthorized interception of user
credentials.
87
6.
Create a new enterprise directory account that has read permission (and only read permission) on the enterprise directory
server that you identified in step 4. This account requires read access to all enterprise directory accounts and to your
enterprise directory schema. This user account is used by Support Center to read information from your enterprise
directory. It is used during the initial integration, and for every single communication from Support Center. Make note
of it; you will need to enter this user account and password in Support Center.
CAUTION
Use a password that is a minimum of eight characters, preferably a combination of letters and numbers.
Keep in mind that if you change this enterprise directory account password, you must also change it in
Support Center.
88
Permit the Data Center server IP addresses to connect inbound through port 636 to each of the IP addresses associated
with the DNS name of your enterprise directory server.
2.
Permit outbound connections through port 16384. This is the port used by Agents to back up data to the Data Center.
3.
Permit outbound HTTPS/SSL connections through port 443. This enables technicians to connect to Support Center and
Agent users to retrieve files using the MyRoam application.
89
2.
Locate the subcommunity that you want to integrate with your enterprise directory. The left hand navigation tree lists
your root and subcommunities. (You might need to expand your root community node to locate the subcommunity that
you want to integrate.)
3.
Click Enterprise Directory in the Community Status page to access the Enterprise Directory Setup page.
4.
In the Enterprise Directory Server URL field, type the URL of the source server. For example, a valid URL for an
Active Directory server would look similar to this:
LDAP://my.edserver.com/dc=edserver,dc=com
5.
Check the Use SSL option. This ensures that inbound Support Center connections are secure.
6.
In the Connection Login DN box, type the enterprise directory user account ID that you created for Support Center to
enable it to connect to your enterprise directory. For example, an Active Directory account would be similar to the
following:
supportcenter@edserver.com
7.
In the Connection Password box, type the account password. Note that this password is encrypted and stored on the
Data Center, and access control is limited to technicians that have the Change the Enterprise Directory user
permission. Refer to Support Center Help for more information about specific technician permissions.
8.
If you want Support Center to use your enterprise directory to authenticate all users who attempt to register a Connected
Backup account, check the Verify existence of users through Enterprise Directory option.
Note
Connected Backup only verifies against deleted PC accounts, it does not verify against disabled
accounts. Disabled accounts are treated the same as active accounts. If you create an account for a
disabled enterprise directory account, you can use Support Center to manually change the account
status to On Hold or Cancelled.
9.
90
Indicate how you want to handle users who do not pass authentication by selecting one of the following options:
Select Change the Account Status to On Hold if you want to temporarily place these accounts on hold until you
can independently verify whether or not they should be allowed to register.
Select Change the Account Status to Cancel if you want to permanently deny the account to register.
10. Continue to the Map data fields procedure to complete the integration.
91
92
To this Netscape
Directory field:
User Class *
Inetorgperson
InetOrgPerson
User
LoginID*
Cn
CN
userPrincipalName
UniqueID*
Uid
Uid
objectGUID
First Name
GivenName
Given Name
givenName
Middle Initial
Initials
Initials
initials
Last Name
Sn
Sn
Sn
Address1
Postaladdress
Postal Address
StreetAddress
Address2
Street
Street
Street
City
City
City
State
st
ST
st
Zip
Postalcode
PostalCode
Postalcode
Country
Country
Country
Telephone
TelephoneNumber
TelephoneNumber
TelephoneNumber
Company
Company
Company
company
Department
departmentNumber
departmentNumber
Department
In the Enterprise Directory Setup page, type the name of the corresponding enterprise directory data field in each field
provided.
Note
Consult the administrator of your enterprise directory if you are unsure which field names to map to
the Support Center fields.
2.
Double-check the spelling, capitalization, and spacing of each field name that you entered.
3.
93
94
Create a new technician account in Support Center and verify that you can use that account to log into Support Center.
Refer to Connected DataProtector/SV Agent Deployment or your Connected Backup documentation set for
instructions about creating technician accounts.
Create a new test PC Agent configuration within the Support Center community that you integrated with your enterprise
directory. Refer to Support Center Help for more information on how to create a PC Agent configuration.
Deploy and install that PC Agent to an enterprise directory user account. Verify that you can install and register the new
PC Agent using the users enterprise directory user account as credentials. Refer to the Connected Backup
documentation for instructions about PC Agent deployment.
After installing a test PC Agent, confirm that the account information appears in the PC Agent. If the account
information fields in the PC Agent are blank, confirm that the fields are populated within the enterprise directory user
account.
8
MANAGING THE DATA CENTER WITH DCMC
About this chapter
This chapter contains the following topics:
To learn about...
Refer to:
97
DCMC overview
DCMC overview
About the DCMC
The Data Center Management Console (DCMC) is a snap-in for the Microsoft Management Console (MMC). The DCMC
enables you to perform a variety of tasks necessary to monitor and control Data Center operations, including managing the
BackupServer, PoolServer, ReplicationServer, IndexServer, BackupHSM, HSMPurge, and Compactor.
DCMC tasks
The DCMC enables you to perform a variety of tasks necessary to monitor and control Data Center operations.
Note
You should be familiar with the Microsoft Management Console (MMC) to be able to work with the
DCMC.
For specific information and procedures on working with the DCMC, refer to the DCMC Help, which you can access through
the DCMC.
With the DCMC, you can:
Start, Pause, and Stop the Data Center services. The icons in the console tree, as well as the information in the details
pane, show whether the Data Center service is started or stopped.
View and modify properties for each Data Center service. The DCMC enables you to view default properties and
properties chosen during Data Center Setup. You can also change these properties as needed (contact Support for
guidance before changing any Data Center service properties).
Monitor multiple Data Center servers simultaneously. The DCMC enables you to monitor all of the servers in a
mirror or cluster at one time.
Manage space used in archive storage devices. You can use the DCMC to view status and monitor usage of all archive
storage devices including tape libraries and EMC Centera.
Monitor current status. Use the DCMC to monitor the status of HSM requests, operations, and tape drive availability.
View event logs and run the Windows Event Viewer. You can view event logs for Data Center operations from within
the DCMC. You can also run the Windows Event Viewer for a selected Data Center. This information is typically used
for problem diagnosis.
Access requirements
To use DCMC, log in to the Data Center server or a remote computer that has the Data Center Toolkit installed using an
account that had administrative privileges. You must also be able to access the following:
98
The Service Control Manager, which allows you to start, stop, and query services.
The disk volumes attached to each machine. Data Center Setup sets these device shares to only allow access to Domain
Administrators by default. You can change this setting to allow access to other administrators.
The SQL Server on the selected server. You must be able to perform read queries on SQL tables as well as inserts,
updates, deletes, and stored procedure calls. The Data Center Setup procedure grants access to the Domain
Administrators group, but you can extend these permissions to other administrators that are not part of the group.
DCMC overview
Starting DCMC
You can run the DCMC on a Data Center server or remotely, if your remote computer has the Data Center Toolkit installed.
Do either of the following to start the DCMC:
b.
c.
If you are working on a remote computer that has the Data Center Toolkit installed, do the following:
a.
b.
c.
If your Data Center does not appear in the DCMC console tree, refer to DCMC Help for instructions to add it.
99
Console tree
Details pane
The console tree, including DCMC-specific icons to make visualizing DCMC components easy.
The details pane, which provides information based on your selection in the console tree.
Console tree
The DCMC console tree (the left pane of the window) contains a view of all of the components of your Data Center, as shown
in the following example:
Console Tree
The console tree uses icons to represent each of the Data Center components. These icons are organized hierarchically to
make it easy for you to locate the components you need:
Servers are listed under the Data Center to which they belong.
Services and components are listed under the server to which they are attached.
Icons for services show whether the service is running, paused, or stopped.
If a service or component contains subcomponents, a plus sign appears to the left of the component's icon. To view the
subcomponents of a given component, expand it by clicking the plus sign (+) or double-clicking the component name.
101
Details pane
The DCMC details pane displays specific information on the item you select in the console tree (discussed in the previous
section). For example, if you select a Data Center in the console tree, the details pane shows the statuses and other
information about all of the services running on the servers connected to that Data Center.
The following example shows the DCMC details pane:
You can set the DCMC to automatically refresh the view of the details pane at set intervals. By default, the service statuses
in the DCMC are set to refresh every five minutes. You can also manually refresh the view of the details pane if you do not
want to use the automatic refresh feature.
Menus
The menus appear in the following forms:
The MMC menu bar includes the Console, Window, and Help menus. These menus are standard to MMC.
The DCMC snap-in menu bar includes the Action and View menus. These menus provide access to DCMC functions
as well as display options for the console tree and details pane.
A shortcut menu appears when you right-click items in the console tree and details pane. This menu enables you to
modify the selected item's properties or to run a command that is relevant to the selected item.
Toolbars
The DCMC contains snap-in toolbars to augment the MMC toolbar. Together, the toolbars provide quick and easy access to
console functionality and DCMC commands, which you could otherwise access through menus. The DCMC also has a
description bar, which displays the name of the current view along with the time the view was last refreshed.
103
9
INSTALLING MANAGEMENT TOOLS
About this chapter
The Connected Backup software includes several tools that you can install on a Data Center for management purposes. It
also includes the DataBundler application, which builds account images you can use to retrieve files and restore a system
using Heal when a network connection is not available.
This chapter contains the following topics:
To learn about...
Refer to:
Available tools
105
Tools overview
Tools overview
The DataBundler application
The DataBundler application is not installed on the Data Center server; you must install it separately.
The DataBundler application allows you to create an image of an Agent account that includes all of the backed-up files from
a specific date.
You can burn the account image onto a CD or DVD. For Server Agent accounts, you can also store the image on a Network
Attached Storage (NAS) device. You can configure DataBundler to automatically create account images when it receives
requests or you can build images manually.
When the DataBundler application builds an account image, it also includes a copy of the Agent application. You can use the
Agent user interface to retrieve files or restore a system using Heal from the account image. You can also use the command
line interface for these tasks.
Refer to the Connected Backup/PC Product Overview manual and the DataBundler Help for additional details about this
application.
Windows 2003 Server Standard Edition or Windows 2000 Server with Service Pack (SP) 4 and all security hotfixes.
Free hard disk space in one volume approximately equal to twice the size of the largest account (at least 6 GB is
recommended).
The DataBundler client should be in the same domain as the Data Center server(s) and must have high-speed LAN
access to the server(s).
While burning a CD or DVD, do not use the DataBundler client for any other purpose. It is recommended that you dedicate
the client solely to CD or DVD making. If you expect to burn a large number of CDs or DVDs, install DataBundler on more
than one computer. Each DataBundler-enabled computer can only burn one CD or DVD at a time.
Before installing
Before starting the procedure in this section, add the CNTD_DataBundler user account to the Power Users group on the
computer where you plan to install the DataBundler application. Power User privileges are required to successfully burn CDs
and DVDs.
Note
If you are upgrading your Data Center from an earlier version, you can continue to use the
CNTD_CDMaker user account on the computer where you installed the DataBundler application.
Refer to the DataBundler Help for details about using this application.
2.
3.
Copy the DataBundler software to a convenient location on the computer. You can copy the DataBundler folder from
the folder where you installed the Data Center software or you can visit the Resource Center to download the
DataBundler software.
4.
5.
Follow the setup program instructions to complete the installation. When prompted for the folder into which the program
will be installed, specify the location of the large disk volume onto which account images are created. The installation
program creates a share for the folder, so that all members of the domain can access it.
107
Ensure that the DataBundler application has write access to its own installation directory.
When starting the DataBundler application, use the user account you specified for the application when you installed
the Data Center (CNTD_DataBundler or CNTD_CDMaker).
The DataBundler user account must belong to the Administrators or Power Users group.
When specifying the location for the media images in the DataBundler application, use a UNC (Universal Naming
Convention) path to a directory the DataBundler application has privileges to access. If the specified path is located on
the local machine, the directory must have write permissions enabled. If the path is located on a remote machine, the
directory must be shared with write privileges enabled.
2.
Install the DataBundler application (do not uninstall the CD Maker software).
The Data Center Toolkit is intended for installation on a non-Data Center computer that is in the same domain as the
Data Center server(s).
Install the Data Center Toolkit on computers that have an English Windows operating system installed only.
The computer on which you install Data Center Toolkit must have network access to the Data Center server(s).
Navigate to the folder where you installed the Data Center software.
If you do not have access to the Data Center software, visit the Resource Center to obtain a copy of the Data Center
Toolkit.
2.
In the folder named Toolkit, double-click setup.exe and follow the prompts.
Tdate
109
10
EVENT LOGGING
About this chapter
This chapter discusses several concepts to help you understand how the Data Center logs information. This chapter contains
the following topics:
To learn about...
Refer to:
Trace logging
111
Event Logging
Event Logging
Overview of event logging
Message logging allows for multiple Data Center components to follow the same standard for reporting event messages,
while providing the additional benefits of multiple levels of logging detail.
The Data Center provides the following levels of logging detail:
Visit the Resource Center for a list of event messages for each component and for information about using the event logs.
The Application event log contains only the event messages specifically designated for the Application event log.
The DCMaint event log contains those event messages specifically designated for the DCMaint event log and repeats
the event messages designated for the Application event log.
If any trace flags are turned on for a Data Center component, the generated trace log file for that component contains
the event messages specifically designated for the trace log and the event messages designated for the DCMaint event
log for that component and the event messages designated for the Application event log for that component.
Note
In order for the Application log to be automatically saved and cleared, the Data Center must be the
source of the message that will cause the log to exceed capacity. In other words, if a different server
component such as SQL Server fills the log, then the log will not automatically be saved and will have
to be saved and cleared manually.
113
Trace Logging
Trace Logging
Using Trace Logging
Trace logging provides for additional event logging when high-level troubleshooting may be required. Trace logging is not
intended to be used in normal circumstances and should typically be used under the advice and assistance of Support.
To generate those event messages that are associated with a trace log, the corresponding trace flag values must be set for the
Data Center component in the Windows registry. Visit the Resource Center for information about turning on trace logging
for specific components.
11
INTRODUCTION TO DATA CENTER MAINTENANCE
About this chapter
This chapter describes the types of maintenance tasks you should perform on a regular basis. This chapter contains the
following topics:
To learn about...
Refer to:
The Data Center maintenance tasks described in this manual Maintenance task overview, on page 118
117
12
DAILY MAINTENANCE
About this chapter
This chapter provides an overview of the daily maintenance tasks required for optimal Data Center performance. Because
there are different tasks that you should perform throughout the day, this chapter distinguishes between morning tasks and
afternoon tasks.
Refer to Daily maintenance checklist, on page 166, for a checklist that you can use to perform routine daily maintenance
checks.
This chapter contains the following topics:
To learn about...
Refer to:
119
Backs up the SQL transaction logs for the Directory and Registry databases (standalone Data Centers only).
Migrates archives to the Secondary Tape Set, if a Secondary Tape Set is being used (only on systems with Hierarchical
Storage Manager).
Calculates statistics on database size, account data totals and archive storage device totals. An archive storage device is
any component used to store data, for example, a tape library, Centera, or SAN device.
Note
If you are running a mirrored or clustered Data Center, the SQL databases are replicated between the
servers. Therefore, the databases are not backed up using the Daily Automatic Procedure. The
complete mirroring of the databases on a mirrored Data Center increases the ease and decreases the
time needed to recover from a database loss.
The script writes the results of these tasks to the dailymaint.out and sqldump.log files, which are located in the
Data Center folder. The difference between these files is that the dailymaint.out file stores the results for only the
previous day while the sqldump.log file. stores an ongoing history.
Open either the dailymaint.out or the sqldump.log file. Both files are located in the C:\Data Center\
folder by default.
2.
Review the output file for errors that might have occurred while the maintenance script was running. The output file
should indicate the following:
3.
The Directory and Registry database transaction logs have been successfully backed up at the time specified, if you
are running a standalone Data Center.
The migration to the Secondary Tape Set was successful, if your Data Center uses a Secondary Tape Set.
Open the Application event log using the Data Center Management Console (DCMC) to verify no errors were recorded
in conjunction with the daily SQL transaction logs backup or the migration of data to the Secondary Tape Sets. You can
review the Application log by expanding the Events node and clicking Application.
If problems are reported in either the log files or the Application event log, you should visit the Resource Center for further
information on errors in the Application event log.
Note
If you are running a large standalone Data Center, you can schedule the dailymaint.sql script
to run more than once daily. Increasing the frequency can reduce the risk of data loss and decrease
the time required to recover a failed system.
2.
Click the History tab and select several of the most recent session logs.
3.
Click View Details to display the log for the selected sessions.
4.
5.
Look for any errors or indications of connection problems. Keep in mind that these types of problems can occur from
time to time and might not indicate a persistent problem.
Open the Disk Status tool and enter your Data Center name in the Server box.
2.
Click Update. The Disk Status tool displays information on disk status.
3.
Make sure that all indicators are within normal parameters (within the appropriate colored indicator).
4.
Ensure that the Purge Start level has not been exceeded.
5.
Ensure that the Migrate Start level has not been exceeded.
6.
121
Operator is alerted.
Additionally, make sure that the alert system is configured properly to respond to the various conditions that are considered
alert-worthy.
2.
3.
4.
Verify that the message is in the Application event log and proper notification is made.
Verifying that Support Center and the MyRoam application are running.
Open DCMC and expand your Data Center node in the Console tree.
Note
If you do not see your Data Center in the tree, right-click Data Centers in the Console tree pane,
and then click Add a Data Center on the shortcut menu. In the Data Centers window, select the
appropriate configuration for your Data Center and then type the Data Center or server name
(whichever is required based on your configuration selection).
2.
Click the name of the server in the Console tree to view the status of its services in the Details pane. The services include
BackupServer, DCAlerter, ReplicationServer, IndexServer, PoolServer, Compactor, BackupHSM, and HSMPurge,
(HSM services are present only when HSM is installed).
3.
If a service is not running, restart it by expanding the server name, right-clicking the service, and clicking Start Service.
If your request to start the service is unsuccessful, a message is written to the Application event log.
4.
Further verify the status of the Compactor service through the DCMaint log. Expand the Events node and click
DCMaint to view its event messages. Look for messages with a Source of Compactor.
5.
If there are warnings or errors for the Compactor service, check the Compactor log for more information. The
Compactor log is located in the Log Files folder and has the compaction date appended to the file name. If the log
is not being written, refer to Chapter 10: Event Logging for more information regarding logging and trace logs.
2.
Expand your Data Center node in the Console tree and then expand the server name.
3.
4.
Look for any warnings or errors in the log window and review them for any actions you need to take. Visit the Resource
Center for more information regarding actions you need to take for error messages.
123
Verify that Support Center and the MyRoam application are running
To verify that Support Center and the MyRoam application (if your organization uses the MyRoam application for PC
Agents) are running, do the following:
1.
Verify that IIS Admin Service and WWW Publishing Service are both running. Open the Services Control Panel and
verify that the Status for both services is Started.
2.
Verify that Support Center is running. Log on to Support Center from a remote computer and perform a quick lookup
of an account. The default URL for Support Center using the following syntax:
http://servername/supportcenter
In the URL, replace servername with the name of the Web server hosting Support Center.
3.
Verify that the MyRoam application is running. Log on to the MyRoam application from a remote computer. The default
URL syntax for MyRoam is:
http://servername/MyRoam
In the URL, replace servername with the name of the Web server hosting the MyRoam application.
2.
Expand your Data Center node in the Console Tree pane and expand the server name.
3.
Click PoolServer. Review and note the values for SendOnce Queue and SendOnce Status. If the SendOnce Queue is
not zero, refresh the window by pressing F5. The value should decrease after a few minutes.
Check replication
Check replication on each mirrored pair of servers in the Data Center. To check replication (for mirrored and clustered Data
Centers only), do the following:
1.
Open DCMC.
2.
Expand the Data Center in the Console tree and then expand the server name.
3.
4.
Review and note the values for Database rows to replicate and Archives to replicate. If the values are not zero, refresh
the window by pressing F5. The values should decrease after a few minutes.
Check tape drive status and tape requests every morning and afternoon.
Remove tapes that you use for Secondary Tape Sets every morning.
2.
Expand your Data Center in the Console tree and then expand the server name.
3.
4.
5.
If any drives are offline, visit the Resource Center for troubleshooting information for dealing with offline tape drives.
You must also verify that requests for migration and data retrieval are being processed. Do the following:
1.
In the DCMC, expand your Data Center in the Console tree and the expand the server with which you are working.
2.
Select Current Requests under the Backup HSM node to display the requests status. Be sure to scroll all the way to
the right of the status window to see if anything is listed as suspended under the Suspended column.
3.
Refresh this view by pressing the F5 key on your keyboard, and verify that requests decrease over time.
Special circumstances
In addition to performing this task as part of your morning tasks, you should also perform it under any of the following
circumstances:
DataCopier is running.
Open DCMC.
2.
Expand your Data Center tree and then the server name.
3.
Expand the Tapes node and then Tape Sets. Locate and click Secondary migration set.
4.
In the Details pane, view the utilization information for each tape in the tape set.
125
5.
To remove a tape marked full from the library, click TapeID and click the Eject button on the tool bar.
6.
A tape that is not yet marked full must be marked full before being taken out of the library. To mark the tape full and
eject it follow these steps:
7.
a.
Right-click TapeID.
b.
If you remove tapes, be sure to save them in a safe location, such as in another building.
13
WEEKLY MAINTENANCE
About this chapter
This chapter provides an overview of the weekly maintenance tasks required for optimal Data Center performance. See
Weekly maintenance checklist, on page 168 for a checklist that you can use to perform routine maintenance checks.
This chapter contains the following topics:
To learn about...
Refer to:
How to verify the results of the Weekly Automatic Procedure Verify results of the Weekly Automatic Procedure, on
page 128
Backups that you should perform on a weekly basis
127
Clears out the transaction log so that it does not continuously grow.
For HSM configurations with Secondary Tape Sets, migrates data to the Secondary Tape Set.
Note
If you are running a mirrored or clustered Data Center, the SQL databases are replicated between the
servers. Therefore, the databases are not backed up using the Weekly Automatic Procedure. The
complete mirroring of the databases on a mirrored Data Center increases the ease and decreases the
time needed to recover from a database loss.
The name of the script file depends on the media to which you back up your databases:
The weeklymainttape.sql script performs the database backup to tape and is automatically used if there is a local
tape device for backups.
The weeklymaintdisk.sql script performs the database backup to disk and is automatically used if there is no
local tape device for backups.
Both of these files are installed during Data Center installation; however, you should make sure your task scheduler is set to
run the specific file that applies to your configuration.
CAUTION
A weekly, full database backup to disk can consume as much disk space to store the backup files as is
consumed by the actual database. If you perform a backup to disk, then you should use some other utility
to copy the backup files to another medium. Be particularly careful not to allow a new full backup to
overwrite a previous full backup in case the new backup should fail.
You should not backup your SQL databases to the same disk partition as the original SQL databases. If
you were to experience problems with the disk partition, you would risk losing both the databases and
the backups.
Review results
The results of the weekly maintenance script are written to the weeklymaint.out and sqldump.log files, which are
located in the Data Center folder. The difference between these files is that the results for only the previous week are
stored in the weeklymaint.out file, while an ongoing history is stored in the sqldump.log file. Both files are located
in the C:\Data Center folder by default.
Review these output files to verify the following:
The Master, Model, MSDB, Directory and Registry databases have successfully been backed up at the time specified,
if you are running a standalone Data Center.
The Directory and Registry database transaction logs have successfully been backed up at the time specified, if you are
running a standalone Data Center.
The start and end times written at the start and end of the output file are consistent with the actual start and end times of
the backups.
2.
Expand the Data Center in the Console tree and expand the server name.
3.
Note
If you are running a large standalone Data Center, you can schedule the weeklymaint.sql script
to run more often. Increasing the frequency can reduce the risk of data loss and decrease the time
required to recover a failed system.
129
Backup tasks
Backup tasks
Overview of tasks
During weekly maintenance, you should back up:
Agent configurations
PEM files
\Customers folder
SQL database
Customers folder
The Customers folder is where end-user data is written. If you are running a disk-only configuration, use Windows
Explorer to check the available disk space on all Customers volumes.
If you are running a Data Center with HSM, use the Disk Status tool to check for available disk space on the Customers
volume. Refer to the Connected Backup/PC Product Overview manual for information about the Disk Status tool.
SQL database
The SQL database continues to grow throughout the life of the Data Center. Do the following to check for available disk
space:
1.
2.
In the left pane, expand Microsoft SQL Servers down to and including your Data Center server.
3.
4.
To activate the Taskpad view, right-click Directory and then click View. Select Taskpad from the shortcut menu. The
Taskpad view displays three sections: Database, Maintenance and Space allocated.
5.
In the Space allocated section, note the space used by both the data and the transaction logs. The unused space plus free
space on the disk partition should be at least two times the size of the data and transaction logs.
6.
Calculate how much the used disk space grew since the previous weekly check to assess how much disk space the
databases need over the next ten weeks or so.
CAUTION
You should not back up your SQL databases to the same disk partition as the original SQL databases. If
you were to experience problems with the disk partition for any reason, you would risk losing both the
databases and the backups.
131
General tasks
General tasks
Check System Time Synchronization
If you are using a mirrored or clustered configuration, the two servers that comprise a mirrored pair should not differ in time
by more than 30 seconds. Check the time on each server and correct any discrepancies that might exist.
To check the system time:
1.
2.
3.
Note
You should also perform this time check after adding any new hardware to either server and after
changes in Standard or Daylight Savings Time.
Based upon your tape consumption measurements, keep at least two weeks worth of tapes available for growth.
Keep at least two spare tapes in addition to the two week reserve in order to replace a bad tape, if necessary.
Open DCMC.
2.
Expand your Data Center tree and then the server name.
3.
4.
Verify that there are an adequate number of labeled blank tapes to handle normal tape usage.
Open DCMC.
2.
Expand your Data Center tree and then the server name.
3.
4.
Check Mount Count for any tapes with excessive mounts. You might have to retire these tapes before they start causing
errors.
5.
Check Date of birth, by scrolling to the right, for any relatively old tapes that might need to be retired.
Note
What is a high mount count and how old is old? These are difficult to define. If you notice a specific
tape causing warnings or errors in the Application event log, it is often an indication of a tape going
or gone bad. Pay particular attention to these tapes in the steps above. Also, check with your tape
media vendor for their qualification of high mount count and the life expectancy of a tape.
133
Before a tape is recycled automatically, a cool-off period of seven days is required. Use DCMC to view recyclable tapes. The
following actions are taken on the tape when recycled:
The starting point for write operations is moved back to the beginning of the tape.
Note
Let tapes cool off after they become recyclable, so that you could use them in case of a
disaster requiring database restoration. If the tapes have been relabeled, the data required to
rebuild the Data Center will be lost. A cooling-off period can last from one week up to a month
prior to recycling.
Review your cleaning schedule and the number of cleaning cycles left on your cleaning tapes.
Keep on hand enough cleaning tapes to last for one month of cleaning cycles.
If you only need one cleaning tape per month, keep a spare cleaning tape on hand just in case you should have a problem
with the first tape.
Open DCMC.
2.
Expand your Data Center tree and then the server name.
3.
4.
Perform a Find using Migration as the description. Read the event messages that you receive to determine the
success of the migrations.
5.
If you find unsuccessful migrations, visit the Resource Center for more information about how to respond to the error
events.
135
14
MONTHLY MAINTENANCE
About this chapter
This chapter provides an overview of the maintenance tasks required for optimal Data Center performance. Refer to Monthly
maintenance checklist, on page 170 for a checklist that you can use to perform routine maintenance tasks.
This chapter contains the following topics:
To learn about...
Refer to:
Verifying that you are using the most current firmware on the Verify firmware is current, on page 146
Data Center server
Check the software licensing for the Data Center
137
Database maintenance
Database maintenance
Performing daily and weekly maintenance
As it does with the daily and weekly maintenance scripts, the Data Center comes with a monthly maintenance script to
perform database maintenance. This monthly script runs the DBCC utility that comes with SQL Server (using the dbcc
checkdb query) for each of the Data Center databases. In turn, the DBCC utility checks the databases for the following:
Data and index pages are consistent against corresponding extent structures.
Indexes are in proper order, all pointers are consistent, data information on each page is reasonable, and page offsets are
reasonable.
When you run the monthly maintenance script, you must perform specific tasks based on your Data Center configuration.
For this reason, the Data Center Setup program does not add the monthly script to the Windows Scheduler (unlike the daily
and weekly scripts, which are set up to run automatically on a schedule). You therefore must run the script manually.
You can run the script using SQL Query Analyzer. The script's file name is dbmaint.sql, and it is located in the
Data Center folder.
Before you run the script, however, be sure to read the rest of this section for specific guidelines and instructions based
on your Data Center configuration. The rest of the section describes the procedure step-by-step so that you can follow along.
It also provides additional information based on your specific configuration.
Procedure
To perform database maintenance, you must do the all of the following tasks in order:
1.
Prepare the mirrored server (for mirrored and clustered Data Centers).
Database maintenance
2.
3.
4.
Open DCMC.
2.
3.
Verify that services are running for Server 2. For more information on verifying that services are running, refer to Verify
that services are running, on page 123.
In the DCMC, expand your Data Center in the Console tree and then expand the server name.
2.
3.
4.
5.
6.
7.
Right-click BackupHSM and click Stop Service, if you are using HSM.
8.
Right-click HSMPurge and click Stop Service, if you are using HSM.
9.
10. Verify that any end-user retrieve requests for Server 1 are complete by right-clicking BackupServer, selecting All
Tasks, and clicking Log Session Statuses. Expand the Events node and click Application. Verify that there are no enduser retrieve requests in progress.
11. When all end-user retrieve requests are complete, right-click BackupServer and click Stop Service.
Verify that the Compactor service is not running. If it is still running, end the process or wait until the process finishes.
2.
3.
If you are running a standalone Data Center and use a tape system for your database backups, open the SQL script file
weeklymainttape.sql. Otherwise, open the SQL script file weeklymaintdisk.sql. Both files are located in the
Data Center folder, default location c:\Data Center.
4.
Click the execute button to run the SQL script. The system performs a backup of the SQL databases and a migration to
Secondary Tape Sets (for HSM systems with Secondary Tape Sets). For more information refer to Verify results of the
Weekly Automatic Procedure, on page 128.
5.
When the SQL script is finished, run the SQL script file dbmaint.sql, which is also located in the Data Center folder.
Depending on the size of your databases, the SQL script could take minutes or hours.
139
Database maintenance
2.
3.
When the SQL script is finished, use the following steps to restart the services for Server 1:
a.
Open DCMC.
b.
c.
Right-click BackupServer, select All Tasks. and click Log Session Statuses.
b.
Use the Disk Status tool to check the available free space on the database volume. If the free space on the volume
is 100MB or less, contact Support. Do not continue until you complete this step successfully.
b.
Account management
Account management
Accounts to remove
As time goes by the Data Center can become cluttered with abandoned accounts. This clutter can take up precious space in
the databases and in archive storage. These abandoned accounts also use up seats in the Data Center license.
To keep clutter on the Data Center to a minimum, look for the following types of accounts on a monthly basis:
Unowned accounts
Duplicate accounts
Inactive accounts
Heavy hitters
Invalid accounts
Unowned accounts
An unowned account is an account where ownership cannot be determined. This type of account is created when a name,
email, telephone or other identifying information is not entered during the Agent setup and registration process.
If you can obtain information for the account, enter it using Support Center. Or you can choose to cancel the account.
In time, Compactor removes it from the Data Center. Visit the Resource Center to obtain a SQL script that you can use to
find unowned accounts on the Data Center.
When you identify the accounts, you should upgrade the version by whichever upgrade method your organization employs.
Visit the Resource Center to obtain a SQL script that you can use to find accounts running unsupported Agent versions on
the Data Center.
141
Account management
Duplicate accounts
A duplicate account is an account that is unused because there are two accounts installed on the same Agent computer.
Duplicate accounts are commonly caused by an issue with the account recovery process. Sometimes a user is confused during
the account recovery process and creates a new account rather than recovering the current account. A new account might be
intentionally created because the user was unaware of the account recovery process or there might have been an error during
the process, forcing the user to start a new account. Duplicate accounts cannot be easily identified using an automated
procedure. However the key factors to examine are as follows:
1.
2.
Determine if the accounts identified in step 1 have the same computer name.
3.
Verify that the last backup activity for one account ends, and a new account is registered shortly thereafter.
4.
Verify that the new account determined in step 3 has current backup activity and the other account does not.
Visit the Resource Center to obtain a SQL script that you can use to find accounts with the same email address on the
Data Center.
Inactive accounts
An inactive account is an account that has had no activity recorded over an extended period of time. An account can become
inactive through:
Attrition
Duplicate account
For best results, choose an account inactivity threshold time frame. For example, if an account has not performed a backup
in the past 90 days, it is considered inactive. The policy created should be published for end users and Help Desk
representatives and should also accommodate end users on extended absence.
Two SQL scripts are available that you can use to identify inactive accounts. One SQL script identifies accounts with no
activity in the past 90 days and the other SQL script identifies accounts with no activity at all. Your organization can choose
to cancel these accounts or notify them that they have not backed up recently. Visit the Resource Center to obtain copies of
these SQL scripts.
Heavy hitters
The heavy hitters reports are Support Center reports that examine the amount of data that each account is backing up to the
Data Center. The reports have the following names:
Heavy Hitters
Both reports are located in the Reports node. Refer to Support Center Help for information about running and viewing the
reports.
If an account is backing up a large amount of data on a regular basis, this often indicates that the account is backing up
unnecessary data. Large backups put undue stress on the Data Center server, HSM (if used), and the SQL databases.
It is up to each individual organization to determine what constitutes heavy usage and how to manage heavy hitters. You
should take steps to reduce or eliminate the load they are putting on the Data Center. You can use the results from the heavy
hitters reports to decide if there are specific types of data you should exclude from backups or to contact accounts about
inordinately large backups.
Account management
Invalid accounts
An invalid account is an account that is unusable. This can occur from a failed registration. The failure could have been from
a network error or some other failure that prevented the system from completing its registration. Occurrences of this type
should be rare. Visit the Resource Center to obtain a SQL script that you can use to find invalid accounts on the Data Center.
143
CPU
RAM
CPU
For best performance, use a one gigahertz or higher Pentium class processor for your Data Center servers. Refer to
Chapter 4: Sizing Your Data Center, beginning on page 43 manual for more information about Data Center sizing
requirements. If the CPU is over utilized, you can add additional processors or upgrade the existing processors to improve
performance.
CPU utilization is generally easy to detect as a potential bottleneck to Data Center performance, but it is often harder to
address than other potential limitations without a complete hardware upgrade. Certain processes (particularly compaction),
however, can consume a large amount of CPU resources. During these peak periods, you should measure CPU utilization.
You can evaluate your server's CPU utilization using the System Monitor feature of your Windows Performance utility. You
should examine the following items for their averages during peak activity:
Average CPU utilization: Processor\ % Processor Time > 80% indicates heavy CPU utilization.
Generally, a healthy CPU has peaks and valleys of utilization, with many of the peaks reaching 100%. This means that
average processor activity during peak times is actually a better reflection of true performance than the peaks
themselves. The average CPU utilization should be under 85%.
System processor queue length: System\ Processor Queue Length > 2 per CPU indicates that CPUs are overwhelmed
and are queuing up requests.
Generally, there should be no more than the number of processors x 2 as an average queue.
If you find the CPU to be under performing, replace the existing CPU(s) with faster CPU(s) rather than more CPUs. This
recommendation is due to the Windows performance overhead incurred with multiprocessing.
RAM
Your server's RAM, along with disk space, is a likely culprit for being a system bottleneck. Unlike disk or CPU usage, you
measure RAM usage by a more indirect means because Microsoft SQL Server, the primary user of RAM in the Data Center,
consistently utilizes close to 100% of memory resources as it attempts to cache as much of the database in memory as
possible.
The primary tool for determining if RAM is a limiting factor in system performance is the System Monitor feature of the
Windows Performance utility. You should examine the following items for their averages during peak activity:
Number of times Windows is going to disk: Memory\Pages/sec > 0 indicates that Windows is going to disk frequently,
costing disk I/O and CPU resources.
Keeping this value close to zero reduces performance problems incurred by going to disk. You can resolve this issue by
adding more RAM to your system.
Number of times per second that Windows has read from the paging file: Memory\Page Reads/sec > 5 indicates that you
might need to add more RAM to resolve a bottleneck in your system.
145
Every server in a mirrored or clustered Data Center must have the same license. That is, every server must be licensed for
the same features and the same number of end-user accounts.
2.
Expand the Data Center in the Console tree and expand the primary Data Center server.
3.
4.
Look or search for the message with a source of License Manager. Event ID 9507 displays the number of seats and
features purchased.
5.
In Support Center, create a report that displays the number of active accounts.
6.
Refer to Requesting a new license, on page 149 to request a new license, if necessary.
2.
Change folder to the Data Center folder. By default, this is C:\Data Center.
147
3.
Type hostid.
The following is an example of the system output:
The HostID for the current machine is:
0050dad5a9e6
Note
You must enable NetBios over TCP/IP on the Data Center servers. The HostID.exe program
requires this configuration to properly verify the Data Center server's MAC address against the Data
Center license.
4.
Refer to Requesting a new license, on page 149 for information about requesting your new license.
2.
Change the folder to the Data Center folder. By default, this is C:\Data Center.
3.
Type hostid.
The following is an example of the system output:
The HostID for the current machine is:
0050dad5a9e6
0026fal7b9r5
0123kel8a6w2
0475der9n3y5
Note
You must enable NetBios over TCP/IP on the Data Center servers. The HostID.exe program
requires this configuration to properly verify the Data Center server's MAC address against the Data
Center license.
4.
5.
Refer to Requesting a new license, on page 149 for information about requesting your new license.
In a Web browser, access the following URL and submit the appropriate information:
http://www.ironmountain.com/US/support/licensedsoftware.asp
2.
After the information is processed, you will receive an email with a new license.dat file and instructions for
installation.
149
2.
Expand the Data Center Console tree and expand the server name.
3.
4.
Click the Action menu and click Start Event Viewer. The Windows Event Viewer opens.
5.
6.
7.
In the Save Application Log As window navigate to the \Log Files folder (by default this folder is located on
the same drive as the \Customers folder).
8.
Name the log file, ensuring that it has a unique name that clearly identifies the log file type and time period of events
contained in the log. For example, you could use the following name to indicate the saved file is the Application event
log for the month of April, 2005:
App9_1_02_to_9_30_02.evt
9.
Repeat the steps in this procedure for the DCMaint and System event logs.
2.
3.
4.
5.
Click OK.
6.
2.
Click Application.
3.
4.
In the Log Size section, under the General tab, modify the Maximum Log Size to 50 MB by either clicking the up
arrow or typing in 50000. You can set this number higher. The recommended value is 50 MB.
5.
Click OK.
151
Use DCMC to stop the HSM services. These include: BackupHSM and HSMPurge.
Make sure you have an adequate supply of cleaning tapes for the number of tape drives in your library.
Cleaning tapes can only be used a fixed number of times before they should be discarded. Note each time you use a
cleaning tape, and discard them immediately after their last use.
Record the date of the last cleaning for each drive in a log. A drive that requires more frequent cleaning indicates that it
might need to be serviced.
Record Keeping
Record Keeping
Verify that record keeping is current
Every month you should perform the following tasks to make sure that your Data Center record keeping is current:
Examine the daily and weekly scheduled maintenance records to ensure that maintenance is being performed and
recorded.
Compile the records of system usage (such as number of end-user accounts, backups, retrieves, and so forth) and publish
them as appropriate for your organization.
Examine the records of service availability. Compile and publish service availability statistics. You should also compile
and publish these statistics on a rolling twelve-month basis.
Examine the records of hardware maintenance, system software upgrades, and Data Center performed procedures to
verify that records are being kept properly.
Examine the training records of Data Center operators to ensure that your entire staff is properly trained.
153
PART V: APPENDICES
A
Data Center Specification Worksheet
About this appendix
Use this appendix to track information regarding your Data Center. Update the information after software, operating system,
SQL Server, and hardware upgrades.
This appendix contains the following information:
To learn about...
Refer to:
157
Software versions
Software versions
Data Center
Use the following table to track the version of the Connected Backup software running on your Data Center. Update the table
after installing hotfixes and service packs.
Server
Version
Installation date
Version/update number
Installation date
158
Version/update number
Installation date
Software versions
Agent
Use the following table to track the version and type of the Agent deployed to each community on the Data Center. Update
the table after installing hotfixes and Service Packs.
Type
(PC or SV)
Community
Version
Deployment date
159
IP address
Primary/
secondary
Registration master
Licensing
Use the following table to keep track of the number of licenses, host IDs, and licensed features on each Data Center server.
Server name
160
Host ID
Number of
licenses
Type
Features
(PC or PC with
Server Option)
B
Data Center Installation Worksheets
About this appendix
This appendix contains worksheets that you can use to record information that you need during installation of the Data Center
server software.
This appendix contains the following information:
To learn about...
Refer to:
161
Installation worksheets
Installation worksheets
Server names and IP addresses
Server names and IP addresses you have assigned for the Data Center server(s):
Server Name
IP Address
CAUTION
When choosing names for your Data Center server(s), avoid using the words BACKUP and
UPDATE (and other keywords used by Microsoft SQL Server) as part of the server name. Using these
words in the server name will cause problems when the Data Center software attempts to perform SQL
queries. You should also avoid using special characters such as a hyphen (-) in the server name.
162
Contents
Size (GB)
RAID Level
Installation worksheets
User ID
Password
Domain name
Name of the Windows domain to which you will add the Data Center server(s). You must know an account and password
that has administrator privileges in this domain; you will use this account to set up the server(s).
NT Domain:___________________________
Domain account
Domain account with local administrative rights to the Data Center server(s); it should be unprivileged except on the
server(s). Setup creates these accounts automatically during installation or you can create them yourself.
Data Center (CNTD_DCServices, by default):
NT Domain Account:_____________________ Password:___________________
Support Center and MyRoamTM (CNTD_WebServices, by default):
NT Domain Account:_____________________ Password:___________________
DataBundler (CNTD_DataBundler by default):
NT Domain Account:_____________________ Password:___________________
Email settings
Email host and address information for the DCAlerter service:
SMTP Mail Host:_____________________________________________________
Administrator Email Address:__________________________________________
Alert Sender Email Address:____________________________________________
163
Installation worksheets
NAS storage
Network Attached Storage (NAS)
Share for the NAS: ________________________________________
Expiration parameters
Expiration parameters, which you will be prompted for during installation. Accept the defaults if you are not sure.
:
Expiration Parameter
Default Value
Canceled
60 days
Deleted
Chosen Value
Recent Versions
Old Versions
164
C
Maintenance Checklists
About this appendix
This appendix contains checklists that you can use when performing Data Center maintenance tasks.
This appendix contains the following information:
To learn about..
Refer to:
165
166
Daily checklist
Morning/ Task
Afternoon
Page
120
M, A
123
M, A
Examine the event log through DCMC for any warnings or errors that might 123
need attention.
M, A
Verify that Support Center and Account Management Website are running. 124
M, A
124
125
122
M, A
For Data Centers using tape libraries, check the tape drive status and tape 125
requests in DCMC.
For Data Centers using Secondary Tape Sets, determine whether or not to 125
remove Secondary Tape Set tapes.
124
167
168
Weekly checklist
Task
Page
Verify the results of the weekly automatic procedure by reviewing the weeklymaint.out
file with a text editor.
128
130
130
130
131
For database backups performed to tape, remove and rotate current backup tape and
store in a safe place.
132
For mirrored or clustered Data Centers: Check time synchronization between mirrored
servers. Time on both servers should be within 30 seconds of each other.
132
132
For Data Centers using tape libraries, check blank tapes, tape use, recyclable tapes, and 133
cleaning tapes.
For Data Centers using tape libraries, check library tape slots.
134
For Data Centers using tape libraries, check the event log to verify successful purge and 134
migrations are occurring on a regular basis.
For Data Centers using tape libraries, check tape and tape drive health.
135
169
170
Monthly checklist
Task
Page
Run the database maintenance script, dbmaint.sql, using SQL Query Analyzer. 138
Run Account Management SQL scripts.
141
Evaluate current Data Center capacity by checking CPU, RAM, disk utilization 144
and tape library utilization.
Verify firmware is current with manufacturers specifications.
146
Check your software licensing by checking the License Manager event in the
Application event log and comparing it to the number of accounts reported in
Support Center.
147
Save and clear the event log using the Windows Event Viewer.
150
For Data Centers using tape libraries, clean the library and tape drives.
152
For database backups performed to tape, clean the backup tape drive.
152
153
171
INDEX
A
access, Data Center Management Console (DCMC) 99
accounts
choosing for tape groups 37
duplicate 142
heavy hitters 142
inactive 142
invalid 143
management 141
reducing unnecessary 141
unowned 141
unsupported Agent versions 141
with excessive backup amounts 142
adding new license
about 149
adding seats to Data Center 147
additional host ID 148
additional NIC 148
changing Agent features 148
Agent
access to Data Center, verifying 66
configurations, backing up 130
licensing, features 148
replication of configuration files, about 19
antivirus software
on the Data Center 54
application event log, automatic backup of 113
Application log
clearing 150
saving 150
archive
balancing tape utilization 33
secondary tape sets, about 30
archive sets
and Compactor 38
deleting, and compaction 38
repackaging, about 38
replication, about 19
archive storage device, Data Center worksheet 164
Attached Storage Network (SAN),using 55
B
back up
Agent configurations 130
databases 128
off-site tapes, about 31
PEM files 75
rotating tape 132
Support Center reports 130
Windows registry key 130
BackupHSM
services 21
backups, managing excessive 142
BackupServer 17
installation, troubleshooting 79
overview 17
verifying operation 77
C
capacity
checking disk space 131
evaluating Data Center 144
tape library 145
Centera
using 56
verifying operation 78
checking
available tape slots 134
Data Center license 147
disk space status 131
hardware firmware 146
recyclable tapes 134
tape drive health 135
tape health 135
tape usage 133
cleaning
SQL database backup tape drive 152
tape library 152
tapes, managing 134
clearing event logs 150
clustered Data Center
about 51
monthly tasks 138
community,tracking Agent version 159
Compactor
and tape groups 37
archive sets, deleting 38
archive sets, repackaging 38
choosing tape account groups 37
Connected Backup Data Center Deployment 173
Index
D
Data Center Management Console (DCMC)
accessing 99
interface 101
menus and toolbars 103
Data Center Toolkit
about 109
description 106
installing 109
invoking 109
requirements 109
Data Center worksheet
email settings 163
data migration and HSMPurge 21
database
backup to disk 128
backup to tape 128
cleaning backup tape drive 152
clearing transaction logs 128
compaction and deleting entries from 38
Master, Model, MSDB, backing up 128
monthly maintenance 138
replication of 19
rotating backup tapes 132
DataBundler
before installing 107
installing 107
requirements for use with version 6.x Agents 108
system requirements 107
usage requirements 108
DBCC utility 138
dbmaint.sql 138
DCAlerter
about 23
configuring 82
Data Center worksheet 163
DCMaint log
clearing 150
174
saving 150
default data expiration settings 40
deleting archive sets, and compaction 38
Directory database,backing up 128
disabling Removable Storage Manager (RSM) 58
disk
space, check available 131
space, checking during Compaction process 37
disk-only configuration
expiration rules, about
expiration, about 40
Distributed AML Server (DAS)
using 58
verifying operation 78
domain account, Data Center worksheet 163
domain controller, using Data Center as 52
domain name, Data Center worksheet 163
domain, Data Center assigning 64
drivers, installing tape library 64
duplicate accounts, managing 142
E
email alerts, configuring DCAlerter 82
email settings, Data Center worksheet 163
EMC Centera
using 56
verifying operation 78
emergency repair disk
creating on Windows 2000 66
creating on Windows 2003 66
enterprise directory
managing 85
errors, checking tape 135
evaluating
CPU utilization 144
Data Center capacity 144
RAM utilization 145
event log
automatic backup of 113
clearing 150
configuring email alerts 82
DCAlerter service 23
maintenance 113
saving 150
excessive backups, managing accounts 142
expiration
about 40
default settings 40
marking files for 38
of files, and Compactor 40
parameters, Data Center worksheet 164
Index
F
features, licensing for Agent 148
file expiration parameters, Data Center worksheet 164
files
marking as expired, about 38
replication, about 19
shared pool, and SendOnce feature 20
uncommon, and PoolServer 20
firmware, checking 146
formulas
average CPU utilization 144
RAM utilization 145
system processor queue length 144
G
groups
tape account, choosing for compaction 37
tape, about 28
guidelines
SCSI ID for multiple SCSI busses 57
SCSI ID for single SCSI bus 57
H
hardware
firmware, checking 146
requirements for MyRoam 68
requirements for Support Center 68
heavy hitter accounts, managing 142
Hierarchical Storage Manager. See HSM
host ID, new license 147
HSM
about 26
adding permanent expansion library, about 33
archive storage devices 26
balancing tape utilization 33
cleaning tape library 152
cleaning tape library drives 152
determining tape capacity 33
Distributed AML Server (DAS), using 58
EMC Centera, using 56
installation, troubleshooting 79
migrating to Secondary Tape Set 128
migration and purge 27
mirgration 27
mixed libraries 34
multiple SCSI busses, guidelines 57
multiple tape libraries 32
primary tape set, about 29
purge 27
Removable Storage Manager (RSM), disabling 58
requirements 56
secondary tape sets, about 30
I
IIS
configuring on Windows 2003 Server 63
installing on Windows 2003 Server 63
using with Support Center and MyRoam 62
inactive accounts, managing 142
IndexServer 18
installation
attached library, troubleshooting 80
BackupServer, troubleshooting 79
Data Center, troubleshooting 79
HSM, troubleshooting 79
Support Center and MyRoam 81
invalid accounts, managing 143
invoking, Data Center Toolkit 109
IP addresses, Data Center worksheet 162
L
libraries
checking available slots 134
different technologies, using 34
expanding 33
multiple, using 32
tape capacity 145
tape usage 133
temporary use of 32
transitioning to new 32
license
adding Agent features 148
adding users 147
additional host ID 148
additional NIC 148
checking Data Center 147
Data Center 51
175
Index
network, verifying 65
replication, verifying 78
synchronizing system time 132
Model database, backing up 128
monthly maintenance
tasks 138
MSDB database, backing up 128
MyRoam
moving the scratch folder 82
MyRoam server
hardware requirements 68
installing 81
preparation 70
requirements 68
software requirements 69
verifying installation 81
maintenance
daily tasks 119
event log 113
monthly tasks 138
weekly tasks 127
managing
accounts excessive backup amounts 142
accounts on the Data Center 141
accounts unsupported Agent versions 141
duplicate accounts 142
heavy hitter accounts 142
inactive accounts 142
invalid accounts 143
unowned accounts 141
Master database, backing up 128
Master Encryption Key (MEK), Data Center worksheet 164
measuring
CPU utilization 144
Data Center capacity 144
RAM utilization 145
Microsoft
IIS 63
software requirements 52
SQL Server 2000, installation guidelines 66
Windows Server, configuration guidelines 62
Windows Server, installation guidelines 61
Microsoft SQL Server, track version 158
Microsoft Windows, track version 158
migration
Secondary Tape Set 128
verifying status 134
mirrored Data Center
about 51
database backup 128
date and time, synchronizing 65
monthly tasks 138
network
assigning Data Center to domain 64
logins, Data Center 60
mirrored Data Center, verifying connection 65
ports 59
remote access to Data Center, verifying connection 66
requirements, Data Center 59
Network Attached Storage (NAS)
Data Center worksheet 164
using 55
new license, requesting 149
NIC
license for additional 148
license for new 147
176
O
obtaining new license 149
off-site tape sets 31
overview
BackupHSM 21
BackupServer 17
DCAlerter 23
event log 112
HSMClient 21
HSMPurge 21
IndexServer 18
PoolServer 20
ReplicationServer 19
P
partitions, Data Center server creating 63
PEM files, backing up 75
performance, evaluating Data Center 144
permanent license, Data Center 51
Index
Q
querying for
duplicate accounts 142
heavy hitter accounts 142
inactive accounts 142
invalid accounts 143
unowned accounts 141
unsupported Agent versions 141
R
RAM utilization, evaluating 145
record keeping,verifying 153
recyclable tapes, checking 134
Registry database,backing up 128
registry key, backing up 130
reinstallation, Data Center server 75
remote access to Data Center, verifying 66
Removable Storage Manager (RSM), disabling 58
removing Agent features, licensing 148
repair disk
creating on Windows 2000 66
creating on Windows 2003 66
replication
about 19
database 19
verifying 78
ReplicationServer 19
reports, backing up Support Center 130
requesting new license 149
requirements
Data Center software 52
HSM 56
MyRoam 68
network, Data Center 59
Support Center 68
Support Center and MyRoam server 68
tape library 56
results
weekly maintenance 128
results,weekly maintenance 128
retrieving files and HSMClient 21
S
saving event logs 150
scratch folder
moving on the Data Center server 82
SCSI
multiple busses guidelines 57
single bus guidelines 57
Secondary Tape Set
deciding to use 30
description 30
migrating to 128
taking off site 31
security
Data Center 60
SendOnce
Copy On Reference process, about 20
PoolServer service, about 20
server
assigning Data Center to domain 64
Data Center install, verifying 76
Data Center worksheet 162
Data Center, reinstalling 75
lmhosts file, configuring 64
SQL Server 2000, installing 66
Web server preparation 70
Windows Server, configuring 62
Windows Server, installing 61
service login accounts, Data Center 60
services, Data Center
BackupServer 17
Compactor 37
DCAlerter 23
HSMClient 21
HSMPurge 21
HSMServer 21
IndexServer 18
PoolServer 20
ReplicationServer 19
settings,file expiration defaults 40
software requirements
for Data Center 52
for MyRoam 69
for Support Center 69
software version
Microsoft SQL Server worksheet 158
Microsoft Windows worksheet 158
SQL database
backup volume, checking for disk space 131
backups, rotating tapes 132
cleaning backup tape drive 152
volume, checking for disk space 131
Connected Backup Data Center Deployment
177
Index
U
T
tape
account groups, choosing for compaction 37
checking available slots 134
checking health 135
checking recyclable 134
checking usage 133
compaction of, about 37
errors 135
groups and account groups, about 28
libraries, using different technologies 34
library capacity 145
managing cleaning 134
multiple libraries 32
primary set and HSM 29
primary set, and HSM 29
reusing 134
secondary set and HSM 30
sets, taking off-site 31
transitioning to new library 32
utilization, balancing 33
tape drives
checking health 135
cleaning 152
tape library
cleaning 152
178
V
validate Support Center technicians 84
verifying
available tape slots 134
BackupServer 77
Data Center install 76
disk space 131
HSM installation 78
mirrored Data Center replication 78
record keeping 153
Support Center and MyRoam installation 81
tape health 135
weekly maintenance results 128
viewing
replication status 19
viruses in archived files, about 54, 118
volumes
Data Center server creating 63
Index
W
Web server
preparation 70
requirements 68
Support Center and MyRoam, installing 81
verifying installation 81
Windows registry key, backing up 130
Windows Server
authentication, Data Center 60
configuring 62
installing 61
worksheet
license information 160
Microsoft SQL Server version 158
server name and IP address 158
179