ADSM-L

Re: 2 SQL backup questions

1999-04-29 14:36:40
Subject: Re: 2 SQL backup questions
From: Del Hoobler <hoobler AT US.IBM DOT COM>
Date: Thu, 29 Apr 1999 14:36:40 -0400
Jeff,

Yes. The databases CAN be active when a backup is taken
using the ADSM SQL Agent.  (You couldn't do this with the
base ADSM client.) The SQL Server itself manages this.
To give you some ideas on your questions...


1. The SQL Agent uses the standard SQL backup interface
   as described in the Microsoft SQL manuals.
   Here is some info I obtained from the SQL 7.0 books:
   ==============================================================
   Creating and Applying Transaction Log Backups:
   ----------------------------------------------
   Backing up the transaction log periodically to create a
   sequence of transaction log backups offers users the most
   flexibility in restoring databases. By creating transaction
   log backups, a database can be restored to any point in time
   contained within the sequence of transaction logs, right up
   to the point of failure.

   When creating a transaction log backup, the starting point
   of the backup is where:
     o The previous transaction log backup ended (if a transaction
       log backup has been created).
     o The transaction log backed up as part of the most
       recent database or differential database backup ended,
       if no previous transaction log backup was created.
       (A database or differential database backup contains a
        copy of the active space of the transaction log.)
   ===============================================================
   So, changes made AFTER the backup starts will NOT be part of the
   transaction log that is backed up but part of the next
   transaction log backup.

   I don't want to repeat the entire SQL 7.0 documentation here...
   ...so please look at it to get very detailed information on this.
   Microsoft does a nice job explaining it.

2. SQL 7.0 is a little different in the way that they always have
   separate transaction logs.  So, using the ADSM SQL Agent, you
   should run a "/BACKUPFULL" followed by a "/BACKUPINCR"
   to get the latest snapshot of the database you are backing up.

I hope this helps a little and gets you started...

---------------------------------------------------------------------------
-----
-----
Thanks,
Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM ADSM Agent Development
hoobler AT us.ibm DOT com

=================================================
> Hi,
> We are using the SQL Connect Agent (1.1.1a) to back up databases that
> reside on SQL Server 6.5 and 7.0.  There are two devices for each user
> database, one for data, one for the transaction log.  We are performing a
> full backup of the each database and log every night (using the
/BACKUPFULL
> command line switch).  It is possible for users to be active in the
> databases while they are being backed up.  I'm trying to get an answer to
> the following questions:
>
> 1) How much of the transaction log is backed up?  Is it the contents of
the
> log at the start of the backup process?  Assuming that transactions are
> being started and/or committed during the backup process, will the log
> entries created be included in the backup?
>
> 2) Does the version of SQL Server being backed up affect the answer to
the
> above questions?  If so, how?
>
> Other relavant info(?):  ADSM Server -  NT 4, SP3, ADSM 3.1.1.3
>                SQL Servers - NT 4, SP3
>
> Any and all info is greatly appreciated.
>
> Thanks,
>
> Jeff Heather
> Network Technology Specialist
> International Data Group
<Prev in Thread] Current Thread [Next in Thread>