Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About l.s

  • Rank
    Occasional Forum Poster
  1. Hello, I run into the following problem and it is still around with the latest Retrospect version. The latest snapshots are supposed to be transfered from more then one disk backup set to a tape. The Checkbox for ejecting media is set. What happens is that after all data from the first backup set are transfered, the media is ejected. Retrospect then starts to wait for the tape it just ejected to transfer the remaining data. Is there a way around this or is that considered to be a bug? Regards, Lars
  2. l.s

    what a nightmare!

    I have a similar problem regarding the activation of the SQL Server Agent: http://forums.dantz.com/showtopic.php?tid/32734/ I'm totally running out of ideas. Regards, Lars
  3. l.s

    Retrospect 7.7 cannot use LTO drive?

    Just an a note: Same not responding problem occures here with Win2k8 and a VXA-3 drive connect via parallel SCSI. Regards, Lars
  4. Is there a way to change the path of the folder 'RtrSec.dir'? I really would like to get possible huge temporary files of the system drive. Regards, Lars
  5. Location of the User Profile varies depending on Windows Version and language. the environment variable %appdata% points to the folder for applications settings that are synced with the server when roaming profiles are used. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\ProfilesDirectory is the registry key where you find and configure the location of the profile folder for the current installation. Regards, Lars
  6. Best is it to move the .pst file to a folder that is on the server or copied there via roaming. It then can be backuped together with the user profile from the server. When you move the pst file to a different location for an existing user, Outlook will ask at the next start for the now missing .pst file. Regards, Lars
  7. Do you have a domain/active directory running?
  8. Sorry I posted to early. The eject option is set for the script. The corresponding options in the application settings are at their default values. I would expect retrospect to eject the tape after all work defined in the script is done. At the moment it ejects once afer every copy operation of a source. And there is no error in the log. It finish copying from the first source, checks the data and then ejects the media. Afterwards it waits for the same tape it just ejected to continue with the remaining source sets. All from whithin one script. If the eject option is disabled, the operation works as expected. Regards, Lars
  9. When running a script that transfers snapshots from two backup set sources to a third destination set (two different disk sets beeing copied to one tape set), Retrospect ejects the tape after copying/comparing the first source is finished. So in the middle of a script? That can't seriously be working as intended? Regards, Lars
  10. I'd run the tests with 7.5. The problem persists there. Is there any possibility to get hold of a newer version where the problem might be fixed? Regards, Lars
  11. Hello! What is really badly missing (and regarding the post I found in the forum, it is not only for me and my customers), is an option to select multiple backup sets as targets of a scripted event and run the backup on the first target that shows up. Why this is needed: A lot of small companies have no changer avalible to rotate the backup media in a relyable fashion. Instead they have a pool of media they want to backup to and interchange them when they feel like it or rember to think of changing the media in the first place. That might be tapes, disks USB sticks or what ever. The important part is, the the backups keep going regardless what media is connected to the backup server - without any further user interaction. At the moment Retrospect expects that one sets up a certain routine for changing media as a script can allways have only one target. Is the scripted target not avaible, no backup will take place. Which is actually the absolute worst case that can happen. To fix this with the current Retrospect logic I would like to see the allready above mentioned option: When a script is set up, you should be able to select more then one backup set as target and let Retrospect execute the script with the first target it finds. Or when you allow the different selectable target sets to be sorted by priority, use the accessible target set with the highest priority. This way there would allways be a backup, as long as at least one set is accessible to the backup server. I'm aware of the fact that this can basically be realiced with running multiple parallel scripts to different targets with a small time offset. But when doing this, lots of error emails are generated and the history is flodded with errors, even when a successfull backup took place. With best regards, Lars Sölter
  12. I reverted the installation to the latest 7.5. When trying to run a backup with 7.5 on the 'full' reporting disk set, it reported 'full' too. I have now 7.5 rebuild the set from disk and will check if error reoccures. Could it perhaps be that the error you fixed in 7.6 was allready present in one or the other form in 7.5? Regards, Lars
  13. Thanks, I will have a look at the older version then. Regards, Lars
  14. Thanks for the clarifying answere. But know I'm kind of confused. Say every day the latest snapshot from a disk set should be copied to a tape. The only userinteraction should be the changing of the tapes. How is this realiced? As when a tape gets kicked from a set, it still has it's old name and so will not be accepted for a backup unless it is formated manually. At least as far as I understand. Regards