Jump to content

AndrewA

Employee
  • Content count

    150
  • Joined

  • Last visited

Community Reputation

0 Neutral

About AndrewA

  • Rank
    Support Staff

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. AndrewA

    A bunch of questions-

    Well if you are getting the -557 error on individual mailboxes that is a known issue but the -557 on the Storage Group is not related. If you have open file backup and you are getting -1020 sharing violation errors then you are probably getting a 1017 error when it tries to use open file backup on that drive. Retrospect leverages VSS so if it is failing for a specific drive you can look at the event viewer for that machine for VSS errors. The IIS Metabase is backed up as part of the system state so for some reason the API call that is being made is getting denied access, I would also check the event viewer to see if there is any related errors or warnings.
  2. It will only restore to new folder when restoring to a mailbox, the user will have to move the contents of the restored contacts folder back to the original contacts folder.
  3. There is a known issue on 10.6 machines where when the machine is logged out Retrospect can not access the client. Unfortunately the only work around right now is to have that machine logged in at the time of backups.
  4. AndrewA

    A bunch of questions-

    What are you getting the -557 error on specifically? Is it a hard drive or maybe a mailbox with Exchange? The 1020 error is coming from Windows itself, the file is open and Retrospect can not back it up. If you do not have open file backup the only thing to do is to make sure that a program that could be using the file is closed, if it is a file the OS is keeping open for some reason then there might not be much you can do. The -1121 error could mean there is file system corruption, if this is a Windows machine I would run a check disk on the drive it is reporting the error for. If this is an Exchange Mailbox go to configure volumes, release and re-add the license for the Exchange server.
  5. AndrewA

    Insert the Backup Set member - tape request

    This is a known bug that only happens with transfers, it happens when Retrospect goes to span to another tape and has to verify the tape it was writing to. What you can do until this gets fixed is turn off verification and run a verification script later.
  6. AndrewA

    Snapshot behavior w/out grooming

    Retrospect will only show 1-2 snapshots with grooming disabled but the other snapshots are still there. You just need to click on Add under the snapshots tab when you get properties for the backup set and you will see all the other snapshots.
  7. Even on the Mac side the File backup set is limited to a Terabyte. I have seen where it has gone beyond 1TB but usually Retrospect has a problem with that set at that point. You need to use the disk sets.
  8. AndrewA

    Continuous backup

    You should still be able to use the continuous backup program if you upgrade to 7.7
  9. It will be in C:\Program Data\Retrospect. You can just double click on it and it will open in Retrospect. I would search for I think Windows Vista because that is how it is identifying 2008 and the assert error should be below that.
  10. What is the assert error that you are getting? I have seen where if a user has a lot of rules on a mailbox it caused Retrospect to crash. Could also be there the mailbox is corrupted and is passing bad information to Retrospect which it does not know how to handle.
  11. AndrewA

    Upgrade for Retrospect 7.7

    Unfortunately no though it should continue to function.
  12. AndrewA

    can't get sql client to connect

    You need to go to Configure Volumes and you can right click no the SQL Database container and select licensing. It will ask if you want to apply your available license and then will ask if you want to authenticate with the SA account or a Domain account. After that you should be able to add the SQL Server container or the individual databases to your script.
  13. AndrewA

    R+etrospec 7.7 - Same issue

    Since the error is happening for open file backup the insufficient storage space error is mostly likely referring to the C: drive of the machine that it is trying to backup. Retrospect uses the volume shadow copy service within Windows and it by default uses space on the C: drive when creating snapshots.
  14. With the way compression works it tries to compress every file that is being backed up regardless of format. If the format of the file is already heavily compressed you can get negative compression where it makes the file larger and take up more space in the backup. In cases like this it is better to just leave compression off as the program is not smart enough to not compress files that would have negative compression.
  15. AndrewA

    Windows Server 2008 R2 NTDS error -1017

    Is Retrospect running as a specific user or as the logged in user under Configure Preferences, Execution Security?
×