Jump to content

Search the Community

Showing results for tags 'Windows'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


There are no results to display.

Found 18 results

  1. New Windows user wants advice

    I've been running Retrospect forever. I am quite familiar with its operation on the Mac. I now am looking at a Windows installation and am rather surprised at some of the differences. The biggest one is that on the mac, the "engine" runs whether anyone is logged on or not, but on Windows, it seems that if I log off, Retrospect stops cold. I don't see (so far) a way to leave it running as a service. I also note that the Windows GUI reminds me of the Windows OS GUI, which has a bunch of annoyances, like the fact that the dialog boxes are generally not resizeable, even when it would be really nice. The displays of media sets, history and sources are (I think) less useful and efficient than the GUI on the mac. Is there anyone on the forum with experience with both Mac and Windows products willing to alert me to any land-mines out there? Do I need to just finish reading the documentation? (600-page! Good stuff.) Thanks, -dgl-
  2. Hi, I use Pegasus RAID formatted HFS on a mac and would like to migrate about 3tb of data back onto the drive after formatting it as NTFS for use on an new windows machine. I use Retrospect 13.5 on a mac. Any tips or suggestions for a fast and reliable method to rehome the data with verify would be much appreciated. Is verify even reliable when changing formats? I was thinking about using retrospect to 'copy' the data either via direct connection and smb or formatting an external hard drive as exfat. I'm not sure whether exfat will be a sensible thing or also whether I would need a windows retrospect license for this. Would appreciate and suggestions or advice on the matter.
  3. I get 'MD 5' errors in backups, verify and most recently in restore. You can see in this thread that I'm not the only one, seems to occur in various platforms of Retro and with several different types of files. I can pin down the history on this particular occurrence since it was a recent failure and was noted in subsequent backup from a newly started (recycled) backup through the next incremental backup and lastly with a restore of that backup to a working drive. See the long standing thread comments from others and myself in context here: http://forums.retrospect.com/index.php?/topic/151903-md5-digest-calculated-incorreectly/ I have not yet verified the specific files with errors listed to see if somehow the files are OK. Suppose it's possible that the files are OK and that this 'error' is really a warning that the files were being modified when the backup was running (hence not the most current version). However that is not my understanding of what the MD5 error means. Which is the last point. If that is indeed the case and the error codes prove inconsequential to the quality of the files recovered then at least, the error codes and their meanings posted elsewhere are BADLY outdated. At least they should be thoroughly updated with current numbering and descriptions... Post of the entire cycle (Backup, Verify, Restore):Retro_MD5 Errors_Backup, Verify, Restore.rtf Thanks for your attention to this matter.
  4. I have Retrospect on Windows Server 2012 R2. I'm trying to rebuild the catalogue (again) so I can restore some files, but the rebuild procedure has failed twice. The errors I got this time were: Can't create Snapshot, error -1001 ( unknown Windows OS error) Can't save Catalog File, error -1001 ( unknown Windows OS error) Can anyone suggest what these errors might be and how I can fix them? I have an urgent requirement to restore some files but with the catalogue file broken it's not possible. Why does the catalogue file break every so often anyway? Thanks, Dan Jackson (Lead ITServices Technician).
  5. I apologize for the cross-post; however, I originally posted this in the wrong forum.... We have two installs of Retrospect 8.1.0 (266); one is running on Windows SBS 2011 and the other is running on Windows Server 2012. Our installation on SBS 2011 is working just fine. Backups run as scheduled and media is ejected afterwards. However, on our Windows Server 2012 install, the backups run as scheduled but the RD1000 media will not eject automatically. Instead, we receive an error message stating that there was an Error Ejecting Media and that it is in use. We have to stop the Retrospect software and then manually eject the media from Windows Explorer and then restart the Retrospect software. Has anyone run into this issue before? Any insight is greatly appreciated.
  6. We have Retrospect 9.5.3 running on a Windows server with an 8TB RAID array for the backup set, and 11.5 Mac clients. Recently the backup set became full up, so we're looking at ways to remove old backups to free up space. We've tried the process described here: http://www.retrospect.com/uk/support/kb/disk-backup-set-grooming-with-retrospect_7 However this does not seem to have had any effect? It seems to be doing something - the status updates variously to "Matching Backup Set" or "Analysing Catalog File" but no space is being freed up. The server is running Windows Server 2012 R2, with a Xeon E3-1220v3 3.1GHz CPU and 16GB RAM. Can anyone suggest what we need to do differently? Thanks, Dan Jackson (Lead ITServices Technician) Long Road Sixth Form College Cambridge, UK.
  7. I have been trying to use a Source Group as a selector inside the Selecting window for a backup script. The main selector is: Include everything + but always exclude file matching volume name exactly matches sourcegroup In picking my conditions, I picked a volume name but put in the Source Group name instead. What did I do wrong? Does it matter if the "source groups container" is a member of the source group, or not? I really like source groups as the source for a backup script. I was hoping that I could apply the same approach to Selecting conditions.
  8. The Instant Scan FAQ (http://www.retrospect.com/en/support/kb/retrospect-instascan-faq) does a good job of explaining how Instant Scan is implemented and describes some of its problems and limitations. The main problems described are: 1. RetroISA can use a high CPU load. Even after the initial scan, the service's use of CPU can spike degrading the performance of other applications. 2. Recently modified files may be missed from a backup if the service hasn't gotten around to scanning them. Additionally, I've had the RetroISA service block a chkdsk /f because it had an open handle on the volume. I wouldn't be surprised if it also interfered with "safe removal" of an external drive. I don't know about the Macintosh platform, but I think this can be done better on Windows. The FAQ indicates that Instant Scan only works on NTFS formatted drives in Windows because it makes use of the USN journal. Since the USN journal is a requirement, doing all this background scanning is largely unnecessary. Background: The USN journal maintains a list of changed, added, deleted and moved files. The old way of doing an incremental backup (in general for any backup application) was to scan the entire disk and compare against the backup catalog looking for changes. The USN journal removed this need. Instead, a backup application only needs to check the timestamp of the last backup, then read the USN journal from that time on. Only if the USN journal wrapped does a full scan need to be done. I've done tests with a different backup product on a 6 TB disk that had millions of files. Time to scan without USN journal: 2 Hours Time to scan with USN journal: 5 minutes This other product does not do pre-scanning like Retrospect's Instant Scan. My point is that just using the USN journal as it was designed offers a huge benefit and you avoid the problems that Instant Scan currently imposes. However, I can see some benefit to doing a pre-scan. In the case of the very first backup, a full scan would likely be required without Instant Scan. So, my recommendations for Instant Scan improvement on the Windows Platform as follows... Keep the RetroISA service, but offer different levels of Instance Scan performance options. 1. Normal: After detection of a new fixed disk, RetroISA should do a full scan saving the cache data as it does now. In this mode, RetroISA should not do any further background scanning of the volume after the initial scan. This immediately eliminates the problem of RetroISA degrading system performance. It also reduces the time when RetroISA can interfere with chkdsk /f or device removal (but see below for a discussion of how to fix this completely.) Then when a backup runs, the main Retrospect application should activate RetroISA asking it to perform a refresh (and wait for it to complete). This would still be very quick in most circumstances and it would avoid the problem of newly changed files not being included in the backup. This mode would provide a nice balance. 2. Minimal: RestroISA does no scanning on its own. Scanning only occurs when a backup runs. This would be closest to the basic implementation of backing up with the USN journal. When the first full backup runs, a full scan should be done on the volume. For all subsequent backups, the backup should ask RetroISA to refresh the cache using the USN journal and wait for the results. There is no background scanning in this mode. There is no pre-scan in this mode. 3. Disabled: For those users that don't want the Instant Scan cache files on their systems. 4. Aggressive: Instant Scan operates as it does now with periodic background scanning. This would eliminate even the 5 minute wait in my previous example. One caveat is that Instant Scan should be a better citizen when doing background scanning (It should also be like this when doing initial background scanning in Normal mode.) What do I mean by being a good citizen? If the user wants to run a chkdsk /f, get out of the way. If the user wants to remove an external device, get out of the way. The WM_DEVICECHANGE_NOTIFICATION can be used to know when one of these events is occurring. An application/service calls RegisterDeviceNotification in order to receive it. Microsoft provides an example of using WM_DEVICECHANGE_NOTIFICATION to handle the case of an external device being removed. https://msdn.microsoft.com/en-us/library/windows/desktop/aa363427%28v=vs.85%29.aspx For the chkdsk /f case, things are slightly different. WM_DEVICECHANGE_NOTIFICATION is still used, but the event that is sent is DBT_CUSTOMEVENT with an event GUID of GUID_IO_VOLUME_LOCK. I couldn't find an online sample of this, but I did write sample code myself, as test, before writing this post. I would be happy to provide this code to you. I know I'm not a Retrospect product manager, but I hope you'll give consideration to making these improvements to Instant Scan. Right now, Instant Scan is a step toward of a good goal, but there's no reason why the problems it currently has need to exist. If you don't want to fully implement all suggested modes, then please just consider implementing either the "Normal" or "Minimal" mode suggestions. Thanks.
  9. We recently updated one of our sites from 7.7 to 9.5 the server is a windows server 2003 x64. After updating however we receive multiple error 102 trouble communicating. For kicks we rolled back the vm to 7.7 and everything works fine. Since this OS is on the supported operating systems is anyone else experiencing this issue with 9.5
  10. Hi, I may not have searched on the proper term(s) so if this question has been addressed, a reference to the info would be appreciated. I want to move my backups from local storage to an iSCSI-based NAS box, keeping the server where it is. How do I go about redirecting where Retrospect looks to continue it's incremental backups? Do I stop Retrospect, just move the backup files, and then edit the 'Member Properties' for the Backup Sets to point them to the new location? Thanks!
  11. AIT Tape Issue

    Hello All, I was hoping someone could shed some light on an issue I am having little luck with. I have been put in charge of a large database of backups. At the time there was an SCSI based SDX-500c on the shelf labeled broken and another in service (I have been using till now). The one in service slowly died with increasing errors. I had suggested servicing the drives but was discouraged from that as other IT people began lending us their AIT machines. An SDX-500c with a USB enclosure and an SDX-900v with SCSI as well. The only thing that worked to read the tape library was to use the original machine. I stripped off the enclosure and mounted it in a PC with a terminated cable and that has kept us alive. I am now terrified that if this machine dies it will mean all of our tapes are unreadable. I am starting to think I should begin transferring the data on the tapes through another machine. Hopefully creating media that can be read on a more reliable machine. I know tape is a bit finicky and because I am younger I haven't really been exposed to scuzzy beyond hardware IDs and terminators. Is there something critical I have missed? Thanks. EDIT: I have now found that the other Sony SDX-500c is not recognizing tapes possibly due to the contacts in the drive that seat against the back of the tape. I am going to try and swab it I suppose. Couldn't hurt. I am using Retrospect 7.6 for the data sets. No older or newer versions. Thanks! JV
  12. We have two installs of Retrospect 8.1.0 (266); one is running on Windows SBS 2011 and the other is running on Windows Server 2012. Our installation on SBS 2011 is working just fine. Backups run as scheduled and media is ejected afterwards. However, on our Windows Server 2012 install, the backups run as scheduled but the RD1000 media will not eject automatically. Instead, we receive an error message stating that there was an Error Ejecting Media and that it is in use. We have to stop the Retrospect software and then manually eject the media from Windows Explorer and then restart the Retrospect software. Has anyone run into this issue before? Any insight is greatly appreciated.
  13. New to Retrospect. I'm sure this is a simple question, i just haven't been able to find a definitive answer. I'm thinking the answer is, "just the logged-in user." Just wasn't sure how to properly search the documentation for this. Environment: Retrospect 8.1 server for Windows Clients, all laptops, Win7 and OS X 10.8.3 or 4 Each laptop has a user profile, which is what is logged in, and an admin profile, which is idle. Retrospect will use a service account with local admin access to laptops. This concerns both Win7 and OS X... When I create a backup script to targeting: -Win7 - predefined "Profile and settings', or custom My Document + Desktop, will the script only target the currently logged-in user, or will it grab the defined directories for all users? -OS X10.8.3 or 4: Full system, or custom Documents + Desktop, will the script target the currently logged-in user or will it grab the defined directories for all users? Thanks
  14. Greetings! Background: I'm in the middle of trying to set up a Disk-to-Disk-to-Tape (D2D2T) backup strategy that involves two instances of Retrospect Server running on Windows and Mac using shared network storage and a single tape drive. Both Windows and Mac RS servers need to write to the network share, and the Mac controls the tape drive. Problem: I've hit a snag when trying to share the Disk-based media between with both machines. I can share the disk-based backups and catalogs between the two servers by manually updating the path to the media set every time a backup runs. I haven't found a way to to make the change automatically, mangle paths, or even to have Retrospect use a relative path to identify the media set's members. Has anybody got any workarounds for this kind of setup? <p> Constraints: Retrospect Server for Windows is required for Exchange Mailbox backup Retrospect Server for Mac OSX is required for fast Xsan backup and tape loader Network share as disk-based media set in Disk-to-Disk-to-Tape (D2D2T) workflow Separate network share for catalogs Backups must be fully unattended, as humans will not be on-site at 2am Approaches Already Tried: Some other odds and ends I've tried along the way Retrospect 10's WebDAV support: The catalog still contains the platform's native representation of the WebDAV path. For the Mac, this is still a local path in /Volumes. Tricks with OSX's mount command to fake a local windows path or UNC path: Forward slashes and backslashes are a bit too incompatible to work with. Switching to a single server: Not possible as a Windows server is needed for backing up Exchange mailboxes. A Mac server is required for Xsan connectivity and Tape loader -- backups are far too slow when run through the Retrospect Client. Manually editing the uncompressed .rbc file with a hex editor: The .rtS chunk has a 4-byte constant (0x00011001) followed by a 16-byte value specifying how many two-byte characters are in the string (UTF-16?), ending with zero-padded to the next multiple of 4 bytes. Running a homebrew length-altering binary search and replace seems somehow unsafe, despite the entertainment value of doing so Further thoughts would be appreciated!
  15. First: Background Chassis: Dell Poweredge T410 Xeon E5620 @ 2.4 GHz 8GB RAM 5TB RAID 5 on a Dell PERC 6/i RAID controller IBM ULTRIUM-HH5 Tape Drive Software Windows Server 2008 R2 Standard x64 Retrospect 7.7.620 -- It all started when I did a standard cleanup on the RAID and it wiped out the entire catalog set. So I dumped that destination, and started over. Ever since I have started having severe issues with the backup process. The screenshot attached says it all. What ends up happening is even on a full reboot, as soon as it tries to backup any client on the network, Memory usage climbs to maximum and the backup either hangs, or fails eventually with the "Not Enough Application Memory" error. On the worst case, Retrospect throws a cpp error and dumps the process. in either case it damages the catalog file belonging to the destination it was accessing, Attempting to rebuild it, fails with the same error... and endless loops ensue. I am honestly at a loss here... I have not backed up the network since the 1st and I am beginning to look at other options. Help?!
  16. Hello all, I have a windows server 2008 standard running as an ESXi VM with Retrospect used to backup the clients of a small net (15 pcs). Retrospect is 7.7.620 single server edition. My problem is that often the backup script begins execution and then hangs (for hours) doing nothing but consuming cpu, no backup is performed. I already tried rebuilding the catalog and checking media files (a remote share on a nas) with no effect. I use the Administrator account to run the backup process. The sever uses Tren Micro Worry Free as antivirus. Any clue? Thanks for your kind attention Alberto
  17. Retrospect Forum: Retrospect for iOS with Retrospect Sever Windows 7.7.620 I tried the iOS App with my iPad 3, and iOS 6.0.1. Twice I tried and had to "Kill" the Retrospect.exe process: after one hour this Process still used almost 100% CPU time (two physical processors). One time the preference file got destroyed in the process (both .dat and .bak files). Fulco
  18. According to the support site, Retrospect only supports up to Windows 2008. Does the current version support the upcoming Windows Server 2012 release? If not, is there a new release planned to add this support? If so, when will it be available?