Results 1 to 4 of 4

Thread: amrecover: empty disk after succesfully dump

  1. #1
    Join Date
    Jul 2013
    Posts
    12

    Default amrecover: empty disk after succesfully dump

    Hi,

    My amanda server has 2 configurations: Mysql and Services. Both do regular dumps without reporting any issue, but when I recover files from them, Services is working nice, but MySQL only works for 1 of defined clients.

    Code:
    $ amcheck MySQL
    Amanda Tape Server Host Check
    -----------------------------
    Searching for label 'MySQL-11':found in slot 11: volume 'MySQL-11'
    Will write to volume 'MySQL-11' in slot 11.
    NOTE: skipping tape-writable test
    Server check took 0.222 seconds
    
    Amanda Backup Client Hosts Check
    --------------------------------
    Client check: 5 hosts checked in 2.436 seconds.  0 problems found.
    
    (brought to you by Amanda 3.3.4)

    This is the mail I get:

    Code:
    Hostname: SERVER
    Org     : MySQL
    Config  : MySQL
    Date    : November 6, 2013
    
    These dumps were to tapes MySQL-6, MySQL-7.
    The next 2 tapes Amanda expects to use are: MySQL-8, MySQL-9.
    
    
    STATISTICS:
                              Total       Full      Incr.   Level:#
                            --------   --------   --------  --------
    Estimate Time (hrs:min)     0:00
    Run Time (hrs:min)          0:16
    Dump Time (hrs:min)         0:15       0:15       0:00
    Output Size (meg)        15562.6    15562.6        0.0
    Original Size (meg)      16844.5    16844.5        0.0
    Avg Compressed Size (%)     92.4       92.4        0.0
    DLEs Dumped                    5          1          4  1:4
    Avg Dump Rate (k/s)      17199.3    17202.7        0.0
    
    Tape Time (hrs:min)         0:15       0:15       0:00
    Tape Size (meg)          15562.6    15562.6        0.0
    Tape Used (%)              126.6      126.6        0.0
    DLEs Taped                     5          1          4  1:4
    Parts Taped                    6          2          4  1:4
    Avg Tp Write Rate (k/s)  17146.7    17154.1        0.0
    
    USAGE BY TAPE:
      Label               Time         Size      %  DLEs Parts
      MySQL-6             0:12       12288M  100.0     5     5
      MySQL-7             0:03        3275M   26.7     0     1
    
    NOTES:
      planner: Last full dump of CLIENT1:mysql_02 on tape MySQL-1 overwritten in 5 runs.
      planner: Last full dump of CLIENT2:mysql_3 on tape MySQL-11 overwritten in 2 runs.
      planner: Last full dump of CLIENT3:mysql_4 on tape MySQL-11 overwritten in 2 runs.
      planner: Last full dump of CLIENT4:mysql_5 on tape MySQL-11 overwritten in 2 runs.
      planner: Full dump of CLIENT5:mysql_01 promoted from 7 days ahead.
      taper: tape MySQL-6 kb 12582592 fm 5 [OK]
      taper: tape MySQL-7 kb 3353535 fm 1 [OK]
    
    
    DUMP SUMMARY:
                                                                  DUMPER STATS    TAPER STATS
    HOSTNAME                DISK        L ORIG-MB  OUT-MB  COMP%  MMM:SS    KB/s MMM:SS    KB/s
    ------------------------------------- ---------------------- --------------- --------------
    CLIENT1   mysql_4     1       0       0   10.0    0:00    22.0   0:00     0.0
    CLIENT2   mysql_5     1       0       0   10.0    0:00    20.6   0:00     0.0
    CLIENT3   mysql_3     1       0       0   10.0    0:00    21.9   0:00     0.0
    CLIENT4  mysql_01    0   16844   15563   92.4   15:26 17202.7  15:29 17154.1
    CLIENT5  mysql_02    1       0       0   10.0    0:00    22.0   0:00     0.0
    
    (brought to you by Amanda version 3.3.4)
    As you can see, only CLIENT4 reports data transfers....

    when I run amrecover on it:

    Code:
    amrecover> listdisk
    200- List of disk for host CLIENT4
    201- mysql_01
    200 List of disk for host CLIENT4
    amrecover> setdisk mysql_01
    200 Disk set to mysql_01.
    amrecover> ls
    2013-11-06-14-27-36 CLIENT4.131106
    2013-11-06-14-27-36 CLIENT4.131105
    2013-11-06-14-27-36 .
    amrecover>

    but if I run amrecover in other clients:

    Code:
    amrecover> listdisk
    200- List of disk for host CLIENT5
    201- mysql_02
    200 List of disk for host CLIENT5
    amrecover> setdisk mysql_02
    200 Disk set to mysql_02.
    amrecover> ls
    2013-11-06-14-42-48 .
    amrecover>
    but the most strange thing is that the server has info about those clients!!

    Code:
    $ amadmin MySQL findCLIENT5 mysql_02 
    
    date                host                    disk     lv tape or file file part status
    2013-11-06 11:58:26 CLIENT5 mysql_02  1 MySQL-11        1  1/1 OK 
    2013-11-06 12:13:46 CLIENT5 mysql_02  1 MySQL-13        1  1/1 OK 
    2013-11-06 12:35:27 CLIENT5 mysql_02  1 MySQL-15        2  1/1 OK 
    2013-11-06 12:50:35 CLIENT5 mysql_02  1 MySQL-1         4  1/1 OK 
    2013-11-06 13:05:50 CLIENT5 mysql_02  1 MySQL-3         1  1/1 OK 
    2013-11-06 13:19:15 CLIENT5 mysql_02  1 MySQL-4         1  1/1 OK 
    2013-11-06 14:07:54 CLIENT5 mysql_02  1 MySQL-6         1  1/1 OK 
    2013-11-06 14:27:36 CLIENT5 mysql_02  1 MySQL-8         2  1/1 OK 
    2013-11-06 14:42:48 CLIENT5 mysql_02  1 MySQL-10        1  1/1 OK

    So, why some client's can't see its dumps if amanda have them?

    TIA,
    Arnau

  2. #2
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    Your backup report it backed up 0MB, that's what you get on restore, nothing.

    The level 1 backup is empty, that's OK if nothing changed.

    Where is the full backup? (level 0)
    You don't have full backup, you should add more tapes (and increase tapecycle) or reduce the dumpcycle.
    Force a full backup with amadmin

  3. #3
    Join Date
    Jul 2013
    Posts
    12

    Default

    Hello martineau,

    well, I've "playing" with disk/slots, I've removed half of them and increased the size per slot.
    dumpcycle 7 days
    runspercycle 7
    tapecycle 16 tapes

    then I ran amdump several times to force the full backup. From the first mail I got:

    [...]
    Last full dump of CLIENT1:mysql_02 on tape MySQL-1 overwritten in 5 runs.
    [...]


    So I ran amdump 5 times, but I did not get the full dump.

    Ok, I'll force the full dump with amadin.
    Thank a lot

    *BTW, I'm moving to zamnda so I'll stop using this mysql amanda dump, ubt I wanted to understand the source of the problem.

  4. #4
    Join Date
    Jul 2013
    Posts
    12

    Default

    I did force the the full backup and now everything is ok.

    thanks lot!
    Arnau

Posting Permissions

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