Jump to content

powermeck

Members
  • Content count

    29
  • Joined

  • Last visited

Community Reputation

0 Neutral

About powermeck

  • Rank
    Occasional Forum Poster
  1. We are using Retrospect Multi-Server in several similar environments. All the networks that we use Retrospect on are basically Fast Ethernet, with Fast Ethernet / Gigabit switches on the backbone. Retrospect Multi-Server was originally running in version 6.0. An upgrade to 6.5 brought all the desired advantages. Backup speeds for Windows and Macintosh clients (both servers and workstations) leveled out at 400-500MB/min.; some really fast Windows servers even delivered close to 900MB/min., which I found quite impressive. Now, with the upate to Retrospect 7, and recently to 7.5 I found that the backup speed for the Macs had radically dropped, while the backup speed for Windows clients improved by about a third. I updated all Retrospect clients (7.5.1.1.6 on Windows and 6.1.130 on OS X, which I think is the latest), yet the Macs rarely deliver 50MB/min., most of the time crouching around at <20MB/min. As the Macs (Dual G5s) are all equipped with GB cards I schlepped them over to the server room and connected them to the same managed GB-switch that the backup server is on (using Cat6-cable of course). The backup server is running a GB-card too. Still, no improvement. Currently I see Retrospect backing up a Macintosh at 17.6MB/min. I have tried both backup to tape and backup to disk, yet the result stays the same. I'm befuddled, to say the least Please throw any questions and suggestions at me; I'll try them in our lab and let you know what happens. Cheers, Karsten
  2. powermeck

    Retrospect 7.5 Released

    Thanks, Foster, that's what I thought. I do have advanced tape support, and I have set up Retrospect the way you described. cheers
  3. powermeck

    Retrospect 7.5 Released

    Does Retrospect 7.5 stream data to a multitude of drives within a library? Specifically: Neo Overland 2000 with two LTO drives. Thanks
  4. And here is what happened: While creating the snapshot Retrospect halted at several files for about two minutes. During each of these halts the file 'RetroSec.dat' grew by 1 to 1.5 GB for each file, which filled up drive C after four to five halts - obviously Retrospect had difficulties handling these files. I resolved this by re-creating the directory structure for each of the ten files that Retrospect halted at, and by moving all files from the respective directory to the new directory. I am glad I could solve this, still I wonder why these files - or directories - confused Retrospect. I could open, modify, duplicate, move and rename the files without any problems; they did not show any signs of corruption, and the file and directory names were absolutely regular. Oh, well
  5. powermeck

    Duplicate the Retrospect Folder

    If my memory serves me correctly, directories bearing the name 'Retrospect' were excluded from backing them up on purpose, in order to avoid backing up a directory that is being written to at the same time. This can be quite a pitfall when you first back up to disk, then to tape, or as in your case to a duplicate disk - those directories will never make it. A while ago natew posted a workaround for this, but I cannot find it at the moment.
  6. Using Retrospect 6.5 Multi-Server we are backing up multiple servers across the network. Only when backing up one specific volume, which is attached to the Retrospect server we receive the above error message. This error started showing 3 weeks ago without any major changes on the network or on the server. The Retrospect server is running Windows NT SP6a Installed RAM is 1 GB with about 800 MB available while backing up - no other apps running All volumes are formatted as NTFS Drive C has 4.5 GB free The catalog file (on C:) is about 300 MB in size The affected volume has 110 GB free, with 210 GB used (6,000 folders, 30,000 files) The target device is an LTO tape library All drives are defragmented to almost no fragmentation. CHKDSK reveals no errors. Thank you for any hints or questions.
  7. Mark, you are correct about stopping Retrospect and moving the files. The recycle backup though does not continue with incrementals, instead it starts with a baseline backup. The idea of a recycle backup really is to dump the catalog before it gets too big and start over from scratch. In our backup scenario we do a recycle backup every Friday night while rotating weekly between three backup sets. hope that helps
  8. Simon, I don't think you're missing anything, and I think you gave the answer in your first post: installing a secondary drive into the Neo will probably double the amount of data that you can back up in a fixed time frame.
  9. powermeck

    Any Help Appreciated with retrospect :)

    Quote: The other problem which i am having is if this happens, i log in remotely to the windows box via RDP and try and open retrospect and it says sorry retrospect is in use arggg i know it is because its caught up on some muppet not changing the tape. The only solution to this that I can think of is to use PCAnywhere from Symantec. PCA actually lets you work with the one existing session instead of opening a new one like RDC. I like both, but PCA works better for me with servers running Retrospect.
  10. I have updated the 39160 driver to version 1.2 on the affected Macs running 10.3, turns out the backup with Retrospect runs absolutely smooth since the update. Thanks again for the hint, Steve.
  11. Quote: Maser said: I've not seen this in the forums yet, so... Panther (Mac OSX 10.3) has the *1.1* drivers for the Adaptec 29160/39160 cards. It *will* overwrite the current (and necessary) 1.2 drivers available on the Adaptec site if you upgrade. I guess that would also explain why my backup attempts of a G4 running Panther and a 39160 card with two hard drives attached to it keep failing. I keep getting -540. Will keep you posted after I have updated the drivers. powermeck
  12. powermeck

    Too much data on backup set?!

    Interestingly enough I received the same 576 GB message last night. The concerned machine is a Mac running OS X; the concerned drive is one that had failed before - difficult to mount, volume structure getting corrupt, and so on. Seems like the drive is reporting an insanely high amount of data due to being corrupt. I'll move all data off the drive and turn it in for replacement immediately. cheers powermeck
  13. powermeck

    empty folders not deleted after file move(delete

    I had something similar happening, whereas in my case the folders were not completely empty - some folders contained an invisible .DS_Store file, which OS X clients had created. Maybe that applies to your case? Just a thought
  14. powermeck

    Too much data on backup set?!

    The problem might actually be on the client side... and as you asked for wild guesses, here are some: - boot the iMac from it's OS 9 CD and examine the hard drive with Disk First Aid - upgrade to 9.1 (I never trusted 9.0) - get a system tool like Disk Warrior and rebuild the volume structure good luck
  15. Recently Retrospect 6.5 MultiServer on NT4 began stalling on me repeatedly. It would not execute scripts anymore, just sit there and stare at me. When I try to quit Retrospect (using the File-Quit command, of course), I would get the sandwatch for hours without any change. Using the Task Manager I then tried to quit all Retrospect instances, but to no avail - they stayed in the task list, running. My only choice is to reboot the server, which takes forever due to all the SCSI-devices attached. Where do I begin?
×