Jump to content

TSM

Members
  • Content count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About TSM

  • Rank
    Occasional Forum Poster
  1. Hi Scott, I haven't had the time to test this yet. There was no mentioning of a bug fix in the release notes... Kind regards, Henrik.
  2. I've been all over the forums to try and figure out if this bug is picked up by EMC. I'm sorry if this is all ready answered, but I ask if someone with the means can confirm this. Several threads on this forum talks about the same problem - this is easy to reproduce: If you make a backup that uses Media Verification (the MD5 thing) and the backup spans more than one media (I've tried disks and tapes, others on these forums have tried DVD's - same result) then Retrospect only recognizes what ever is on the last media. Everything that is all ready backed up on the other media (all media except the last) is backed up again. If I do the exact same backup with Thorough Verification then everything works as it should. I'm using Retrospect Multi Server 7.5.324, RDU 7.5.9.102, Windows Server 2003 R2 with the latest patches. Any help is kindly appreciated. Happy holidays to everyone that celebrates Christmas :-) Kind regards, Henrik
  3. Hi AndrewA No - the files are not changed. This is confirmed. I now believe this is a bug in the MD5 checksum verify functionality when the backup spans more than one medium. This is easy to reproduce: If you make a backup that uses Media Verification (the MD5 thing) and the backup spans more than one media (I've tried disks and tapes, others on these forums have tried DVD's - same result) then Retrospect only recognizes what ever is on the last media. Everything that is all ready backed up on the other media (all media except the last) is backed up again. If I do the exact same backup with Thorough Verification then everything works as it should. I'm using Retrospect Multi Server 7.5.324, RDU 7.5.9.102, Windows Server 2003 R2 latest patches. Kind regards, Henrik
  4. Hi there. Using Windows 2003 R2, Retrospect Multi Server 7.5 - all the latest patches. Backing up to a Tandberg Superloader LTO-2 SCSI. Using the Open File backup add-on. Suddenly - when starting af new backup-set, Retrospect will offcourse backup everything the first time. But when the backup starts again the next day, Retrospect feels the need to backup almost all data again? And the data has not changed. It's not everything the second time. Only around 90% or so. I don't understand. This only happens when the source is "big" +100Gb, +100,000 files. I've been using Retrospect for many years - I've never seen this before? Please help - any suggestions are welcome. I am unable to backup at the moment! TIA, Henrik
  5. Hi there. I'm using the latest Retrospect Multi Server for Windows on my backup-server and trying to backup several other servers with the Retrospect Client. I also have the Open File Add-On. With one of the "client" servers I'm getting a lot of -1017 errors. I'm wondering with what permissions is the Retrospect Client running on the server? Event though Retrospect on the server is running as a given Administrator - can I control with what permissions the Client is executing? This particular server is not a member of the Domain - the rest of the "client" servers are - as well as the Backup Server it self. The Backup Server is running as a Domain User with admin-privs - maybe this is the problem with the server outside the domain? Please advise... TIA, Henrik.
  6. Quote: Quote: Does the loader have bar code support? Do the tapes have bar codes on them? Do the barcodes start with "CLN". Try disabling Bar code support on the loader and running a device scan with Retrospect. Yes the device has barcode support and the tapes have barcodes. Retrospect correctly shows the barcodes (even asks for tapes with given barcodes when they are not in the drive). Yes the barcodes start with CLN - is this bad? [feeling wierd] Oh - My - God! CLN - CLeaNing tape? Does the barcode that begins with CLN designate a Cleaning Tape??? All the labels that came with the tapes says CLNXXXXX... Is this what confuses Retrospect? Kind regards, Henrik Otterstrøm
  7. Quote: Hmmmmmmm, Try this: Close Retrospect and move the retro.config file (in the Retrospect preference folder) to another location on disk. Then launch Retrospect again. You will be prompted for your license code. If Retrospect asks if you want to import old preferences say "default". If the problem persists you can close Retrospect and move your old config files back into place. Does the loader have any emultation modes? Make sure it is set to run in its native mode (not emulating another device). Does the loader have bar code support? Do the tapes have bar codes on them? Do the barcodes start with "CLN". Try disabling Bar code support on the loader and running a device scan with Retrospect. Thanks Nate I have tried the config file move you suggest. I have also completely de-installed Retrospect and installed it fresh again several times. This does not help. I dont think I can emulate any modes with my Superloader. Yes the device has barcode support and the tapes have barcodes. Retrospect correctly shows the barcodes (even asks for tapes with given barcodes when they are not in the drive). Yes the barcodes start with CLN - is this bad? I have no idea how to disable the barcode reader except for taking the Superloader apart and removing some cables. Kind regards, Henrik Otterstrøm
  8. Quote: If you have time, shut down the machine, change the IDs on the loader, shut down the loader, wait 30 seconds, boot the loader, wait till thats done then boot the computer. I follow this procedure (reboot of Xserve was necessary) and have tried ID 2 for the drive and ID 5 for the library and vice versa. Theres is no change in the way Retrospect sees the tapes - thay are all still Cleaning Tapes in the Library, and usable once (manually) moved to the drive. Help And thanks for your time so far! Regards, Henrik.
  9. Quote: SCSI Voodoo my friend. Changing IDs shouldn't make any difference but it does help in a lot of cases. I would try Drive at 2 loader at 5 and vice versa. You can tell Retrospect to reinitialize its device data by clicking on initialize elements from the device menu at the top of the screen. Allright - I'll try this right away. (So I should not need to reboot the Xserve after changing ID's? Reinitialize device data is sufficient?) Regards, Henrik.
  10. Quote: Sorry - my mistake. That is the other card that Dantz supports for Panther. Quote: How does this device show up in the configure->devices->device status window in Retrospect? Does it show one entry for the tape drive and another for the loader? Make sure to doublecheck termination and cabling. Have you tried changing the IDs of the loader and tape drive? It is shown as to separate entities: SCSI-A:4:0 QUANTUM UHDL 000F Quantum Library (5.02) SCSI-A:5:0 HP Ultrium 2-SCSI F45Z HP Ultrium Gen 2 DC (5.04) This is also the case in the configure->devices tab; the HP Ultrium drive is sort of enclosed in the Quantum Library (can I attach a picture in this forum?) And I have doublechecked cable and termination. I have not tried changing SCSI ID - should that help? What ID's should I try? The crazy thing is I can drag a tape (wrongly marked as a Cleaning Tape) from the library and to the drive. After a while the tape shows up in the drive with the correct name and is usable hereafter. It's just that Retrospect cant do this automagically during backup - proberbly because it thinks the library only contains Cleaning Tapes... Regards, Henrik
  11. Quote: Is this a SCSI device? If so what SCSI adapter and driver version are you using? At the moment Dantz only supports the ATTO UL3S/D and UL4 cards in Panther. Yes this is a SCSI device. It's the Xserve G5 with the Apple BTO SCSI card option. I believe it's a LSI Logic thing. Are you telling me Retrospect will not be able to control the Tandberg Superloader in this configuration? Regards, Henrik
  12. Quote: Quote: Well - I discovered I did not use the latest Retrospect 6.0.193, so I upgraded and tested again. What version of the RDU (Retrospect Device Upgrade) are you using? Dave I'm running Retrospect 6.0.193 (includes an updated Device Access bundle version 1.0.5), Retrospect Driver Update 5.6.102 on an Xserve with Mac OS X 10.3.4 (latest everything). Any ideas? Regards, Henrik.
  13. Well - I discovered I did not use the latest Retrospect 6.0.193, so I upgraded and tested again. Unfortunately it is the same - Retrospect does not see the tapes in the loader (calling them Cleaning Tapes) only the tape in the drive is usable. If anyone can help please do so. This is a real problem for me. TIA, Henrik.
  14. Running Retrospect 6.0.178, driver update 5.6.102 on an Xserve with Mac OS X 10.3.4 (latest everything). I'm trying to this up with a Tandberg Superloader (Quantum Library, HP Ultrium drive). This should be fully supported according to Dantz website. No matter what I do, Retrospect only recognizes the tape in the drive - all the tapes in the library is seen as Cleaning Tapes, and Retrospect cannot autmatically load a tape from the library? I basically only have a single drive available? Any help or suggestions is highly appreciated! Regards, Henrik.
  15. Problem seems to be solved now... I've had problems with my network after installing 10.2 App's takes forever to launch (bounces and bounces), returning from sleep can take several minutes, getting the password dialog to get out of the screen saver can also take several minutes. I was getting errors like this in the console: Sep 2 12:38:57 hot netinfod local[264]: unable to bind to parent - RPC: Timed out I postet this to the Apple Discussion board ('Jaguar and Netinfo errors') and got this response from Charles Lloyd: 1) launch the "Directory Access application" (/Applications/Utilities/Directory Access). 2) under the "Services" tab, uncheck the "Netinfo" option. 3) logout and login again. This solves my problems alltogether! Perhaps this will cause some other issues, but for now everything seems fine... Best regards, Henrik.
×