Jump to content

boskovuk

Members
  • Content count

    21
  • Joined

  • Last visited

Community Reputation

0 Neutral

About boskovuk

  • Rank
    Occasional Forum Poster
  1. boskovuk

    networked storage - not able to backup?

    quick update: The actual backup finally started (after 4-5 days of 'scanning' phase). Apparently, the whole 'scan' phase took really long (don't know why). Well, it has been 30+ hours as Retrospect has been backing up 155 GB of data. This is the backup status at the moment: - completed 62.1GB - remaining 93.8 GB I see that the backup side fluctuates a lot. At certain times it drops below 1 MB/min. I am willing to wait until this backup execution is completed (to see the results from this backup requests). Would any of above symptoms sound familiar to anybody, so we get better understanding of the low performance?
  2. boskovuk

    networked storage - not able to backup?

    3,5 days gone and this backup is still running ("One execution running ...") Actually, I spent some time now to look at the number of files, etc. and noticed that Retrospect Backup process is still 'scanning' the networked drive. It keeps slowly increasing the number of scanned files. The current status report looks like this: Remaining: 382815 files 153.4 GB Completed: 0 files zero KB I just obtained (Windows) properties of the (network) folder: 393947 files 155 GB This definitely looks like Retrospect is still in a scanning mode. I hope it will finally start backing up the data soon (probably sometime tonight). I will report back with the results. I am still puzzled with this delay and slow scanning speed. This is my first attempt to backup the folder on the networked drive. Previous successful backup requests were only against USB attached external hard disks.
  3. boskovuk

    networked storage - not able to backup?

    I would like to attach the image of my Backup request - not sure how to do this? My repeat attempts to backup the networked drive are not going through. It's been ~3 days now, 'One execution running ...' still! Remaining: 348359 files 150.7 GB Completed: 0 files zero KB Any suggestion on fixing this show-stopper?
  4. This is the environment where Retrospect runs: - Windows XP - Retrospect 7.6.123 (including all latest hot fixes) - networked drive DNS-323 with total of ~1TB of available space: http://www.dlink.com/products/?pid=509 This space is networked, i.e. connected to our LAN (the router box). The Retrospect is trying to snapshot about 155GB of space for the backing up purposes. However, it is not able to pass 125GB mark (it has been running now more than 24 hours). This is the first time I am trying to work within this environment (with DNS-323 networked storage). Previously, this Retrospect version was successfully backing up to/from USB connected external hard drive unites. Am I missing something here? Why is this not working? Any advice or pointer will be appreciated?
  5. boskovuk

    can't write, error -1128 (path too long)

    When this fix/update to this 7.6 bug will be happening - what is current estimated time?
  6. boskovuk

    error 1128 (path too long)

    Robin, would you be able to submit this request/report/feedback to the development team so they (hopefully) include this fix in upcoming patch releases?
  7. boskovuk

    error 1128 (path too long)

    Robin, Your latest suggestion (uncheck the problem folders so they don't get restored) seems to be working. As you can expect, the problem is the 'restore' will stop every time the underlying condition is detected and Retrospect with error 1128. question: It seems to me that you guys perfectly understand the cause of the problem and you could easily confirm if an individual file will fail Retrospect restore request. I am puzzled why Retrospect stores these problematic files if you know that these files will stop 'Retrospect restore' action and trigger error 1128? The proper way to handle this condition would be not to store these into the backup sets at all, since these individual objects are not retrievable (regardless of who is to blame, Windows or Retrospect). Does the above makes sense? ???
  8. boskovuk

    error 1128 (path too long)

    Mayoff, thanks for repeated replies and guidance. I understand, these files will need to be individually retrieved. However, I have more important issue to deal with. I don't know how to force Retrospect to proceed with the retrieval process. It stops once 'error 1128' condition is detected. I still have ~80GB of data to be retrieved from Retrospect backup files. Please, advise. TIA.
  9. boskovuk

    error 1128 (path too long)

    Hmmm, it seems we are not on the same page (you don't see what I see). The file(s) that is crashing Retrospect retrieval process existed at this location: "F:\bosko\download_instalacije\hard disks\Seagate Barracuda 7200.10 250GB 7200 16MB ATA-100 EIDE (Oct 2006)\Seagate Barracuda 7200.10 250GB 7200 16MB ATA-100 EIDE\Seagate Barracuda 7200.10 250GB 7200 16MB ATA-100 EIDE OEM Hard Drive ST3250620A in Canada at TigerDirect.ca.mht" That was within Windows environment. The Retrospect is instructed to retrieve this toward the same box (Windows based), where it existed before. Are we sure that the error is caused by Windows and not by some internal Retrospect problems/bugs? :eyes:
  10. boskovuk

    error 1128 (path too long)

    Additionally, I am confused with: "...Windows will not allow files to be written into a path longer then 245 characters ..." The above doesn't make sense. These files existed previously on my Windows based PC. Retrospect stored them into its internal catalogs. Restoring it back to the same Windows environment should not fail. Am I missing something here? :confused2:
  11. boskovuk

    error 1128 (path too long)

    Mayoff, thanks for quick feedback and explanation. I wonder why Retrospect stops executing the restore action when these files are found (with long file names)? It should skip these and proceed with the work anyway. At the moment, I don't know how to proceed from here - there are so many files that need to be retrieved and the restore stop working due to the error condition. See details of my job: ----26/08/2008 9:06:07 AM: Execution incomplete --------Remaining: 228466 files, 89.7 GB --------Completed: 154540 files, 44.8 GB --------Performance: 877.6 MB/minute --------Duration: 00:52:23 (00:00:09 idle/loading/preparing) How do I force Retrospect to skip errors and to continue execution regardless of 'error 1128'?
  12. boskovuk

    error 1128 (path too long)

    This is my environment: Retrospect Professional 7.6.111 (driver update and hot fix: version 7.6.1.101) Windows XP - SP3 I am trying to restore from existing Backup Set to an empty hard drive (~150GB). However, the restora fails with several (~50) errors: ........ error -1128 (path too long) (see below for one example). I have searched other discussion for 'error 1128', however, couldn't find anything that seems to be similar/identical to my problem. Help appreciated. Thanks! + Executing Restore from Backup at 26/08/2008 11:25 PM To volume r on TESTIRANJE (G:)... - 26/08/2008 11:25:01 PM: Restoring from initial (nov 4 2007), Snapshot bosko, 25/08/2008 7:26:08 AM File "F:\bosko\download_instalacije\hard disks\Seagate Barracuda 7200.10 250GB 7200 16MB ATA-100 EIDE (Oct 2006)\Seagate Barracuda 7200.10 250GB 7200 16MB ATA-100 EIDE\Seagate Barracuda 7200.10 250GB 7200 16MB ATA-100 EIDE OEM Hard Drive ST3250620A in Canada at TigerDirect.ca.mht": can't write, error -1128 (path too long) Trouble writing folder "G:\r\licno\Trazenje Posla - tehnicka proslost\BAU-Solutions\tehnologije\JAVA technologies\Web Services\The Java Web Services Tutorial for JWSDP v1.1\Download Java Web Services Developer Pack Tutorial 1.1\tutorial\examples\cb\server\src\com\sun\cb\messages", error -1128 (path too long) 26/08/2008 11:25:39 PM: Execution incomplete Remaining: 62283 files, 13.1 GB Completed: 178 files, 47.9 MB Performance: 89.6 MB/minute Duration: 00:00:37 (00:00:05 idle/loading/preparing)
  13. boskovuk

    7.5 and 'error -1128 (path too long)'

    Good points - I am sure this will fix the problem. Thanks!
  14. This is the environment: Windows Retrospect 7.5.387 When restore happened, the error condition was detected on this file: File "F:\kobos\data\kupovina\kupovina-caku-ukca\oct2006\Casopisi\ConcreteNetwork\Concrete Photo Gallery - Patios, Pool Decks, Driveways, Countertops & Floors - The Concrete Network_files\33548-fl-concrete-n-counters-white-patio-furniture_785.jpg": can't write, error -1128 (path too long) I researched various posts, but couldn't find a definite reply in regards to avoiding this problem (or potential fixes). Suggestions appreciated ....
  15. AmyC, The problem is gone. I followed your suggestion and closed all applications and did some process-cleanup procedure. After I restarted the machine, both the backup and the restore procedures worked as expected. I still do not what caused the problem. At this time, I have several applications opened and Retrospective is working smoothly. Therefore, I'm guessing that some of those 'services' or 'processes' that i have disabled/killed caused previous problems. Thanks for the support and help This is the latest test case log info: + Executing Immediate Backup at 09/06/2003 11:44 PM (Execution unit 1) To Backup Set test6-owl-to-NTFSdisk... - 09/06/2003 11:44:28 PM: Copying downloads_instalacije on E-drive (celeron500) on Pigeon 10/06/2003 12:42:30 AM: Snapshot stored, 1,349 KB 10/06/2003 12:42:32 AM: Comparing downloads_instalacije on E-drive (celeron500) on Pigeon 10/06/2003 3:02:41 AM: Execution completed successfully Completed: 6379 files, 4.2 GB, with 0% compression Performance: 84.3 MB/minute (73.7 copy, 98.6 compare) Duration: 03:18:12 (01:38:25 idle/loading/preparing)
×