Jump to content

FuzzyJohn

Members
  • Content count

    156
  • Joined

  • Last visited

Posts posted by FuzzyJohn


  1. I had one JPG file that had no problems running Retrospect Single Server v6.5. After upgrading to v7.5 I started getting the "File did not compare error". A week ago I installed v7.6 and the error remains.

    I made a copy of the file and the copy also fails to verify. I resaved the file and the newer version verifies OK. I have no problem ditching the original (which did not compare) but I am uneasy as this may still come up with other files.

    The verification method I use is the default.

    Fast forward two years.

    As my last post indicates, resaving the 2 files eliminated the "file didn't compare" errors.

    Now I started getting the same error on 2 different JPG files. These are files that have been backed up without any problems for about 8 months and now, all of a sudden, I get the "files didn't compare" errors. The files have not been changed ever since they were placed on the server.

    OS: Windows Server 2000

    Retrospect: Retrospect Backup Single Server v7.6.111.

    Verification Method: Default.

    I can copy the files to other locations without any error messages from Windows.


  2. I am setting up a Windows XP Pro SP-3 machine from the ground up.

     

    I did a quick backup test using Retrospect Single Server v7.6.123. When I started the backup I did not see the message saying "Preparing for open file backup". During the backup I had several files with Error -1020 (sharing violation). I checked the Volume Shadow Copy service and found it not to be running.

     

    On a wim I uninstalled Retrospect Single Server v7.6.123 and installed Retrospect Professional v7.0.326. When I started the backup I saw the message saying "Preparing for open file backup". The backup completed without errors. I checked the Volume Shadow Copy service and fond it to be running.

     

    Why the difference between the 2 versions? In Retrospect Single Server v7.6.123 when I tried to enable Open File Backup I got a message saying that my license does not cover that feature.

     

    Does the Single Server version require a separate license for open file backup in XP while the Professional version will use XP's VSS? Will Retrospect Professional v7.6 use XP's VSS?

     

    I was under the impression that the additional license for open file backup is to use Retrospect's Open File Backup not the Volume Shadow Copy service.


  3. Check the date that the excluded folder was backed up. You say you did a Normal backup, so I'm wondering if the folder was backed up prior to the time you excluded it in the Selector. Make a new test Backup Set and see if it gets included. Or do a Recycle on an existing backup set.

    I created a new backup set and used it about 10 days ago. The results are the same. The excluded folder does show up when browsing the snapshot, and I can restore from it, but it does not show in any of the individual sessions. This new backup set was created and used after the exclusion was created.

     

     


  4. Using Retrospect Single Server v7.6.111.0 under Windows 2000 Server.

     

    Files excluded thru the Selector are still backed up.

     

    One of the exclusions in the selector excludes where Windows Drive Letter is D: and folder name exactly matches "COMSEG Repository".

     

    Testing the selector correctly shows that folder "COMSEG Repository" and its subfolders and files are excluded from backup.

     

    Checking a backup set that used this selector, browsing the first session of the backup set shows that folder "COMSEG Repository" is not backed up. I browsed several other sessions in the backup set and I was unable to find the folder there.

     

    However when I browse the snapshot for the same backup set I can see folder "COMSEG Repository" together with its subfolders and files. A retrieve operation for several files while browsing this snapshot restored those files.

     

    So even though the Selector Test and the first session of a normal backup set show that the folder is not backed up, it is really there as indicated by the snapshot and by the ability to restore files from it.

     

    Other backup sets that used the same selector exhibit the same problem.

     


  5. I had one JPG file that had no problems running Retrospect Single Server v6.5. After upgrading to v7.5 I started getting the "File did not compare error". A week ago I installed v7.6 and the error remains.

    I made a copy of the file and the copy also fails to verify. I resaved the file and the newer version verifies OK. I have no problem ditching the original (which did not compare) but I am uneasy as this may still come up with other files.

    The verification method I use is the default.

     


  6. Oh also, in general, it would be nice for retrospect to be able to tell the backup operator, for any given tape drive attached, how many hours of use have occurred since the last tape cleaning operation. Maybe that should go in feature requests? :)

    Go to devices, highlight your tape drive listed there and get its properties. You can highlight the tape too and get the same information.

    I am a newcomer to v7.5. In earlier versions Retrospect had to be running at the time the tape drive was cleaned to record the cleaning action. I really don't know if that is still the case with 7.5.

     


  7. Sounds like you are blocking either UDP packets or subnet broadcast or multicast. You need to make sure all of these are open, not just the port.

     

    What is your exact Retrospect version? 7.0 has not been tested with XP SP3

    The exact version is 7.0.344.

    Adding Retrospect to the Windows Firewall did the trick. :banana:

    I guess (again) that this was introduced by XP SP-3 as until today I did not have ports 497 TCP and 497 UDP and Retrospect in the Windows Firewall Exceptions. Also, even though the FAQ say that "If you install Retrospect 7.x or the Retrospect 7.x Client software on a PC running Service Pack 2, the install process will open the necessary network ports. No additional action should be required" it did not do so. But it worked on XP SP-2.

     

     


  8. I Have Retrospect Professional v7 on a Windows XP machine and a Retrospect Client on a Windows 98 machine. Up until yesterday I had no problems backing up the XP machine and volumes on the 98 machine via the client.

    Yesterday I installed Windows XP SP-3. Also yesterday I changed the IP addressing on the network.

    Today when I attempted to run Retrospect Professional it cannot find the client on the 98 machine unless I turn the Windows Firewall off. I did set exemtions in the Windows Firewall for port 497 TCP and UDP but that didn't help. The exemptions were not there before SP-3 and everything worked.

    If I use Direct Access it will see the client, but the client is on a DHCP workstation. I can work around that but I prefer to use multicast for detecting clients.

    Is there anything new that EMC knows relating to Windows XP SP-3?.

     

     


  9. The boot disk on the client that gets this error is NTFS.

     

    I poked around some more and compared this particular client with another one that has no problem. One thing I found is that the client that gets this error does not have the ROFF.SYS file in C:\WINNT\System32\Drivers. This is a client I just setup and installed the latest v6.5 client software I downloaded from the website about 2 weeks ago. Could this be the problem? The older client (the one which has no open file backup problems) has an older build of the v6.5 client software which obviously installed this file.

     

    I checkced both registries for references to ROFF.SYS and found them to be the same. So I manually copied ROFF.SYS to the new client and restarted it. Tomorrow morning I should see if this solved the problem.


  10. I added a client to the network with Retrospect Client v6.5.138. Now Retrospect comes up with the "Can't use Open File Backup option Error -1012 (feature unsupported)" when it gets to backup that client.

     

    The client is running Windows 2000 SP-4 and it is a brand new installation, very similar to other clients on the network that Retrospect has no problem backing up. There is no other Open File Manager software installed. The boot drive is a Basic Disk. The volume defined for backup is on the boot drive. The biggest differences in this client setup are:

    - 4 dynamic disks set up as Stripped Volume.

    - Sony DVD Burner with Nero 6.6.1.4 and InCD installed.

     

    The other Windows 2000 clients on the network have no problems. The other clients on the network run Retrospect Client software v6.5.136 or earlier.

     

    Server:

    OS: Windows 2000 Server

    Software: Retrospect 6.5.350 & Open File Backup license installed.

     

    Can you suggest things for me to try?

     

    Thanks.


  11. Reviving this 10 month old thread.

    Now that Retrospect 7.5 was released, what are the chances for the restore from snapshot bug decribed above, to be fixed in Retrospect 7? Or will the fix be available only in v7.5?

    I am familiar with the "standard restore" method. In my case however I find that I have to restore more files deleted from a server by users. These files are in the latest snapshot and much easier to restore from there.

×