ACRONIS Backup & Recovery 10 Advanced Server User's Guide Page 21

  • Download
  • Add to my manuals
  • Print
  • Page
    / 404
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 20
Copyright © Acronis, Inc., 2000-2009 21
1.3.4.2. Storage Node
Acronis Backup & Recovery 10 Storage Node is a server aimed to optimize usage of various resources
(such as the corporate storage capacity, the network bandwidth, or the managed machines' CPU
load) required for the enterprise data protection. This goal is achieved through organizing and
managing the locations that serve as dedicated storages of the enterprise backup archives (managed
vaults).
The storage nodes enable creating highly scalable and flexible, in terms of the hardware support,
storage infrastructure. Up to 20 storage nodes can be set up, each being able to manage up to 20
vaults. The administrator controls the storage nodes centrally from the Acronis Backup & Recovery 10
Management Server (p. 391). Direct console connection to a storage node is not possible.
Setting up the storage infrastructure
Install the storage nodes, add them to the management server (the procedure is similar to the
managed machine registration (p. 392)) and create centralized vaults (p. 385). When creating a
centralized vault, specify the path to the vault, the storage node that will manage the vault, and the
management operations to be performed on the vault.
A managed vault can be organized:
on the hard drives local to the storage node
on a network share
on a Storage Area Network (SAN)
on a Network Attached Storage (NAS)
on a tape library locally attached to the storage node.
The management operations are as follows.
Storage node-side cleanup and validation
Archives, stored in unmanaged vaults, are maintained by the agents (p. 382) that create the archives.
This means that each agent not only backs up data to the archive, but also executes service tasks that
apply to the archive, the retention rules and validation rules specified by the backup plan (p. 383). To
relieve the managed machines of unnecessary CPU load, execution of the service tasks can be
delegated to the storage node. Since the tasks' schedule exists on the machine the agent resides on,
and therefore uses that machine’s time and events, the agent has to initiate the storage node-side
cleanup (p. 393) and the storage node-side validation (p. 393) according to the schedule. To do so,
the agent must be online. Further processing is performed by the storage node.
This functionality cannot be disabled in a managed vault. The next two operations are optional.
Deduplication
A managed vault can be configured as a deduplicating vault. This means that identical data will be
backed up to this vault only once to minimize the network usage during backup and storage space
taken by the archives. For more information, please see the "Deduplication (p. 73)" section in the
User Guide.
Page view 20
1 2 ... 16 17 18 19 20 21 22 23 24 25 26 ... 403 404

Comments to this Manuals

No comments