- Allow
for deferred activation of production keys
|
- Error
exporting history files for stores that have no history
|
- Exchange
Plans for storage groups that are successful have Warnings
|
- No
warning message if the last storage group on a server is offline
|
- Checkup
report does not allow semicolon (;) separated email addresses only
comma (,) separated
|
- Store
copy task ends OK when store is write-protected.
|
- Store
copy tasks end with Parameter is incorrect if source or destination
store is offline
|
- Logging
too excessive with Invalid Store Exceptions when store is offline.
|
- Running
initial plans from multiple remote computers at the same time causes
warnings
|
- Unable
to restore large files over a network on Windows 2008 R2
|
- Unable
to edit folder selections when creating file protection path
|
- UI
errors when
user temp folder is deleted
|
- Deleting
a store that is offline does not delete the store share
|
- Plans
running for more than 24 hours are not showing up in the checkup
report
|
- Change
the scans and restores to use configuration files to allow for
unlimited file selection
|
- Change
checkup report title to Archive Manager from ArchiveIQ
|
- Allow
share creation for USB based stores in EPS
|
- Allow
user to select backup of all available SQL instances and databases
- Allow
user to select backup all available Exchange storage groups/databases
|
- Remote
AccessDir registry key is not getting removed during upgrades.
|
- Exchange
2010 DAG snapshot is not capturing all databases after failover
|
- Minimum
Recovery Points invalid value in the archive configuration is not
handled correctly
|
- ProcessCatalogs
with /createIndex2 parameter ends with error
|
- Restore
failing for files on the root of the second volume
|
- Unable
to explore catalogs with missing folder records
|
- UI
appears hung waiting for SQL and Exchange lists to populate
|
- Customer
reports that the EPS MMC crashes on refresh
|
- Error
in log file attempting to update index1.dat after a failure to flush
buffers
|
- Canceling
creation of a store task when prompted for run as information does not
return to finish page
|
- Removing
a store via the UI also removes that drive's admin share.
|
- Plan
history displays green flags though plan did not protect any files
|
- Prescript
parameter fails when relative path is used
|
- Viewing
Storage Usage and Store Task History can stall the MMC UI
|
- Expire
exception, 'cannot create a file when the file already exists'
|
- Deleting
an Archive may result in a 1223 error
|
- Exchange
protection is failing with not enough temp space
|
- Viewing
Store Copy Task settings may crash Archive Manager UI
|
- Plan
run shows success but plan log shows exception, no files protected
|
- Archive
job reports ‘Initializing...' during copy of staged files when using
remote caching
|
- Slow
Explore and Restore performance on Windows 7 and 2008 R2
|
- MMC
crashes with TargetInvocationException when closing Plan History
window.
|
- Verify
job shows green check icon with 2 errors and 2 warnings
|
- Deleting
one of two plans sharing the same configuration deletes the
configuration.
|
- Cannot
clear archive name from saved configuration
|
- Store
not completely removed when removing via UI
|
- USN
Journal not always enabled for Exchange data drives
|
- Setting
or changing ‘Advanced’ properties in saved configuration clears
Folders settings
|
- "Object
reference not set to an instance of an object" when creating
Protection Plan to offline store
|
- Removing
store but leaving data on the media ends with error: filename not
valid or too long.
|
- ESEUTIL
default throttling for Ex 2010 needs to be much less than the current
default
|
- Get
'object reference' error when using a dot in the task name when
creating store tasks/protection plans.
|
- $temp$ and $store$ not resolved if mixed- or
upper-case
|
- MMC
crashes with TargetInvocationException when running plan on
disconnected remote computer
|
- Unable
to select a store that uses NAS storage as a source to pull data for a
store copy
|
- Restoring
a link to file that has not yet been restored causes 3L warning
|