Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Backup failed
#1
Exclamation 
please help, I can't backup both auto and manual.

Log:
Auto backup starting: folder=D:\VUZE Backups
Writing to D:\VUZE Backups\2017-02-12
Syncing current state
Reading configuration data from C:\Users\Royal\AppData\Roaming\Azureus
Copying '.certs' ...144.2 kB
Copying '.keystore' ...32 B
Copying 'active' ...2742 files, 112.50 MB
Copying 'azureus.config' ...475.3 kB
Copying 'azureus.config.bak' ...475.3 kB
Copying 'azureus.statistics' ...309 B
Copying 'azureus.statistics.bak' ...309 B
Copying 'banips.config' ...371 B
Copying 'banips.config.bak' ...264 B
Copying 'custom' ...88 B
Copying 'debug.zip' ...114.6 kB
Copying 'devices' ...0 B
Copying 'devices.config' ...44.4 kB
Copying 'devices.config.bak' ...44.4 kB
Copying 'dht' ...6 files, 1.1 kB
Copying 'dlarchive' ...0 B
Copying 'dlhistorya.config' ...273.6 kB
Copying 'dlhistorya.config.bak' ...273.6 kB
Copying 'dlhistoryd.config' ...60.3 kB
Copying 'dlhistoryd.config.bak' ...59.2 kB
Copying 'downloads.config' ...768.0 kB
Copying 'downloads.config.bak' ...768.0 kB
Copying 'exported_params.properties' ...399 B
Copying 'filters.config' ...12 B
Copying 'ipfilter.cache' ...0 B
Copying 'java.vmoptions' ...20 B
Copying 'java.vmoptions.bak' ...10 B
Copying 'java.vmoptions.lastgood' ...20 B
Copying 'metasearch.config' ...6.3 kB
Copying 'metasearch.config.bak' ...6.3 kB
Copying 'net' ...10 files, 210.0 kB
Copying 'plugins' ...420 files, 97.52 MB
Copying 'rcm.config' ...152.6 kB
Copying 'rcm.config.bak' ...152.5 kB
Copying 'rcmx.config' ...543 B
Copying 'rcmx.config.bak' ...533 B
Copying 'rss' ...0 B
Copying 'shares' ...0 B
Copying 'sharing.config' ...15 B
Copying 'sharing.config.bak' ...242 B
Copying 'sidebarauto.config' ...651 B
Copying 'sidebarauto.config.bak' ...651 B
Copying 'stats' ...Auto backup failed
Backup Failed: Failed to copy file 'C:\Users\Royal\AppData\Roaming\Azureus\stats\2016\04\05.dat'




java.lang.Exception: Failed to copy file 'C:\Users\Royal\AppData\Roaming\Azureus\stats\2016\04\05.dat'
    at com.aelitis.azureus.core.backup.impl.BackupManagerImpl.copyFilesSupport(BackupManagerImpl.java:658)
    at com.aelitis.azureus.core.backup.impl.BackupManagerImpl.copyFilesSupport(BackupManagerImpl.java:620)
    at com.aelitis.azureus.core.backup.impl.BackupManagerImpl.copyFilesSupport(BackupManagerImpl.java:620)
    at com.aelitis.azureus.core.backup.impl.BackupManagerImpl.copyFilesSupport(BackupManagerImpl.java:620)
    at com.aelitis.azureus.core.backup.impl.BackupManagerImpl.copyFiles(BackupManagerImpl.java:586)
    at com.aelitis.azureus.core.backup.impl.BackupManagerImpl.backupSupport(BackupManagerImpl.java:866)
    at com.aelitis.azureus.core.backup.impl.BackupManagerImpl.access$600(BackupManagerImpl.java:70)
    at com.aelitis.azureus.core.backup.impl.BackupManagerImpl$7.runSupport(BackupManagerImpl.java:555)
    at org.gudy.azureus2.core3.util.AsyncDispatcher$1.run(AsyncDispatcher.java:160)
    at org.gudy.azureus2.core3.util.AEThread2$threadWrapper.run(AEThread2.java:294)

Please tell me how to fix this.

Many thanks,
Reply
#2
I had a similar problem.  Try update to the latest Java and, assuming you are running on a 64 bit machine, make sure you have a 64 bit version of Java installed.

Also make sure you have ownership of the file that cannot be copied.
Reply
#3
if I delete this "05.dat" file from 'C:\Users\Royal\AppData\Roaming\Azureus\stats\2016\04\05.dat' what will happen.

 
it seems like that only file"05.dat" cause the the problem of the whole backup failed.


if I do that will vuze crash beyond repair and I will have to re-install the whole thing?
what is that 05.dat file are for?
Reply
#4
Frankly, I do not know what data is within that file, but here is a suggestion: why not rename it and try running the program?  Sometimes Vuze will recreate various files and sometimes not.  In any case, you do not have to delete it, just rename it to 05.bak .  See what happens.  BTW, if you do not know, you will probably not be able to rename it with Vuze active or open, so close it first.  You can always return it to its original name if it screws the pooch. :)

Would you please confirm for me that you have permission to access the file in the security properties of the file?
Reply
#5
LuvVuze\ dateline='\'1486990541' Wrote: Frankly, I do not know what data is within that file, but here is a suggestion: why not rename it and try running the program?  Sometimes Vuze will recreate various files and sometimes not.  In any case, you do not have to delete it, just rename it to 05.bak .  See what happens.  BTW, if you do not know, you will probably not be able to rename it with Vuze active or open, so close it first.  You can always return it to its original name if it screws the pooch. :)

Would you please confirm for me that you have permission to access the file in the security properties of the file?

 

Yes I have permission to access the file in the security properties



 I try to delete the 05.dat file, but my pc freeze on just clicking at the file. So it can't be rename because I can't even just click at the file. maybe it's better to reinstall vuze and try to delete that 05.dat file again
Reply
#6
I do not have the same issue with renaming 05.dat, so it would seem that either you have a system problem (your computer or OS), which is beyond the limits of this forum, or you have a corrupted Vuze install.

Reinstall may be your easiest and best option.  Also look into a free program called "Take Ownership", which will assure you have full access to anything you want.
Reply
#7
(03-05-2017, 08:32 AM)'LuvVuze' Wrote: I do not have the same issue with renaming 05.dat, so it would seem that either you have a system problem (your computer or OS), which is beyond the limits of this forum, or you have a corrupted Vuze install.

Reinstall may be your easiest and best option.  Also look into a free program called "Take Ownership", which will assure you have full access to anything you want.

 



I found the problem, the file was written on the bad sector of my Hdd ( or in the way that location of the file 05.dat was gone to bad sector )

this explained the freeze that happend when I click at the 05.dat file

so I have 2 options:

the first one is try to fix the bad sector by using a program, but what I did was formated the drive and re partition the drive that the 05.dat was located in (whish is drive C:Windows) and reinstall the whole thing (windows and vuze) and just go with the latest backup that works ( have set a backup up to 3 backups in my vuze setting)

Now Vuze is working fine like before and no backup failed popup any more

Many Thanks to LuvVuze for reply and  help me with the problem,
Cheers
Reply
#8
So happy to hear!  Never thought it was an issue with Vuze :)
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Magnet links "Failed" which work in other clients coyote2 3 1,767 02-14-2017, 11:01 AM
Last Post: parg
  Failed to establish listen on port 9091 Flinxxx 1 1,164 02-05-2017, 04:46 PM
Last Post: Flinxxx



Users browsing this thread: 1 Guest(s)