Post reply

Old SQL 6.5 Server Not Backing Up

  • January 4, 2006 at 8:08 pm

    #111593

    Greetings people,

    I have a question that I need to throw open to the masses.

    I'm trying to migrate away from an old SQL server and then update it on a new machine.

    To facilitate this, I need to backup the databases in question. Easy you might say. I shall continue.

    The hard drive on the server is almost full so I can't back it up locally. I need to back it up to a network drive. It keeps failing with an operating system error=null.

    I've checked permissions and even started the services as Administrator for the domain with the same result.

    No access denied errors or anything.

    When I do a drive list in backup devices, there is no F: drive (which is the mapped drive on another machine) only C: and D:. I can type in the mapped drive manually but it won't have a bar of it....same message appears.

    I'm hoping there's something I'm missing and the situation is not that you CAN'T back up to a network drive.

    Any suggestions pls?

    Thanks,

    Lloyd.

  • January 6, 2006 at 4:03 am

    #613148

    Hi Lloyd,

    Oh dear, old technology eh? I've had this problem myself in the dim and distant, this was it :

    http://groups.google.co.uk/group/microsoft.public.sqlserver.datawarehouse/browse_thread/thread/87b66eec639cae0a/c3f619f71ea3e9cd?lnk=st&q=sql+server+7.0+backup+to+network&rnum=2&hl=en#c3f619f71ea3e9cd

     

    HTH

    Rich

  • January 6, 2006 at 12:24 pm

    #613372

    That referenced discussion is pretty good information.

    We also did something similar way back when ... using UNC targets specified with dump devices (as opposed to files). You definitely need a domain type account to run SQL Server and it has to have access to the UNC share and file structure within it. This will necessitate a stop/restart of SQL server once the UNC and security is set up. We also used mapped drives and dump devices as well.

    You do have to be wary of network stability. If you do not have a robust network backbone your database backups may fail or appear to complete but be corrupt (you won't know until you try to restore them). Additionally, network performance will also be a factor as well.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • January 6, 2006 at 1:25 pm

    #613382

    Ideally, you'd want to backup but if you can't get that working, and you're at wits end, you might consider detaching the databases and copying the mdf and ldf files out to the new machine and reattaching to another v6.5 sql server db. It may be too much if you're dealing with alot of databases though.

    Just a thought.

     

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply