Post reply

Best way to safeguard tables? - Newbie

  • June 23, 2003 at 4:30 pm

    #159369

    Is this the best way to safeguard my tables?

    I recently converted from Access to SQL Server. Well the frontend is still Access but the tables are SQL Server with ODBC.

    So I have to make sure the tables are backed up. They are not very big but they are important.

    I created a Maintenance Plan which runs a complete backup of database and transaction files at 10:00 PM and creates files in a separate directory on the local drive.

    This directory is then backed up on tape with normal backup at 11:00 PM. I don't have a backup program which can directly backup SQL server

    Any suggestions would be great.

    TIA-TOMG

  • June 23, 2003 at 9:39 pm

    #462723

    Yo

    Maintenance plans are the way to go if your new to it all, they are simple and you cant go wrong.

    Do a FULL each night on all databases.

    Do you require point in time recovery? (apply a full back and restore to a defined point in the day?), then your database recovery model should be full or bulk-logged and create a maintenance plan to backup the databases logs each hour or something like that.

    If you dont require PTR, the set a "simple" recory model for your db.

    As you have done, backup this dir to tape, and in the maintenance plan, check the option to remove files older than N days.

    Dont alter the system databases recovery models.

    Backup to disk, then use another product to backup to tape.

    Cheers

    Ck

    Chris Kempster

    http://www.chriskempster.com

    Author of "SQL Server 2k for the Oracle DBA"


    Chris Kempster
    www.chriskempster.com
    Author of "SQL Server Backup, Recovery & Troubleshooting"
    Author of "SQL Server 2k for the Oracle DBA"

  • June 25, 2003 at 9:24 pm

    #463163

    and I recommend testing a restore of one or all of your user databases. The full process, from retrieving the backup off tape to doing the sql restore from that retrieved file. You can restore to another (test/dev) sql server, or - being very careful - restore under another database name on the same server. However, I recommend the former.


    Cheers,
    - Mark

Viewing 3 posts - 1 through 2 (of 2 total)

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