Jump to content

Search the Community

Showing results for tags 'bug'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 11 results

  1. Retrospect seems to have a bug on Windows with its handling file names and path/folder names containing ampersand characters. The bug is shown in the two annotated screenshots attached to this post. When specifying a single ampersand '&' character in a file/path name, the ampersand is omitted and an underscore is shown in the following character. When doubling the ampersands && the problem seems to go away but the selector is then internally incorrect. I verified this with at least one selector, where despite it looking incorrect with the underscore (caused by the single ampersand), it worked fine in finding the path containing the single ampersand, but when doubling the ampersands && (which escapes them for the UI components), while the UI looked correct, the selector was then incorrect with a double ampersand. Some classic Windows UI elements use ampersand as a way of indicating accelerator characters for UI fields and controls. For example, to specify "&First name" while creating UI resources leads to the F appearing underlined in the UI to indicate to the user it is the accelerator character. My guess is that Retrospect isn't filtering or dealing with this, and just displaying raw user entry into Windows components that are interpreting characters to be accelerators. Note, I notice this problem also affects files already backed up which contain paths with ampersands... if I go to the backup sets and view snapshots or sessions for such a file, and choose Properties, the UI will show paths which actually contained a single ampersand by omitting the ampersand itself and underlining the following character... my guess is that the UI is incorrect but that the underlying backup and name of the path is correct. For example, a backed up file with a path "C:\This & That" will show up in the UI properties for the file as "C:\This _That" because the UI control is seeing a single non-escaped ampersand so it then uses that to underline the next character which is the space before "That" so you get "C:\This _That" in the UI which is very confusing. Thankfully this appears to be a UI issue only but it's incredibly painful when one is trying to solve integrity problems elsewhere and examining things so an eventual fix would be nice. It seems as though some filtering/escaping is required to fix this. Thanks so much for listening!
  2. From time to time, I realize that I've seen no emails reporting backup successes or failures. I go to Retrospect (11.5.2 right now) and see that no scheduled backups are running when they *should* be, and they haven't run for a few days or a few weeks. Why does the engine fail so catastrophically? This is a *very serious issue*! I see a couple files in Console named RetroEngine_2014-11-18-233330_Tube.cpu_resource.diag and RetroEngine_2014-12-18-233356_Tube-2.cpu_resource.diag (the 2nd one was just generated after I rebooted my Mac Pro and forced the backups to start again by pausing and then resuming all jobs (because for some reason they wouldn't start automatically like they should've at 23:30). And now both backups are stuck at "Preparing to execute" even after 20 minutes. I've attached both logs. Anything else I can provide? I'm running 10.10.1, and I just turned off Instant Scan before the reboot, because I'd previously turned it off in an older version of Retrospect because I hate how much CPU and disk i/o it uses when I need it. Archive.zip
  3. Environment: DELL PowerEdge T110 II Windows Server 2008 Standard Retrospect 8.5.0 (136) Single Server OEM DELL RD1000 Issue: Since installation we've been having problems with Retrospect returning a "Waiting for Media" message when scheduled backup jobs run over night. We're using 5 tapes on a Recycle Backup scheme, I have each tape added as a member of a corresponding Backup Set (Monday A, Tuesday A, Wednesday A etc) We've recreated the backup numerous times using the Retrospect wizard and manually and we always get the same result. If we set the Media Timeout in the options the job will just cancel after the set time. Also, when clicking the 'Check Media' button on the verify job screen, it reports that the media is unavailable even though it's sat in the drive waiting. Having struggled with this for a week or so I believe it to be a bug in the software, as a workaround to this issue is to do the following: Before the backup job runs, click "Devices" under "Configure" and wait for a few seconds for the RD1000 drive to appear in the window, once it does, close down the Devices window and the backup job will run fine, also 'Check Media' reports the tape as being ready. I then have to leave Retrospect open but minimised as closing Retrospect down seems to break the link to the RD1000 drive again (meaning you have to go back in and do the above) While this workaround is OK it means every Sunday when the Server updates and reboots I have to remember on the Monday to log in, open Retropsect and do the above, then leave it running minimised.
  4. hitting "stop" in the activities view with a grooming operation selected does not stop the selected operation. i have a runaway groom operation that is crashing retroengine. every time it crashes, it restarts itself and comes back trying to do the same groom. hitting the stop button seeming accomplishes nothing. the status of the task switches to "please wait...", then nothing happens for a while. then the engine eventually crashes again.
  5. i'm seeing assertion failures from retrospect engine. oddly, they are happening at 5 minute intervals. they seem to be related to an instability i observed with client communications (reported under a separate thread). "Assertion failure at "grx.cpp-1089", on threadID <hexID>"
  6. i'm running retro v10 console on my server, connected to the local retro engine and roughly every 5 mins, the console "blanks out", acting as though it has just restarted itself. it jumps up to the top level default display. from the log view within the retro console app, it appears that this is happening every 5 mins give or take a few seconds, with occasional "skips" where the interval is roughly 10 mins. in the console log view, i also see one odd msg of the form: "StucOpen: IOCreatePlugInInterfaceForService(kIOMMCDeviceUserClientTypeID) (error -536870210)". also, i had been away for a while and came back to the machine to find the console app had crashed. i have the crashdump and can post if it is useful. in this situation i'm running the latest retrospect v10 console and engine (installed ~4 days ago). the retro engine is running locally on the same box as the retro console. my system is running mac os x 10.6.8 server. in the system console on the machine, i see bunches of msgs at 5 minute intervals of the form "Server::updateScriptsCache exception: MacRequestor::Request: connection closed by remote endpoint" or " and other similar msgs involving updateSetsChangeCounter, updateSelectorsCache, etc. i'll post these log records as an attachment - it actually looks like there might be a lot of different things going on there that don't look familiar, including some scary-looking assertion failures - hmmm... RetroEngine or Retrospect.txt
  7. retrospect engine process in a new V10 upgrade is generating multiple pairs of log lines per second of the form: TVol::GetInfo: UGetVolumeInformation failed, /private/var/folders/Sw/blahblahblah MapError: unknown Mac error 22. i reported this some time back (under either v8 or v9). iirc, i was told that these are not a sign of anything wrong and can be ignored. even so, i consider it a significant bug and i'm not happy that a previously reported problem survived into v10. i don't like my log files getting spammed like this - for several reasons.
  8. It seems that the client only registers for multicast request on the first active interface. If another interface comes up, it will not register (and respond) on that interface. In addition, if the first interface is taken down, the client doesn't reregister on the remaining active interface(s), which means that it now will not respond on any interface. I have verified this with "netstat -g" and my own retrospect multicast client querier hack. This has become a huge problem to us. At our site we have a WiFi network that won't relay multicast but that everyone is always connected to. When people want backup they have to connect an ethernet cable too. But even if they do, the client won't register for receiving the queries on the wired interface, and they will not get a backup. Even if they disable the wavelan interface, they still will not get a backup. They have to first turn of wavelan, and then connect the ethernet cable to get backups. I strongly believe that the client should register and respond on all active interfaces (and that the response of course should contain the ip address of the interface the query was received on). We think that this has worked before, and that the problem started around the end of january 2012, somewhere around the updates 10.7.3 and 10.6 Security Update 2012-001. Maybe something has changed in the IP stack around that time that causes this new behavior. The problem seems to be exactly the same with both the 9.0.0 (319) and the 6.3.029 clients. /ragge
  9. Retrospect Pro 7.7.562 on a Quantum LTO-5; When I use Archive Files and create a new backup set/add a member from the wizard, when I actually go to run the archive it tells me that the drive is busy and it will wait until it's not. But the drive isn't busy, and in fact if I pull up the Storage Devices window it shows it as "Ready." I have to quit Retrospect and do the Archive again for it to go.
  10. I just upgraded to Retrospect Pro 7.7 from 7.6. Using 'Find Files', I selected 4 backup sets (made under 7.6) to search for some archived folders not knowing which set they were in. Upon setting up the restore location and search criteria, I was presented with the summary Retrevial window and got the following: Notice that under Files Chosen that Project Arc 003 is shown twice, when in fact the last one should be Project Arc 004 which indeed has a few thousand files found. If I click the Files Chosen button I'll get a window showing the found contents of Project Arc 004. If I go back and remove Arc 003, I'll then properly see Arc 004. If I then go back and add Arc 003, it will show Arc 004 twice instead. If I add more than 4 backup sets, I'll see whichever is in the #3 slot twice and the rest are not shown at all. In any event I think 4 is the max number of backup sets I've ever searched for, but I am quite positive that under 7.6 it did properly show all 4 in the Retrieval window. This doubling of #3 is happening now in 7.7 (7.7.562 to be exact.) I was going to use the 'Contact Support' link but that form is a bit useless, you can only type 250 characters in for the problem description!
  11. Here is my problem: Retrospect Server 9.0x (latest version) running on Mac OS X Lion 10.7.2, the Client settings don't stick. I can check all the "allow clients to..." checkboxes in the Server preferences, but they don't do anything client-side and, if I quit and relaunch the console app, the boxes are unchecked... Meaning I can't allow my clients to abort a backup, trigger a restore or simply deactivate Retrospect Client! That plus the fact that, sometimes, even if the Server is not doing anything (no Activity currently running), the RetroEngine eats up 80%+ of the machine it's running on, and I can't turn the Server off from the OSX preference pane, I have to kill it using a terminal command while sudo rooting. Way to go Retrospect. Although it IS nice finally having a real 64bits, Lion ready version. Also, I'd really like to know two things: 1) why are the retrospect server preferences still stored in the old cryptic format and not using the standard XML .plist format? 2) why in Hell are OPERATION LOGS stored in the Config80.dat file, mine grew up to 20MB! and 3) now that Retrospect is version 9.x, maybe that file should be called Config90.dat? Note: this problem is mentioned in another thread about another server issue: http://forums.retrospect.com/index.php?/topic/147522-clients-v9-cant-back-up-now-only-work-as-schedule-proactive/
×