Server to server backup

  • 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

  • - 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

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - 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

  • 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.

  • 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.

  • 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

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - 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

  • 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.

  • 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

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - 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

  • 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.

  • 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.

  • you first install Magic Backup[/url], 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

Viewing 10 posts - 1 through 9 (of 9 total)

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