July 22, 2011 at 9:31 am
I've had a bunch of errors on several of our databases. It's been suggested to stop copying off to a different server and instead copy locally and then move the .bak afterward. I already have the backup job so I assume I just need to add another Step in the job. What is the exact line to put into the Step 2? I see people just say to use xcopy or robocopy or something else is suggested but I don't know what the exact line(s) to put into the second step of the backup job.
July 22, 2011 at 11:40 am
When you say copy - do you really mean backup? It isn't clear what you are referencing...
If you are having performance or network issues trying to backup across the network, the recommendation is to backup locally - then copy the backup file (bak) to the network location. To do that, change the backup step to use local storage instead of network - and add a second step to perform the copy.
How you copy is up to you - but I would recommend using Robocopy myself. What the command will be again is up to you - based on what your requirements are.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
July 22, 2011 at 11:49 am
That's going to be my plan; to backup up locally and then copy it off.
I don't know what the actual command line should look like.
I open the backup job, go to Steps, put in a Step name, change Type to Operating system, but I'm not sure of the syntax to put in there.
July 22, 2011 at 12:48 pm
You have a few different options. You can write a VBScript or powershell script to move it, use the move DOS command, or put a third part utility like robocopy on the server and call that. The exact syntax is going to depend on how you decide to do the move.
August 2, 2011 at 11:10 am
We have same issue long back because of network load and we implemented same process which you are going to implement.."Backup Db Locally and Copy Backup file to different server".
we use different tool for running jobs in Production and Test but below is command which you need to add as step-2 in your SQL job.
Type :- Operating System(CmdExec)
Run as :- need permission for both folder
Command :-COPY \\MyServer\D$\MyDB.bak \\YourServer\D$\MyDB.bak
I hope this does helps you..:-)
August 3, 2011 at 6:48 am
Thank you, that's what I was looking for (felt like i was talking to someone in sales). I wasn't sure if i could use basic DOS commands in that window or had to be a type of SQL.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply