|
|
|
|
|
|
|
|
|
ANNUAL SAVINGS FROM DECREASED BACKUP TIME AND COSTS
|
Native tools
|
Quest Recovery
Manager for Active Directory
|
|
Number of domain
controllers
|
|
|
|
|
Number of AD backups
per month (i)
|
|
|
|
|
Time to monitor
backup process per DC (minutes) (ii)
|
|
|
|
|
Annual time to
monitor backup tasks (hours)
|
|
|
|
|
Time to set up a
backup task per DC (minutes) (iii)
|
|
|
|
|
Number of times
backup tasks are reconfigured (annually) (iv)
|
|
|
|
Annual time to
re-configure backup tasks (hours)
|
|
|
|
|
Annual backup
administration costs
|
|
|
|
|
|
|
Annual savings
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ANNUAL SAVINGS FROM DECREASED RESTORE COSTS
|
Native tools
|
Quest Recovery
Manager for Active Directory
|
|
Number of network outages connected with AD object errors, per
year (see a note *) (v)
|
|
|
|
|
Time to prepare for
AD restore process (minutes) (vi)
|
|
|
|
|
Time to restore a
single AD object from backup (minutes) (vii)
|
|
0.1
|
|
Time to restart a
domain controller (minutes) (viii)
|
|
|
N/A
|
|
Time to re-create an
AD object (minutes) (ix)
|
|
|
N/A
|
|
Errors severity (average number of AD objects affected per
network outage) (see the note *) (x)
|
|
|
|
|
Annual
administrative time to restore AD objects (hours)
|
|
|
|
Annual
administrative costs to restore AD objects
|
|
|
|
|
|
|
Annual savings
|
|
|
|
|
|
(*)
Please note that our estimate is used until you input yours. A valid estimate
should be more than zero; non-valid estimates will be ignored.
|
|
|
|
|
|
|
|
|
ANNUAL SAVINGS FROM
REDUCED DOWNTIME
|
|
|
Annual direct
downtime (hours)
|
|
|
|
|
Average number of
employees affected during downtime
|
|
|
|
Network downtime
impact on employees' productivity
|
|
|
|
|
Annual employee productivity loss due to downtime connected with
AD object error
|
|
|
|
|
|
Potential business
losses due to lost transactions per hour of downtime (xi)
|
|
|
|
|
|
Annual potential
business losses
|
|
|
|
|
|
|
Total downtime costs
(xii)
|
|
|
|
|
|
|
Annual downtime cost
savings
|
|
|
|
|
|
|
|
|
|
|
COSTS WITH QUEST
RECOVERY MANAGER FOR ACTIVE DIRECTORY
|
|
Your local license
fee for Quest Recovery Manager for Active Directory per enabled AD user
account
|
|
|
|
Total license fee
|
|
|
|
|
|
Maintenance fee as
percent of license fee
|
|
|
|
Annual maintenance
fee
|
|
|
|
|
|
Number of AD
administrators who will use Quest Recovery Manager for Active Directory
|
|
|
|
Number of training
hours per AD administrator
|
|
|
|
Training cost
|
|
|
|
|
|
|
COMMENTS
|
|
|
(i)
Typical company's IT policy requires organization to make an Active Directory
backup every day.
|
|
(ii)
Total time required to ensure that a backup task is successfully executed.
The only way to check the success of backup tasks (when using only native
tools) is to look through the list of backup files and check the date and
size of each file (at least). Recovery Manager for Active Directory generates
logs which show the status of backup tasks. All that administrator have to do
is simply to scroll through the corresponding log (the viewer is built-in
into Recovery Manager interface) and look for errors in the same way as he
does with Windows event logs.
|
|
(iii) When using native tools, you have to schedule a backup
task on each domain controller individually (either by visiting a DC or
through a terminal session). The time needed to configure backup jobs using
Recovery Manager for Active Directory cannot be done on a strictly per DC
basis because the product enables you to put multiple DCs into a collection,
set the configurations once, and have them applied to all DCs in the
collection. Typically, it takes 30 to 60 minutes at most to configure all
backup jobs using Recovery Manager for Active Directory (of course, if you
have already designed the backup sytem architecture.)
|
|
(iv) As your network infrastructure changes, you may want to
revise and reconfigure backup tasks. We assume that the changes are made once
a year. You can modify this value according to your policies and expertize.
|
|
(v) You have to enter your value according to your experience
and expertize. Based on our experience, we assume that a middle company (with
up to 3000 users) may have about 2-3 network outages connected with AD object
errors per year. Larger companies may have 1 such outage per 2000-user
network segment.
|
|
(vi) Before you restore the Directory database, you should
perform some critical operations: restore the Sytem State for NTDSUTIL
(refers to native tools) or unpack the Recovery Manager for Active Directory
backup data correspondingly.)
|
|
(vii) Native tools require to restore each object individualy by
typing its full path in the command line (NTDSUTIL command). It takes 3 - 6
minutes from a professional system administrator and requires a deep
knowledge of AD structure. With Recovery Manager for Active Directory all you
have to do is to select the directory objects to be restored and then
Recovery Manager for Active Directory will automatically fix them. It takes
2-6 seconds for an individual object.
|
|
(viii) When using native tool, you will need to do 2 restarts
(DC is rebooted once into “recovery mode” and then again into regular mode
once the recovery is complete). Each restart may take about 10-15 minutes.
With larger AD database, DC restart time can take longer. Recovery Manager
for Active Directory does not require to restart a domain controller.
|
|
(ix) This is an average time required to manually re-create a
deleted or corrupted AD object and re-assign all related permissions.
Recovery Manager for Active Directory allows to granulary restore individual
AD objects and does not require the DC to be restarted; so there is no point
in such operations.
|
(x) You have to enter your value according to your experience
and expertize. Our assumption is given for your information only. If a domain
controller state is regularly monitored, probability of an AD database
failure due to hardware problems is near-zero and can be ignored in
calculations. However, due to the high complexity of administrative tasks,
there is a possibility of erroneous actions with AD objects (e.g. user or an
entire organization unit (OU) may be deleted or incorrect properties may be set.)
This value shows the expected average number of objects affected per
downtime incident due to AD administrators' error. It primarily depends on
the complexity of your AD structure. It is assumed that in larger networks an
average OU affected by downtime would contain more user accounts (in sub-OUs)
than in smaller networks.
|
|
(xi)
In accordance with some researches, it is assumed that average network
downtime business loss (from lost transactions) in a large company is about
$84000 per hour per incident with 3000 users (or $28 per user). For
simplicity of calculations, it is also assumed that there is direct
dependence between average number of affected users per downtime incident and
downtime business losses.
|
(xii) According to some surveys, the annual average network outages among
Fortune 1000 companies start from $3-$3.5m (excluding the cost of lost
employee productivity) and up to $32.7m (or 2% of annual revenue) in lost
revenue and productivity.
Downtime losses from poorly managed networks (99% availability) may result
in $247m per year.
|
|
|