cancel
Showing results for 
Search instead for 
Did you mean: 

backing up remote SQL Server

diomedes
Not applicable
I have recently upgraded from version 9 to 11 and am having some issues.
 
I have 3 Servers I backup;
 
1.  Backup Exec Host Server / SQL 2000
2.  Windows 2003 File Server with SAN
3.  MS 2000 SQL Enterprise Server
 
now using the Remote Agents I can back up the to disk SQL back on the SQL server but not the database it just gives me this in the log;
 

Errors
Click an error below to locate it in the job log
Backup- serenity.internal.lbs.local Database \Axapta3 was not found, or could not be accessed.
Database \AxaptaHelpDesk was not found, or could not be accessed.
Database \CreditClaim was not found, or could not be accessed.
Database \HelpDesk was not found, or could not be accessed.
Database \LangsHelpDesk was not found, or could not be accessed.
Database \master was not found, or could not be accessed.
Database \model was not found, or could not be accessed.
Database \msdb was not found, or could not be accessed.
Database \pubs was not found, or could not be accessed.
Database \QuotesRegister was not found, or could not be accessed.
Database \TestAxapta3 was not found, or could not be accessed.
Database \WHS was not found, or could not be accessed.

Exceptions
Click an exception below to locate it in the job log
Backup- serenity.internal.lbs.localV-79-57344-34110 - AOFO: Initialization failure on: "serenity.internal.lbs.local". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
SQL Prepare for Freeze failed for snapshot.
Backup- serenity.internal.lbs.local The item serenity.internal.lbs.local\Axapta3 in use - skipped.
The item serenity.internal.lbs.local\AxaptaHelpDesk in use - skipped.
The item serenity.internal.lbs.local\CreditClaim in use - skipped.
The item serenity.internal.lbs.local\HelpDesk in use - skipped.
The item serenity.internal.lbs.local\LangsHelpDesk in use - skipped.
The item serenity.internal.lbs.local\master in use - skipped.
The item serenity.internal.lbs.local\model in use - skipped.
The item serenity.internal.lbs.local\msdb in use - skipped.
The item serenity.internal.lbs.local\pubs in use - skipped.
The item serenity.internal.lbs.local\QuotesRegister in use - skipped.
The item serenity.internal.lbs.local\TestAxapta3 in use - skipped.
The item serenity.internal.lbs.local\WHS in use - skipped.

However the backup of the I do every lunch time as a SQL to disk backup works fine from this machine;

AOFO: Started for resource: "\\SERENITY.internal.lbs.local\F:". Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP).
AOFO: Symantec Volume Snapshot Provider (VSP) snapshot cache file settings for volume "F:" : Initial: 0 MB. Maximum: 42965 MB. File: "\\?\Volume{46ad2542-0e79-40d1-b71f-41f54995d402}\Backup Exec AOFO Store\_BEVspCacheFile_0.VSP".
AOFO: Symantec Volume Snapshot Provider (VSP) snapshot settings used: Quiet Time: 5 seconds. Time Out: 2000 seconds.
Network control connection is established between 10.10.1.8:2268 <--> 10.10.1.13:10000
Network data connection is established between    10.10.1.8:2272 <--> 10.10.1.13:2603

Set Information - \\SERENITY.internal.lbs.local\F: SQL Data
Backup Set Information
Family Name: "Media created 20/12/2006 7:48:18 PM"
Backup of "\\SERENITY.internal.lbs.local\F: SQL Data"
Backup set #26 on storage media #1
Backup set description: "Langs Daily"
Backup Method: Full - Back Up Files - Reset Archive Bit

Backup started on 5/04/2007 at 12:37:13 AM.
Backup completed on 5/04/2007 at 12:49:50 AM.

I've tried it with AOFO on and off and stil get no joy..

Thinking that the MS SQL 2000 server doesn't like the remote agent service or something, as all the disk based backups are working remotely just fine, and the local SQL server i backup on the backup exec machine also works fine.

really need a solution to this as the remote sql server is our main data set and of extreme importance, kind of losing sleep now.

 

 

 

 

2 REPLIES 2

Greg_Meister
Level 6
On both the Backup Exec and the SQL servers, follow these steps:
 
- Open Regedit
- Navigate to HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Engine\NTFS
- Select "Restrict Anonymous Support" key in right-hand pane
- Modify data value from 0 to 1. If already 1 leave as is.
- Close Regedit
- Cycle all Backup Exec services on media server, Remote Agent service only on SQL server.
 
After these staps are complete, create a new test job to back up a single database from that server. I'd recommend a new job to make sure that there is no possibility of a corrupt job or selection list causing a problem.
 
Regards,
Greg

Cameron_Eldri1
Level 2
I am getting exactly the same problem, however when i look at those registry entries they are already set to 1. Is there any other things to try?