rustyjones40 Posted May 8, 2006 Report Share Posted May 8, 2006 I am running Retrospect Multi server on 2 Windows 2003 servers. I am backing up 42 servers between the 2 backup servers. Almost every day a backup will fail on one of the servers. All I have to do is restart the Retrospect Client on the server that failed, and it will run the next backup job. Its not the same server every time, sometimes I'll have 3 or 4 in one day. Its just a hassle to restart the services. I checked the web site and have the latest updates. any idea's? Link to comment Share on other sites More sharing options...
martyrs29 Posted May 9, 2006 Report Share Posted May 9, 2006 What error is being logged at the time the backup fails? (i.e. network communication failure, backup client reserved, etc.) What OS is the client running? Link to comment Share on other sites More sharing options...
rustyjones40 Posted May 11, 2006 Author Report Share Posted May 11, 2006 Cant access volume or Cant access backup client. The servers are Windows 2003 server. Link to comment Share on other sites More sharing options...
martyrs29 Posted May 11, 2006 Report Share Posted May 11, 2006 Hey Rusty. Does this happen if it is the only execution unit running? In other words, are there several executions running when this seems to happen? What version of Retrospect is running on the client? Link to comment Share on other sites More sharing options...
rustyjones40 Posted May 11, 2006 Author Report Share Posted May 11, 2006 I dont know, my backups run all night. There is about 100gig in changes a day so there is almost always 2 backups running, I sometimes have 8 running at the same time. The clients are 7.5.116 dated 2006-04-27, the server 7.5.251 dated 2006-02-07 Link to comment Share on other sites More sharing options...
martyrs29 Posted May 12, 2006 Report Share Posted May 12, 2006 Hey Rusty. Thanks for this info. Are you backing up to a NAS or SAN? I've seen the issue you are referring to when I have several (usually four or more) executions running where they all are accessing the same NAS. This problem disappears, however, when I moved the backup sets to a SAN. I'm not sure if it was a throughput issue, and IO issue, or what, but that was my only fix for that problem. I don't think it was a throughput issue, as both the backup server and the NAS it was connected to were utilizing Gig NICs connected to a Gig switch. Then again, I'm still not ruling this out. Link to comment Share on other sites More sharing options...
Guest Posted May 15, 2006 Report Share Posted May 15, 2006 I also have this same issue. I am using Retro (7.5.251) to backup about 10 servers and 60 or so clients to a local RAID on the backup server, and every day one or more clients will fail. Doesn't seem to matter what Windows OS they are running. The retro client needs to be restarted so the server can access it again. This has been happening ever since version 7.5 came out, and sadly, EMC has not fixed the problem yet even though they just released a new client 7.5.116... Link to comment Share on other sites More sharing options...
ComputerX Posted May 17, 2006 Report Share Posted May 17, 2006 Me Too. I have a batch file that restarts the service on all clients a few minutes before I do a regular backup. That has solved the problem for desktops but laptops still don't get backed up. I just scheduled the script to run every two hours during the day but I am afraid of what is going to happen when I restart the client service in the middle of a backup. It feels like that would be a Very Bad Thing . Dan Link to comment Share on other sites More sharing options...
fifolifo Posted May 18, 2006 Report Share Posted May 18, 2006 I don't mean to pile on here, but this is a serious issue. As stated in this thread, this problem began with the 7.5 version of Retrospect. I'm running into the same issue since I upgraded to 7.5. I'm running Retrospect Multi Server 7.5.251 on Windows 2003 Standard server. The bulk of my backups are written to disk with a weekly dump of the disk stores to an lto3 autoloader. I just came to the site to see if a newer windows client had been released. I was excited to see the 7.5.116 client release, but I see from a post on this thread that this client does not resolve this issue. I've been using Retrospect Multi Server since 2003 and have been for the most part a happy user, but this is a BIG problem. Please address it. Link to comment Share on other sites More sharing options...
rustyjones40 Posted May 18, 2006 Author Report Share Posted May 18, 2006 So I dont seem to be the only one having this issue. I backup to a local RAID on the server Retrospect is installed on. Its a 7.5 TB array. I have thought about setting up a script as mentioned by Dan. Maybe I will give it a try. But if it is a bug, it needs fixed. Link to comment Share on other sites More sharing options...
Guest Posted July 5, 2006 Report Share Posted July 5, 2006 It would appear that the latest update to the Retrospect Server (ver 7.5.285) seems to finally address this issue. I have not had to restart the clients on our servers since the update (which was about two weeks ago). Thank you, EMC (finally!!). Link to comment Share on other sites More sharing options...
PhilP Posted July 15, 2006 Report Share Posted July 15, 2006 I just installed the latest versions of 7.5 on my server and clients and I still have this issue. Link to comment Share on other sites More sharing options...
Fulco Posted July 17, 2006 Report Share Posted July 17, 2006 Same here. Fulco Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.