pramod1
asked on
EXCHANGE 2010 DAG
I am getting below error on my DAG database back up failures:
we can see that the CommVault operation is failing because it is unable to locate the shadow for the DB during backup.
exTiDbBackup.log
=============
948 1d10 02/06 03:16:07 1453502 [CsExchangeShadow::FullBac kup] failed to backup file [\\?\GLOBALROOT\Device\Har ddiskVolum eShadowCop y944\DB\IM E.Db.edb
948 1d10 02/06 03:16:07 1453502 Abort shadow operation
948 1d10 02/06 03:16:07 1453502 Entering [CVSSClientShadow::AbortSh adow]
948 1d10 02/06 03:16:07 1453502 CsSnapRequestor::DeleteSna pshot() - Call m_vss-DeleteSnapshots(m_sn apshotSetI d, type, bForceDelete, &lDeletedSnapshots, &NondeletedSnapshotID) [FAILED, throwing CV exception] - Code = 0x80042308, Description = VSS_E_OBJECT_NOT_FOUND
948 1d10 02/06 03:16:07 1453502 CsSnapRequestor::DeleteSna pshot() - Error deleting a8132c1e-3d54-43a0-a9ec-2f d3f834143d shadow set - VSS_E_OBJECT_NOT_FOUND
948 1d10 02/06 03:16:07 1453502 CsSnapRequestor::BackupCom plete() - Call DeleteSnapshot() [FAILED, throwing CV exception] - Code = 0x80042308, Description = VSS_E_OBJECT_NOT_FOUND
948 1d10 02/06 03:16:07 1453502 CsSnapRequestor::BackupCom plete() - Failed to delete the snapshot set VSS_E_OBJECT_NOT_FOUND
948 1d10 02/06 03:16:07 1453502 [::Backup]: Failed to perform VSS backup. Backup .
=============
we can see that the CommVault operation is failing because it is unable to locate the shadow for the DB during backup.
exTiDbBackup.log
=============
948 1d10 02/06 03:16:07 1453502 [CsExchangeShadow::FullBac
948 1d10 02/06 03:16:07 1453502 Abort shadow operation
948 1d10 02/06 03:16:07 1453502 Entering [CVSSClientShadow::AbortSh
948 1d10 02/06 03:16:07 1453502 CsSnapRequestor::DeleteSna
948 1d10 02/06 03:16:07 1453502 CsSnapRequestor::DeleteSna
948 1d10 02/06 03:16:07 1453502 CsSnapRequestor::BackupCom
948 1d10 02/06 03:16:07 1453502 CsSnapRequestor::BackupCom
948 1d10 02/06 03:16:07 1453502 [::Backup]: Failed to perform VSS backup. Backup .
=============
Are any of the VSS writers in an error state?
ASKER
no
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes
If you filter the application and system log for criticals, warnings and errors only can you see anything relevant? especially in and around the time of the job/errors.
How many servers in DAG?
How many servers in DAG?
Have a look at this http://documentation.commvault.com/commvault/v10/article?p=products/windows/backup_troubleshooting.htm
Also just check if space on any of the related drives where the server is creating the snapshot are less than 20% free space total or not?
Also just check if space on any of the related drives where the server is creating the snapshot are less than 20% free space total or not?
Two similar situations we had. TL;DR, check your drive space, you may be at or very near capacity.
Commvault wants to make a VSS. On our Exch 2010 environment, this landed on our DB mount points. Unfortunately many of our mount points were at or near capacity. This caused the VSS to not update. Checking the Volume Shadow copies and where they were 'landing', I moved a couple around to spare drives in the DAG. Now the VSS could be created and dbs backed up.
Corollary, our Commvault server was running low on storage space. This caused the opposite effect of 1. Instead the backups couldn't complete so it wasn't deleting the old VSS off the server. Checking the DBs, we had 4-5 VSS created for each, in some places, filling up my DB copies with 'hidden data'. We ended up having to change our CV solution so that the backups were smaller. More incrementals, less fulls. Retire backups so they dropped off in half the time, etc.
Commvault wants to make a VSS. On our Exch 2010 environment, this landed on our DB mount points. Unfortunately many of our mount points were at or near capacity. This caused the VSS to not update. Checking the Volume Shadow copies and where they were 'landing', I moved a couple around to spare drives in the DAG. Now the VSS could be created and dbs backed up.
Corollary, our Commvault server was running low on storage space. This caused the opposite effect of 1. Instead the backups couldn't complete so it wasn't deleting the old VSS off the server. Checking the DBs, we had 4-5 VSS created for each, in some places, filling up my DB copies with 'hidden data'. We ended up having to change our CV solution so that the backups were smaller. More incrementals, less fulls. Retire backups so they dropped off in half the time, etc.
ASKER
can this be a issue
vss-.PNG
vss-.PNG
ASKER
ASKER
it is reported event id 36
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.