Bacula-users

[Bacula-users] Over-zealous cancel command

2011-01-03 04:29:26
Subject: [Bacula-users] Over-zealous cancel command
From: Ross Boylan <RossBoylan AT stanfordalumni DOT org>
To: bacula <Bacula-users AT lists.sourceforge DOT net>
Date: Mon, 03 Jan 2011 01:08:33 -0800
Running bconsole for bacula 2.4.4 on Debian Lenny, the cancel command in
bconsole insisted on cancelling something.  It did not let me exit from
the cancel dialog without selecting a job to cancel, and when I hit
enter a few times it cancelled my currently running job (trashing 18
hours of work).  

Is this a bug?

Does anyone care, given the old version?  I notice that 2.4 was still
listed as the production release in some slided from the recent bacula
conference.
Is there a way to exit from the cancel dialog other than ^c?

I gather there is no way to resume the job.

Some comments on the list seem to indicate that even the files that were
backed up will be unrecoverable.  Is that the case?  The backup volumes
were encrypted (by bacula) and on disk.

Below is a log with some # comments added later.

*status dir
# Cyrus job is running and scheduled
corn-dir Version: 2.4.4 (28 December 2008) i486-pc-linux-gnu debian 5.0.7
Daemon started 01-Jan-11 23:37, 3 Jobs run since started.
 Heap: heap=290,816 smbytes=90,675 max_bytes=99,107 bufs=583 max_bufs=607

Scheduled Jobs:
Level          Type     Pri  Scheduled          Name               Volume
===================================================================================
Incremental    Backup    10  02-Jan-11 23:40    LinSysRoot         
Inc2011-01-01_3709
Incremental    Backup    15  02-Jan-11 23:40    LinHome            
Inc2011-01-01_3709
Incremental    Backup    20  02-Jan-11 23:40    LinLocal           
Inc2011-01-01_3709
Incremental    Backup    20  02-Jan-11 23:40    Cyrus              
Inc2011-01-01_3709
Incremental    Backup    40  02-Jan-11 23:40    LinSysVar          
Inc2011-01-01_3709
Full           Backup    99  02-Jan-11 23:42    BackupCatalog      *unknown*
====

Running Jobs:
 JobId Level   Name                       Status
======================================================================
  6589 Full    Cyrus.2011-01-01_23.40.01.05 is running
  6590 Full    LinSysVar.2011-01-01_23.40.01.06 is waiting for higher priority 
jobs to finish
  6591 Full    BackupCatalog.2011-01-01_23.42.00.07 is waiting execution
====
# .....
*cancel
Select Job:
     1: JobId=6589 Job=Cyrus.2011-01-01_23.40.01.05
     2: JobId=6590 Job=LinSysVar.2011-01-01_23.40.01.06
     3: JobId=6591 Job=BackupCatalog.2011-01-01_23.42.00.07
Choose Job to cancel (1-3): 0
Please enter a number between 1 and 3
Choose Job to cancel (1-3):
# There was a very long pause after I hit enter on the previous line.
# I hit the second enter before the following messages or prompts appeared.
Expected a positive integer, got:
# In particular, I hit no keys after the next prompt appeared:
Choose Job to cancel (1-3):
2001 Job Cyrus.2011-01-01_23.40.01.05 marked to be canceled.
3000 Job Cyrus.2011-01-01_23.40.01.05 marked to be canceled.
# notice the first enter lead to a second prompt, while the 2nd enter cancelled 
the running job.
# presumably because it was the first one listed.



Thanks.
Ross Boylan



------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>