Quantcast
Channel: Symantec Connect - Backup and Recovery - 讨论
Viewing all articles
Browse latest Browse all 6482

Backup Exec 2012 SP2 Deduplication Store goes offline

$
0
0
我需要解决方案

Hello,

The Deduplication Store goes offline in Backup Exec 2012 SP2 Hotfix 209149 after the queue of transaction logs are being processed in J:\DedupStore\queue. Following entries are logged in storaged.log:

October 18 00:42:34 INFO [00000000136EA3C0]: Sleeping for 5 minutes because queue processing failed for 4 times.
October 18 00:47:34 WARNING [00000000136EA3C0]: 25036: Connection to crdb was severed (connection reset by peer). Attempting to reconnect to localhost:10085
October 18 00:47:36 ERR [00000000136EA3C0]: 25036: Connection reset to crdb at localhost:10085 failed (could not connect to server: Connection refused (0x0000274D/10061)
    Is the server running on host "localhost" and accepting
    TCP/IP connections on port 10085?
)
October 18 00:47:36 ERR [00000000136EA3C0]: 25004: Database query failed.
Query      : SELECT value FROM counters WHERE name = '%s'
Called by  : pqCounterSelectCompatible
Reason     : could not connect to server: Connection refused (0x0000274D/10061)
    Is the server running on host "localhost" and accepting
    TCP/IP connections on port 10085?
October 18 00:47:36 ERR [00000000136EA3C0]: 25004: Could not retrieve the value of counter "tlogid": unknown error
October 18 00:47:36 ERR [00000000136EA3C0]: 25004: Queue processing failed five times in a row. Queue processing will be disabled and the CR will no longer accept new backup data. Content router has been totally shut down. Please contact support immediately!
October 18 00:47:37 CRIT [00000000136EA3C0]: 25004: Content router has been totally shut down. Please contact support immediately!

Initially during queue processing the PostgreSQL Server 8.3 stoppes what explains the "Database query failed" error. After 5 attemps of processing the queue the Backup Exec Deduplication Engine Service stoppes as well by producing the error message "Content router has been totally shut down".

The steps given below didn't solve the problem:

  • Rebooting the server
  • Deleting Deduplication Store in Backup Exec and adding a new one with the old data
  • Starting PostgreSQL manually after stopped state
  • Pausing/Disabling Dedup Store

Backing up and restoring works fine as long the Deduplication Store doesn't go offline. The PostgreSQL Server 8.3 and Backup Exec Deduplication Engine Services can be started manually what brings the Deduplication Store online again.

Thank you for you help.

 


Viewing all articles
Browse latest Browse all 6482

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>