The following fixes/enhancements are included in this update.
EvMgrS service may crash when a user who does not have
required capabilities tries to modify Email and IIS settings
(Update 0008)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
File System iDataAgent Windows XP
EvAlerts.dll
File System iDataAgent Windows 2000
EvAlerts.dll
File System iDataAgent Windows 2003
EvAlerts.dll
MediaAgent
EvAlerts.dll
QSnap
EvAlerts.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the Galaxy CommServe
as administrator and ensure that no jobs are in progress. It is also recommended
that all tape drives be empty. If a job is in progress while you attempt to install
this update the installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Movedir.exe is missing from the Base folder on CDR client
installs.
(Update 0104)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
File System iDataAgent Windows XP
MoveDir.exe
Continuous Data Replicator iDataAgent
MoveDir.exe
File System iDataAgent Windows 2000
MoveDir.exe
File System iDataAgent Windows 2003
MoveDir.exe
MediaAgent
MoveDir.exe
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
For Oracle IDA, it is possible to restore Oracle instance
using SCN number stored in details
of backup history. SCN number was not being stored in correct format in
details of backup history.
(Update 0004)
For Oracle CDR and QRA, application discovery will no
longer fail if Archive Log destination is set to
USE_DB_RECOVERY_FILE_DEST.
(Update 0035)
Optimize user credentials lookup to not require a query
to the CommServe.
(Update 0045)
This update provides a performance enhancement for Windows File System when
using Data Classification as a scan method.
(Update 0045)
System state backups of RIS crash.
(Update 0046)
DataPipe setup fails with multistream backups.
(Update 0046)
Online content indexing backup jobs can crash.
(Update 0046)
Fast server encounters failure when encrypted files are attempted to be
content indexed.
(Update 0046)
Support added for backup and restore of FSRM.
(Update 0047)
System state backups of RSM fail.
(Update 0047)
Browse/restore impersonate user fails to restore stub files.
(Update 0047)
File level restores of UNICODE data from Image level backups fail.
(Update 0047)
System state backups with VSS of IIS components incorrectly report failure
when IIS is not installed.
(Update 0047)
System state SFP component restores fail on Vista. not installed.
(Update 0047)
Stub Overwrite option not working for Restore By Job.
(Update 0047)
ACL only restore fails.
(Update 0047)
Update fixed an issue with manual mount and dismount of VSS Recovery Points
of a mount point. When replication set
contains pairs that have a Windows mount point as the destination, manually
mounting or un-mounting Recovery Points
that use VSS as the snap engine will not fail.
(Update 0048)
Fixed issue when VSS snapshots were not deleted when CDR replication sets
with mounted snapshots were deleted. When
a replication set is manually deleted and still contains mounted RP's creates
with VSS snapshots, it will be automatically
attempted to remove the snaps during the auto-cleanup. The VSS snapshots
were successfully dismounted, but were failing to
be deleted leaving the snaps lingering on the machine after the rep set
is gone. This update fixes the auto cleanup so it
properly deletes the VSS snapshots.
(Update 0048)
Exchange resources are quiesced multiple times when running QR snapshot
creation jobs involving Exchange 2003 and using QSnap engine.
(Update 0049)
SQL 2005 databases that were protected with VSS and QR are not put into
loading state when recovered.
(Update 0049)
During the optional backup to tape phase of CDR RP creation, a potential
for an incomplete scan of all the
modified data since the last backup exists.
(Update 0132)
No connection string is allowed in the rman script for
qoperation backup command.
(Update 0163)
Qcommands does not have an option to let the rman runtime
logs to be written where the user wants it.
(Update 0163)
Ability to generate job summary report using QCommands.
(Update 0163)
Fix for CDR CRP's of SQL Server that fails with "Path
too long" error.
(Update 0163)
Enhancement Fix for CDR to add support for creation of
VSS CRP's on Windows
Vista and Server 2008.
(Update 0163)
Fix for a linkage\dependency error in the file Wincomp.dll
specifically on Windows
2000 which caused file system and system state backups to fail (manifested
by a dll missing entrypoint
error on the client and a loss of control process message on the server).
(Update 0163)
Fix for malformed SQL 2005 default instance name when
manipulating SQL resources for QR and CDR operations.
(Update 0163)
System aborted pairs sometimes incorrectly restart in
less than 3 minutes.
(Update 0163)
CDR RPs and CRPs are marked with incorrect creation times.
(Update 0163)
The CDR service can crash if a pair is aborted while it
is in a failed state.
(Update 0163)
Attributes of folders do not get transferred to the destination
during init sync.
(Update 0163)
Orphan file processing removes old orphan processing data,
which makes orphan processing history unavailable.
(Update 0163)
When stub files are recalled using File Archiver for Windows
while a pair is aborted,
the recalled files are not properly replicated to the destination when the
pair is restarted.
(Update 0163)
Encrypted files become hidden on the destination after
initial sync.
(Update 0163)
CDR service can crash when pairs are aborted immediately
after a cluster failover.
(Update 0163)
If a pair is paused and throttling is triggered on the
source, the pair is not properly
system aborted.
(Update 0163)
If the source computer name is exact 15 characters in
length, replayer fails to replay logs
and causes pair to put in Aborted State.
(Update 0163)
Logs for paused pairs are not transferred if a replication
set has aborted pairs which are started.
(Update 0163)
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
Updated Galaxy Service Control Manager with localized strings
(Update 0166)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
File System iDataAgent Windows XP
GalaxySCM.exe
File System iDataAgent Windows 2000
GalaxySCM.exe
File System iDataAgent Windows 2003
GalaxySCM.exe
MediaAgent
GalaxySCM.exe
QSnap
GalaxySCM.exe
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
When an object has comma in its name then after the backup the user is not
able to browse the object for restore.
(Update 0175)
Trying to perform a full Active Directory backup crashes when large numbers
of objects are present in the Active Directory
with lengthier Distinguished Names.
(Update 0175)
Shared Services Provider Restore job from tape media will no longer wait
with reason
“The media is already Reserved…”. Windows Update 70 is required for full
functionality of this fix.
(Update 0179)
Enhance Galaxy to fully support CDR to a UNC path on a
Network Appliance file server. Support added in this update includes creating
a recovery point which is a ONTAP snapshot of the replicated data, copy
back of the replicated data from the recovery point to the source location,
and backup to tape of the data replicated to the UNC path.
(Update 0181)
Enhance Galaxy to fully support CDR to a UNC path on a Network Appliance
file server. Support added in this update includes creating a recovery point
which is a ONTAP snapshot of the replicated data, copy back of the replicated
data from the recovery point to the source location, and backup to tape
of the data replicated to the UNC path.
Enhance Galaxy to fully support CDR to a UNC path on a Network Appliance
file server. Support added in this update includes creating a recovery point
which is a ONTAP snapshot of the replicated data, copy back of the replicated
data from the recovery point to the source location, and backup to tape
of the data replicated to the UNC path.
Scan, Backup and restore jobs involving UNC paths as content may fail with
access denied message
(Update 0197)
Fixes Active Directory incremental backup failures.
(Update 0200)
Active Directory backups going into pending state with indexing errors when
the backup user credentials is not part
of the domain admin's or lacks permissions on the directory information
tree.
(Update 0200)
Support for DPM 2007 added to Simpana 7.0 DPM iDataAgent.
(Update 0207)
Fix for issue in 7.0 DPM iDA restore browse where local drive letters are
shown and not DPM backup content.
(Update 0207)
When performing Exchange 2007 VSS backups, storage groups protected with
Exchange LCR may cause the backup to fail.
(Update 0207)
Added support for Exchange 2007 DB out of place non-exchange location restores
in both DB recovery and non-recovery mode. Recovery mode will restore files
to user specified non-exchange location and employ VSS to replay logs when
the restore has completed bringing the databases fully up to date and in
clean shutdown mode. Non-recovery mode will simply restore databases and
logs to user specified location with no VSS or exchange involvement.
(Update 0207)
If the page size is set to a smaller value than the number of objects added
before the incremental, not all the objects are seen during browse for restore.
(Update 0244)
Single Sign On may hang when logging into CommServe with error "errorcode[10][Referral]"
in the EvMgrS.log
(Update 0264)
When trying to add an external group it may take a long
time to fetch all the groups and may not return all the groups
(Update 0264)
Reports and alerts are not being delivered after an upgrade
from 5.9 to 7.0 because of a
line terminator in the SMTP header.
(Update 0264)
When performing Exchange 2007 VSS backups, storage groups protected with
Exchange LCR may cause the backup to fail.
(Update 0264)
Support for DPM 2007 added to Simpana 7.0 DPM iDataAgent.
(Update 0264)
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
Fixed issue when Out-of-band sync tool does not properly
allow new pairs to be started with smart sync and used full sync.
(Update 0268)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
Continuous Data Replicator iDataAgent
CDRXHelp.exe
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
Added new localization strings for QUninstaller.exe
(Update0171)
Italian and French languages is not selected properly during install and
uninstall.
(Update 0310)
Dependency on Other Updates
Requires
None
Obsoletes
0171
Related
None
List of Files
This update updates the following files.
Platform
File
File System iDataAgent Windows XP
CommonUI.dll InstallString.dll
File System iDataAgent Windows 2000
CommonUI.dll InstallString.dll
File System iDataAgent Windows 2003
CommonUI.dll InstallString.dll
MediaAgent
CommonUI.dll InstallString.dll
QSnap
CommonUI.dll InstallString.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
This update fixes an issue where SQL agent backup jobs were not honoring
the "Backup Rules" convert option when the option is off.
(Update 0073)
This update provides support for SQL 2005 VSS Differential backups.
(Update 0073)
SQL database restores were failing with no resources, the media is already
incorrectly reserved by other jobs.
(Update 0073)
In the application resource detection routines for Galaxy QR and CDR, detection
of SQL 2005 default instances may fail.
(Update 0190)
SQL system database restores fail if the default instance is on a cluster.
(Update 0288)
SQL backups complete with errors if databases configured in a subclient
are deleted from the SQL Server.
(Update 0288)
Adds support for SQL point-in-time restores without restoring full backups
from SQL iDataAgent.
(Update 0288, Update 0287)
(Update 0288)
Several critical operations would experience failures when the Snapview
snap engine was used in conjunction with QR RD remote activate/deactivate
configurations.
(Update 0328)
SQL database backups fail if the backups are converted from Log to Differential
and then from Differential to Full.
(Update 0339)
Additional fixes for SQL database backups failing when the backups are converted
from Log to Differential and then
from Differential to Full.
(Update 0383)
NOTE: Update 0384 must be removed before installing ServicePack
2, OR installing this update. With update 384
installed the installation of either SP2 or this update will fail due to
an update numbering change.
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
When using tape hardware encryption feature, auxiliary copy job fails if
tape block size being used is bigger than 64K.
(Update 0060)
Media Mount Manager service may crash on Solaris MediaAgent during restore
from VTL.
(Update 0060)
Jobs writing to WORM tape media may fail due to issue where new file marker
not written to WORM tape media after partial chunk.
(Update 0060)
Media not marked as bad when media error is encountered.
(Update 0060)
Job pending reason is not set correctly when one of the multiplexing jobs
fail.
(Update 0060)
Failure in creating mountpath for Magnetic Library. The error given is:
The parameter used for the current operation is not supported by the Operating
System
(Update 0119)
Adds support for Quantum DAT 160 drive.
(Update 0168, Update 0167)
(Update 0168)
Stuck tape recovery does not work when device disappears from OS and then
later reappears.
(Update 0168)
NAS iDA backup is failing in the archive index phase when the file server
is behind a firewall. An attempt is being made to connect to the file server
on a port which is not opened on the firewall - the CVD log shows the connection
failure.
This update requires a registry key (below). When this registry key is set,
Galaxy will choose a port according to the Galaxy firewall configuration
rather than the file server choosing the port - the file server will connect
to Galaxy rather than Galaxy connecting to the file server.
Please create the following registry key to set the debug level:
DWORD type registry key value 'nNASMFS_LISTEN' with a value of '1' at location:
HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\<Instance Name>\MediaAgent
(Update 0214)
Index backup to NAS-attached media fails when spanning tapes.
(Update 0254)
Exchange Database full backup to NAS-attached media fails.
(Update 0254)
Jobs fail on Dell RD1000 USB removable disk when there is no cartridge loaded
in the drive.
(Update 0262)
Added ability to scratch aged media in CentricStor VTLs before the media
is mounted for reuse.
(Update 0314)
Backup jobs may fail on shared tape drives with the error "SCSI Reservation
Conflict" when SCSI3 reservation is enabled and there is a serial number
mismatch for the drive from one of the Media Agents.
(Update 0314)
Enhancement to have software-based automatic data replication for a replica
shared magnetic library configuration.
(Update 0314)
Single instanced backups fail with the job pending reason "Could not launch
the SIDB engine on the target MediaAgent"
(Update 0391)
Single Instance Database takes up large amount of space on disk even with
small amount of data stored.
(Update 0391)
AIX and Linux 1-touch restore fails using single sign-on.
(Update 0391)
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
In the application resource detection routines for Galaxy QR and CDR, detection
of SQL 2005 default instances may fail.
(Update 0190)
Several critical operations would experience failures when the Snapview
snap engine was used in conjunction with QR RD remote activate/deactivate
configurations.
(Update 0328)
Fix for failure in VSS command line operation execuables when used in a
scripted command line scenario (ProxyHost, etc).
(Update 0402)
Fix for QR snapshots of Oracle application data with more than one drive
and using QSnap snap engine.
NOTE:
Arguments for new option are as follows (also available in Vsssnapshot.exe
usage).
-backuptype
Specifies a VSS snapshot backup type.
Values can be {"full", "incr", "diff", "log"}.
Default backup type without option is VSS COPY snapshot.
(Update 0402)
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
When the extent size is changed on one cluster node, the
node can crash and not boot properly.
(Update 0228)
If there are VSS Shadow Copies on the same volume as Qsnap snapshots and
the Qsnap snapshots are deleted, the VSS Shadow Copies are deleted as well.
(Update 0406)
Dependency on Other Updates
Requires
None
Obsoletes
0228
Related
None
List of Files
This update updates the following files.
Platform
File
File System iDataAgent Windows XP
CVVolume.dll
Continuous Data Replicator iDataAgent
CVVolume.dll
File System iDataAgent Windows 2000
CVVolume.dll
File System iDataAgent Windows 2003
CVVolume.dll
MediaAgent
CVVolume.dll
QSnap
QST2.exe
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
When executing CDR consistent recovery points on replication sets containing
Exchange data, the process may fail with an application error when using
the VSS provider for online quiescing.
(Update 0429)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
Continuous Data Replicator iDataAgent
FLRSnapTool.exe
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
Memory consumed by QSDK service process may keep growing when CLI commands
are run continuously.
(Update 0454)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
File System iDataAgent Windows XP
cvsessionXML.dll
File System iDataAgent Windows 2000
cvsessionXML.dll
File System iDataAgent Windows 2003
cvsessionXML.dll
MediaAgent
cvsessionXML.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
View orphan file list from GUI fails for CDR.
(Update 0023)
This update provides a performance enhancement for Windows File Archiver
using Data Classification.
(Update 0063)
Recalls fail when opening the alternate file stream before opening the main
file first.
(Update 0106)
This update provides a performance enhancement for Windows File Archiver
using Data Classification.
Recalls fail when opening the alternate file stream before opening the main
file first.
Selecting Find & Recover hangs Outlook if the Galaxy 6.1 version of the
Outlook add-in is installed and the DataArchiver for Exchange agent on the
Exchange server has been upgraded to 7.0.
(Update 0116)
Embedded messages fail to get recalled from the Outlook add-in.
(Update 0116)
Method for user to identify corrupt stub files, when stub files get corrupted
due to improper AV settings.
(Update 0146)
Driver does not hook mount points on a cluster, when the cluster has ALLOW-Failback-Immediately
settings.
(Update 0146)
DMNAS filtering logic does not work with paths, and combination of paths
and file types.
(Update 0146)
DMNAS exception to filters would now work.
(Update 0146)
Restub logic fails when stub file is moved.
(Update 0146)
Query Info recalls can not be turned off on W2K.
(Update 0146)
Popup message fails on a cluster when files are recalled remotely
(Update 0146)
Scan speed improvement for Windows File System data Archiver with data Classification.
(Update 0146)
FSDM - Restriction on number of stub recovery does not work as per the values
set (recall throttling feature)
(Update 0146)
Delete Stub/Overwrite stub option does not work when message is recalled
from Outlook.
(Update 0204)
Stub recalls from PST are invoking Public folder persistent recovery job
and hence recalls are failing when customers install Exchange Data Archiver
for Exchange 2000 and Exchange Data Archiver for Public Folder at the same
time on an Exchange server.
(Update 0220)
This update integrates functionality between QSM Windows File System and
Windows File System Data Archiver.
Now Windows file System QSM can run the Threshold for “Run Data Archiver”
from Capacity by File System Report.
(Update 0227)
Add enhancement to migrate and recall files using Celerra EMC XML interface.
This enhancement includes logic to store proxy stub files on the FSDM agent
machine. The files on the filer are stubbed with a redirect to the FSDM
agent machine via HTTP or CIFS address.
The local files on the FSDM agent are stubbed using FSDM stubbing logic.
(Update 0257)
Added logic to perform restubbing at both filer and at FSDM agent.
(Update 0257)
Added logic to FSDM service to programmatically perform routine cleanup
of the local proxy stub folder.
(Update 0257)
Added logic to restub filer files using XML interface, and to create the
FSDM stub file on the local agent proxy stub path.
Note: Update 0251 must be installed for full functionality.
(Update 0257)
Restubbing of previously stubbed and recalled files is now supported for
regular DMNAS and for FPolicy.
(Update 0327)
When converting a sub-client from regular DMNAS to FPolicy DMNAS, previously
migrated files do not get recalled via FPolicy.
(Update 0327)
Added registry key option, to allow user to disable access time being preserved
on recalls and/or migrations. (Separate key for each).
[1] GXHSM_PRESERVE_ACCESSTIME_ONRECALLS - Preserves access time on recalls
[2] GXHSM_PRESERVE_ACCESSTIME_ONMIGRTNS - Preserves access time on migrations
**IMPORTANT** **IMPORTANT** **IMPORTANT** **IMPORTANT**
This update requires update 264. However, it's not a programmatic requirement
(Not forced by the installer)...
[1] DMNAS client will fail to start services if update 251/264 is not installed.
-
[2] FSDM service will fail to start if update 251/264 is not installed.
--
[3] FSDM agent will fail migrations and recalls if update 251/264 is not
installed. --
**IMPORTANT** **IMPORTANT** **IMPORTANT** **IMPORTANT**
(Update 0327)
Migrations fail when min-size rule is set to a number greater then 2GB
(Update 0480)
Recalls fail when file name contains percent character with a number.
Example: foo%20s.txt
**IMPORTANT** **IMPORTANT** **IMPORTANT** **IMPORTANT**
This update requires update 264. However, it's not a programmatic requirement
(Not forced by the installer)...
[1] DMNAS client will fail to start services if update 251/264 is not installed.
-
[2] FSDM service will fail to start if update 251/264 is not installed.
--
[3] FSDM agent will fail migrations and recalls if update 251/264 is not
installed. --
**IMPORTANT** **IMPORTANT** **IMPORTANT** **IMPORTANT**
(Update 0480)
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
Service pack minor version is not displayed in the version tab of client
properties window.
(Update 0021)
End user search for e-mails returns lesser items when smtp address is not
based on the alias name of the user.
(Update 0107)
Encrypted backups take a long time to complete
(Update 0292)
During Auxcopy of 6.1 NRS data, CVD on the target MediaAgent may experience
crashes.
(Update 0293)
Group object's 'member' attribute property is not being restored.
Create a registry key to allow restore of first 1500 values for 'member'
attribute of an object. Key location:
bRestoreMemberRangeVals DWORD 1 After creating the registry key, select 'member;range=0-1499'
attribute for restore instead of 'member' attribute.
(Update 0365)
Communication Service on the MediaAgent may crash during Auxiliary Copy
or Data Protection operation.
(Update 0405)
AuxCopy from NAS attached to NAS attached media sometimes fails. Log files
show a device busy error accessing the destination tape drive.
(Update 0430)
Total data size and single instanced data size may be incorrectly reported
on a single instanced storage policy copy.
(Update 0487)
Some users are not able to log in to the JAVA console using SSO functionality
(Update 0524)
Enhancements for Legal Hold. Support for Legal Hold backup and restore on
MediaAgents
(Update 0566)
End user search may not return results for some users.
(Update 0566)
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
Enable MediaAgent to communicate with the IBM 3494 Server on x64 Winodws.
(Update 0654)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
MediaAgent
CVIPTapeLibrary.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
This update fixes an issue where certain documents containing UNICODE characters
in the name, would fail to be viewed from the WEB GUI. This update needs
to be installed on the Web Search Server for full functionality of this
update.(Update 0111)
1-Touch Client Preparation shows “no driver found”.
When 1-Touch portion of System state backup identified a driver with missing
entries, it would fail to gather the next driver but the backup would show
the 1-Touch component backup was successful. The backup will now continue
to the next valid driver and log the invalid driver in the backup log.
(Update 0230)
If running a Full iDA Restore from Galaxy 6.1/7.0 on a client already upgraded
to version 7.0, Galaxy service will not start after rebooting the machine.
(Update 0273)
(Update 0273)
Performing a system state restore on Windows Server 2008 would leave the
windows event log service unable to start or read the logs that were restored.
(Update 0326)
File scan doesn't scan the contents if the subclient content is Root Volume.(Update
0360)
When a file system iDA backup job goes into pending because either the client
or commserve abnormally terminates (system crash, power loss, cluster failover,
etc), the resumed backup job may experience a crash.(Update 0363)
In Windows Server 2008 and Windows Vista, the ACLs of the symbolic link
objects may be restored to the target objects instead of the symbolic links.
An example of this problem can be checked when after a full iDA restore,
a user will get an
access denied error message when selecting Explorer from the right-click
menu of the "Start" button.(Update 0369)
After a full iDa restore in a Windows Longhorn Server machine, WINS server
service fails to start(Update 0393)
in Windows 2000 computers, backup and restore jobs fail to start
(Update 0394)
Unable to restore files after Incremental backups with no content change(Update
0452)
Backup job may crash due to stack overflow(Update 0468)
Windows 2000 Domain Controller recovery halts during 1-Touch recovery.
Microsoft Windows 2000 Domain Controller 1-Touch Recovery.
After the windows installation and automatic reboot and login,
Press OK to the message “You are currently running in safe mode…”.
From a command prompt: (c:\OneTouchTmp), run
Dcrestoreboot.bat
(Update 0473)
After installing Service Pack 2, file system backup fails to create VSS
snapshots.(Update 0517)
System State Restore of a computer that acts as a domain controller may
leave the domain controller in a bad state after the restore
(Update 0530)
Enhancements for Legal Hold. Support for Legal Hold backups and restores
on Windows File System Agent.In Windows Server 2008 file scan may detect
system junctions as mount point, causing the file scan phase to fail.
(Update 0620)
DR backups may fail with JPR: [Loss of control process clBackup.exe.] on
a machine where only CommServer is installed.
(Update 0631)
Fix problem in Windows Server 2008 where backup of the cluster database
was failing. With this fix, the registry entry CLUSTERDB_WRITER_BACKUP will
be ignored for Windows Server 2008 and beyond
(Update 0666)
Exclude the folder %SYSTEMROOT%\WinSxS from the file system scan
(Update 0666)
For systems where file system iDa, file system data migrator and possibly
data classification are installed, allow the use of any scan methods besides
classic scan if a certain registry key is present (HKEY_LOCAL_MACHINE\SOFTWARE\CommVault
Systems\Galaxy\Instance001\FileSystemAgent\ nOmitFSDMRestrictionsForBkp).
Keep in mind that if the key is present, the access time of the file will
not be preserved.
(Update 0666)
Web Server IIS GUI of a Windows Server 2008 machine fails to start after
rebooting the computer under the following 3 conditions:
- Ran a full iDa restore from a backup that included the Web Server IIS
component
- The machine at the time of the restore did not have the Web Server IIS
component installed
- The backup used to do the full iDa restore was done using the Windows
Change Journal as the file system scan method
(Update 0666)
Avoid the backup job entering in a hung state in case of backing up a WMI
database that is corrupt. The default timeout period is 5 minutes but it
can be change via the registry entry nWMIBkpTimeOut
(Update 0666)
Fix issue where online content indexing backup jobs can terminate unexpectedly
(Update 0666)
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
Restored files with status "BAD MEDIA" are not displayed in "Failed" category.
(Update 0024)
Added functionality to support CDR on Vista.
(Update 0129)
Adds support for localized events
(Update 0169)
Launching "Find & Recover" from Add-In in Outlook 2000 for the first time
generates an error "Cannot get Exchange agent application information."
(Update 0205)
Adds support for Celerra Data Migrator Proxy.
(Update 0251)
When hard deleting physical node after deleting installed agent the following
error may occur "Could not complete delete operation".
(Update 0334)
Enhancement to select folders for migration for exchange archiver
(Update 0334)
Adds support for localized events
Exchange Database restore fails when iDataAgent machine is also a MediaAgent
with index cache user impersonation
(Update 0347)
Enhancement to add licensing support for LegalHold feature.
(Update 0518)
The GUI locks up every few days and services need to be recycled on the
CommServe so new GUIs can be opened. EvMgrS.log contains many of these lines:
### writeBlocking() - Error [10053-WSAECONNABORTED] while sending on socket.
(Update 0679)
Change Windows longhorn name to read Windows Server 2008
(Update 0681)
Exchange CCR backup is started on the wrong machine.
(Update 0681)
Lotus Notes new feature to allow it to operate as a backup agent without
stubbing so its content can be content indexed.
(Update 0681)
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
The NAS backups of a NAS default subclient with content of "/" are backing
up too much data - they are backing up data that is in other subclients.
This issue applies to file servers that do not support filters. If a file
system, or subdirectory of a file system, is in another subclient then the
backup of the default subclient should not backup that file system.
(Update 0083)
NAS iDA restore fails with error (job failed) at 0% and error (app) at 5%.
This happens when the file system being backed up has some corruption causing
the file server to pass inodes that don't exist. With this update the backup
will succeed and restores will be possible from the valid data.
(Update 0236)
Incremental backups of subclients with more than 1 content path may do a
full backup of some content paths if the previous job went to pending and
then restarted and completed.
(Update 0375)
Support for SUN STK 5320 file server.
(Update 0375)
Pillar Data Systems backup option to not backup ACLs would backup the ACLs.
Pillar Data Systems block backup fails indicating a full volume must be
selected.
(Update 0375)
Isilon DAR restores of files fail.
(Update 0375)
NAS backup jobs which have a failure writing to tape are failing rather
than going to pending and retrying. Media write failures are not always
incremented.
(Update 0422)
A NAS backup to a tape drive on the MediaAgent that does not receive any
data from the file server in 3 hours may fail with a communication error
or may hang-up indefinitely with 0 bytes written to tape. This update will
increase the default timeout to 5 hours, correct the indefinite hang when
the timeout occurs, and will bring back in support for the “nREADSOCKETTIMEOUT”
registry setting to control this timeout. The “nREADSOCKETTIMEOUT” registry
setting is a DWORD value located in the NDMP_API key – it is the timeout
period in seconds.
(Update 0445)
NAS multistream backup sometimes does not use additional resources granted
after start of backup, and also does not de-allocate them properly. This
fix can be disabled with string registry key 'sFreeDrives' set to 'n' (in
"NAS" registry folder).
(Update 0682)
NAS Auxillary Copy fails when using NDMP version 3.
(Update 0682)
NAS backup job to a tape drive attached to the file server with SCSI3 reservations
enabled fails on tape spanning. The tape spanning will wait for 30 minutes
and then timeout.
(Update 0694)
It is recommended that backups on all iDataAgents requiring the update as well
as a Disaster Recovery Backup be run prior to installing this update. If this update
is being installed on a CommServe or Media Agent, log on to the CommServe as administrator
and ensure that no jobs are in progress. It is also recommended that all tape drives
be empty. If a job is in progress while you attempt to install this update the installation
will detect the running job and exit.
The following fixes/enhancements are included in this update.
Media Mount Manager Service may go offline while checking for Tape Alerts.
(Update 0442)
Adds support for Quantum LTO4 Tape Drive Hardware Encryption.
(Update 0492)
Tape drives may go offline when write protected tapes are used during backups.
(Update 0757)
Adds enhancement for automatically detecting cleaning media loaded in drive for tape drives attached to filer.
(Update 0757)
Fixes Media Mount Manager Service crash which may happen when login to filer fails for filer attached tape drives.
(Update 0757)
When run a backup/restore job with the tape that is write-protected on Linux using native Linux driversm it will fail with error: "Unable to communicate with the device [#######].
(Update 0757)
Dependency on Other Updates
Requires
0391
Obsoletes
0442 0492
Related
None
List of Files
This update updates the following files.
Platform
File
MediaAgent
CVScsiTape.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
NAS restores using hardware encryption fail. The event viewer shows “A restore protocol error has occurred while executing a restore for the client”. The CVD log on the CommServe shows error “ArMgrCS::getNextChunk NULL or empty MA network host name passed.”.
(Update 0762)
Dependency on Other Updates
Requires
0694
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
MediaAgent
nasMediaLib.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
SaveMergeBitmap does not detect clustered volumes on Windows Server 2008 and bitmaps are not merged on failover.
(Update 0825)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
Image Level iDataAgent
SaveMergeBitmap.exe
Quick Recovery Agent
SaveMergeBitmap.exe
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Adds support for Plasmon UDO2 drive (7.0.0 update 0651 also needs to be installed on CommServer).
(Update 0847)
Adds support for optical devices for Windows x64.
(Update 0847)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
MediaAgent
CvScsiMODisk.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Enhancements to handle situations where Snapview snapshots are deleted outside of Galaxy.
(Update 0414)
When using QR or CDR with Exchange 2007 application resources, the detection of the version of Exchange installed may fail yielding no actual application resources to be returned.
(Update 0700)
Discover of Exchange databases does not work for Exchange DB agent, CDR or QR.
(Update 0848)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Support provided for updating Linux PPC clients from CommServe Gui.
(Update 0647)
Fixes the problem where sybase agent updates were not getting installed on windows clients.
(Update 0647)
Properties screen on the CS GUI was wrongly reporting that Unix RecoveryDirector needs update.
(Update 0647)
CS GUI version tab was wrongly reporting that ServicePack was missing for Unix Copymanager package.
(Update 0647)
Friendly names are displayed incorrectly for some 7.0 updates in GUI and report.
(Update 0647)
"Download Needed" alerts for updates will not be received any more if CommServe cache is in sync with the ftp site contents.
(Update 0720)
"Updates Available to Download" alerts for updates will not be received if additional updates at CommServe cache are in sync with the ftp site contents.
(Update 0780)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
When viewing property settings of a fpolicy stub file, recalls are triggered.
On-Demand backup fails to migrate files.
**IMPORTANT** **IMPORTANT** **IMPORTANT** **IMPORTANT**
This update requires update 264. However, it's not a programmatic requirement (Not forced by the installer)...
[1] DMNAS client will fail to start services if update 251/264 is not installed. -
[2] FSDM service will fail to start if update 251/264 is not installed. --
[3] FSDM agent will fail migrations and recalls if update 251/264 is not installed. --
**IMPORTANT** **IMPORTANT** **IMPORTANT** **IMPORTANT**
1. Uninstall 6.1 Data Migratory for Network Storage Client to use FPolicy recall.
2. To disable recalls when right clicking a file, create the registry key GXHSM_FOLICY_EXCLUDE_NON_GENERIC and set the value to Y.
3. Note that some of the files may be partially viewable during the recall operation, this does not affect the complete recall of the file.
(Update 0625)
Fix to allow fpolicy recalls via NetApp Autohome feature
(Update 0695)
Fix restub logic for fpolicy
(Update 0695)
Added enhancement to optionally disabled recall trigger for fpolicy stub files when viewing property
(Update 0695)
Enhancement to sparse files by default when using fpolicy for NetApp 7.2 and higher
(Update 0695)
Fix GXHSMind crash related to migrating a DataClassSet
New fpolicy registry keys, with default value in [] brackets:
"GXHSM_FPOLICY_ENABLE_POPUP" [N]-- Enables popup message to notify user of a file being recalled via netsend
"GXHSM_FPOLICY_EXCLUDE_NON_GENERIC" [Y]-- When set to Y, ignores file notifications that don’t have the generic_read or generic_write flag set
"GXHSM_FPOLICY_RECALL_ON_OPEN_NOT_SPARCE" [Y]-- When set to Y, will recall files on open notification if the file is not sparse
"GXHSM_FPOLICY_PRESERVE_STUB_ATTRIB" [Y]-- When set to Y, preserve attribute changes made to the stub file, after the file has been recalled
"GXHSM_FPOLICY_AUTO_ENABLE" [N]-- When set to Y, will automatically enable fpolicy
"GXHSM_FPOLICY_ENABLE_MULTISERV" [N]-- Preserved for future use
"GXHSM_FPOLICY_ENABLE_ONTAPADMIN" [Y]-- When set to Y, will recall files using the ONTAP_ADMIN$ path
"GXHSM_FPOLICY_ENABLE_ONTAPADMIN_DBG" [N]-- When set to Y, will perform additional access test on a file using ONTAP_ADMIN$ path, and log results
"GXHSM_FPOLICY_SCREEN_FS_OP_CREATE" [N]-- When set to Y, will register FS_OP_CREATE for fpolicy file event notification *
"GXHSM_FPOLICY_CREATESPARSE" [Y]-- When set to Y, will create stub files that are sparse **
Notes:
*GXHSM_FPOLICY_SCREEN_FS_OP_CREATE default value is Y in NetApp 7.0 version and N for NetApp 7.2 and 7.1
** GXHSM_FPOLICY_CREATESPARSE default value is N on NetApp 7.1 after first recall
(Update 0695)
When recalling files that have certain German characters from a German OS, files fail to recall.
**IMPORTANT** **IMPORTANT** **IMPORTANT** **IMPORTANT**
This update requires update 264. However, it's not a programmatic requirement (Not forced by the installer)...
[1] DMNAS client will fail to start services if update 251/264 is not installed. -
[2] FSDM service will fail to start if update 251/264 is not installed. --
[3] FSDM agent will fail migrations and recalls if update 251/264 is not installed. --
**IMPORTANT** **IMPORTANT** **IMPORTANT** **IMPORTANT**
[4] New fpolicy registry keys, with default value between **
[a]"GXHSM_FPOLICY_CREATESPARSE" *Y* -- When set to Y, will create stub files that are sparse **
[b]"GXHSM_FPOLICY_RECALL_ON_OPEN_NOT_SPARCE" *Y* -- When set to Y, will recall files on open notification if the file is not sparse
[c]"GXHSM_FPOLICY_ENABLE_POPUP" *N* -- Enables popup message to notify user of a file being recalled via netsend
[d]"GXHSM_FPOLICY_EXCLUDE_NON_GENERIC" *Y* -- When set to Y, ignores file notifications that don’t have the generic_read or generic_write flag set
[e]"GXHSM_FPOLICY_PRESERVE_STUB_ATTRIB" *Y* -- When set to Y, preserve attribute changes made to the stub file, after the file has been recalled
[f]"GXHSM_FPOLICY_SCREEN_FS_OP_CREATE" *N* -- When set to Y, will register FS_OP_CREATE for fpolicy file event notification *
Notes:
*GXHSM_FPOLICY_SCREEN_FS_OP_CREATE default value is Y in NetApp 7.0 version and N for NetApp 7.2 and 7.1
(Update 0723)
File System backups failed to start in environments using firewall and IPV6
(Update 0732)
Remove excessive log messages in the filescan.log file
After this patch is installed, all new log information that it is supposed to be written to the files OnlineCIScan.log and DRFileScan.log will be written in the FileScan.log file
(Update 0732)
In a system with FSDM, DC and File System iDa, without the patch installed, the file system backup will always default to classic scan and the access time of the files will always be preserved. If the patch is installed and the registry entry is added then the file system scan will use whatever scan method has been selected in the properties screen of the backup set. The file access time will not be preserved.
Add the key nOmitFSDMRestrictionsForBkp (DWORD) under the FileSystemAgent. Value is irrelevant
(Update 0788)
Logic associated with registry key nDMRSendFileStatus is turned on by default when key does not exist.
This may cause the GUI to crash when viewing restore history with lots of recalled files. This update turns off the ability to display recalled files when viewing the recalled history. The registry key nDMRSendFileStatus located HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\EventManager turns this feature back on.
(Update 0807)
Fpolicy stub files do not get recalled after moving folder to parent folder sub path.
(Update 0807)
Celerra-DM fails to migrate files when filer has VDM configuration.
Logic requires user to create new registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\WinFSDataMigrator\AliasMappedPath
And user needs to add sub keys (REG_SZ) types that have key name as the filer path, and value as the VDM path.
Example:
[HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\WinFSDataMigrator\AliasMappedPath]
"\\MyFilerName\"="\\MyFilerName\root_vdm_2\"
Note:
Restubbing and auto-proxy stub recreation is not functional with VDM.
(Update 0824)
Browse backup data does not show all drives.
(Update 0901)
Some files are not showing up on the browse or as failed objects in report.
(Update 0901)
Backup and restore windows junction points. Note: This patch fixes data loss problem.
(Update 0901)
Qsnap would be the snap option only if DWORD "nOverrideVSSSnapSelection" is present under FileSystemAgent key of galaxy registry. For Windows 2000, if snap were selected, it would be Qsnap even in absence of above registry key.
DWORD "nOverrideVSSSnapSelection" under FileSystemAgent key for selection of Qsnap. Value does not matter.
(Update 0901)
When the customer does a browse he gets different results depending on which method he chooses to do.
(Update 0914)
GXHSMPopup fails to run on x64 and ia64
(Update 0914)
Can not do browse for DMNAS migrations using UNIX media agent
(Update 0914)
Recall failure and GXHSMService crash
(Update 0914)
Custom popup message not working
(Update 0914)
Remote popup doesn't work on Vista and Windows 2008
(Update 0914)
Corrupt DMR_58.dat causes migration failure.
Added new registry key option GXHSMN_REMOTE_POPUP_VIA_MSG_CMD.
This key is not created by default, and when the key is absent, it's default behavior is disabled.
To enable this logic, create this key (REG_SZ) type, and set the value to Y.
This key enables logic that replaces the net send command with a msg command.
This option may be desirable for Vista and Windows 2008 machines, which do not honor the net send option.
(Update 0914)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
The Library and Drive Configuration tool device detection does not
detect any devices on a NetApp GX file server. The devices can be
manually added using the option to add an NDMP drive, but they cannot be
detected.
(Update 0068)
This update addresses a problem where memory consumption of the
Auxiliary Copy process (AuxCopy.exe)
continually grew when Content Indexing of Lotus Notes Archiver data was
in progress.
(Update 0095)
This update prevents the restore process from consuming an unnecessary
amount of memory when preparing
a large amount of Lotus Notes e-mail for viewing.
(Update 0095)
This update fixes a problem where only the first attachment within a
Lotus Notes e-mail containing multiple
attachments was viewable when using the Web-based Search Console. Now
all attachments within one e-mail will be
viewable and all of the associated contents correct.
(Update 0095)
Content indexing for Exchange email fails with c-tree error.
(Update 0123)
Media agent folder used by Content indexing jobs may grow huge.
(Update 0123)
Content Indexing jobs for Exchange email data may cause extremely high
memory usage and freeze the system.
(Update 0123)
Exchange emails with non-English content failed to be searched.
(Update 0123)
Cannot search a document based on the file name for online content
indexed documents.
(Update 0123)
Adds support for Dell RD1000 USB drive.
(Update 0136)
Library Controller may not fail over when medium changer device drops
out of operating system.
(Update 0156)
Lotus Notes emails containing unicode characters in the body do not show
up properly in
the search results and cannot properly be searched.
(Update 0185)
Auxcopy process may disappear while an offline content indexing job for
exchange email data and will cause the job to go pending.
(Update 0216)
Auxcopy process may crash during an offline content indexing job for
exchange email data after logging a c-tree error.
(Update 0216)
Offline Content Indexing job for Exchange Mails is failing with the
following error in cvd.log on the Admin node of Content Indexing Server.
"FIXMLGenerator ERROR: DocumentException: FIXML has illegal UTF-8 byte
sequences in url.path, url."
(Update 0240)
Offline content indexing job for exchange data failed with the error,
"Invalid UTF-8 sequence in data".
(Update 0249)
Replication of FAT32 volumes on Vista does not work.
(Update 0271)
On a computer that is running Vista and is the source for replication,
if a large number of pairs are aborted, then the CVReplication service
may crash.
(Update 0271)
When files are copied from a network share to a directory that is being
replicated, the copied files may not be replicated correctly. The
destination versions may be corrupt and/or attributes may not be
correct.
(Update 0271)
Source folders on FAT filesystems will be replicated as compressed
folders on the destination.
(Update 0271)
CDR does not use the configured Data Interface Pairs.
(Update 0271)
Orphan file handling does not properly delete read-only files.
(Update 0271)
Support for SDR added.
(Update 0271)
If the ACL's for a file is bigger than 4KB, pipeline may fail to send
the ACL.
(Update 0271)
If replication fails for a pair, the status of that pair is not updated
properly in the GUI.
(Update 0271)
If the source or destination path has Unicode characters, replication
may not work properly.
(Update 0271)
When the physical nodes of a cluster are rebooted and the cluster is the
source of CDR replication, the destination CVReplication service may
crash.
(Update 0271)
When a cluster that is the source for CDR replication is rebooted a
number of times, the CVReplication service may crash on startup.
(Update 0271)
CDR services crash on destination while replaying log.
(Update 0305)
Offline content indexing job for Exchange failed with following logging
in AuxCopy.log: "Failed to add ... to guid table".
(Update 0307)
Offline content indexing job for Exchange failed with following logging
in AuxCopy.log: "Getting the data in the middle of chunk for archive
file".
(Update 0307)
Performance counter for time consuming operation to pinpoint the
bottleneck.
(Update 0307)
Offline Content Index job performance goes down during processing data
from backup jobs with smaller data size.
(Update 0316)
Auxcopy process may exit during an offline content indexing job while
indexing files which contain special characters in file names.
(Update 0316)
Performance improvement for Content Indexing of Exchange Mails
(Update 0367)
Content Indexing of Exchange Mails takes a very long time
(Update 0367)
Adds performance counters for the restore process on the Media Agent.
(Update 0426)
Reduce the verbosity of logging when unbuffered I/O is switched on at
the mount path level.
(Update 0478)
Auxcopy from a single instanced copy for large backup data may go
pending after copying some data.
(Update 0478)
Exchange Data Archiver recalls are failing with the error, "Failed to
connect to EvMgrC service" after upgrading to 7.0 from 6.1 in cluster
configuration.
(Update 0502)
Offline Content Indexing job for Exchange Mailbox data may become
unresponsive after indexing some portion of the data.
(Update 0503)
Enhancements for Legal Hold. Support for Content Indexing of Legal Hold.
(Update 0538)
File system scan fails when the subclient's content is a UNC Path with
wild cards and the option "Treat characters as regular expressions" is
checked (ex. \\server\share\[A-E]*)
(Update 0544)
When files with old time stamps are copied to the source folder,
destination does not preserve the old time and updates files to new
time.
If files have a space in the beginning of the name, those files will be
picked up as orphan.
Files with System and Hidden Attribute set ( like thumbs.db) can
experience error ACCESS_DENIED ( 5 ) on destination.
Compression setting changes on files can update time stamp on replicated
file on destination.
When files with just the READ ONLY attribute set are overwritten on a
source computer, the destination file can lose the READ ONLY attribute.
Pairs started on SDR system can go in replication state instead of
stopped.
(Update 0569)
Reports and Alerts do not display the list of failed files for Data
Protection jobs on a Clustered Configuration.
(Update 0570)
Media Mount Manager Service on the Media Agent may go offline if there
are multiple library controllers configured on that Media Agent.
(Update 0592)
Exchange DB backups to tape drives attached to filer fail with error
Unknown error. With this update, Exchange database backups will succeed.
(Update 0641)
All outstanding recalls should succeed in case of CS cluster failover.
To implement this new enhancement for FSDM and EXDA, other supporting
updates also needed.
The following updates from FSDM and EXDA is needed.
FSDM: 695
EXDA: 670
Details:
There will be 2 keys available to control the retry behavior both for
FSDA and EXDA.
FSDA
Location: HKLM\Software\CommVault Systems\Galaxy\\EventManager
nRetry_Recall_Delay (DWORD in second) : The default is 300
nRetry_Recall_Timeout(DWORD in second) : The default is 60
EXDA
Location: HKLM\Software\Microsoft\Office\Outlook\Addins\Galaxy.Ex2KMBDM.CVEAAddin
RecallRetryTimeout (DWORD in second) : The default is 300
DelayBetweenRetries (DWORD in second) : The default is 60
The idle timeout (nDMRSIDLETimeout) for the pipe should be relatively
short and should be equal to delay time above. The key should be located
at HKLM\Software\CommVault Systems\Galaxy\\EventManager on the agent
machine.
(Update 0644)
Enable MediaAgent to detect the SAS tape drives that are connected to
the HP SAS raid controller cards.
(Update 0652)
Aux Copy process may hang on linux powerpc platform.
(Update 0653)
Enhancement for Dynamic WWN Port Number tracking for AIX MediaAgents
(Update 0657)
This update requires at least 11.0.1.0 version of the Atape driver from
IBM. If the Atape version is prior to 11.0.1.0, the system may crash
when executing passthru commands. The crash was observed only on systems
booted in 64 bit mode.
(Update 0657)
Use the utility setAtapeOnMA to enable passthru commands via Atape.
NOTE: Do not run the utility 'setAtapeOnMA' to change option for a given
MA while backups are running on that MA.
(Update 0657)
On the Library controlling Media Agents, set the following registry key
manually before turning on the dyntrk=yes.
MediaAgent/USE_ATAPE_FOR_PASSTHRU to 1
(Update 0657)
CDR replication can stop with the error "Replication log is locked" when
the network connection is broken.
(Update 0657)
Checksum may be run twice during smart sync on files that are locked.
(Update 0657)
Orphan File Processing can cause the data on destination to be deleted
if the case of the folder name does not match on source and destination.
(Update 0657)
Exchange DB backups to tape drives attached to filer fail with error
Unknown error. With this update, Exchange database backups will succeed.
(Update 0657)
Enable MediaAgent to detect the SAS tape drives that are connected to
the HP SAS raid controller cards.
(Update 0673)
Unable to View Failed Items from Job History.
(Update 0680)
Unable to View On-demand reports
Additional Symptoms: The problem is intermittent and is resolved by
restarting client services.
(Update 0680)
Added descriptive advise strings for the error events related to SCSI
sense codes and device errors.
(Update 0686)
CommServe services sometimes may go down due to network issues.
(Update 0707)
In a multi node cluster environment of 32on64 setup, stub recovery
failed to bring back the message.
(Update 0721)
The stub recovery from 6.1 addin for 7.0 agent failed to bring back the
message.
(Update 0721)
On Linux PPC platform, when a single instanced backup is run, Single
instancing database engine does not launch and the job goes to pending
with "internal software error"
NA
(Update 0724)
When only IPv6 is available as the communication method between the CS
and MA machine the MediaAgent will fail to come online.
(Update 0727)
Enhancement to support more documents per CI node.
(Update 0744)
The file exclusion filter based on file extensions do not work for
Exchange data.
(Update 0744)
The offline content indexing job for Exchange Data goes pending in a
specific email repeatedly.
This update requires the FAST pipeline changes to take a full effect on
the indices. Please inquire within Professional Services for further
assistance on this pipeline changes.
(Update 0744)
Fix for occasional CVD service crash due to random buffers sent by port
scanning softwares.
(Update 0751)
Large number of files created by a single instancing backup affects the
performance of the file system where the magnetic mountpath is
configured.
(Update 0774)
After a suspend, backups may restart from a wrong location which could
result in data loss.
(Update 0774)
Single Instanced Restore/Auxcopy fails after user credentials are
modified for network mountpaths.
(Update 0774)
Restore job may go to waiting state with error "There are not enough
drives in the drive pool" when exchange of media fails.
(Update 0774)
Synthetic full jobs may fail with error "Failed to mount medium. Failed
to get media information for volume."
(Update 0774)
Improving the Performance of multistream backups.
(Update 0774)
Fix for backup/restore failures due to Multi-homed Clustered Commserver
(Update 0774)
In backup target (EZ configure), handle multiple mount paths by
disallowing edit operation for the mountpath location.
(Update 0776)
Enhancement to optionally search case-sensitive data with
case-insensitive search patterns for UNIX and NDMP data.
(Update 0776)
This update enables pruning of multiple jobs through the command
qoperation agedata using the option -deljobbyid.
In case of multiple commcells with the same name exist,
Please create the following registry key:
DWORD type registry key value 'QSDK_USE_COMMCELL_NUMBER', and set the
value to 1 at location:
HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance00x\EventManager
(Update 0798)
Modify the EZ Wizard behavior based on the type of install.
(Update 0798)
Based on the given Media Agent, provide library list to GUI.
(Update 0798)
File System Archiver restore after wild card search is sometimes
incomplete
(Update 0833)
EvMgrS crashes upon restart when Oracle jobs are running.
Although EvMgrC.exe exists on all machines, it is required only on the
CS to fix this crash.
(Update 0834)
Added localization support for strings for Disk Management features.
(Update 0838)
Added localization support for Commserve Disaster Recovery GUI tool.
(Update 0838)
Library and Drive Configuration Tool may not automatically add the tape
drives into the library if the drive vendor name has 8 characters in it.
(Update 0863)
This update enables Stamp Media Operation from Command Line, use
qdrive stampmedia
(Update 0867)
QSDK support the Data Path options to allow Oracle backups specify a
data path as a job option.
(Update 0882, Update 0881)
(Update 0882)
Auxcopy fails with "Undefined Software Error occurred" with unbufferred
IO option for Magnetic library backups.
(Update 0905)
Adds support for new VDS Disk Management features.
(Update 0908)
Auxcopy from a single instanced storage policy copy may fail with
"Undefined software error" while copying backups of very large files.
Note: This patch fixes data loss problem
(Update 0915)
Auxiliary copy job fails on IPV6 networks.
Discovery of Exchange and SQL fails on IPV6 networks.
(Update 0917)
It is recommended that backups on all iDataAgents requiring the update as
well as a Disaster Recovery Backup be run prior to installing this update. If
this update is being installed on a CommServe or Media Agent, log on to the
CommServe as administrator and ensure that no jobs are in progress. It is also
recommended that all tape drives be empty. If a job is in progress while you
attempt to install this update the installation will detect the running job and
exit.
The following fixes/enhancements are included in this update.
SQL backups are being marked as completed even when the chunks are not committed, this is causing restores to fail. Note: This patch fixes data loss problem
(Update 0932)
Dependency on Other Updates
Requires
0383
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
SQL Server iDataAgent
PipelineSetupUtility.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Failure when multiple users try to view searched document from the Web interface
(Update 0189)
Backups to single instanced storage policy may go pending with error "Internal Error. Could not get the port on which SIDB is listening"
(Update 0934)
Dependency on Other Updates
Requires
None
Obsoletes
0189
Related
None
List of Files
This update updates the following files.
Platform
File
File System iDataAgent Windows XP
CvBasicLib.dll
DriverForFileSystemDM
CvBasicLib.dll
File System iDataAgent Windows 2000
CvBasicLib.dll
File System iDataAgent Windows 2003
CvBasicLib.dll
MediaAgent
CvBasicLib.dll
QSnap
CvBasicLib.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
NAS backup of 3 or more streams may terminate early with WaitForMultipleObjects error in the NasBackup log.
(Update 0779)
On Unix clients, NAS backup of a subclient with many paths may terminate early with no error.
(Update 0779)
NAS backup of a subclient in which at least one path fails to backup may restart from the beginning instead of the job completing with status of partial success.
(Update 0779)
EMC Celerra backup of a Virtual Data Mover file system with VBB option selected fails with error - "EMC VBB only supported on the root of a filesystem."
(Update 0938)
Dependency on Other Updates
Requires
0694
Obsoletes
0779
Related
None
List of Files
This update updates the following files.
Platform
File
MediaAgent
nasBackup.exe
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Driver does not hook mount points on a cluster, when the cluster has ALLOW-Failback-Immediately settings.
(Update 0147)
Query Info recalls can not be turned off on Windows 2000. This update adds the ability to through a registry key.
To turn off query info recalls, please set the following registry key:
String value "GXHSM_RECALL_ON_QUERY_INFO_IRP" set to 'Y' be default, under location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GXHSM\
New GXHSM_RECALL_ON_QUERY_INFO_IRP driver registry key available for Windows 2000, which can be used to turn off query
information IRP recalls.
This gives the Windows 2000 driver functionality similar to 6.1 GA version.
This key is on 'Y' by default on Windows 2000 and off 'N' by default on all other platforms.
On Windows 2000, when this key is turned on, it allows correct functionality of recalls when file mapping applications are used. However, a side
effect is that it can cause recalls to trigger when user views property settings of a file.
(Update 0147)
Added support for Windows Server 2008.
(Update 0343)
GXHSMNet driver crash
(Update 0870)
Fix for oplock issue. Systems include following:
a) Removed 34 second delay when recalling files via UNC path
b) Fixed Copy&Paste and Cut&Paste failure via UNC path
A new registry key, GXHSM_OPLOCK_BREAK, has to be added at location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GXHSM???\GXHSM_OPLOCK_BREAK
The key is of string type, and the disabled value is 'N'. Enabled value is 'Y'. The key is not created by default. When the key is absent, the default behavior is for GXHSM_OPLOCK_BREAK to be enabled.
(Update 0989)
Fixed BSOD issue related to NO_RECALL logic.
(Update 0989)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Added Window Vista 32-bit and x64-bit Support as a 1-Touch client.
1-touch boot cd for all 7.0 supported locales.
Considerations:
Do not move the boot partition to a new partition location on the target if the 1-Touch recovery is a domain controller. Filtering
the boot.ini during the recovery of a domain controller will not work because the process copies and reapplies the
boot.ini from backup during the automated recovery.
After restoring the event logs in a Windows Server 2008, the event log service may not be able to start up
(Update 0728)
During a restore with “Do not overwrite files” option selected, some of the existing files that are locked get deleted Note: This patch fixes data loss problem
(Update 0753)
After a system state restore in a Windows Server 2008 computer, Server Manager may not show the installed role and feature of the computer
(Update 0890)
In a Windows Server 2008 cluster, during a system state backup, if one of the new clusters hive resides in a drive different from the system drive, the Writer Registry backup may fail.
This update should also be applied to a 1-Touch Server via copytocache for deployment to 1-Touch clients during recovery process.
(Update 0890)
The backup job always hangs up at "Scan" phase, then it fails due to "the loss of control process ifind.exe"
(Update 0896)
Any restore operations initiated from web search console of celerra DM data, always shows failure
(Update 0928)
"Export to PST" breaks the quick view links of emails
(Update 0928)
Download to PST of malformed emails fails and the restore process exit unexpectedly.
(Update 0928)
1-Touch Client Preparation Wizard detect all the disk size as 0 GB.
(Update 0947)
1-Touch recovery failed. The source disk is 1 MB bigger than the destination disk, but the recovery is to original machine.
(Update 0947)
System state filters not working for windows 2000 server, they work correctly on windows 2003 servers.
adding filter: {WMI Database}
(Update 0947)
Importing foreign disk using diskpart 2008 fails.
(Update 0947)
This update requires the update 923.
Windows File System Agent data protection operations would fail in the Archive Index phase.
(Update 0961)
Windows File System data protection jobs go pending due to error code 19:599 (ifind.exe) when all Windows registry Event DWORD entries for File Name include a literal path.
(Update 0970)
GUI server may run out of memory and crash when backup jobs are running in machines where the "Server" service is down
(Update 1005)
Win2k3 incremental b/u runs fine but a Synthetic full jobs will always fail w/ a network error.
(Update 1024)
Out of place restore of the sysvol folder brings back the junction points
(Update 1024)
System state restore does not bring back the SysVol shares
(Update 1024)
Full system restore to a different hardware causes stop 7B BSOD
(Update 1024)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Galaxy 7.0 NAS restore does not allow full control of the destination file structure. The full backup path structure is recreated on restore. This update is an enhancement to the NAS iDA to handle the "Preserve Source Path" options presented on the restore options dialog for NAS restores.
There are corresponding updates for the GUI to provide the "Preserve Source Path" options, and for the NDMP restore enabler to handle the new options. To use this new functionality please be sure the GUI and NDMP restore enabler updates are in place.
(Update 0812)
When a NAS restore with the "Use Direct Access Restore" (DAR) option selected from a backup that was suspended and resumed is converted to not use DAR, the restore fails when moving to the second archive (the restarted backup). This happens when using the NDMP Remote Server product. The restore logs a media failure. Restores will be converted to not use DAR when a directory is selected for restore and the file server does not support DAR restore of a directory for that backup.
(Update 1026)
Restore of an entire backup out of place is running too slow. The nasRestore log shows it is using Direct Access Restores (DIRECT=Y) which should not be used in this case.
(Update 1026)
An Isilon directory restore in Galaxy 7.0 from a backup taken in Galaxy 6.1 is restoring only the top level directory - it should restore the entire tree.
(Update 1026)
Dependency on Other Updates
Requires
0694
Obsoletes
0812
Related
None
List of Files
This update updates the following files.
Platform
File
MediaAgent
nasRestore.exe nasRestoreLib.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Auxcopy process exits unexpectedly on offline content indexing job when content indexing malformed mails
(Update 0943)
Junk characters shown on online CI search result.
(Update 0943)
Search returns zero result for exchange public folder data.
(Update 0943)
Auxcopy job from a single instanced storage policy copy may fail with error "Data read from media appears to be corrupted" if the block size for the Single Instance datapath is changed.
(Update 0996)
Synthetic fulls may fail with error "Data from the media is corrupted" on Magnetic mountpaths with Unbuffered I/O option.
(Update 1014)
Database restores via multiple Media Agents may fail if the client version is older than 7.0 and MA version is 7.0
(Update 1072, Update 1071)
After commcell migration, restore may fail when it needs to restore data from multiple backup jobs performed in different commcells.
(Update 1072, Update 1071)
The disk space used for failed single instanced jobs is never cleared off and recovered for reuse.
(Update 1072, Update 1071)
For Oracle10g and above, Oracle restores from Magnetic uses only one stream.
(Update 1072, Update 1071)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Index processing for active directory and file system job types have errors for specific media agent (which is also the CommServe in this case).
(Update 0587)
AD restore on a group that has 2500 members restores nothing.
(Update 0600)
SSO login goes into an infinite loop eventually causing the EVMGRS service to crash
(Update 0716)
AD restore on a group that has 2500 members restores nothing.
(Update 0773)
Some users may not be able to log into CommCell console via SSO
(Update 0773)
The problem has to do with authentication. When providing credentials in the DOMAIN\USER format, the back-up reports to be successful but it actually isn't. The back-up will always be 3,57MB and a restore is not possible. When browsing for a restore, CommVault shows no objects below the Organization object. Note: This patch fixes data loss problem
(Update 0959)
Active Directory data protection operations would fail to complete and remain in a running state. The following would seen in the log file "cvldap () - CvLdapSearch:enumerateChildrenW" for the running job. This might occur if backing up a range attribute for an object.
(Update 1085)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Auto configure operation of tape drives does not work correctly on multi-HBA based MediaAgents and if they are zoned to see only certain drives.
(Update 0966)
For EZConfig, the tape library should always be configured as sighted library.
(Update 0966)
Adds support for new VDS Disk Management features.
(Update 0967)
Adds support for new VDS Disk Management features.
(Update 1019)
Replicated magnetic library using SDR (Simple Data Replication) may not automatically replicate contents if mountpath is created on root folder.
(Update 1019)
Adds support for new VDS Disk Management features.
(Update 1037)
Adds support for new VDS Disk Management features.
(Update 1049)
Adds support to use removable SATA drive for PnP Disk Library.
Set the DWORD reg key "bSupportPnPSATADrives" under MedaAgent to 1 to support SATA as PnP Disk. It also ignores "Stamp For Blank Only" GUI option.
(Update 1087)
Adds ability to control SDR pair start interval using registry key on Media Agent.
For SDR start interval: Create SDRPairStartIntervalMins DWORD Registry value under MediaAgent section of Commvault Registry to control interval at which SDR Paris should be kicked off. Value of the key cannot be less than 30.
(Update 1087)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
If the Incremental QR is suspended during the initial full copy, it doesn't reset the destination bitmap and that it turns fails the subsequent QRs.
(Update 0077)
Image Back up is not getting suspended in reasonable Time, it suspends after it copies the entire Data.
(Update 0134)
Image Back up is not getting suspended in reasonable Time, it suspends after it copies the entire Data
Image Level backups are failing to backup large volumes with more than 400GB of data.
(Update 0298)
On a restart of a full Image Level backup, the backup fails with the error message "Data received on the media agent from the client is corrupted."
(Update 0298)
Image Level iDA backups fail on concatenated volumes created using a third party software volume manager.
(Update 0880)
Added support for nOverrideVSSSnapSelection key under ImageLevel to override the default use of VSS and use QSnap instead, when value is non-zero. This affects both CVVIBackup.exe and CVVIScan.exe.
(Update 0925)
Ignored GUI setting for VSS or QSnap in favor of always using VSS except when above registry key is defined except under Windows 2000 or Windows XP where QSnap will always be used no matter what is defined by the registry key.
must manually create this DWORD registry key:
Location: HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\ImageLevel\nOverrideVSSSnapSelection
Service cycle is not required to recognize this key, just create it and go. It should be put on any windows image machines that support VSS so that VSS will automatically be used by default as the source snap engine. On win2000 and winxp (OS’s that don’t support VSS the way we require) Qsnap will be used by default so the registry key is not required on those.
(Update 0925)
During Image Level Backup, customer is getting Mount/reservation errors
(Update 1097)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
WORM Media gets marked bad after first use.
(Update 0002)
Library Arm Controller failover interval is not honored when all library controllers are offline.
(Update 0120)
Prevent Export operation on multiple media does not save the expiration time.
(Update 0120)
Library deconfiguration fails when there are Vaultracker actions running for the library.
(Update 0120)
Export for media in resumed Vaultracker action does not occur if there is only one media to be exported.
(Update 0120)
Services fail to start on a DR site, reporting error Invalid CommCell ID.
(Update 0120)
Cancelling export from the 'Exports in Progress' view may fail with error "Invalid Inputs for Vault Tracker command".
(Update 1099, Update 1098)
Backup jobs may wait with JPR as "No Resources" when all available media in library are pending to be exported.
(Update 1099, Update 1098)
Vault Tracker Actions may not fire up due to Database deadlocks when many vault tracker policies are scheduled to run at the same time.
(Update 1099, Update 1098)
Dependency on Other Updates
Requires
None
Obsoletes
0120
Related
1098
List of Files
This update updates the following files.
Platform
File
MediaAgent
MediaMovement.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Can't restore SQL 2000 databases to another SQL 2000 instance when the original instance is now SQL 2005.
Registry Key to be added: Created in: CommServe computer Location: HKEY_LOCAL_MACHINE\Software\CommVault Systems\Galaxy\Instance Key: CVD Value Type: DWORD Value: bDoNotCheckSqlVersion Valid Range
0 = Disabled - SQL versions lower than the restoring database version will not be shown
1 = Enabled - all SQL instances that are configures on the CS will be shown
(Update 1106)
Enhancement to execute qscripts from qcommand
Note: qcommand displays the output of the qscript to the console. To see this result update 1064 should be installed.
(Update 1106)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
If a computer has a large number of volumes, the machine may not start properly.
(Update 0061)
When performing initial sync with CDR, the source client may become unresponsive if
snapshots associated with initial sync for multiple pairs are created and deleted simultaneously.
(Update 0061)
CDR source client may crash after exceeding max cache space during init sync.
(Update 0061)
System crash of x64 client may occur while using Windows Disk Management.
(Update 0061)
Added Vista support as source client for CDR.
(Update 0061)
When the extent size is changed on one cluster node, the node can crash and not boot properly.
(Update 0228)
Windows Server 2008 support added for Qsnap.
(Update 0336)
While the cache file is expanding during heavy I/O conditions the server may crash with bugcheck D1.
(Update 0642)
When a snap is being deactivated simultaneously with another snap being activated the server may freeze.
(Update 0642)
Snap operations fail with error 1450 (insufficient system resources).
(Update 1114)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Additional fixes for SQL database backups failing when the backups are converted from Log to Differential and then
from Differential to Full.
(Update 0416)
Backup failure occurs when backing up Exchange DB data using VSS on the passive node of an Exchange CCR configuration.
(Update 0444)
Backups of databases with Unicode characters in their names fail.
(Update 0564)
This update addresses an issue where win_7.0.0B76_0382 was not installed during the application of SP2 causing
metadata associated to successful SQL backups to not be recorded. If your SQL backups fail after applying this update please contact support for corrective action.
If your SQL backups continue to succeed there is no further action on your part
(Update 0688)
System state restore from a backup using VSS in a Windows Server 2008 computer may fail
(Update 0891)
Backup job crashes on computers using the German language while backing up system state
(Update 0981)
During SQL restore even though unconditionally overwrite option is not selected data is overwritten if user is performing an in-place restore.
(Update 1023)
SQL master database is not getting converted to full if user disables the Backup Rules at subclient level.
(Update 1023)
FS Backup of Virtual Node Backing up Local Drives on the Active Node.
(Update 1025)
SQL Server VSS restores fail for Unicode databases. (Update 1043)
If instance is added by typing in the name through the Console, during backup the SQL version is not updated. This cause the Destination Server field be empty during restores.
(Update 1043, Update 1048)
SQL Server iDA backups fail on Windows 2008 if User Account Control (UAC) is turned on.
(Update 1043)
ifind.exe fails to come up as it has query.dll dependency on server core
(Update 1047)
System state backups appear not to be deleting VSS snaps.
(Update 1063)
Synthetic backup is small for a Win 2k3 machine if the sub client content is a mount point
(Update 1063)
System protected files component failures during system state VSS backup on windows 2008.
Any subclient where System State is included only supports single stream backup operations.
Multiple stream backups of System State is not supported.
(Update 1131)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
Patches are required on both the client and the MediaAgent for this to work
as designed. Using a patched client and an unpatched MediaAgent will cause
protection jobs to go Pending.
NetWare MediaAgent is not supported. Using a patched client on a Netware
MediaAgent will cause the job to go Pending.
The following platforms are not being supported:
FreeBsd
MAC
IRIX
Previously, hard linked data that was backed up would duplicate data by
making a copy of the data for each hard link saved. This fix will cause only
a single copy to be saved for the hard linked files.
The following registry key enables/disables this functionality.
Registry location:
/etc/CommVaultRegistry/Galaxy/Instance001/FileSystemAgent
Key:
HLINK Y - If hard links exist, the backup data should not be duplicated for
linked files.
Hark links will be preserved on the restore.
HLINK N - If hard links exist, the hard links are ignored on backup and the data
is duplicated on the media (additional storage is allocated).
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Job goes pending :Current backup is Single instanced. It is prevented from multiplexing on to same
(Update 0965)
Warning log entries are filling the clbackup log files. Entries containing ‘No path conversion for file’ will be suppressed unless the log level is raised to Debug.
(Update 1124)
Duplicate search results in end user search of Online content indexed data.
(Update 1132)
System protected files component failures during system state VSS backup on windows 2008
(Update 1145)
Dependency on Other Updates
Requires
0163 0264 0480 0666 0914
Obsoletes
0965 1124 1132
Related
None
List of Files
This update updates the following files.
Platform
File
File System iDataAgent Windows XP
clBackup.exe
File System iDataAgent Windows 2000
clBackup.exe
File System iDataAgent Windows 2003
clBackup.exe
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
ArchiveIndex is slow when there are many full backup cycles for the subclient in the index cache.
(Update 0213)
Sharepoint Document iDataAgent backup and restore will support metadata information more than 32Kb.
(Update 0237)
Search after Erase Selective Data sometimes hangs.
(Update 0523)
Enhancement to view the top N largest files protected by a Data Protection job
To use this feature the following Registry Keys have to be created on the
MediaAgent under the MediaAgent Section
All keys' defaults ==0 (by name ascending, all report records returned).
nFileListSortOrder DWORD
nFileListTopN DWORD
nFileListNotLessThan STRING ( 64 bit number )
Keys values:
All report records with size
nFileListSortOrder
0==sort by name ascending
1==sort by size descending
All other values will be replaced with default one (0).
nFileListTopN
>1000000 - all lines will be returned (overhead of the list limiter: 8 bytes per line)
>0 but <=1000000 - up to given number of rows will be returned - could be less if number of files in the list is less than
<=0 - all records will be returned
(Update 0619)
Customer is unable to browse files from an Image level backup. This is due to Metadata collection failing (hardlinks on the volume), however GUI show the phase completes successfully.
(Update 0619)
Image File Level Restore from a clustered MediaAgent may fail
(Update 0633)
Fix createIndex failure during some Unix FS backups
(Update 0767)
Indexing sometimes fails with corruption in space reservation file.
Typically following log lines are seen in createIndex.log on Media Agent
ICACHEDIR: invalid line '' in reserve file /fisc/backup/galaxy/MediaAgent/IndexCache/CV_Index/reserveFile
(Update 0954)
Failures in recovery after Exchange Mailbox Archiver search.
(Update 0969)
View all versions or search across cycles sometimes fails when MA is on a cluster group.
(Update 1007)
Browse sometimes does not show a directory
(Update 1044)
List Media Precise operation no longer shows pop-up which requests unnecessary index restore or close the Media window.
Enhancement is also made to be able to hide indexing tapes when no index restore is needed
(Update 1096, Update 1093)
(Update 1096)
Added Hard-Links backup and restore support for Unix FS IDA. Avoids backing up duplicate data.
(Update 1144)
System State and File System data restored from from multi-stream data protection operations may leave certain files corrupt after restore completes.
(Update 1153)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Some file locks on UNIX MediaAgents may not be removed and may result in failure to start services.
(Update 1185)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
Continuous Data Replicator iDataAgent
MMDebug.dll
File System iDataAgent Windows XP
MMDebug.dll
File System iDataAgent Windows 2000
MMDebug.dll
File System iDataAgent Windows 2003
MMDebug.dll
MediaAgent
MMDebug.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
When an intermittent failure occurs during a DMNAS migration in the backup phase, files are getting backed up as directories or as zero size files. This results in recalled files getting recalled to zero size. Note: This patch fixes data loss problem
(Update 0955)
Files modified between the backup phase and stub phase get migrated, which could cause recent changes to be lost. Note: This patch fixes data loss problem
(Update 0955)
Win FSDM data does not single instance properly with Win FS data
(Update 1038)
Recovery failes when DM message from field is x400.
(Update 1052)
Win FSDM data does not single instance properly with Win FS data.
(Update 1055)
Recall retry logic cannot be turned off via registry key, and the retry logic settings cannot be modified.
To turn off recall retry logic, the following keys should be created and set to zero value:
EventManager\nRETRY_RECALL_TIMEOUT
EventManager\nRETRY_RECALL_DELAY
Both keys are of DWORD type.
(Update 1055)
Stubbed data from a DataClassSet subclient cannot be browsed\recovered via Browse.
(Update 1055)
When a UNIX client recalls a file on a NetApp filer, the UNIX file attributes gets changed. If the recall is triggered by a local UNIX user, the file owner changes to root after the recall.
(Update 1092)
GXHSM_FPOLICY_CREATESPARSE is turned on by default on 7.0, 7.1, and 7.2 OnTap version of NetApp filer. This value should be turned off automatically when any of these three versions are detected.
(Update 1092)
Added the following two registry key options:
1. GXHSMRESTORE_USE_CREATE_ALWAYS
2. GXHSMRESTORE_NAS_SEC_ACL
(Update 1092)
The GXHSMRESTORE_USE_CREATE_ALWAYS registry key is defaulted N, and should not be set to Y, unless directed by a Commvault Customer Engineer.
(Update 1092)
GXHSMRESTORE_NAS_SEC_ACL By default, the internal value of this key is set to Y. The purpose of this key is to enable or disable the logic in the restore which restores the security ACL's. Restoring of the Windows security ACL's is not compatible with fpolicy shares that are in MIX mode, and have UNIX clients. When this key is set to N, the recalled file retains the security ACL which the stub file already had.
2a. For Celerra, GXHSMRESTORE_NAS_SEC_ACL key should be set to Y. It is not created by default, and the restore service uses the default value of Y on a restore.
2b. FSDM does not use GXHSMRESTORE_NAS_SEC_ACL key, and FSDM restores will always restore security ACL’s.
2c. For traditional DMNAS GXHSMRESTORE_NAS_SEC_ACL key should be set to Y. It is not created by default, and the restore service uses the default value of Y on a restore.
2d. For fpolicy GXHSMRESTORE_NAS_SEC_ACL key will be set to “Default N” by the GXHSMFPDM.dll process. The key is created by default the first time this process has a share to monitor. If the user wants to turn this on, the key should be set to Y. For fpolicy this key should only be turned on if the share is NTFS or if the share is MIX mode, but the user is not going to use any UNIX clients to trigger recalls.
**Note 2**:
By default, UNIX files which have readonly access from the agent do not get migrated. If the GXHSMSTUBPERSERVEREADONLY registry key is set to Y, then the agent will migrate readonly files. *However*, one of the attributes will get modify in the process.
--w-------
This particular attribute can not be removed by the agent, and this is a side effect of migrating UNIX readonly files.
Example:
-r--r--r-- Before migration
-rw-r--r-- After migration
-r-xr-xr-x Before migration
-rwxr-xr-x After migration
---x--x--x Before migration
--wx--x--x After migration
(Update 1092)
Running Ondemand backup causes a value of "\" to be added to the FSDM Drives registry key
(Update 1190)
When a "\" value is in the FSDM Drives registry key, user can not map to the agent machine
(Update 1190)
Running Celerra migration with invalid configuration, causes gxhsmstub to crash
(Update 1190)
Migrating Celerra files with certain unicode characters causes gxhsmstub to crash
(Update 1190)
Proxy Pruning logic in GXHSMService caused service to crash when scanning extended UNICODE characters.
(Update 1190)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
During a backup or auxcopy to a single instanced storage policy copy, the, Single Instance Database Engine may fail to start with error "SIDB Index files are missing"
(Update 0988)
Auxcopy from a single instanced storage policy may fail with error "Failed to read chunk" if encryption is enabled on the backups.
(Update 1015)
Adds command line options to dump Single Instance Database and statistics to text file format for troubleshooting purposes and as input for other tools.
(Update 1205)
Dependency on Other Updates
Requires
0163 0264 0391 0480 0566 0676 0681 0917
Obsoletes
0988 1015
Related
None
List of Files
This update updates the following files.
Platform
File
MediaAgent
SIDB.exe
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
When Hardware based Single Instancing is enabled, the retention lock is not set on all files on the disk backup storage.
In order to make sure that the retention lock on the backup files are set correctly, when setting the retention on the Storage Policy Copy properties, make sure that both the following retention properties are set to the same value.
a. "Basic Retention Rule for All Backups"
b. "Basic Retention Rule for Data/Compliance Archiver Data"
If they are not the same, the largest retention value among these will be taken into consideration for setting the retention lock.
(Update 1206)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Folder inclusion feature for exchange mailbox.
(Update 0817)
Job Summary Report hangs for some clients
EvMgrC portion of the change has already been released as 7.0 Update 834, so please make sure that is installed onto the clients for which the report is hanging, along with this Update. Also please install this update onto the CommServe.
(Update 1018)
EvMgrC handle count keeps growing until Galaxy Services are stopped.
(Update 1123)
Provide folder inclusion/exclusion functionality for Lotus Notes Archiver.
In order to see the enhanced functionality, a GUI Update + CommClient Update will also be required.
(Update 1187)
Enhancement to change the default priority setting for aux copy job
Use the QScriptToSetAuxCopyJobPriority.sql qscript to set the priority number in the database.
(Update 1215)
Galaxy services may fail to communicate across firewall in certain configuration.
(Update 1234)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Offline Content Indexing job for Exchange data fails
(Update 1182)
Auxiliary Copy job throughput may go to zero when multiple Mediaagents are involved in a copy and it takes longer than a few minutes to copy chunks
(Update 1207)
Offline CI for exchange data does not handle the single instanced attachments data.
If update 1183 is installed on the Exchange clients, this update is required.
(Update 1239)
Dependency on Other Updates
Requires
0163 0264 0391 0480 0566 0676 0681 0917 0983 1072
Obsoletes
1182 1207
Related
None
List of Files
This update updates the following files.
Platform
File
MediaAgent
AuxCopy.exe CVMAAppDataRetriever.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
This update enables client to be deconfigured from commandline using the option -deconfigure in qcommand qdelete.
usage: qdelete -c clientname -deconfigure
(Update 1240)
Dependency on Other Updates
Requires
None
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
File System iDataAgent Windows XP
qdelete.exe
File System iDataAgent Windows 2000
qdelete.exe
File System iDataAgent Windows 2003
qdelete.exe
MediaAgent
qdelete.exe
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Sql Database backup jobs are in running state but no data transfer for several hours. In the case of a VDITIMEOUT, the job will go into pending state and the SQlBackup process will fail.
Jobs should no longer remain in a hung state.
(Update 1241)
Dependency on Other Updates
Requires
0383:MSSql 1131
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
SQL Server iDataAgent
CvSQLVDIBase.dll SqlDataReaderWriter.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Fixed issue with starting a large number of pairs when the source computer was crashing with bugcheck code 0xA.
(Update 0154)
Replication journal log file will be released while uninstalling CDR.
(Update 0154)
Corrects the issue with high kernel memory consumption when there is a high rate of change in the directories replicated by CDR.
(Update 0154)
Fixed issue with crash observed on clusters when a file or folder on a CIFS share from the cluster is renamed.
(Update 0154)
A computer that is acting as the source for CDR replication can become unresponsive for 10 minutes if the rate of I/O on that computer is high and memory allocation for CDR logging fails.
(Update 0226)
Source computers may crash if they run out of nonpaged pool memory.
(Update 0270)
On Vista, if small files are deleted during a smart sync operation, they appear as 0 size files on the destination.
(Update 0270)
Source computers running Vista may crash if subfolders of a monitored path are moved to the Recycle Bin.
(Update 0270)
Added CDR Driver support for Windows2008.
(Update 0270)
Some application created files are missing on destination after replication.
(Update 0568)
When files are accessed on the network using an application such as Autocad, non-readable files appear on destination.
(Update 0568)
After replication the file times are not updated correctly.
Sometimes Destination files can be newer than Source by few seconds.
Reason:
File System Uses some internal tracking to determine when to update Modified time on the file which is not notified to the filter drivers. CVFSJ Driver determines such scenarios based on identifying patters and nature of change and at the end when files are no longer used, uses System time to be used as Mod Time for File on destination. There can be a skew of time between NTFS updating the Modified time on the file and Driver determining the need to update the modified time on destination.
Some times Destination Files will have ARCHIVE attribute bit set even though source files do not have ARCHIVE bit.
(Update 0568)
CDR source machine may crash with bugcheck 0x19, if CDR source volume also has Windows FRS configured to replicate.
(Update 0822)
When replicating user profiles, permissions on the profile folder do not get replicated correctly. Note: This patch fixes data loss problem
(Update 0926)
Server appears to freeze while CDR is replicating.
(Update 1245)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Using CV search addon in Outlook stops the Galaxy services on EX server.
(Update 1051)
Prepend user defined prefix to message subject in stubs in offline archiving.
Key name: LMArchivePrefix
Type: String
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\Galaxy.Ex2KMBDM.CVEAAddin
Value: desired prefix
(Update 1252)
Expand environment variables set in the "LM_PST_LOCATION" registry key.
(Update 1252)
optional time range selection for search operation in "find and browse" via registry key
Key name: nSearchRangeDays
Type: DWORD
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\Galaxy.Ex2KMBDM.CVEAAddin
Value: Default number of days to search for protected messages in Outlook Addin Find and Recover
(Update 1252)
OWA Recalls fail with "LDP Lookup Failed" in the CAS proxy setup.
NOTE: Run following commands from exchange management shell to configure exchange impersonation on exchange server for archiver user.
Get-ExchangeServer | where {$_.IsClientAccessServer -eq $TRUE} | ForEach-Object {Add-ADPermission -Identity $_.distinguishedname -User (Get-User -Identity ArchiverUser | select-object).identity -extendedRight ms-Exch-EPI-Impersonation}
Get-MailboxDatabase | ForEach-Object {Add-ADPermission -Identity $_.DistinguishedName -User ArchiverUser -ExtendedRights ms-Exch-EPI-May-Impersonate}
NOTE: ArchiverUser should be replaced by real user.
NOTE: To enable archiver user impersonation in owa, add the following entries to 'appsettings' section of 'web.config' file
<add key ="CVOWA:UseArchiverAccount" value="true"/>
NOTE: To disable archiver user impersonation in owa, remove obove entries or set its value to "false".
(Update 1252)
Attempting to recall stubs via OWA external URL fails.
(Update 1252)
Update for windows2008(IIS7) compatibility for stub recalls from OWA 2007.
(Update 1252)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
IFind.exe crashes virtual machine with many virtual drives.
(Update 0623)
Uninstall crashes during virtual uninstalls
(Update 0623)
Uninstall crashes during uninstalls on cluster machines with more than 60 disk resources.
(Update 0689)
New shortcut was added for install on DVD. Uninstall code is applied via a patch only.
(Update 0985)
SP4 installs some new EXEs to Base folder, but are not removed during uninstall.
(Update 0985)
Windows File System backup of Physical Node Skips Local Drives on the Active Node.
(Update 1164)
System State backup may fail when tries to backup a file path longer than 260 characters.
System State backup may hang at disk quota component.
In Windows Server 2008, if IIS 6.0 and IIS 7.0 are installed, only IIS 6.0 is backed up.
(Update 1164)
New API to return drive lists for virtual server
(Update 1189)
If IIS 6.0 and IIS 7.0 are installed in a Windows Server 2008 computer then the IIS 6.0 files may not be backed up
(Update 1198)
During restore of IIS in a windows server 2008 computer, files may fail to be moved during reboot if the parent folders do not exists
(Update 1198)
When Job results folder are on a drive other than system drive the IIS are not getting moved properly.
(Update 1198)
Some System protected files may be skipped from the backup in Windows Server 2008 and Windows Vista
(Update 1198)
In Windows Server 2008 or Windows Vista, system protected files may fail to be moved from the staging folder if the file path has more than 260 characters
(Update 1198)
clbackup crashes on windows 2000 during onetouch component backup when extended disks partitions are present
(Update 1253)
During a restore of Exchange 2007 database data, job may fail with a VSS error relating to the database component not being found in especially a CCR setup running on Windows 2008.
(Update 1253)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
Error while writing to job results directory can cause Remote Office backup to not replicate all data.
For short file name to be replicated create following registry key
\HKLM\Software\Commvault System\Galaxy\InstancexxX\FileReplication
nReplicateShortName REG_DWORD 0x1
abort Pair, delete data on destination and perform full sync.
(Update 0941)
Destination CDR service crash observed when a pair was being aborted.
(Update 1100)
CDR service sending false alert for Remote Office Backup after finishing sync.
(Update 1100)
Remote Office backup replication can fail with "could not decrypt folder" error.
(Update 1100)
Remote Office Backup may delete root folder from destination while performing Orphan File Processing for server 2008.
(Update 1100)
Remote office backup may fail over WAN if WAN optimization is turned on.
(Update 1100)
Remote office backup auxiliary copy may fail due to missing files on destination.
(Update 1100)
Data pipe restart during operational window can cause high bandwidth usage.
(Update 1100)
CDR service on destination machine crashes while processing certain MA chunks during smart sync, when running in Remote Office Backup Mode.
(Update 1254)
CDR Service on destination may consume high memory while processing single instanced chunk, when running in Remote Office Backup Mode.
(Update 1254)
Paused replication due to throttling may not resume automatically after services are recycled on destination during throttling conditions.
(Update 1254)
FAN-IN RP are now allowed if pairs are not replicating.
(Update 1254)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
SAP MaxDB incremental backups are shown as FULL Backups.
(Update 0313)
Enhancement to support selective copy for third party SAP MAX DB backups
(Update 0801)
SAP backup failed but the backup was left hanging on SAP server.
(Update 0849)
SAP IDA, Support for Multistream log backup are needed.
(Update 1167)
backint fix for reporting Media Manager errors correctly to Job Manager and mark the job pending
(Update 1265)
Dependency on Other Updates
Requires
None
Obsoletes
0313 0801 0849 1167
Related
None
List of Files
This update updates the following files.
Platform
File
SAP for MaxDB
backint.exe
SAP for Oracle
backint.exe
File System iDataAgent Windows XP
CVJobRepCntl.dll
File System iDataAgent Windows 2000
CVJobRepCntl.dll
File System iDataAgent Windows 2003
CVJobRepCntl.dll
MediaAgent
CVJobRepCntl.dll
QSnap
CVJobRepCntl.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
OnDemand Instance does not allow for database/instance management in the job controller.
Currently can only see 'On Demand Instance' but can not identify which database instance is currently being backed up.
(Update 0053)
For Oracle IDA, archive log backup from an archive log destination fails when archive log destination path contains archive log directory and part of archive log name.
(Update 0053)
No connection string is allowed in the rman script for qoperation backup command.
(Update 0053)
Only 3 characters can be used in the RMAN channel variable - oracle does not have this restriction when user supplies rman script for qoperation backups.
(Update 0053)
The RMAN output file in the job results directory does not get flushed out immediately.
(Update 0053)
qcommand bbackup does not have an option to pass the rman output file path where rman runtime logs to be written.
(Update 0053)
During Selective Online full logs backup, controlfile is not backed up.
(Update 0053)
Add SBT Performance statistics if the registry key sORASBTPERFSTAT is set.
(Update 0053)
Oracle Jobs complete with error when Suspended.
(Update 0263)
Oracle IDA Multiplex Restore performance improvement.
(Update 0317)
Qoperation oracle backup fails when connection string is specified in the rman script.
(Update 0317)
On AIX connecting to Oracle instance fails in Galaxy, if "/" is used as connect string
(Update 0317)
RMAN duplicate fails in Galaxy when database has many files.
(Update 0596)
Oracle IDA backup fails when Oracle instance have NLS_LANG set to non American_America.US7ASCII character set.
To enable different character set other than American_America.US7ASCII, specify NLS_LANG environment settings through _NLS_LANG registry key. If the registry key is not set NLS_LANG will be set to American_America.US7ASCII.
For RAC IDA, specify the above registry settings in all the RAC instance nodes.
Example:
To set NLS_LANG env to AMERICAN_AMERICA.WE8ISO8859P1 for Oracle Instance with SID rman10g,please add the registry key under OracleAgent/.properties
rman10g_NLS_LANG AMERICAN_AMERICA.WE8ISO8859P1
(Update 0596)
Oracle instance DB Status is shown as UNKNOWN if Oracle database has custom sqlplus settings (e.g heading off)
(Update 0726)
DataAging fails when Commserver host name is different from Client's Commserver host name.
(Update 0726)
Command line backup does not exit properly, incase of incorrect Channel arguments are passed.
(Update 0726)
Generate RMAN script(optimizer_mode=rule) for Oracle 10g backup failures with registry key on CS sRMANOPTIMIZERMODE.
Create instance from GUI may fail if the key “sSRVORAAGENT Y” is located on the CommServe.
(Update 0726)
Media Id is returned incorrectly for Oracle backups.
(Update 0859)
Allocate RMAN sbt channel with first Galaxy Instance name and client name if CvInstanceName and CvClientName are not passed.
(Update 0927)
Duplicate database fails if auxiliary Oracle instance is on a different client and Oracle instance not created in Galaxy GUI.
(Update 0927)
Oracle RAC iDA cross machine restores support is added from command line.
For Commandline Restores (RAC cross machine and duplicate) add the
following channel ENV parameters
(Update 0930)
CvClientName - Galaxy client name where SBT process runs
(Update 0930)
CvInstanceName - Galaxy Instance name where SBT process runs
(Update 0930)
CVOraRacDBName - Source RAC database name
(Update 0930)
CVOraRACDBClientName - If restoring to a machine which is not part of the RAC pseudo client setup, specify this parameter to point to the one of Galaxy physical client that is part of RAC pseudo client.
(Update 0930)
Oracle 11G Support On windows
(Update 1042)
Update SCN number accurately after logs backup job.
(Update 1053)
Handle custom sqlplus settings during Oracle instance Browse.
(Update 1154)
Disable Oracle DeMultiplex restore by default
(Update 1154)
sbtio.log file size keeps increasing in UDUMP dir when jobs are run and not pruned periodically
Registry key sMAXORASBTIOLOGFILESIZE to be added under /etc/CommVaultRegistry/Galaxy/Instance/OracleAgent/.properties.Thevalue set is in bytes to control the size of sbtio.log file.
(Update 1208)
SCN is not updated correctly during Oracle Offline Backup.
(Update 1266)
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Media Mount Manager Service may go offline when there are multiple library controllers configured on the Media Agent.
(Update 0425)
Library may go offline when the physical inventory for the library takes more than 10 minutes. Offline reason "The command Inquiry failed due to The request could not be performed because of an I/O device error."
After applying the update, user has to enable "prevent physical inventory" option in library properties page and reset the library.
(Update 0486)
VaultTracker export failed for ACSLS library with error: "Failed to export media in slot [xxx] from library [STK ACSLS] due to error: The operation failed because the IP Library Server returns error."
(Update 0486)
While importing tapes into the Tape Library, do not use the slots that are the source slots for the media mounted in drives.
(Update 0974)
During Reset operation on tape library with auto import option enabled, the exported media in I/E port will not be imported back to the slots.
(Update 1108)
When Export media is performed for Spectra Gator library which is configured to do unload queue, the media in unload queue may be used for the subsequent backup job and fails with error: "The SCSI device reported that conflict element is reserved."
(Update 1269)
Dependency on Other Updates
Requires
0391
Obsoletes
0425 0486 0974 1108
Related
None
List of Files
This update updates the following files.
Platform
File
MediaAgent
CVMALibHandler.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Enhance the NAS iDA support to include the Sun 7000 file server. The Sun 5320 is already supported.
(Update 1271)
Dependency on Other Updates
Requires
0694
Obsoletes
None
Related
None
List of Files
This update updates the following files.
Platform
File
File System iDataAgent Windows XP
LibNdmpClientAccess.dll
File System iDataAgent Windows 2000
LibNdmpClientAccess.dll
File System iDataAgent Windows 2003
LibNdmpClientAccess.dll
MediaAgent
LibNdmpClientAccess.dll
QSnap
LibNdmpClientAccess.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
NAS attach to MA attach NAS auxiliary copy fails with 'chunk mismatch' error in the AuxCopy.log.
(Update 0752)
AuxCopy of direct attach NAS data to MA attach data path may fail with "Failed to read chunk[x] in media[y]...". Will happen if the aux copy is interrupted while copying the first chunk of an archive file and then is resumed.
(Update 1213)
Data verification of NAS data fails if the backup being verified was of a read only file system. The AuxCopy log shows an NDMP_INTERNAL_ERROR returned from the file server.
With this update, a registry string value named "sDATAVERIFICATION_DESTINATIONDIR" can be added to the NAS key on the MA running the verification. This registry key can be used to specify a writeable location to be used during the verification. A "tmp" directory may be created under this location but nothing else will be written.
(Update 1275)
Dependency on Other Updates
Requires
0694
Obsoletes
0752 1213
Related
None
List of Files
This update updates the following files.
Platform
File
NDMP Remote Server
CVNdmpRemoteServer.exe
MediaAgent
NasAuxCopyLib.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
SQL 2000 authentication problems without built in administrators group present.
(Update 1218)
When performing SQL transaction log backups outside our product, the next differential backup converts to full.
(Update 1276, Update 1278)
Dependency on Other Updates
Requires
0383 1131
Obsoletes
1218
Related
1278
List of Files
This update updates the following files.
Platform
File
SQL Server iDataAgent
SQLClientDll.dll sqlDMO.dll
Before You Install the Update
It is recommended that backups on all iDataAgents requiring the update
as well as a Disaster Recovery Backup be run prior to installing this
update. If this update is being installed on a CommServe or Media Agent,
log on to the CommServe as administrator and ensure that no jobs
are in progress. It is also recommended that all tape drives be empty.
If a job is in progress while you attempt to install this update the
installation will detect the running job and exit.
The following fixes/enhancements are included in this update.
Fixes for the SharePoint Server Database Agent on MOSS 2007 or WSS 3.0:
- Shared Services Provider Restore hosted on Web Application “Default
Web Site” will succeed.
- Shared Services Provider Restore job from tape media will no longer
wait with reason “The media is already Reserved…”.
Windows Update 179 is required for full functionality of this fix.
(Update 0070)
Fix for the SharePoint Server Database Agent:
- During Database components Restore SQL VDI timeout value might be
increased if DWORD type registry key value
'nSqlVdiTimeOut' is created and set to more than 100000 sec.
Please create the following registry key to set the timeout value:
DWORD type registry key value 'nSqlVdiTimeOut' is created and set to
more than 100000 sec at location
HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\MSSharePoint
Default value of SqlVdiTimeOut is 99999 seconds when registry key value
doesn't exist.
(Update 0070)
Fixes for the SharePoint Server Document Agent on MOSS 2007 or WSS 3.0:
- Restore of versioned List item with attachments will no longer fail
on.
- Correct values for column Translator for List type Translator will be
restored during entire site restore.
- Correct values for columns Created and Created By will be restored.
- Libraries and Lists default View will be set appropriately after
restore data from Sharepoint 2003 to Sharepoint 2007 sites.
If Libraries and Lists default Views for upgraded from Sharepoint 2003
to Sharepoint 2007 sites are still not restored properly
then DWORD registry value bRESTOREVIEWTOOLBAR should be created and set
to 0 under
HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance[Number]\MSSharepointDocAgent
prior to restore.
Remove the key once the restore is completed.
(Update 0070)
Fix for the SharePoint Server Document Agent on SPS 2003 or WSS 2.0:
- Backup will pick up the content of Virtual Servers in “Upgrade” state.
The Virtual Server should be upgraded prior to restore of any data to
it.
(Update 0070)
Fixes for the SharePoint Archiver Agent:
- Items will be successfully archived from Libraries with setting
“Require Check Out”=Yes.
- Stubs will be pruned in SPDAStubDatabase.db when Archive Rule is set.
- Temporary files created during recall will be deleted.
(Update 0070)
Fix for the SharePoint Archiver Agent on MOSS 2007 or WSS 3.0:
- Correct values for columns Created and Created By will be restored.
(Update 0070)
Subsequent run of Automatic Updates is not installing ServicePack on
agents that were added after the initial installation of the ServicePack
on the client.
(Update 0208)
Added support for Exchange 2000 for one-pass restore feature.
(Update 0252)
Version tab for Lotus Notes Doc and Lotus Notes DB iDAs does not report
updates as installed after Galaxy services are recycled.
(Update 0715)
Restores to clients from a CS/MA with multiple network interfaces may
fail if the client is unable to communicate with the primary interface
on the CS/MS.
(Update 1196)
This update fullfills partial requirements for support of remote client
upgrades (e.g. clients not on the same machine as CS) to release 8.0
through the CommCell Console. This feature allows for upgrades to be
initiated from the CommCell Console. Feature specific documenation will
be provided in Simpana release 8.0 Books On Line when the feature is
made available in 8.0. This update is a pre-requisite for full feature
functionality.
(Update 1249)
Restores to clients from a CS/MA with multiple network interfaces may
fail if the client is unable to communicate with the primary interface
on the CS/MS.
(Update 1283)
It is recommended that backups on all iDataAgents requiring the update as
well as a Disaster Recovery Backup be run prior to installing this update. If
this update is being installed on a CommServe or Media Agent, log on to the
CommServe as administrator and ensure that no jobs are in progress. It is also
recommended that all tape drives be empty. If a job is in progress while you
attempt to install this update the installation will detect the running job and
exit.