Jump to content

askirkland

Members
  • Content count

    21
  • Joined

  • Last visited

Community Reputation

0 Neutral

About askirkland

  • Rank
    Occasional Forum Poster
  1. I have upgraded these OSX clients to 5.1 and I am still having the issue of the server locking up. It would not be such a big deal, but the server's proc usages hit 100% and I have to manually recreate the backup set from tape everytime this happens. Any other ideas?
  2. Server: Win 2000 5.00.2195 SP4 Retrospect Multi Server Edition V 6.0.206 Clients: Apple PowerBook G4 OS X 10.3.5 Retrospect Client for OS X v5.0.540 I only have a few OS X Clients... but it seems to happen on all of them. It seems to occur if they disconnect from the network or sleep while backing up. Thanks!
  3. I have an issue with my Win 2000 Server running Retrospect Multi-Server v6.0. The server seems to hang if/when OS X Client Sleeps / Disconnects from network during backup. I am using Proactive backups. The server's proc usaga spikes to 100% and the only way to stop it is to kill the retrospect server executable. Then to add insult to injury; I then need to recreate the backup set from tape as the crash causes the backup set to become out of sync. Occasionally I get an error -519 after I kill the retrospect executableI have an issue with my Win 2000 Server running Retrospect Multi-Server v6.0. The server seems to hang if/when OS X Client Sleeps / Disconnects from network during backup. I am using Proactive backups. The server's proc usage spikes to 100% (+95% is retrospect.exe) and the only way to stop it is to kill the retrospect server executable. Then to add insult to injury; I then need to recreate the backup set from tape as the crash causes the backup set to become out of sync. Occasionally I get an error -519 after I kill the retrospect executable. I have tried checking my OS X network settings… I have adjusted the DHCP lease times… anything else to try?
  4. askirkland

    Fast Laptop Backup

    ?
  5. askirkland

    Fast Laptop Backup

    I have a number of OS X laptops on a wireless network that need to be backed up. They have anywhere from 10GB to 40GB of data each. Mostly video, images, and PowerPoint / Keynote presentations. I have another OS X Tower with about 500GBof data with a wireless connection (could be wired to 100mbps net) that needs to be backed up. These laptops are not in the office everyday or overnight ever. Is there a good way connect these via Firewire to and external backup server? (Without having to take the laptop running target mode and manually connect another computer with some storage. I was also thinking about getting some external Firewire drives and making images of the laptops... then bouncing this image to tape. Then wipe the drives for the next laptop archival. Can anyone think of a good... very fast... semi or completely automated way of accomplishing this? Info - I have an airport extreme wireless network connected to a 10/100 wired network. One of the laptops has a airport extreme card in it… I currently have a win2k server running Retro Multi-Server v6 with an 8 tape DDS4 autoloader running all day and night on the network for other clients. Thanks! Spence
  6. askirkland

    6.0 to 6.5

    Darrin, What are your talking about with your multi-tape recycle issue? I have multiple tape backups and recycle them every 6 weeks... I have never had an issue where the backup job sits and waits for me to hit proceed. Am I misunderstanding you? What is your config and backup type... possibly there is some other work around... Oh yeah... I have been burned by Dantz's version upgrades a couple times already... Seems like the upgrades are getting more frequent and more costly over the years. I think I'll wait, until I find some real reason to upgrade... -S
  7. FYI – Airport Users There are some issues that older Apple Airports are having with their capacitors and overheating. I have an Airport that is having these problems. (I am sending it to Apple for replacement…) How does this affect Retrospect? This has caused my Retrospect Server to crash. I am running Retrospect Multi Server v6 on Win2k SP3. When my server tries to scan files to backup on a windows pc (via airport) it just times out with a -519 error. However when it tries to backup a Mac (OS 10.2.3 w/ current Retrospect Client), it locks up retrospect.exe and uses all available processor cycles. I have had to hard reboot my server 4 times in the past 2 weeks… every time it tries to backup a Mac via the Airport. Hard reboots during a backup job have caused my backup set catalog to be out of sync. Updating the backup set does not fix the problem. I have to erase the last tape in the backup set (which removes it from the backup set catalog automatically) and resume backups to that tape by letting Retrospect add it back to the set. Today I swapped out my bad Airport (Graphite) with a new Airport Extreme… took care of all my Retrospect issues with my wireless users. More info: http://discussions.info.apple.com/WebX?14@244.VJnKawsSmGi.0@.3bc31555 http://www.vonwentzel.net/ABS/ http://airport.tber.com/infopg.html
  8. Update - Issue resolved. I checked with Dell for a driver update for the Intel Pro 1000 integrated NIC... downloaded/installed it. Now the backup seem to be working ok... no more Assert Log errors. Thanks for the help...
  9. I think you can do this with task scripts with Retrospect (depending on you flavor of Retrospect, I have Server version 6)... look in the help "index" section of your retrospect Search: External Scripts, Email Notifier I was unable to get this to work because of my current mail server setup, but it is supposed to work.
  10. askirkland

    Unattended

    I have 2 servers in different locations running backups running during the day for laptops... the backup definitely slows down the computers quite a bit, especially during the snapshot creation. A pain but necessary... Also the 2 servers run backups all night to get all the workstations. My backup sets are about 5 to 6 DDS-4 20/40 GB tapes each per server. I use an autoloader, so I just load them up once a week... I usually fill up the extra slots with a blank (allow for backup set growth) and the first tape (and second... if space) of the next backup set in the rotation. This makes it so I don't have to be there to swap tapes on Saturday. I think you are right on the backup set creation idea... I could have created them all at once. In case you didn't see this tip... might help, although I am not certain it works yet... just changed my scripts to incorporate this technique. web page
  11. askirkland

    Unattended

    You just need to setup your backup to do a recycle of the backup set you want to reuse. My backup runs with 6 backup sets that I have already created... Day 1 of Week 1 - Run Recycle to Backup Set A Day 2 thru last day of Week 1 - Run normal mode to Backup Set A Day 1 of Week 2 - Run Recycle to Backup Set B Day 2 thru last day of Week 2 - Run normal mode to Backup Set B Etc... I did have to supply blank tapes for the first round of rotations... then I label the media with the appropriate tape # and Backup Set name. Kind of a backward way of doing a rotation/recycle, but Retrospect is kind of basic in this way. Hope this helps…
  12. You are not alone... I'm having the same and other similar problems. My current workaround is to manually backup my problem workstations... and remove them from my automatic backup schedules... pretty lame but at least I know when retrospect crashes and I can restart it... and it doesn't interfere with all my other clients’ backup schedules. I have 2 machines that get the -3102 NIC adapter error... same NICs... could both be bad or does Retrospect not support Dell integrated Intel Gigabit NICs?
  13. I use Retrospect v6 for Windows multi server... I need to speedup the backup process for remote OS X clients. Any ideas on what would be a list of directories that I should include in my daily OS X backup routine? I.e. users, documents, etc... I need to scale back my backup to just include what I can't get back from reinstalls. This backup will be for OS X laptop users over WIFI... too slow to backup everything reliably… can’t do it @ night either. Would it make more sense to buy some other backup device, and have these users do their own backups locally via Firewire or something? Thanks!
  14. Is there a way to write a proactive backup so it will cycle through multiple backup sets. i.e. Week 1 - Monday recycle set A; Tues - Sat normal backup to set A Week 2 - Monday recycle set B; Tues - Sat normal backup to set B Week 3 - etc... Also, can a backup script (normal) start on a monday and go through the following sunday. (not sunday through sat.) Right now I have to change the script to use the next set and manually recycle the set when I cycle the next set of media into the server.
  15. I tried backup/volume scan from my other Retrospect server... same version of retrospect. It does not seem to have the same problem. However this is not an exact comparison, as it connects over VPN via T1. But I would think if this were really a -3102 error (network card) it would show up with the slower connection too. I have this problem consistently with 2 new desktops that I recently added. They have never worked correctly with this server. These are the first 2 WinXP Pro workstations that I have tried to backup with this backup server. However, I tried to backup my laptop (w/ winxp pro) from the problem server, and did not have the same problem. This was also over VPN via T1. (Just got an elem.cpp-861 error on problem server connecting to problem client.) It seems to be a server side issue to me… Thanks!
×