Jump to content

1bdb4f25-865c-49fd-9b71-d85f702209ac

Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About 1bdb4f25-865c-49fd-9b71-d85f702209ac

  • Rank
    Evaluating Retrospect And Have Questions
  1. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Groom doesn't seem to be working

    Okay, thanks. Very counterintuitive, but everything about this software is. I've used many backup products and this one has, without a doubt, the most poorly thought out user interface i've ever seen :-)
  2. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Groom doesn't seem to be working

    Daniels - thanks. But if this is the case, why does it ask for a grooming option when the backup set is created?
  3. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Groom doesn't seem to be working

    Thanks. I'm getting plenty of backups, I believe. One user with about 250G of data had ovet 1T of backup space used on the server. I ran a manual groom and it dropped it down by 2/3 even though it was not dropping as expected during a regular backup (with grooming enabled). The same for a couple of others. So I don't think the 'groom' setting in the backup is working. Maybe I'm misinterpreting, I don't know for sure. Anyplace i can look for more detail on what exactly happens as each step of the backup executes? Or other troubleshooting info?
  4. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Groom doesn't seem to be working

    I tried searching in the forum for something like this, but it never liked my search terms. guess i'm stoopid (or the forum search is) Retrospect 7.7.620 for windows Server: Win XP Clients: Win XP Backup device: 8T NAS (dlink) Problem: I've told each backup set to use the Retrospect defined policy (delete stuff if disk gets full, etc.) but it doesn't seem to be working. The 8T disk is full. The logs, however, don't indicate a grooming problem - they don't say anything about grooming usually. I check the directory sizes on the backup NAS using SpaceSniffer and they are HUGE. There's no way the machines I'm backing up have anywhere near that much data on them. Grooming seems to have worked for several months to a year before failing (yes - I've rebooted everything) So: 1) how can i tell if grooming is actually occurring? 2) Is 'backup set' -> 'properties' ->' groom to retrospect defined policies' the right place to look to see the setting? (looks like it) 3) is it possible to change the 'defiend policy'?
  5. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    How Do I Remove Snapshots?

    Unintentionally duplicated a backup by having a machine in multiple scripts. How do i delete all info related to this machine in all but the desired backup? that is - how do i get the data off the disk, snapshots removed, etc? (I'm sure i'm not using the terminology correctly)
  6. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Error -519 Every Time I Try To Backup Server

    Never found a cause. Switched to a different server and it seems okay now.
  7. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Error -519 Every Time I Try To Backup Server

    Thanks. i've got a trouble ticket open with Roxio.
  8. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Questions Re. Initial Install: Location Of Catalogs

    Ah - your first paragraph is the answer I've been looking for, I think. The only problem i can see is if the NAS units don't get swapped for some reason, but that may not be a problem with this method. Thanks!
  9. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Questions Re. Initial Install: Location Of Catalogs

    Thanks. Here's why i want them on the NAS: 2 NAS units Week 1: backup to NAS1 Week 2: Take NAS1 offsite, backup to NAS2 What gets backed up week 2? Case 1: Catalogs on server - only files changed since Week 1 get backed up to NAS2 (NOT the goal - want another full backup) Case 2: Catalog on NAS: all files since this particular NAS was used get backed up. the goal is to rotate NAS units, keeping one offsite. That way, if there's a catastrophic failure, I'll have a complete backup at most one week old stored offsite. If the catalogs are on the server I will never get a complete backup after Week 1. NAS1 will get out of sync with what's on NAS2, and NAS2 will never have gotten a full in the first place. How to implement with the catalogs on the server??? Thanks
  10. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Error -519 Every Time I Try To Backup Server

    Oops - so client means client and not server, huh? Sorry.. Here is my entire log (not too long, but longer than i like to post on fora like this) Note: 10.0.0.3 is the client interface on the SAN network 192.168.9.30 is its interface on the NAS network 192.168.9.53 is the retrospect server The NAS IP, 192.168.9.222, never shows up. 1310046389: Main: Client version is 7.7.114 1310046389: NetStop: signaling gEndEnumIntfEvent 1310046393: NetStart: starting interface thread 1310046398: ConnStartListen: starting thread ConnStartListen for 127.0.0.1:58999 1310046398: netCheckNewInterfaces: found new address 10.0.0.3:0 1310046398: iplud: bound to address 10.0.0.3 1310046398: ipludAddMembership: adding membership for 10.0.0.3 1310046404: IPNSRegister(1): registered: "apps2"/"f87a5b2cc3ad6130" 1310046404: ConnStartListen: starting thread ConnStartListen for 10.0.0.3:0 1310046404: netCheckNewInterfaces: found new address 192.168.9.30:0 1310046404: iplud: bound to address 192.168.9.30 1310046404: ipludAddMembership: adding membership for 192.168.9.30 1310046410: IPNSRegister(1): registered: "apps2"/"7ede50ed7d67d291" 1310046410: ConnStartListen: starting thread ConnStartListen for 192.168.9.30:0 1310046431: Connection established by 192.168.9.53:1124 1310046447: IPNSRegister(0): registered: "apps2"/"7ede50ed7d67d291" 1310046467: ConnReadData: Connection with 192.168.9.53:1124 closed 1310046502: Connection established by 192.168.9.53:1127 1310046535: ConnReadData: Connection with 192.168.9.53:1127 closed 1310047374: Connection established by 192.168.9.53:1139 1310047398: ConnReadData: Connection with 192.168.9.53:1139 closed 1310047430: Connection established by 192.168.9.53:1142 1310047446: ConnReadData: Connection with 192.168.9.53:1142 closed 1310049412: Connection established by 192.168.9.53:1158 1310049435: ConnReadData: Connection with 192.168.9.53:1158 closed 1310049541: Connection established by 192.168.9.53:1161 1310049571: ConnReadData: Connection with 192.168.9.53:1161 closed 1310050284: Connection established by 192.168.9.53:1200 1310050293: ConnReadData: Connection with 192.168.9.53:1200 closed 1310050365: Connection established by 192.168.9.53:1205 1310050389: ConnReadData: Connection with 192.168.9.53:1205 closed 1310050389: Connection established by 192.168.9.53:1208 1310056587: ConnReadData: Connection with 192.168.9.53:1208 closed 1310056601: Connection established by 192.168.9.53:1279 1310056625: ConnReadData: Connection with 192.168.9.53:1279 closed 1310056626: Connection established by 192.168.9.53:1282 1310059688: ConnWriteData: send() failed with error 10054 1310059688: ConnReadData: Connection with 192.168.9.53:1282 was reset 1310059688: ConnWriteData: send() failed with error 10054 1310064514: Connection established by 192.168.9.53:1364 1310064538: ConnReadData: Connection with 192.168.9.53:1364 closed 1310064539: Connection established by 192.168.9.53:1367 1310066907: ConnReadData: Connection with 192.168.9.53:1367 was reset 1310066907: ConnWriteData: send() failed with error 10054 1310066907: ConnWriteData: send() failed with error 10038
  11. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Error -519 Every Time I Try To Backup Server

    Thanks for responding. So far it happens every time. I'm just now implementing the software and have tried multiple times this afternoon. The client is a rarely-used file server (but it has almost 2T of files). Monitoring network and cpu load shows nothing excessive. In the client log file it says : Can't reserve backup client client_name error -519 (network communication failed) [date/time] Execution Incomplete Total Performance 243.5 MB/minute Total Duration 00:44:04 (00:18:54 idle/loading/preparing)
  12. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Error -519 Every Time I Try To Backup Server

    Here's the configuration: Retrospect Server: WinXP Dual 2GHz processor, 2.5G RAM Client: Win Server 2003 Source of files to be backed up: SAN attached to Windows server (the client) on gigabit ethernet Destination of files to be backed up: NAS on gigabit ethernet Retrospect Server, client, NAS on Subnet1 SAN on Subnet2 (Win Server (the client) has 2 ethernet cards, both gigabit, one on the net with the SAN, the other on the net with the Retrospect server and the NAS) Every time i try to back up the drive, it fails with error 519 after a while. It starts and runs a while, then fails. Thoughts?
  13. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Questions Re. Initial Install: Location Of Catalogs

    Hi - Tech support has been less than helpful, so i thought i'd ask my questions here: 1) My setup requires that i store the catalog files on the backup disks (if you want to know why ask). I don't care to know why this is a bad idea, as tech support keeps telling me, i just want to know how to configure the backups to look for the catalog files in a non-default location. 2) If I'd known this before buying, I wouldn't have: according to tech support, each simultaneous backup session requires 15G (!!!) of space on the system volume. The person who set up my servers made the system volumes of minimal size (12 - 40 G) and needless to say they're getting full, and i'd like to not have to set up yet another machine solely for running as backup server(we're 14 people in the company, and so far have 5 servers doing various things). Can these 15G requirements be directed to another disk attached to the server? Again - I don't care why it's a bad idea, i just need to now if i can do it. Many thanks
  14. 1bdb4f25-865c-49fd-9b71-d85f702209ac

    Evaluating Retrospect And Have Questions

    Am evaluating Retrospect for use in a small network. Have submitted the following question through the tech support web site, but no one replies, so I thought I'd ask here: 1) If possible, how do i configure it to do hourly incrementals? 2) For the hourly incrementals, if I want to keep n versions of a given file before overwriting, how do I configure it? Thanks also - the client crashes on my test machine after each backup. I have foolishly not written down the exact failure text, but will ammend later if it happens again. Anyone seen this (I know - too little info...)? (WinXP SP3, Client version 7.7.114)
×