Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Backups
»
Server to server backup
Server to server backup
Rate Topic
Display Mode
Topic Options
Author
Message
parthi-1705
parthi-1705
Posted Saturday, November 21, 2009 12:01 AM
Mr or Mrs. 500
Group: General Forum Members
Last Login: Wednesday, December 26, 2012 11:03 PM
Points: 586,
Visits: 2,195
Server-A it is in My home
Server-B it is in another home
they both are connected to the N/W
is it is possible for me to take the backup of server-B(another home) and place it in my server-A (my home) through the maintenance Plan back up from My server-A(My home)
Both are SQL 2005
Microsoft SQL Server 2005 - 9.00.1399.06 (Build 3790: Service Pack 1)
Thanks
Parthi
Thanks
Parthi
Post #822853
ALZDBA
ALZDBA
Posted Saturday, November 21, 2009 2:17 PM
SSCertifiable
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 2:17 AM
Points: 6,862,
Visits: 8,049
- if the service account of the source server has write authority at the target servers backup location, you can initiate the backup to that location without a problem, or create a local backup and xcopy / robocopy it to the target servers backup folder. (last one is how I would prefer)
- if the service account of the target server have auth to read the .bak file on the source location, you can initiate the restore without a problem.
Johan
Jul 13
Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere
-
How to post Performance Problems
-
How to post data/code to get the best help
-
How to prevent a sore throat after hours of presenting ppt ?
"press F1 for solution", "press
shift
+F1 for urgent solution"
Need a bit of Powershell? How about
this
Who am I ?
Sometimes this is me
but
most of the time this is me
Post #822940
Atul DBA
Atul DBA
Posted Monday, November 23, 2009 6:18 AM
SSC Eights!
Group: General Forum Members
Last Login: Wednesday, September 19, 2012 12:43 PM
Points: 806,
Visits: 412
Adding to the point, if you can make shared drive on servers which can be accessed by each others, then you can save the Backup files to shared drive by providing the full network name of servers along with Shared Folder name. You can even map the shared drive for better access.
Post #823214
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Monday, November 23, 2009 8:22 AM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 3:30 PM
Points: 31,436,
Visits: 13,751
Keep in mind that when you connect to B, the backup is made local to B, meaning from the drives that the service account on B can see.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #823284
ALZDBA
ALZDBA
Posted Monday, November 23, 2009 11:31 AM
SSCertifiable
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 2:17 AM
Points: 6,862,
Visits: 8,049
I would stick to using the UNC path so any investigating DBA will immediately recognize the backup is being taken at the other physical location.
backup yourdb to disk="\\theotherserver\abackupshare$\yourdbFULL.bak"
Johan
Jul 13
Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere
-
How to post Performance Problems
-
How to post data/code to get the best help
-
How to prevent a sore throat after hours of presenting ppt ?
"press F1 for solution", "press
shift
+F1 for urgent solution"
Need a bit of Powershell? How about
this
Who am I ?
Sometimes this is me
but
most of the time this is me
Post #823428
Atul DBA
Atul DBA
Posted Tuesday, November 24, 2009 1:33 AM
SSC Eights!
Group: General Forum Members
Last Login: Wednesday, September 19, 2012 12:43 PM
Points: 806,
Visits: 412
I disagree with Stev. We can take the backup to other disk if they are accessible by SQL Server resource list.
This is highly possible in stand alone servers. But yes, it is difficult to do in cluster environment due to nature of arctitecture.
Post #823723
ALZDBA
ALZDBA
Posted Tuesday, November 24, 2009 2:16 AM
SSCertifiable
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 2:17 AM
Points: 6,862,
Visits: 8,049
Atul DBA (11/24/2009)
I disagree with Stev. We can take the backup to other disk if they are accessible by SQL Server resource list.
This is highly possible in stand alone servers. But yes, it is difficult to do in cluster environment due to nature of arctitecture.
hmm ... that is not quit correct ...
IMO Steve has been refering to server B as just another server, regardless if clustered or not.
Accessable is meanth as "Having the authority granted to read/write on that location".
Once again, regardless if clustered or not.
Best practise for clustered instances:
create an extra fileshare resource in your resource group and use that in your (remote) backup statements.
But indeed, using a backup location on a clustered environment can be an issue if during a backup failover occurs (because of the (minimal) 30sec unavailability during failover).
Johan
Jul 13
Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere
-
How to post Performance Problems
-
How to post data/code to get the best help
-
How to prevent a sore throat after hours of presenting ppt ?
"press F1 for solution", "press
shift
+F1 for urgent solution"
Need a bit of Powershell? How about
this
Who am I ?
Sometimes this is me
but
most of the time this is me
Post #823733
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Tuesday, November 24, 2009 7:30 AM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 3:30 PM
Points: 31,436,
Visits: 13,751
The backup is always made from the instance, so it goes to drives that are visible from that instance. Local might have been a poor choice of words, but it doesn't matter if you are clustered or not. Only those drives/paths that the instance can see are where the backup goes.
It does not matter from where you originate the backup. Meaning that if you can see the ServerX/PathA from your workstation, but the server service account cannot see it, you cannot run a backup to that location.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #823871
briogene
briogene
Posted Tuesday, February 02, 2010 12:17 AM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, December 13, 2012 2:19 AM
Points: 36,
Visits: 190
How big is the data involved?
You can use Replication to Copy the data from Server A to Server B and perform a normal back up on server B.
This is just a suggestion. If you decide to give it a try....i would suggest you go for merge replication.
Post #857750
matdamn01
matdamn01
Posted Friday, February 05, 2010 3:21 AM
Forum Newbie
Group: General Forum Members
Last Login: Friday, February 05, 2010 3:17 AM
Points: 1,
Visits: 0
you first install
Magic Backup
, it may take from several hours to several days to make the initial copies of your files. This time will depend on the number and size of the files you need backed up, and on the speed of your Internet connection. Remember that Magic Backup operates silently in the background to perform all of its work, and won't interfere with the normal use of your computer.
Once this "initial backup" of your files is complete, Magic Backup will monitor all of your files and backup only the changes and new files that you create. New and changed files will start being backed up 10 minutes after they stop changing. Once a file is backed up, that same file won't be backed up again for 24 hours. This ensures that you always have the most recent versions of your files backed up
Post #860282
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.