Results 1 to 4 of 4

Thread: BackUps

  1. #1
    Join Date
    Feb 2004
    Location
    Alpine Califormia
    Posts
    1,789

    Unanswered: BackUps

    I am trying to learn as much as possible about backups, and not just book knowledge but the actual on the job experience. I dont handle backups here, our IT guys do they use Backup Exec. So what i want to do is practice on our test server (which where I basically live anyways) I want to back it up, then drop table or just kinda thrash it then have to restore it. I'm going to get started on that, I learn best buy reading then doing. Any suggestion would be appreciated

    One of our database has moderate use (which I have a dup of on the test server)

    I would like to back it up

    what would you guys suggest?
    Last edited by desireemm; 08-26-08 at 20:16.

  2. #2
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    My suggestion:

    1) Backup an existing database. Dev, prod, or other as you see fit.
    2) Restore that backup into a playground area
    3) Backup the playground
    4) Clobber something important in the playground
    5) Verify the important thing is clobbered in the playground
    6) Backup the clobbered playground (yeah, sounds weird)
    7) Restore the playground backup from step 3
    8) Verify that the important thing is no longer clobbered in the playground
    9) Restore the clobbered backup from step 6
    10) Verify that the important thing is again clobbered.
    11) Restore the backup from step 1
    12) Verify that the important thing is nifty again.

    This process takes you through several steps, around a couple of kinks that can occur in the backup/restore cycle, and gives you a chance to work with them all in an environment where if you fry the whole mess all you are out is your playground. I'll leave you to experiment, discover the kinks, and work through them. This is a good learning exercise, and it RARELY if ever goes without several hitches for an inexperienced DBA.

    -PatP

  3. #3
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    To expand a little on what Pat has said, you can try substituting differential or log backups in the later steps. As an advanced exercise, you can do the one FULL backup at the start, do a few updates, table creates/drops, stored procedure creations/updates all separated by a couple minutes, of course, then see if you can restore from the log to a point in between each action.

  4. #4
    Join Date
    Feb 2004
    Location
    Alpine Califormia
    Posts
    1,789
    Quote Originally Posted by Pat Phelan
    My suggestion:

    1) Backup an existing database. Dev, prod, or other as you see fit.
    2) Restore that backup into a playground area
    3) Backup the playground
    4) Clobber something important in the playground
    5) Verify the important thing is clobbered in the playground
    6) Backup the clobbered playground (yeah, sounds weird)
    7) Restore the playground backup from step 3
    8) Verify that the important thing is no longer clobbered in the playground
    9) Restore the clobbered backup from step 6
    10) Verify that the important thing is again clobbered.
    11) Restore the backup from step 1
    12) Verify that the important thing is nifty again.

    This process takes you through several steps, around a couple of kinks that can occur in the backup/restore cycle, and gives you a chance to work with them all in an environment where if you fry the whole mess all you are out is your playground. I'll leave you to experiment, discover the kinks, and work through them. This is a good learning exercise, and it RARELY if ever goes without several hitches for an inexperienced DBA.

    -PatP

    Thank you Pat
    will do

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •