only aborted which occurs when the fail over occured. All other databases as
of the job were backed up. That does not affected at all.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
>
> A job that is running will be aborted and not be re-scheduled to run
> immediately again. It will run at the next scheduled time.
>
> A Maintenance plan does submit backups to be run in parallel, so you were
> just lucky that 9/10 had completed already.
>
> Regards
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program:
http://www.microsoft.com/mvp >
> Blog:
http://www.msmvps.com/epprecht/ >
> "Siva Prasad [SIVA]" <SivaPrasadSIVA@discussions.microsoft.com> wrote in
> message news:12D631E9-F26C-4A70-8D0E-E1AEEF5F44B9@microsoft.com...
> > My question is :
> > What would happen to the jobs which are running,while failover occurs?
> >
> > I have a Active \ Passive SQL Server 2000 EE SP3a with Hotfix MS03-031 on
> > Windows 2003 Enterprise Edition.
> >
> > When I testesd the Fail over from the Primary node (Node1) to Secondary
> Node
> > (Node2) there was a backup job running.
> >
> > The backup job created using using 'database Maintenance plan which
> backups
> > all the user database. There are 10 databases to backup.
> >
> > The thing is that when the database1 being backed up the "FAIL OVER"
> happend
> > and SQL Server failed over to Node2.
> >
> > When I checked on the 'Job History' there was no entry at all for this
> job.
> >
> > But the database backup except to the database2 (i,e during the time fail
> > over happened) all the databases were backed up.
> >
> > The strange thing is there was no entry on 'Backup job history' at all for
> > the job ran.
> > There are entries in NT event viewer log.
> >
> > Can anyone explain on How SQL Server would handle the Jobs which are
> running
> > while the fail over is happening?
>
>
