HP StoreOnce D2D4324 HP D2D25xx, 41xx and 43xx Backup System user guide (EH985 - Page 132

Recovering Devices that have ‘failed to start’ or have become read-only, Replication fails

Get HP StoreOnce D2D4324 PDF manuals and user guides View all HP StoreOnce D2D4324 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 132 highlights

Replication fails If replication needs to take place through a firewall, the network administrator will need to open (TCP) ports 9387 (Command protocol) and 9388 (Data protocol) to allow the replication traffic to pass to and from the HP StoreOnce Backup Systems. If necessary and the D2Ds conflict with another device on the network, these ports can be changed from the defaults when you create the replication pairing or from the Local Appliance's General Settings page. If the replication Source Appliance fails and goes offline whilst it was performing a NAS replication job, the replication target share appliance may be left in an inconsistent state. This state may result in failure to recover from some files in the share or perform a list of files in the share because relationships between files and folders have been lost. This will automatically be repaired by the target appliance as soon as it detects the loss of the source appliance, however it may take up to 10 minutes to complete this repair during which time the share will not be available for access. If some files are failing to replicate and remain out of sync for long periods of time, check that the backup application is not holding open those files. This can be done by checking that there are no queued or paused jobs in the backup application, or restarting backup application services. If neither action resolves the problem, reboot the backup application server. Recovering Devices that have 'failed to start' or have become read-only If the D2D detects a potential issue with data integrity for a Virtual Tape Library or Share it will immediately set the status of that device to 'failed-to-start' or 'read-only', this is to minimize the possibility of any further potential corruption being introduced on the device. If a device enters one of these states it is reported on the GUI and selecting that device will give you some options to attempt to restore the device to a working state. Three options are available: • Quick Repair: This forces the device to ignore the error condition and the device is restarted. However, if following a quick repair the D2D continues to detect a possible integrity error then the status may once again return to 'failed to start' or 'read-only'. If this is the case, it is recommended that you try the Repair or Recover option. Running the quick repair option on a failed device more than once is not recommended as this can lead to further corruption. • Repair: This reboots the D2D Backup System and during the boot-up process the disks are checked for errors. Once the D2D has finished rebooting, if the device can now be safely returned to an online state, it will be returned to that state automatically. If the device remains 132 Troubleshooting

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
Replication fails
If replication needs to take place through a firewall, the network administrator will need to open
(TCP) ports 9387 (Command protocol) and 9388 (Data protocol) to allow the replication traffic
to pass to and from the HP StoreOnce Backup Systems. If necessary and the D2Ds conflict with
another device on the network, these ports can be changed from the defaults when you create the
replication pairing or from the Local Appliance's General Settings page.
If the replication Source Appliance fails and goes offline whilst it was performing a NAS replication
job, the replication target share appliance may be left in an inconsistent state. This state may result
in failure to recover from some files in the share or perform a list of files in the share because
relationships between files and folders have been lost. This will automatically be repaired by the
target appliance as soon as it detects the loss of the source appliance, however it may take up to
10 minutes to complete this repair during which time the share will not be available for access.
If some files are failing to replicate and remain out of sync for long periods of time, check that the
backup application is not holding open those files. This can be done by checking that there are
no queued or paused jobs in the backup application, or restarting backup application services. If
neither action resolves the problem, reboot the backup application server.
Recovering Devices that have ‘failed to start’ or have become read-only
If the D2D detects a potential issue with data integrity for a Virtual Tape Library or Share it will
immediately set the status of that device to ‘failed-to-start’ or ‘read-only’, this is to minimize the
possibility of any further potential corruption being introduced on the device.
If a device enters one of these states it is reported on the GUI and selecting that device will give
you some options to attempt to restore the device to a working state.
Three options are available:
•
Quick Repair:
This forces the device to ignore the error condition and the device is restarted.
However, if following a quick repair the D2D continues to detect a possible integrity error
then the status may once again return to ‘failed to start’ or ‘read-only’. If this is the case, it is
recommended that you try the
Repair
or
Recover
option. Running the quick repair option on
a failed device more than once is not recommended as this can lead to further corruption.
•
Repair:
This reboots the D2D Backup System and during the boot-up process the disks are
checked for errors. Once the D2D has finished rebooting, if the device can now be safely
returned to an online state, it will be returned to that state automatically. If the device remains
132
Troubleshooting