robvil

www.retrospect.com does still not work ... there must be something wrong with the cname.... C:\DIG>dig retrospect.com ; <<>> DiG 9.3.2 <<>> retrospect.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1803 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;retrospect.com. IN A ;; ANSWER SECTION: retrospect.com. 840 IN A 64.27.57.24 retrospect.com. 840 IN A 64.27.57.29 ;; Query time: 4 msec ;; SERVER: 10.0.0.4#53(10.0.0.4) ;; WHEN: Mon Nov 21 10:31:03 2011 ;; MSG SIZE rcvd: 64 C:\DIG>dig www.retrospect.com ; <<>> DiG 9.3.2 <<>> www.retrospect.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1169 ;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.retrospect.com. IN A ;; ANSWER SECTION: www.retrospect.com. 900 IN CNAME cold-mountain-6475.herokuapp.com . ;; AUTHORITY SECTION: herokuapp.com. 600 IN SOA a.ns.zerigo.net. hostmaster.zeri go.com. 1320244339 10800 3600 604800 900 ;; Query time: 102 msec ;; SERVER: 10.0.0.4#53(10.0.0.4) ;; WHEN: Mon Nov 21 10:31:14 2011 ;; MSG SIZE rcvd: 148 C:\DIG>ping cold-mountain-6475.herokuapp.com Pinger argon-stack-1879049447.us-east-1.elb.amazonaws.com [107.22.180.215] med 3 2 byte data: Anmodning fik timeout. Ping-statistikker for 107.22.180.215: Pakker: Sendt = 1, modtaget = 0, tabt = 1 (100% tab), Control-C ^C C:\DIG>ping www.retrospect.com Ping-anmodning kunne ikke finde værten www.retrospect.com. Kontroller navnet, og prøv igen. robert

Hmm how many times shall Retrospect be spinned of ..... ? Seems like no one wants to own retrospect. Anyway going to www.retrospect.com only gives us a dns error saying the host does not exist (which is correct) as we cannot resolve www to anything. How smart is that! But http://cold-mountain-6475.herokuapp.com/ works Robert

CTRL + ALT + P + P

Hi, Where do I find the release notes for 7.7.562 build? Regards Robert

Who has decided NOT to remove version 7.7.553 from the update page? This version does not work at all and a big warning label must be posted. Do retrospect not care about there customers at all. Regards Robert

we still see these errors on windows 2008 and newer systems. It is only when using retrospect we get these, using MS build in backup tool do not log these entries, so hallo! Come retrospect - it is a issue with your software. Robert

of cause they dont. This is a major bug fix Regards Robert

I totally agree here ... Retrospect should publish some information on what the hell is going on and what they intend to do about this situation. All that outsourcing to india (or what ever the place is) is bad bad and it get worse if the product has to many bugs (as it has now)! Robert

Retrospect is too much behind. If they want to be a business product they certainly need to speed up the development process and fix some of these periodicly grooming issues plus make it a true service application. In this type of marked it is way too late to release support for products that was released from other venders more than 1 year ago and many people do not have a choice other than migrate to other competitors which do support currently released products. How hard can it be to fix the VSS writer issues on windows 2008, fix grooming issues, fix configuration corruption ect. I do not know how EMC did business, but it seems as they did make things slow down extremly much, so lets us hope now where EMC is out of the picture things will speed up. Currently Retrospect looks more as a desktop backup product more than a business backup solution. Regards Robert

And I still have these errors on all my 2008 and 2008r2 servers ... and I´ll bet it is a Retrospect issue we are seeing here. Why else does a builtin MS backup not produce the same errors? Robert

Hi When can we expect support for exchange 2010? Regards Robert

I have always just installed the Linux TAR package on my Debian and Ubuntu servers. Robert

Is the volume rearly bigger than 2TB? Is it a GPT volume? Robert

Hi, When trying to restore from a disk backup-set at the same time the backup-set is being transfered to tape we get a message saying the backup-set is locket by another process. This is with version 7.7.325 update 7.7.3.102. This used to work in version 7.6. Is this a bug or by design? Should we not be able to do multiple reads from a backup-set, restore and transfer. Regards Robert

Can you try adding the line 'export LANG=C' without the quotes to /usr/local/dantz/client/rcl? It should be added before the line that says CLIENTDIR=/usr/local/dantz/client. Be sure to restart your client after you make the changes. Robert