Can anyone suggest a plan with backup full and backup log without backup diff ?

  • I need only one backup full at mid night, and one backup log each hour, It works ?

    How should I do?

  • Yes it works, differential backups are optional and are there for a convenience factor when you have loads of logs to restore really as it makes the restoration process easier.

    How to do it, that will depend how you are taking backups.  Native backups, Maintenance Plans, Ola, MinionWare, 3rd party (CommVault/Veritas etc)

    You just need to configure the right settings and schedules that you need to fulfil the requirements.

  • In addition to @Ant-Green's excellent answer, after you get the backups working, practice doing restores. Do a full restore, then do point in time restores with the logs. Make sure you know how the restores work. That's even more important than taking the backups in the first place.

    "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

  • You could also use it as a learning opportunity by doing the research and then writing your own.

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

  • As a bit of a sidebar, I do nightly fulls and, depending on the server, transaction log backups er 15 to 30 minutes with a twist... I don't backup the log files unless something changed.  In other words, if the logfile recycle reason is "Nothing", I don't back it up.

    --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 5 posts - 1 through 4 (of 4 total)

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