Jump to content

retro1

Members
  • Content count

    28
  • Joined

  • Last visited

  • Days Won

    1

retro1 last won the day on July 24 2015

retro1 had the most liked content!

Community Reputation

5 Neutral

About retro1

  • Rank
    Newbie
  1. Is the recommended way to use group policy? If so is there some instructions on how to do this? We have a Windows domain running windows 7 clients with the users logged in with standard non-admin accounts so it appears Retrospect won’t be able to update the clients. I’m running Retrospect multi-server 10.5 on Windows Server Also got a number of Macs connected to the same domain with the same problem. Thanks
  2. Thanks Phil, i'll see if I get any other replies.
  3. Hi Phil, Thanks a lot for your thoughts on your upgrade. When I had a look earlier on the Retrospect website it mentions speed increases of up to 200% for certain tasks, which seems impressive. Glad to hear it’s been stable, that's the main thing. Did you upgrade straight to 10 from 8.5 or did you upgrade to 9 first and then 10? Also did you have to upgrade all the retro clients for them to work with 10 or do the older clients work with 10 as well?
  4. Hello all, We are currently using Retrospect 8.5 multi-server. I've been receiving a popup telling me that Retro 9 and 10 are available to download. My question is how reliable\stable is Retrospect 10 compared to 8.5? New features are great but my number one priority is stability and then performance. Any advise appreciated. Many thanks.
  5. Hello again Lennart, The backup set is indeed a disk based type. This all seems fine a bit of a faff, easily solved by allowing multiple snapshots to be forgotten at once (shift-click). The second option certianly sounds better, think i'll go with that. Thanks
  6. I have a single backup set that holds the backups for a number of computers. Something like this. The following computers… Computer 1 Computer 2 Computer 3 Computer 4 ..are backing up to… Backupset1 Now let’s say Computer 3 has been disposed of and therefore no longer needs to backed up. How do I go about removing that computer from Backupset1 and archiving the data somewhere else? I’ve noticed the Transfer snapshots option which allows me to copy selected snapshots to a new backup set. So I can see how to get the data out but then how do I delete it from backupset1 after I’ve copied it out? Does the forget option simply hide the computer or does it actually remove the data and free up space, which is what I’m after? Is this the recommended way to archive data from backup sets once computers no longer need to be backed up?
  7. OK i'm going to monitor the backup report over the next few days to see what happens. I noticed today that one system has gone up to two days now. I appreciate your help guys, many thanks.
  8. Ah now I see the columns, thanks JoTraGo. I've configured the report as you suggested but i'm only seeing a figure under elapsed days for systems that have backed up today\yesterday (either a 0 or a 1). The other systems just don't have anything listed next to them. For instance looking at one particular computer, if I look at the backup set for this system, under snapshot, the last time it created a snapshot was the 14/05/2014 yet it doesn't show anything under the elapsed days column. Shouldn't I be seeing figures next all these based on when they last backed up?
  9. Indeed, it maybe something critical or may not. That's why I want a list of all computers that haven't backed up in x number of days. This way I can determine if a system just had a one off error (someone turned the comuter off) or if there's a persistant issue. Lennart do you see the "Elapsed Days" column in your backup report window? I think this would be the answer for me.
  10. Lennart I get a lot of -519 errors, that's really what I meant. Retrospects working on those machines but something prevented it from completing. These are the ones i'm interested in. JoTraGo where is this "Elapsed Days" Column? This sounds like it's exactly what i'm after. The only columns i'm seeing are: User/Volume Errors, Warnings Backup Set Script I’m running Multi Server version 8.5.0
  11. What’s the best way to monitor Retrospect for serious problems? For instance if a computer completely stops backing up? Nearly all my systems run on a proactive schedule and I get multiple errors every day relating to computer’s not backing up. A lot of the time it’s simply down to the system not being active at that particular time when the proactive backup tries to run. It’s then usually picked up later that day or the following day, so it’s not something I need to worry about. What I’m after are the ones that I do need to worry about, the ones that haven’t backed up in a few days and have a permanent failure. How would I go about getting this information from Retrospect? The backup report just seems to show me if a client backed up last time it ran and doesn’t show me any history to work with.
  12. Another Retrospect failure

    I don't see how they can say not being able to backup open files is optional when doing a full system backup. The way I see it the open file add-on is mandatory and IS a prerequisite.
  13. If it's not a prerequisite then how can you do a full system backup without the ofo add-on? As you've seen some files, such as NTUSER.DAT, are always going to be in use. I would say you really do need ofo to do this job properly and its not just recommeneded but mandatory. From what you're saying it sounds like the free windows backup utility is more capable than the base Retrospect at this. What are you planning to do Matt?
  14. Backup Strategy?

    Thanks for sharing your setup Lennart. I'd thought about backing up computers over night but we're required to shutdown systems over night to save power. If they go to sleep, they don't always tend to wake up so I don't think we can get away with it.
  15. We currently use Retrospect to back up around a dozen computers. I have a separate backup set and script for each computer which is working fine. Soon I’d like to expand this out so that another 70 or so computers will be backed up. If I continued to use my current process which is having a separate backup set and script for each computer it’s going to be a lot to setup and manage. What’s the recommended way for handling a medium to large amount of computers? Do people backup multiple computers to the same backup sets? I guess I’d still need separate scripts for each computer? The Retrospect server backs the files up to hard disk.
×