Dell DR4300 DR Series System Administrator Guide - Page 180

Scheduling DR Series System Operations, Creating a Cleaner Schedule, Filesystem Check - Unsuccessful

Page 180 highlights

NOTE: When in Maintenance mode, image expiration fails because the DR Series system is in a read-only state. If this occurs, the DMA assumes that the backup images have expired. However, the DR Series system administrator may be unaware that the backup data images still reside on the DR Series system. Filesystem Check - Unsuccessful: when the Maintenance mode halts at the Completed Generating Report stage, this indicates that the filesystem check detected some repairable files, and listed them in the Repair Report pane on the Maintenance Mode page. To return to the Operational mode, click Confirm Repair Filesystem on the Maintenance Mode page options bar to repair the files listed in the Repair Report. Confirm Repair Filesystem is the only active option you can select when the progress bar indicates that some filesystem files are in need of repair. Scheduling DR Series System Operations The most important thing to remember when scheduling critical DR Series system operations is that you want to ensure that you perform each of these operations at a time when it will not overlap or interfere with the running of any of the other key system operations. By better scheduling when you run system operations, you can optimize your system resources and make it possible to achieve the best possible DR Series system performance. To do this, plan and schedule time periods in which to perform the following critical system operations: • Data ingests (which are dependent upon the DMAs) • Replication process • Cleaner process (space reclamation) The main goal in planning and scheduling operations is running the Cleaner and Replication operations at times when they do not overlap or interfere with other important system operations. You want to make sure that by properly scheduling and planning, your system can perform each of these key operations independent of the other. The best practice is to run these two operations during non-standard business hours, so that they do not conflict with any of your other backup or ingest operations. In short, efficient scheduling maximizes the best use of your system resources. Dell recommends scheduling resource-intensive operations during specific time periods when no other system operations are being performed. This approach is called windowing, which requires scheduling a specific block of time (or "window"), each with a set starting and stopping point so that you can perform data ingests, replication, or space reclamation operations without interfering with the running of any other operation. Creating a Cleaner Schedule Performing scheduled disk space reclamation operations are recommended as a method for recovering disk space from system containers in which files were deleted as a result of deduplication. The best method is to schedule a time when you can run the Cleaner on your DR Series system with no other planned processes running. Alternately, another method lets the Cleaner process on the DR Series system run whenever it determines that there are no active data ingests. NOTE: Even if no Cleaner schedule is set, but the system detects that there is disk space that can be reclaimed, the Cleaner process runs. However, the Cleaner will not start until the following conditions are met: it detects that there are no active data ingests, that two minutes of system idle time have elapsed since the last data file ingest was completed, and that the Replication process is not running (the Cleaner process runs as a lower system priority operation than the Replication process). NOTE: Running the Cleaner while ingesting data, reduces system performance. Ensure that you schedule the Cleaner to run when backup or replication is not in progress. 180

  • 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
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186

NOTE:
When in
Maintenance
mode, image expiration fails because the DR Series system is in a read-only state. If
this occurs, the DMA assumes that the backup images have expired. However, the DR Series system
administrator may be unaware that the backup data images still reside on the DR Series system.
Filesystem Check — Unsuccessful
: when the
Maintenance
mode halts at the Completed Generating Report stage, this
indicates that the filesystem check detected some repairable files, and listed them in the Repair Report pane on the
Maintenance Mode
page.
To return to the
Operational
mode, click
Confirm Repair Filesystem
on the
Maintenance Mode
page options bar to repair
the files listed in the Repair Report.
Confirm Repair Filesystem
is the only active option you can select when the progress
bar indicates that some filesystem files are in need of repair.
Scheduling DR Series System Operations
The most important thing to remember when scheduling critical DR Series system operations is that you want to ensure
that you perform each of these operations at a time when it will not overlap or interfere with the running of any of the
other key system operations.
By better scheduling when you run system operations, you can optimize your system resources and make it possible to
achieve the best possible DR Series system performance. To do this, plan and schedule time periods in which to perform
the following critical system operations:
Data ingests (which are dependent upon the DMAs)
Replication process
Cleaner process (space reclamation)
The main goal in planning and scheduling operations is running the Cleaner and Replication operations at times when
they do not overlap or interfere with other important system operations. You want to make sure that by properly
scheduling and planning, your system can perform each of these key operations independent of the other.
The best practice is to run these two operations during non-standard business hours, so that they do not conflict with
any of your other backup or ingest operations. In short, efficient scheduling maximizes the best use of your system
resources.
Dell recommends scheduling resource-intensive operations during specific time periods when no other system
operations are being performed. This approach is called
windowing
, which requires scheduling a specific block of time
(or “window”), each with a set starting and stopping point so that you can perform data ingests, replication, or space
reclamation operations without interfering with the running of any other operation.
Creating a Cleaner Schedule
Performing scheduled disk space reclamation operations are recommended as a method for recovering disk space from
system containers in which files were deleted as a result of deduplication. The best method is to schedule a time when
you can run the Cleaner on your DR Series system with no other planned processes running. Alternately, another
method lets the Cleaner process on the DR Series system run whenever it determines that there are no active data
ingests.
NOTE:
Even if no Cleaner schedule is set, but the system detects that there is disk space that can be reclaimed,
the Cleaner process runs. However, the Cleaner will not start until the following conditions are met: it detects that
there are no active data ingests, that two minutes of system idle time have elapsed since the last data file ingest
was completed, and that the Replication process is not running (the Cleaner process runs as a lower system
priority operation than the Replication process).
NOTE:
Running the Cleaner while ingesting data, reduces system performance. Ensure that you schedule the
Cleaner to run when backup or replication is not in progress.
180