Copy Backup to DVD

  • Hi,How can I automate copying Last Backup to DVD using SQL Server Job.

    Regards

  • alnawrass2002 (1/5/2014)


    Hi,How can I automate copying Last Backup to DVD using SQL Server Job.

    Regards

    Schedule the manual process that you're currently doing using Windows Scheduler.

    As a bit of a sidebar, I think that backing up to DVD will lead to a real world of hurt in the future. I strongly recommend that you invest in a quality tape system.

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

  • If the process you're currently using has a command line, try using PowerShell. You can fire a powershell command right from SQL Agent.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Or maybe a SQL scheduled job that backs up the DB to a local drive, then step 2 runs a batch file to copy to DVD ??

  • Thanks a lot all participates

    I Think its easy to follow the last technique which is dividing the process to two parts copy to local hard disk then copy to DVD using scheduled patch file

  • alnawrass2002 (1/5/2014)


    Hi,How can I automate copying Last Backup to DVD using SQL Server Job.

    Regards

    DVD copy with an automated job sounds like more than a world of hurt. You cannot copy to a DVD as if it was another hard drive; it requires a burning program. It also requires manual intervention to insert a new disk or to handle a backup larger than the DVD. A SQL job can be made to run a command line program, but this sounds like the incorrect approach.

    Either invest in cloud backup (carbonite, iDrive, etc. -- which requires no SQL job to grab and save your backup file, but has size considerations based on bandwidth) or as Jeff said a good tape drive, which will likely come with a serviceable backup agent that you schedule outside SQL Server.

    Thanks

    John.

Viewing 6 posts - 1 through 5 (of 5 total)

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