Barracuda Backup doesn’t work

Situation: The client create a Barracuda backup job on a new server. It doesn’t work with this error:

Errors

———————————–

    System State

    Filesystem

  -=[ Files ]=-

  Duration:    August 28 2021 10:36PM to 10:36PM CDT for —

  Items:

  Backup Size: 0 bytes at —

  Scan Rate:   0 items at < 1 item/sec

Troubleshooting 1: on the new server, check the Network under File Explorer. We find the problem is Network discovery is turned off.

Graphical user interface, text, application, email Description automatically generated

Turning network Discovery on fixes the problem.

Troubleshooting 2:

Please turn off, restart, and start these services in the order presented, making sure of the correct startup type where listed. As this is a template, it is not likely that all services will be listed on any given server. If the service is not there, just move to the next. 

STOP 
########### 
Volume Shadow Copy (Set to manual startup type) 
Microsoft Software Shadow Copy Provider (Set to automatic startup type) 
SQL Server VSS Writer (if present) 
Microsoft Exchange Information Store (if present) 
HyperV Virtual Machine Management (if present) 
Barracuda backup agent 

Background Intelligent Transfer Service

RESTART 
############ 
Cryptographic Services 
COM + Event Systems 

START 
########### 
Volume Shadow Copy 
Microsoft Software Shadow Copy Provider 
SQL Server VSS Writer (if present) 
Microsoft Exchange Information Store (if present) 
HyperV Virtual Machine Management (if present) 
Barracuda backup agent – MAKE SURE TO START LAST

Background Intelligent Transfer Service

Published by

Bob Lin

Bob Lin, Chicagotech-MVP, MCSE & CNE Data recovery, Windows OS Recovery, Networking, and Computer Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com

One thought on “Barracuda Backup doesn’t work”

  1. If the Background Intelligent Transfer Service is failure or don’t start, there are a number of different things that can lead to the error, timing being one of them. Below there are a number of action items to review on the server experiencing the issues. In my experience, working through these eventually leads to a stable system without BITS failures. Please review and let me know if you have any questions.

    1. First, ensure all writers are stable by reviewing with vssadmin list writers in an Admin level command prompt and restarting any necessary service.

    2. Check the event logs for Event ID 513, Cryptographic Services failure, and apply the fix from the following link.
    https://docs.microsoft.com/en-us/troubleshoot/windows-server/backup-and-storage/event-id-513-vss-windows-server

    3. Check for an event in the Application Event log with the message ‘Open Procedure for BITS failed’ and if present, run through the following steps to reset the performance counters.
    https://www.admin-enclave.com/en/articles/windows/306-resolved-the-open-procedure-for-service-bits-in-dll-c-windows-system32-bitsperf-dll-failed-performance-data-for-this-service-will-not-be-available-the-first-four-bytes-dword-of-the-data-section-contains-the-error-code.html

    4. Verify there are no Windows Updates, or other Windows based data replication services running at the time of our backups. That can cause windows to lock BITS causing this error.

    5. Use the built in Windows BITS Troubleshooter to see if the OS can determine why the service is not performing correctly.

    6. Make sure the Background Intelligent Transfer Service is set to ‘automatic’ in services.msc

    7. Finally if none of that helps resolve the issue, you may need to re-register the writer. The following link has more information on that.
    http://woshub.com/vss-writer-failed-re-registering-vss-writers-windows-server/

Leave a Reply