Results 1 to 10 of 10

Thread: No incremental for CIFS shares?

  1. #1
    Join Date
    Oct 2011
    Posts
    17

    Default No incremental for CIFS shares?

    Part of my DailySet1 includes several CIFS shares (from a NAS where I can't install the client). It appears these shares don't dump incrementally properly. For example, I am the only person that has access to the "ICT-Vault" share, but I know I did not change anything on that share yesterday; and certainly not 81gb of data. The "TechDept" share also did not have 12gb of data changes.

    Is this expected behavior or is something wrong?

    Code:
    HOSTNAME     DISK        L ORIG-GB  OUT-GB  COMP%  MMM:SS    KB/s MMM:SS    KB/s
    -------------------------- -------------------------------------- --------------
    localhost    -/ICT-Vault 1      81      54   67.5  118:01  8065.0 118:01  8065.2
    localhost    -Multimedia 1       0       0  100.3    1:09   236.8   1:04   253.4
    localhost    -l/TechDept 1      12      10   86.0   23:11  7777.4  23:11  7777.9
    disklist:
    Code:
    localhost	//nas-office-01.natorg.local/ICT-Vault		comp-user-tar	-1	gigenet
    Code:
    define dumptype comp-user-tar {
            auth "bsdtcp"
            holdingdisk auto
            program "GNUTAR"
            index
            comment "user partitions dumped with tar"
            priority medium
            compress client fast
    }
    Code:
    define interface gigenet {
            comment "gigabit local ethernet network; assume lacp bond"
            use 250 mbps
    }

  2. #2
    Join Date
    Nov 2008
    Posts
    20

    Default

    what does the log say? or at least amreport.

    -P

  3. #3
    Join Date
    Oct 2011
    Posts
    17

    Default

    Quote Originally Posted by prelude View Post
    what does the log say? or at least amreport.
    Thanks for your reply
    Which log would be most useful? I'm still not clear on the various log files in /etc/amanda/<poolname>/ and /var/log/amanda/

    Here is amreport:
    Code:
    Hostname: svr-amanda.ftg.nato.com.au
    Org     : My Company Daily Backup
    Config  : DailySet1
    Date    : December 12, 2011
    
    These dumps were to tape DailySet1-4.
    The next tape Amanda expects to use is: DailySet1-5.
    
    
    STATISTICS:
                              Total       Full      Incr.   Level:#
                            --------   --------   --------  --------
    Estimate Time (hrs:min)     0:03
    Run Time (hrs:min)          4:58
    Dump Time (hrs:min)         4:54       0:24       4:30
    Output Size (meg)       142458.9    10974.0   131484.9
    Original Size (meg)     220961.9    14206.3   206755.6
    Avg Compressed Size (%)     64.5       77.2       63.6
    DLEs Dumped                   55         20         35  1:35
    Avg Dump Rate (k/s)       8261.9     7868.7     8296.6
    
    Tape Time (hrs:min)         4:52       0:23       4:29
    Tape Size (meg)         142458.9    10974.0   131484.9
    Tape Used (%)               27.2        2.1       25.1
    DLEs Taped                    55         20         35  1:35
    Parts Taped                   55         20         35  1:35
    Avg Tp Write Rate (k/s)   8331.6     8219.9     8341.1
    
    USAGE BY TAPE:
      Label               Time         Size      %  DLEs Parts
      DailySet1-4         4:52         139G   27.2    55    55
    
    NOTES:
      planner: Full dump of fw2.ftg.nato.com.au:/etc promoted from 2 days ahead.
      planner: Full dump of fw1.ftg.nato.com.au:/etc promoted from 2 days ahead.
      planner: Full dump of backup-mx.nato.com.au:/root promoted from 2 days ahead.
      planner: Full dump of theta.ftg.nato.com.au:/usr/local promoted from 4 days ahead.
      planner: Full dump of svr-edi-tux1.ftg.nato.com.au:/home promoted from 1 day ahead.
      planner: Full dump of theta.ftg.nato.com.au:/etc promoted from 1 day ahead.
      planner: Full dump of epsilon.ftg.nato.com.au:/root promoted from 1 day ahead.
      planner: Full dump of fw1.ftg.nato.com.au:/usr/local promoted from 1 day ahead.
      planner: Full dump of fw2.ftg.nato.com.au:/usr/local promoted from 1 day ahead.
      planner: Full dump of backup-mx.nato.com.au:/home promoted from 1 day ahead.
      planner: Full dump of natorgsvr.natorg.local:merak promoted from 2 days ahead.
      planner: Full dump of svr-addc-01.natorg.local:olde promoted from 2 days ahead.
      planner: Full dump of natorgsvr.natorg.local:adbackup promoted from 4 days ahead.
      planner: Full dump of svr-app-win1.natorg.local:genpro promoted from 4 days ahead.
      taper: Slot 4 with label DailySet1-4 is usable
      taper: tape DailySet1-4 kb 145877946 fm 55 [OK]
      big estimate: svr-app-win1.natorg.local "C:/" 1
                      est: 4G    out 0G
    
    
    DUMP SUMMARY:
                                            DUMPER STATS               TAPER STATS
    HOSTNAME     DISK        L ORIG-GB  OUT-GB  COMP%  MMM:SS    KB/s MMM:SS    KB/s
    -------------------------- -------------------------------------- --------------
    backup-mx.na /etc        1       0       0    6.0    0:00    24.4   0:00    60.0
    backup-mx.na /home       0       0       0   54.7    0:01   228.6   0:02   164.0
    backup-mx.na /root       0       0       0   35.7    0:43   339.3   0:44   334.3
    backup-mx.na /usr/local  1       0       0    4.3    0:00    14.9   0:00    30.0
    backup-mx.na /var/spool  1       0       0    3.3    0:00    10.7   0:00    20.0
    epsilon.ftg. /etc        1       0       0    7.2    0:05     2.7   0:00   130.0
    epsilon.ftg. /home       1       0       0    5.0    0:05     1.6   0:00    70.0
    epsilon.ftg. /root       0       0       0   54.0    0:07  2754.5   0:07  2583.1
    epsilon.ftg. /srv/tftp   0       1       1   98.5    1:58  5805.2   1:58  5788.8
    epsilon.ftg. /usr/local  1       0       0   98.6    0:12  5537.5   0:12  5560.8
    epsilon.ftg. /var/www    1       0       0    6.9    0:05    16.7   0:01    90.0
    fw1.ftg.nato /etc        0       0       0   38.9    0:01  4340.1   0:01  5382.0
    fw1.ftg.nato /home       1       0       0    5.0    0:00    39.1   0:00    20.0
    fw1.ftg.nato /root       1       0       0   23.8    0:00   279.1   0:00   190.0
    fw1.ftg.nato /usr/local  0       0       0   36.1    0:01  2490.7   0:01  1902.0
    fw1.ftg.nato -lib/vnstat 1       0       0   12.5    0:00   158.1   0:00   100.0
    fw2.ftg.nato /etc        0       0       0   33.5    0:01  8100.9   0:01  5437.0
    fw2.ftg.nato /home       1       0       0    3.3    0:00    27.6   0:00    10.0
    fw2.ftg.nato /root       1       0       0   23.3    0:00   223.9   0:00   140.0
    fw2.ftg.nato /usr/local  0       0       0   36.1    0:01  2465.7   0:01  1902.0
    fw2.ftg.nato -lib/vnstat 1       0       0    8.8    0:00   121.1   0:00    70.0
    localhost    -/ICT-Vault 1      81      54   67.5  118:17  8047.2 118:17  8047.0
    localhost    -Multimedia 1       0       0   82.4    1:07    24.2   1:02    26.0
    localhost    -l/TechDept 1      12      10   86.0   23:34  7685.2  23:34  7683.6
    localhost    -cal/Trydel 1       1       1   87.8    1:28  8320.4   1:28  8291.5
    localhost    -/pst-files 1      74      46   61.8  102:36  7764.9 102:35  7766.0
    localhost    -_marketing 0       9       7   80.6   15:57  7749.0  15:56  7754.7
    localhost    /etc        1       0       0   21.0    0:01  2630.0   0:00 14380.0
    localhost    /home       1       0       0    7.3    0:00   127.8   0:00   110.0
    localhost    /root       0       0       0   22.2    0:00   173.2   0:00   200.0
    localhost    /usr/local  1       0       0    5.8    0:05     1.6   0:00    70.0
    natorgsvr.na "F:/"       1       3       0    5.0    3:06   732.4   2:56   772.9
    natorgsvr.na adbackup    0       1       0   39.8    1:25  5546.8   1:15  6280.4
    natorgsvr.na merak       0       0       0   66.7    0:13     0.2   0:02     1.0
    svr-addc-01. "E:/backup" 1       0       0     --    0:14     0.1   0:03     0.3
    svr-addc-01. "-artments" 0       1       1   83.0    0:51 16449.6   0:41 20540.1
    svr-addc-01. "E:/home"   1      20      13   62.5    9:46 22386.8   9:36 22773.8
    svr-addc-01. olde        0       0       0   75.3    0:20  7902.6   0:10 15908.5
    svr-addc-01. oldf        1       0       0   88.0    1:12  1895.9   1:02  2200.2
    svr-addc-01. vision      1       2       0   10.7    1:25  2236.5   1:14  2561.8
    svr-app-win1 "C:/"       1       1       0   45.3    3:10  2277.6   3:00  2403.4
    svr-app-win1 "-/backups" 1       9       4   42.6    3:35 18059.8   3:26 18890.2
    svr-app-win1 "E:/var"    0       1       1   94.7    1:04 17873.4   0:54 21132.7
    svr-app-win1 genpro      0       1       0   60.3    0:42  9941.0   0:31 13317.2
    svr-edi-tux1 /etc        0       0       0   13.4    0:05  1330.7   0:05  1360.8
    svr-edi-tux1 /home       0       0       0   42.3    0:04  2504.8   0:04  2611.5
    svr-edi-tux1 /mnt/backup 1       0       0   99.8    0:13  8774.7   0:13  8554.5
    svr-edi-tux1 /root       1       0       0   21.8    0:00   134.0   0:00   240.0
    svr-edi-tux1 /srv/edi    1       0       0   13.1    0:12  4173.9   0:13  3993.2
    svr-edi-tux1 /usr/local  1       0       0    4.7    0:00    99.4   0:00    70.0
    svr-edi-tux1 -b/rabbitmq 1       0       0    5.0    0:00    41.7   0:00    20.0
    theta.ftg.na /etc        0       0       0   13.0    0:03  1695.6   0:03  1813.7
    theta.ftg.na /home       1       0       0    5.0    0:00    42.2   0:00    20.0
    theta.ftg.na /root       1       0       0   20.7    0:00   413.8   0:08     3.9
    theta.ftg.na /usr/local  0       0       0   35.7    0:11  3851.5   0:11  4011.0
    
    (brought to you by Amanda version 3.3.0)

  4. #4
    Join Date
    Nov 2008
    Posts
    20

    Default

    You can see it says that the full dumps have been promoted from x days ahead. This usually happens due to the algorythms used by amanda. A variaty of parameters play a part in this as far as I understand it. So, incrementals should work but since amanda never uses a tape twice for a different backup it tries to fill it the best it can. It will sometimes promote fulls to keep the daily load of backups equal. In your case, it seems it has decided to make full dumps all the time

    Perhaps you should tune your setup a bit more.

    I am no expert on this but this is what I have found using amanda in the past years.

  5. #5
    Join Date
    Oct 2011
    Posts
    17

    Default

    The only CIFS DLE's are the 'localhost' ones; only 1 of those got promoted, the rest should have been level 1:

    Code:
    localhost    -/ICT-Vault 1      81      54   67.5  118:17  8047.2 118:17  8047.0
    localhost    -Multimedia 1       0       0   82.4    1:07    24.2   1:02    26.0
    localhost    -l/TechDept 1      12      10   86.0   23:34  7685.2  23:34  7683.6
    localhost    -cal/Trydel 1       1       1   87.8    1:28  8320.4   1:28  8291.5
    localhost    -/pst-files 1      74      46   61.8  102:36  7764.9 102:35  7766.0
    localhost    -_marketing 0       9       7   80.6   15:57  7749.0  15:56  7754.7
    The same amount of data is backed up each day from "TechDept" and "ICT-Vault". I am the only person with access to "ICT-Vault" and I do not modify 81gb of files on it everyday! The entire contents of the share adds up to 81gb

    How does the Samba client determine which files have changed? Timestamp? Perhaps there is something the NAS is doing to make it think that everything has changed? Is there a setting that I can change to make it a bit more liberal? (eg, like --modify-window for rsync?)

  6. #6
    Join Date
    Nov 2008
    Posts
    20

    Default

    Hmm,

    I must admit I do not do much with cifs. There should be a planner file in the logs which reports a few things. Perhaps therein lies the answer.

    -P

  7. #7
    Join Date
    Oct 2011
    Posts
    17

    Default

    Looks OK there as best I can tell...

    Code:
    OPTIONS features=ffffffff9efefbffffffffff0f;maxdumps=1;hostname=localhost;config=DailySet1;
    
    (...trim...)
    
    <dle>
      <program>GNUTAR</program>
      <estimate>CLIENT </estimate>
      <disk>//nas-office-01.mydomain.local/ICT-Vault</disk>
      <level>0<server>YES</server></level>
      <level>1<server>YES</server></level>
      <spindle>-1</spindle>
      <auth>bsdtcp</auth>
      <compress>FAST</compress>
      <record>YES</record>
      <index>YES</index>
      <datapath>AMANDA</datapath>
    </dle>

  8. #8
    Join Date
    Oct 2011
    Posts
    17

    Default

    Doh....! I think I've found the problem:
    Quote Originally Posted by http://wiki.zmanda.com/index.php/Backup_client_(old)#Instructions_for_using_Samba
    A user must be created on the PC with full access rights (read/write) to the share. Amanda, via the Samba server, will connect to the PC via this user. If the user does not have full access, incremental backups will not work and the whole share will be backed up every time (the archive bits are never reset).
    I will see tonight....

  9. #9
    Join Date
    Nov 2008
    Posts
    20

    Default

    Ah

    yes, I was kinda asuming that had been the case. After all, if you cannot write how would you restore a file?

    Oke, let us know.

    -P

  10. #10
    Join Date
    Oct 2011
    Posts
    17

    Default

    Quote Originally Posted by prelude View Post
    yes, I was kinda asuming that had been the case. After all, if you cannot write how would you restore a file?
    Well I don't like to restore to original location anyway; I prefer to restore to a temp location then copy/paste what I want manually

    Of course, my vtape partition filled up overnight, and for some reason amanda still refuses to use my holding disk (Issue 1: [url]http://forums.zmanda.com/showthread.php?t=3939[/url]) so backups failed... Will try running a manual one this morning now Iv'e cleared up some space.

Posting Permissions

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