ERROR CODE [62:1247]: Encountered network error while talking to the SIDB engine.

Last post 12-04-2012, 8:32 AM by Jason.L. 3 replies.
Sort Posts: Previous Next
  • ERROR CODE [62:1247]: Encountered network error while talking to the SIDB engine.
    Posted: 11-19-2012, 9:00 AM

    My full backup took 3 days (normally only takes 2). My full backups for Data Written is roughly 20+ GB on average, but this weekend it was 767GB Data Written.

    I do not see anything that indicates a network issues occurred but it was telling me "Encountered network error while talking to the SIDB engine."

    Any ideas?

  • Re: ERROR CODE [62:1247]: Encountered network error while talking to the SIDB engine.
    Posted: 11-19-2012, 10:12 AM

    Good morning,

    It would probably be best to open a call with the Support Hotline to have this investigated further.  There could be a few reasons for this and it may be an issue with the current store.

    JW

  • Re: ERROR CODE [62:1247]: Encountered network error while talking to the SIDB engine.
    Posted: 11-19-2012, 10:16 AM

    Not canon but I have seen this message crop up when the SIDB engine server is very busy especially when there are a number of SIDB2.EXE instances running. We normally only have 4 as max but occasionally when stores have been sealed this can cause extra processes to be run.


    R D Roberts
    Server Team - Technical Lead
    Gwynedd Council
  • Re: ERROR CODE [62:1247]: Encountered network error while talking to the SIDB engine.
    Posted: 12-04-2012, 8:32 AM

    The problem with this was from me upgrading from version 8.0 a few months back to version 9.0. The deduplication stores were still using the old format. Apparently you have to create a secondary copy, seal old stores, then make secondary copies primary once again. The single instance database doesn't "upgrade" and still uses the old deduplication format which from what I'm gathering the old and dated format of deduplication. I got the errors because with the newer version of clients (that were recently updated), the SIBDB goes slow with the old deduplication format using the newer 9.0 clients.  

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