HP 12000 HP VLS Solutions Guide Design Guidelines for Virtual Library Systems - Page 135

HP Data Protector, HP Data Protector Application Overview

Page 135 highlights

Figure 60 Preparing the Network Connection for Replication in a VLS You must maintain time synchronization between the source and target VLS devices; if they become more than one minute out of sync, the replication will go offline with a warning message. The recommended method of achieving this is configure both source and target VLS devices to use a single NTP server. You can configure the NTP settings in the VLS GUI on the Network Settings screen. NOTE: If you have any network firewalls between your source and target devices then you must ensure the firewall is configured to allow traffic on the required ports needed for replication to work: • The source VLS must be able to contact the target VLS on HTTP port (80), SSH port (22), and ICMP. • The replication data transfers will use the 'Un-Encrypted Data Transfer Port' setting with a default value of 5570 (which you can modify on the target). After preparing your source and destination VLS devices, following the steps outlined in "Replication Setup" (page 101) to configure replication. HP Data Protector This section includes both general and deduplication guidelines as well as other useful information for HP Data Protector. HP Data Protector Application Overview The Data Protector cell is a network environment that includes a Cell Manager and client systems that run agents. Client systems are imported into a cell and belong to a single Cell Manager. Multiple cells may exist, each with their own Cell Manager. This environment may be managed by a single Manager of Managers or "MoM." • Cell Manager: the main system in the cell. The Cell Manager is the "traffic cop" that controls the activities and contains the Internal Database (IDB) within the Data Protector cell. It is not HP Data Protector 135

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160

Figure 60 Preparing the Network Connection for Replication in a VLS
You must maintain time synchronization between the source and target VLS devices; if they become
more than one minute out of sync, the replication will go offline with a warning message. The
recommended method of achieving this is configure both source and target VLS devices to use a
single NTP server. You can configure the NTP settings in the VLS GUI on the Network Settings
screen.
NOTE:
If you have any network firewalls between your source and target devices then you must
ensure the firewall is configured to allow traffic on the required ports needed for replication to
work:
The source VLS must be able to contact the target VLS on HTTP port (80), SSH port (22), and
ICMP.
The replication data transfers will use the ‘Un-Encrypted Data Transfer Port’ setting with a
default value of 5570 (which you can modify on the target).
After preparing your source and destination VLS devices, following the steps outlined in
“Replication
Setup” (page 101)
to configure replication.
HP Data Protector
This section includes both general and deduplication guidelines as well as other useful information
for HP Data Protector.
HP Data Protector Application Overview
The Data Protector cell is a network environment that includes a Cell Manager and client systems
that run agents. Client systems are imported into a cell and belong to a single Cell Manager.
Multiple cells may exist, each with their own Cell Manager. This environment may be managed
by a single Manager of Managers or “MoM.”
Cell Manager: the main system in the cell. The Cell Manager is the “traffic cop” that controls
the activities and contains the Internal Database (IDB) within the Data Protector cell. It is not
HP Data Protector
135