Exchange DB Backup - Loss of control process extidbbackup.exe

Last post 04-19-2012, 11:45 AM by Higgi. 7 replies.
Sort Posts: Previous Next
  • Exchange DB Backup - Loss of control process extidbbackup.exe
    Posted: 04-19-2012, 10:17 AM

    Simpana 9 backing up MS exchange 2007 on a windows 2008 R2 box

    3 storage groups in seperate subclients (1 in each)- until recently all worked 100%.

    Now all jobs run go to pending with error "Loss of control process exTiDbBackup.exe"

    I have so far restarted all services on exchange server and made sure all updates applied - commserve. MA and client all runing SP5B. I have not, as yet, had a reboot of exchange server.

    I'd be much obliged if anyone can shed any light?

    Extract from extiddbbackup log:

    6124 1490 04/19 15:05:14 ### [::main]: Using client focus as [exchangeservername]
    6124 1490 04/19 15:05:14 ### ::main() - Passive node backup property not enabled backup will be done on current node.
    6124 1490 04/19 15:05:14 ### [::main]: I am in a First Phase of the backup so do backup as directed..
    6124 1490 04/19 15:05:14 224036 JM Client  CVBkpJobClient::init(): Initializing job object with token [224036:3:1].
    6124 1490 04/19 15:05:14 224036 Init() - Initializing job control [token=224036:3:1,cn=exchangeservername], serverName [COMMSERVE], ControlFlag [1], Job Id [224036]
    6124 1490 04/19 15:05:14 224036 CVJobCtrlLog::registerProcess(): successfuly created file [C:\Program Files\CommVault\Simpana\Base\JobControl\6.124]
    6124 1490 04/19 15:05:14 224036 [::main]: *** Exchange Server Name: 'exchangeservername'. ***
    6124 1490 04/19 15:05:14 224036 [::main]: Event check is not enabled
    6124 1490 04/19 15:05:14 224036 [::main]: Set discover wait time to 9984 seconds
    6124 1490 04/19 15:05:14 224036 [::main]: Mutex acquired. Continuing...
    4876 1090 04/19 15:05:15 ### [::main]: Using client focus as [exchangeservername]
    4876 1090 04/19 15:05:15 ### ::main() - Passive node backup property not enabled backup will be done on current node.
    4876 1090 04/19 15:05:15 ### [::main]: I am in a First Phase of the backup so do backup as directed..
    4876 1090 04/19 15:05:15 224035 JM Client  CVBkpJobClient::init(): Initializing job object with token [224035:3:1].
    4876 1090 04/19 15:05:15 224035 Init() - Initializing job control [token=224035:3:1,cn=exchangeservername], serverName [COMMSERVE], ControlFlag [1], Job Id [224035]
    4876 1090 04/19 15:05:15 224035 CVJobCtrlLog::registerProcess(): successfuly created file [C:\Program Files\CommVault\Simpana\Base\JobControl\4.876]
    4876 1090 04/19 15:05:15 224035 [::main]: *** Exchange Server Name: 'exchangeservername'. ***
    4876 1090 04/19 15:05:15 224035 [::main]: Event check is not enabled
    4876 1090 04/19 15:05:15 224035 [::main]: Set discover wait time to 9984 seconds
    6124 1490 04/19 15:08:48 224036 No public folder databases detected.
    6124 1490 04/19 15:08:48 224036 No public folder databases detected.
    6124 1490 04/19 15:08:49 224036 No public folder databases detected.
    6124 1490 04/19 15:08:49 224036 Following paths were discovered...
    6124 1490 04/19 15:08:49 224036 ****Database Path[0]: Microsoft Information Store\Storage Group 1\SGNAME Store 2 ****
    6124 1490 04/19 15:08:49 224036 ****Database Path[1]: Microsoft Information Store\Storage Group 1\SGNAME Store 1  ****
    6124 1490 04/19 15:08:49 224036 ****Database Path[2]: Microsoft Information Store\Storage Group 1\SGNAME Store 3 ****
    6124 1490 04/19 15:08:49 224036 ****Database Path[3]: Microsoft Information Store\Storage Group 1\SGNAME Store 4 ****
    6124 1490 04/19 15:08:49 224036 ****Database Path[4]: Microsoft Information Store\Storage Group 2\SGNAME Store 5 ****
    6124 1490 04/19 15:08:49 224036 ****Database Path[5]: Microsoft Information Store\Storage Group 2\SGNAME Store 6 ****
    6124 1490 04/19 15:08:49 224036 ****Database PathDevil [6]: Microsoft Information Store\Storage Group 2\SGNAME Store 7 ****
    6124 1490 04/19 15:08:49 224036 ****Database Path[7]: Microsoft Information Store\Storage Group 2\SGNAME Store 8 ****
    6124 1490 04/19 15:08:49 224036 ****Database PathMusic [8]: Microsoft Information Store\Storage Group 3\SGNAME Store 9 ****
    6124 1490 04/19 15:08:49 224036 ****Database Path[9]: Microsoft Information Store\Storage Group 3\SGNAME Store 10 ****
    6124 1490 04/19 15:08:49 224036 ****Database Path[10]: Microsoft Information Store\Storage Group 3\SGNAME Store 11 ****
    6124 1490 04/19 15:08:49 224036 ****Database Path[11]: Microsoft Information Store\Storage Group 3\SGNAME Store 12 ****
    6124 1490 04/19 15:08:49 224036 Found the default Subclient.
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 1\SGNAME Store 2'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 1\SGNAME Store 1'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 1\SGNAME Store 3'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 1\SGNAME Store 4'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 2\SGNAME Store 5'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 2\SGNAME Store 6'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 2\SGNAME Store 7'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 2\SGNAME Store 8'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 3\SGNAME Store 9'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 3\SGNAME Store 10'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 3\SGNAME Store 11'
    6124 1490 04/19 15:08:49 224036 [::discoverNewDB]: PATH = 'Microsoft Information Store\Storage Group 3\SGNAME Store 12'
    6124 1490 04/19 15:08:49 224036 [::main]: Mutex released.
    6124 1490 04/19 15:08:49 224036 [::main]: Use vss was not set.
    6124 1490 04/19 15:08:49 224036 [::getSubClientDefs]: BACKUP TYPE REQUESTED = 2.
    6124 1490 04/19 15:08:49 224036 No database of the subclient being discovered.
    6124 1490 04/19 15:08:49 224036 CVJobCtrlLog::unregisterProcess(): successfuly removed file [C:\Program Files\CommVault\Simpana\Base\JobControl\6.124]
    6124 1490 04/19 15:08:49 224036 ** CVSession::sendBytes(...) iSocketMember=788 send failed, err=[1][10093][Either the application has not called WSAStartup, or WSAStartup failed.].

    6124 1490 04/19 15:08:49 224036 ** CVSession::sendMessageInt(...):
            - RemoteHost=COMMSERVE.
            - RemoteProcess=AppMgrSvc.exe.
            - sendBytes() failed. Error=9000012.

    6124 1490 04/19 15:08:49 224036 ** CVSession::disconnect (void)
    - RemoteHost=COMMSERVE.
            - RemoteProcess=AppMgrSvc.exe.
            - sendMessageInt CVS_PM_DISCONNECT_REQ failed. Error=9000012.

    4876 1090 04/19 15:08:49 224035 [::main]: Mutex acquired. Continuing...

     

     

  • Re: Exchange DB Backup - Loss of control process extidbbackup.exe
    Posted: 04-19-2012, 10:21 AM

    Are there any issues with your subclient content ? All your storage groups are still assigned in the subclients that you would have expected ?

    The log seems to suggest that even though databases were seen, none match up to this current subclient content which could cause the job to fail

    6124 1490 04/19 15:08:49 224036 No database of the subclient being discovered.


    Wearer of Many Hats
  • Re: Exchange DB Backup - Loss of control process extidbbackup.exe
    Posted: 04-19-2012, 10:33 AM

    Agree with Stephen.

    If you had subclient content which has now disappeared it could be related to the discovery taking longer than our job timeout.

    If this is the case please set the below key on each exchange node to extend the timeout.

    Name: DiscoverWaitTime
    Location: HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\InstanceXXX\MSExchangeDBAgent
    Type: DWORD
    Value: 1200 Seconds


    CommVault Messaging Support
  • Re: Exchange DB Backup - Loss of control process extidbbackup.exe
    Posted: 04-19-2012, 10:41 AM

    Thank you gentlemen - good call

    It seems the content for the 3 subclients had changed - all the content was listed under the default subclient (which is not scheduled to do anything) and my 3 storage group specific subclients were empty - I have now run discovery and changed content back - jobs are running at 15% and moving data so it looks good - will report back with success.

    I am puzzled though as to what might have made this change in content as it was not done manually by me - any ideas?

  • Re: Exchange DB Backup - Loss of control process extidbbackup.exe
    Posted: 04-19-2012, 10:46 AM

    There have been issues in the past where subclient content could be lost in cases where discover took too long to return results. In recent service packs we have made more enhancements to try and prevent this from happening as much as possible.  I see you already have the discover timeout key set so going forward it should not happen again. If it does, you can escalate to support and we can take a look at it


    Wearer of Many Hats
  • Re: Exchange DB Backup - Loss of control process extidbbackup.exe
    Posted: 04-19-2012, 10:47 AM

    Sorry - I meant to say 0 the "DiscoverWaitTime" reg key is already set to 2700 as I previously had a discovery issue

  • Re: Exchange DB Backup - Loss of control process extidbbackup.exe
    Posted: 04-19-2012, 11:42 AM

    Just so you know, you set it to 2700 "HEX", which actually translates to 9984 seconds in decimal

    4876 1090 04/19 15:05:15 224035 [::main]: Set discover wait time to 9984 seconds


    Wearer of Many Hats
  • Re: Exchange DB Backup - Loss of control process extidbbackup.exe
    Posted: 04-19-2012, 11:45 AM

    Thanks Man - I noticed that too and changed it but thanks for pointing it out

     

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy