Jump to content

vac

Members
  • Content count

    20
  • Joined

  • Last visited

Community Reputation

1 Neutral

About vac

  • Rank
    Newbie
  1. as expected no reply, this forum is dead aswell their software... or they simply don't give a sh... about their customers...
  2. unfortunately another problem which is simply ingored by the support / company.... I just wait for "upgrade to the latest version".....
  3. Hi, here is a link to the March 2014 Update of MAPI CDO, unfortunately both version does not fix our problem. http://www.microsoft.com/en-sg/download/confirmation.aspx?id=42040
  4. Hi, same here "Error in Cmdlet Get-PublicFolderDatabase, Parameter {Identity=Mailbox Database 2013032212}." It is definitly caused by Retrospect, so how to fix it? Enviroment: SBS 2011 & Exchange 2010 latest SP, Retrospect SBS 8.5.0. (136).
  5. Hi, same problem here, only solution is to stop and restart retrospect. Regards
  6. push - important thing to fix restrospect!
  7. vac

    E-mail Notification Not Working in 8.1

    and we're still waiting for fix. come on guys, what can be so difficult to fix such a clearly problem?
  8. Nowadays... easy decision.. we recommend cutomers to use another backup software. Why? As Exchange 2007 was released there were also no support for Exchange 2007 within a timely manner. That they now have exactly the same "problem" with Exchange 2010 is unbeliveable. [irony]But hey, it was absolutely surprising that a new Exchange version was released by MS so it was impossible to "get" a working agent for Exchange 2010 within one year after RTM-Version of Ex2010[/irony]
  9. Update: I solved my problem moving the problematical server to the end of my volume list. During the problem he was at the top of the volume list, after moving it to the end the problem was gone. best regards
  10. UPDATE: I tried a CHKDSK yesterday on the mentioned terminal server, sadly without any success. Oh wait, the first backup after the reboot runs fine, I started later the day another backup to verify that my problem is solved. Guess what... this backup actually has a throughput 0,0MB/min and hangs. Some more solutions? best regards
  11. Hi, because this server is a terminalserver it runs 24/7. it was never restarted during a backup or something like that. best regards
  12. Hi Daniels, hi Lennart, thank you both for the reply and suggestions. @Lennart: will try that @Daniels: those cache files were just an example. You're right, there's no need for them, but the verify also stops on other, more important, files. I can exclude the mentioned files, but this won't help me with the rest. Anyway, I will try a chkdsk on this machine and we'll see if this solve my problem. If someone have more ideas, let me know. best regards
  13. Hello everybody, I have a environment of two Windows 2003 servers. One fileserver and one terminalserver, both on the latest Microsoft patchlevel. We are using Retrospect 7.6, Retrospect is installed on the fileserver with a external Tandberg Data Storageloader 1U sttached (SCSI), the terminalserver is backuped using the Retrospect client 7.6. After several months/years without any problems I got now the following error: After finishing the backup, the verify process starts. Then suddenly, the data throughput drops to 0,0MB/min and the verify process does not continue. If I make nothing, the job will run endless and will never finish. The curious thing is: the verify process stops at different files. For example job a) stops at some windows internal files, I cancel this job and start job and this fails for example on some user data files. the last message within the backup protocoll was for example (translated) There are no additional error messages in the eventlog on the fileserver or the terminalserver. We made no changes to this systems, except Windows updates. What did we tried: - rebooting both servers - deactivated antivirus software - reinstalled and readded the client on the terminalserver - updated network drivers - changed network cables - changed scsi cables - changed scsi terminator - changed order within the backup source groups - try to add the volumes of the client to retrospect instead the whole client Any ideas how to resolve this issue? best regards
  14. vac

    login to the SQL Server failed

    not as far as I know. We only get it working with the "sa" user. Anyway, I don't care, cause we're go to switiching our backup software soon. I mean, hey, no agent for Exchange 2010 while other vendors have it already and there's still no date for availability? Sorry, but this is unbeliveable. best regards
  15. vac

    login to the SQL Server failed

    yes, I see all configured databases
×