Obsolete Releases > SME 8.x Contribs
affa makes no hardlinks
adlaw:
Hi,
I'm backuping one SME with affa (smeserver-affa-2.0.0-rc5) on a NFS share on a Linux Mint station (Mint 13 Maya, based on ubuntu 12.04 Precise Pangolin). But the problem is that affa doen't makes hardlinks, and the backup disk is quicly full as everyday all files are copied. And as I have almost 100 G of data, the backup takes a very long time !
I'm surprised, because I have another SME where affa is backuping on FreeNAS (NFS share also), and it's working well...
Here is the affa job config :
--- Code: ---# db affa show
AffaGlobalDisable=no
DefaultAffaConfig=default
sendStatus=weekly
status=enabled
baksme=job
AutoUnmount=yes
AutomountDevice=192.168.1.53:/mnt/BAKSME/affa
AutomountOptions=-t nfs -o nolock
AutomountPoint=/var/affadevice
ConnectionCheckTimeout=120
Debug=yes
Description=SME backup on local station
DiskSpaceWarn=strict
EmailAddresses=admin@mydomain.local
Exclude[0]=
Include[0]=
RPMCheck=no
RetryAfter=600
RetryAttempts=3
RetryNotification=yes
RootDir=/var/affadevice
SMEServer=yes
SambaShare=no
TimeSchedule=2030
Watchdog=yes
chattyOnSuccess=0
dailyKeep=1
doneDaily=2013199
doneMonthly=201304
doneWeekly=201328
doneYearly=2013
localNice=0
monthlyKeep=0
postJobCommand=
preJobCommand=
remoteHostName=localhost
remoteNice=0
rsync--inplace=yes
rsync--modify-window=3600
rsyncCompress=no
rsyncTimeout=900
scheduledKeep=1
sshPort=22
status=enabled
weeklyKeep=1
yearlyKeep=0
--- End code ---
Where could be the problem ?
Stefano:
maybe a different NFS settings on the target machine?
adlaw:
Hi Stefano,
Thank you for this so fast reply :-)
Yes, maybe some NFS settings. I'll re-read the man, but I think that I already did and I don't see which setting could prevent affa to make the harlinks... Any idea ?
Stefano:
yes.. take a look in the affa's logs ;-)
adlaw:
Ooops ! I thought it was a problem with NFS only, as I recently changed the backup station. Affa seems to make correctly the backups if we except the hardlinks... But in fact, in the logs I have failed chown on each file ! (why affa is not sending a mail to warn about this ?)
The newly created folder with job name is owned by nobody:nogroup, with 755 rights. But it has been created by affa, and the rights of the parent folder are 777...
How must I do so that affa creates the folder with the good rights and owner ? Is it a problem with affa settings, or NFS settings ?
Navigation
[0] Message Index
[#] Next page
Go to full version