Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server 2000 backup on network device Expand / Collapse
Author
Message
Posted Wednesday, March 24, 2004 2:48 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, December 23, 2004 3:45 AM
Points: 2, Visits: 1

I've tried to do a backup of some databases from SQL Server 2000 on network share on File server under MS Windows Server 2003. I've changed the account for MS SQL Server Agent to be a domain user account, added the network device with sp_addumpdevice stored proc., put it in built-in Sysadmin group, gave all necessary permissions according to BOL and MSDN and got nothing at all!

Does anybody know the solution for this problem?

Milan

 




Post #107894
Posted Wednesday, March 24, 2004 6:18 AM
SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: Moderators
Last Login: Wednesday, March 26, 2014 3:38 PM
Points: 8,369, Visits: 732
What error is it giving and however are you creating your backups?


Post #107933
Posted Wednesday, March 24, 2004 7:13 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, December 23, 2004 3:45 AM
Points: 2, Visits: 1

I used a mapped network drive from File Server as drive F: on SQL Server machine, then added that mapped drive F: as Backup network device using stored procedure sp_addumpdevice. After that, from Enterprise Manager I tried to backup database Master using backup device 'F':.

I've got error message MS SQL-DMO (ODBC SQL State: 42000) - Cannot open backup device 'asnetwork'. Device error or device off-line. See the SQL Server error log for more details.

BACKUP DATABASE is terminating abnormaly.

In error log I've found next:

BackupDiskFile::Create Media:Backup device 'F:\asbckp.bak' failed to create. Operating system error = 5 (error not fpund).

I've also tried to manage without network mappings, using simple file path to the network share on File Server as a backup device, but with similar results.

 

 




Post #107949
Posted Wednesday, March 24, 2004 8:41 AM
SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: Moderators
Last Login: Wednesday, March 26, 2014 3:38 PM
Points: 8,369, Visits: 732

Try using the UNC path instead as the F mapped drive will not be visible to SQL Agent only the logged in user at the time the map is created.

'\\server\drive$\path\filename.bak'




Post #107974
Posted Thursday, March 25, 2004 2:08 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 26, 2004 5:59 AM
Points: 1, Visits: 1

Hi,

I know it's possible because someone ask me for the same thing in a long time.

With SLQ server 2000 I've enabled a specific option...but I'm sorry I don't remember the syntax of the command.

I think it was something like : "trace flag" + a specific number.

Did you look in Microsoft KB ? I've found that :KB827452

Regards,

CCzzz

 

Post #108155
Posted Thursday, March 25, 2004 1:50 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, April 27, 2009 2:59 PM
Points: 342, Visits: 68
yes use a UNC share.  The server you are backing up to - is that on the same domain as the DB server.  Is your SQL Server running under a domain account?  If your SQL Server is running under a domain user account and the server that you are backing up to is on the same domain, then you should be good.  If the server you are backing up to is not on the domain,  then you can create a local account with the same username/pw as the account SQL server is running in and give the account the neccesaary permissions on that server and it should work fine. 


Post #108292
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse