Koozali.org formerly Contribs.org

Affa initial Backup

Affa initial Backup
« on: August 08, 2013, 11:44:06 AM »
Hi

We have recently upgrade our 2TB backup USB drive with a 3TB drive but we are running into some issues.

With our previous change of backup disk (1tb to 2tb) when we initiated the affa backup it did a full backup of the system and file were after it continued with the normal updates for the files that just changed. This is not the case anymore and i cant see any change in the below configuration which would stop affa from doing the initial backup?

Can i ask if someone can check and let me know if they see anything wrong?

# EDIT THIS:
my %job=(
        'remoteHostName'=>'localhost', # FQHN or IP address
        'TimeSchedule'=>'2300', # HHMM,HHMM,...
        'Description'=>'affabackup', # text string.
        'scheduledKeep'=>1, # integer >= 1
        'dailyKeep'=>7, # integer >= 1
        'weeklyKeep'=>4,# integer >= 1
        'monthlyKeep'=>12,# integer >= 1
        'yearlyKeep'=>2,# integer >= 1
        'SMEServer'=>'yes', # yes | no
        'Include[0]'=>'', # additional files or directories to include
        #'Include[1]'=>'',
        #'Include[2]'=>'',
        'Exclude[0]'=>'', # files or directories to exclude from backup
        #'Exclude[1]'=>'',
        #'Exclude[2]'=>'',
        'RPMCheck'=>'no', # yes | no
        'DiskSpaceWarn'=>'risky', # strict | normal | risky | none
        'localNice'=>0, # -19...+19
        'remoteNice'=>0, # -19...+19
        'Watchdog'=>'yes', # yes | no
        'sshPort'=>22, # default ssh port is 22
        'ConnectionCheckTimeout'=>120, # seconds
        'rsyncTimeout'=>900, # seconds
        'rsyncCompress'=>'no', # yes | no
        'EmailAddresses'=>'bnotify@tagsa.co.za', # name@domain.com,name@domain.com,...
        'chattyOnSuccess'=>999, # send N success notifications
        'postJobCommand'=>'', # full path to local program/script
        'preJobCommand'=>'', # full path to local program/script
        'AutomountDevice'=>'/dev/sdc1', # Device to auto mount (e.g. USB drive)
        'AutomountPoint'=>'/mnt/affadevice', # the mountpoint for AutomountDevice
        'AutomountOptions'=>'', # Optionstring passed to mount command e.g. '-t cifs'
        'AutoUnmount'=>'yes', # umount if fs was not mounted before Affa ran
        'RootDir'=>'/mnt/affadevice', # where to save the archives.Don't use /root or /home/e-smith
        'SambaShare'=>'yes',
        'Debug'=>'no', # yes | no
        'status'=>'enabled', # enabled | disabled
        'rsync--inplace'=>'yes', # yes | no : rsync on source supports '--inplace' option
        'rsync--modify-window'=>0, # integer >= 0, timestamp window
        );

### nothing to edit below this line ####

Kind regards

Re: Affa initial Backup
« Reply #1 on: August 08, 2013, 12:03:12 PM »
Check filesystem on both USB-disks if there are any differences.

Quote
fdisk -l /dev/sdc

...

Re: Affa initial Backup
« Reply #2 on: August 08, 2013, 12:21:10 PM »
below is the fdisk feedback i receive from the 3TB drive:

[root@netkeeper ~]# fdisk -l /dev/sdc
Note: sector size is 4096 (not 512)

WARNING: The size of this disk is 3.0 TB (3000592982016 bytes).
DOS partition table format can not be used on drives for volumes
larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID
partition table format (GPT).


Disk /dev/sdc: 3000.5 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 45600 cylinders
Units = cylinders of 16065 * 4096 = 65802240 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1       45601  2930265088   83  Linux


For the 2TB i dont have the Sector size is 4096 (not 512) warning but the rest it the same. File system is ext3.

Let me know if you need more information.

PS: the backup is stating but only initiating the incremental backup and not the full backup as its suppose to with nothing else on the disk.

Re: Affa initial Backup
« Reply #3 on: August 08, 2013, 12:37:25 PM »
Let me know if you need more information.

PS: the backup is stating but only initiating the incremental backup and not the full backup as its suppose to with nothing else on the disk.

Is the incremental not in fact a full backup as the incremental from nothing is, yep, a full backup?
...

Re: Affa initial Backup
« Reply #4 on: August 08, 2013, 01:05:06 PM »
Is the incremental not in fact a full backup as the incremental from nothing is, yep, a full backup?

The size of the first backup doesnt not come close to the actual size of the system being backed up. My system size at the moment with all file which needs to be backed up is >1.6TB. The initial back is only 7.6GB. Also if i view the files not everything is there.

Re: Affa initial Backup
« Reply #5 on: August 08, 2013, 07:20:24 PM »
will anyone be able to assist with this - from all the forums i have seen i cant find any were were spomething similar has happened or were it was replicated.

Offline janet

  • ****
  • 4,812
Re: Affa initial Backup
« Reply #6 on: August 08, 2013, 07:39:44 PM »
derekb

Quote
The size of the first backup doesnt not come close to the actual size of the system being backed up. My system size at the moment with all file which needs to be backed up is >1.6TB. The initial back is only 7.6GB. Also if i view the files not everything is there.

What folder name is on the backup disk ?
Is it a scheduled.running or similar ?
If so that means affa has not yet finished the full backup due to timeout, & will continue the first full backup on the next scheduled run.
Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Re: Affa initial Backup
« Reply #7 on: August 08, 2013, 09:08:04 PM »
hi janet

thank you for the reply.

the issue is that no matter what happens this is the status after multiple disk tried, etc. the backup just never passes the 7.6gb.

I have left this previously for a week without any luck


Re: Affa initial Backup
« Reply #8 on: August 08, 2013, 09:38:30 PM »
Well, then it is time to turn on the debug I presume? I remember mine choked on lots of AVI files. These are now excluded.

Ref: http://forums.contribs.org/index.php/topic,49303.msg246043.html#msg246043

Also I remember similar behaviour with a !new! broken USB disk, it started to time-out during writing.

Write test it with badblocks.
« Last Edit: August 08, 2013, 09:53:31 PM by elmarconi »
...

Offline janet

  • ****
  • 4,812
Re: Affa initial Backup
« Reply #9 on: August 08, 2013, 10:34:44 PM »
derekb

Quote
the issue is that no matter what happens this is the status after multiple disk tried, etc. the backup just never passes the 7.6gb.
I have left this previously for a week without any luck

Well that's why I am asking for precise answers, not just a generalised "it does not work after a week" type answers.
If you want proper help with diagnosis, then please answer the question accurately

Manually mount the drive using the mount command & then look at the created backup.
What folder name is on the backup disk ?
Is it a scheduled.running or similar ?

Do a
ls -al
to show us what is there.

Also look in the affa log files to see what has exactly happened with the backup, post appropriate parts here for analysis.
« Last Edit: August 08, 2013, 10:37:16 PM by janet »
Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Re: Affa initial Backup
« Reply #10 on: August 08, 2013, 11:23:52 PM »
Hi Janet

Sorry, i though my reply did say that the file created is scheduled.running. so to answer your questions as below:

What folder name is on the backup disk ? The initial folder name is the job name for my backup ("ext_backup")
Is it a scheduled.running or similar ? yes this is the case and is the only folder i the ext_backup directory. Within the directory there is though some files "backed up"/"folders created".

At the moment i have reverted as all the other forum are indicating that the issue lies wit the 4096 sector size on the disk. I have finally created a guid partition with gdisk but i'm having some issue formatting it to ext2/3/4.