how to take DataBase Backup from remote server to local system

  • hi..

    i want to take the DB Backup from the

    remote server to the local system..

    i'm using sql server2008 enterprise edition and the remote server is sql server2008 express

    how to do it..

    please help me...

  • on local machine create shared folder with full permissions..

    on remote server take backup

    example

    backup database model to disk ='\\localmachinename\shared_foldername\model.bak'

  • Other Option: use this tool, it will store a fresh BAK file from a remote database to your local harddisk: https://www.fida.org/gc.aspx?p=1001&p1=7

  • This was removed by the editor as SPAM

  • mail4olek - Tuesday, March 13, 2018 7:35 AM

    To perform remote backups isn't a reliable backup method...

    Not sure what you mean there.  While I don't like doing it, if you mean having one machine invoke the backups on a different machine, I've not seen a problem unless the "Central" machine that invokes the backup goes down (single point of failure that will cause all hell to break loose on the log files of the machines that aren't being backed up.

    For each machine to have an autonomous backup system to a central but remote repository, I've never had a problem and, yes, I do a nightly restore on the two most important (1.4 TB total) databases with no problems either with performance or reliability.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • This was removed by the editor as SPAM

  • mail4olek - Wednesday, March 14, 2018 8:31 AM

    The main issue with remote SQL servers is that you can run SQL scripts, including BACKUP DATABASE command, but accessing the resulting *.bak file is problematic. The *.bak file is placed somewhere on the drive local to that SQL server. And if you don’t access to that location, you can not copy the backup file for further processing like compression, encryption, storage, etc. Then your options are limited to creating a script file.

    Well how remote are you talking about?  If SQL Server can run a BACKUP to a location it should be able to run a RESTORE from that location, unless something changes with regards to location in between the two.

  • mail4olek - Wednesday, March 14, 2018 8:31 AM

    The main issue with remote SQL servers is that you can run SQL scripts, including BACKUP DATABASE command, but accessing the resulting *.bak file is problematic. The *.bak file is placed somewhere on the drive local to that SQL server. And if you don’t access to that location, you can not copy the backup file for further processing like compression, encryption, storage, etc. Then your options are limited to creating a script file.

    No... I don't backup to the local server.  Not ever.  It's a death sentence if the machine hurls before you can copy the *.bak file off it.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 8 posts - 1 through 7 (of 7 total)

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