Jump to content

dad4zeus

Members
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dad4zeus

  • Rank
    Newbie

Profile Information

  • Gender
    Not Telling
  1. dad4zeus

    Time zone handling wrong in email

    Add me to the list. Have two Retrospect 9.0.2 (107) servers and both have this bug. It is extremely annoying when away from the office and I'm trying to verify when the backup finished. Any hope of this being fixed?
  2. Russ, Yep during the clone I made sure all services were off and even rebooted in safe mode to do the clone. But I have more news. At lunch time I lucked out in being able to have some down time for that server, so I updated it from OS 10.4.8 to 10.4.11. Rebooted, turned all the services that we use back on and tried to run the backup again. It ran perfectly. First time in 16 days. I double checked my notes and that was when the drives were swapped out with the 500 GB ones. The previous backups before that ran just fine with server 1 being 10.4.11 and server 3 being 10.4.8. Maybe the update corrected something on the boot volume, I don't know. I did check the Startup Disk settings, nothing was selected, and this was after the successful backup. I clicked on the proper volume anyway. Any guesses on why this worked? I am not going to call this fixed untill it backs up for a week straight. Thanks
  3. I have three Xserves too. Xserve 1 is a Dual 2.3 GHz PowerPC G5, 1 GB Ram, OS 10.4.11. It backs itself up, one drive partitioned, one small partition of 10 GB and another partition of 450 GB. Xserve 2 is a Dual 2.3 GHz PowerPC G5, 1 GB Ram, OS 10.4.11. It backs itself up, two volumes, one is 76 GB and the other is a RAID 5 array of 3 TB with about 1 TB of data on it. Xserve 3 is a 2 GHz Dual-Core Intel Xeon, 3 GB Ram, OS 10.4.8. It is a Retrospect client and is backed up by Xserve 1. It has two volumes, the boot volume is 40 GB with 24 GB of data and the Data Volume is 35 GB with 5 GB of data. Retrospect version 6.1.126 on both Xserve 1 and 2. Client version 6.1.107 on Xserve 3 and it is backed up by Xserve 1. Both Xserve 1 and 2 use Firewire removable drives and use either 500 GB of 750 GB drives as the backup media. Server 1 and 2 are just file servers. Server 3 is a file server and Pop Mail server. Only about 30 users. All three xserves mostly just idle along, they are never pushed hard. This backup setup has worked for over 2 years without problems. An occasional bad backup drive but that's just a bad drive. Two weeks ago I needed to put bigger drives in Xserve 3 since it is the mail server. I shut down all services and rebooted in safe mode. I used Carbon Copy Cloner 3 to clone the boot volume to a new firewire drive and copied the other volume to it's own folder on that drive (just data). Rebooted from the firewire drive to be sure it worked. It did just fine. --------------- Keep in mind I have used CCC to do stuff like this for years without a problem for client Macs and many servers. -------------- I then shutdown the server. Pulled the two original mirrored drives. Swapped with Seagate Barracuda 500 GB drives, ones that are used in servers. Booted from the Firewire drive in safe mode. Used Disk Utility to create mirrored partitions. The boot volume is 400 GB with 24 GB of data and the Data Volume is 55 GB with 5 GB of data. I then cloned the boot volume back. Copied the other data to the smaller partition. Rebooted and turned each service back and and tested. All works great for the users. THE PROBLEM Since then I get the dreaded 519 error, network communication failed. What is interesting is Xserve 3, the Retro client, has two volumes, if I put the Data Volume that is 35 GB with 5 GB of data first and the boot volume second in order of backup, the Data Volume backs up just fine, it stops on the boot volume during scanning. WHAT DOES THIS ALL MEAN? My network is just fine. My Xserve 1, 2 and 3 are just fine. The boot volume on Xserve 3 changed somehow by being cloned. Every time this happens I launch Activity Monitor on Xserve 3 and a service called PITOND is pegged at 99% or 100%. If I force quit I then have to Launch the Retro Client and turn it back on. What did cloning the boot volume do to affect Retrospect? Before I did that this setup has worked for 2 years. Nothing else has changed. Have looked at all the various posts on this and read the 519 Trouble Shooting page. Nothing helps yet. I am planning on upgrading to 10.4.11 later today. Any insight would be very well appreciated.
×