Chris_Pofahl
Level 2
Joined 20 years ago
User Profile
User Widgets
Contributions
Re: B2D Failures
Well, this issue was solved. I had to increas the amount of concurrent operations to the B2D folder. Also, the way you mention adding B2D folders is not right, it works,but not right. You should be creating B2D folders by UNC.By creating by shares the job will run from the remote server to the to the management station then to the B2D. By configuring it by UNC it goes straight to the B2D.371Views0likes0CommentsB2D Failures
Hello, I am trying to run duplicate jobs, first run the job to my Wondows 2003 Apliance Server( or NAS). I am able to successfully complete a differential job of 1 server that is approx 3 GB in size, but when I try and run my Full Backup which consists of about 12 servers and 400GB of data it fails. The error message I get is: "Storage device "servername" reported an error on a request to write data to media. Error reported: The specified network name is no longer available. V-79-57344-34036 - An unknown error has occurred. I have looked this up and the solution was to use a domain logon account to run the job,but I already am using a domain admin account to run the job. The B2D folder is not directly attatched to my Media Server, I have the B2D folders mapped using UNC. The properties of my folders are: Max size for B2D files: 10GB Max # of backup Sets: 100 Device settings: Auto Concurrent Operations Allow: 1371Views0likes3Comments