Jump to content

paulockenden

Members
  • Content count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About paulockenden

  • Rank
    Occasional Forum Poster
  1. paulockenden

    Proactive backing up too many files

    Quote: The troublesome volume is NTFS and being accessed via the client, correct? Yup. Quote: What operating system is this client? Windows Server 2000 Quote: Are these files in a location where the modification date may be updated by workstation access or some kind of virus/malware scanning application? Not at all. The machine has three drives. The other two back up normally, but the troublesome one always gets EVERY file backed up. Even files with a modification date several years ago. Quote: You say it backs up *all* of the files everytime? Does this happen with an immediate backup? Can you check the properties of a few control files before and after subsequent backups? Hmmm.... that's odd. Just did an immediate backup and only 4 files were backed up. But the last half dozen cycles of proactive backup have backed up everything... P.
  2. I've got Proactive backup working well across my network, but there's one drive on one server where Retrospect always backs up all of the files - it doesn't seem to take account of the files it already has in the backup set, it just grabs everything again. Anyone got any ideas? I did a search in the tech support and forums, but didn't see anything. Oh, Retrospect 7.0 BTW, latest version and client, and the volume in question is NTFS. Thanks, P.
  3. paulockenden

    Can't see SQL container

    Hmmm... that MS article seems somewhat broken! Instructing you to register an rll file! I tried re-registering the .dll, but that made no difference. I'm really nervous about letting the installer re-build the registry because I've seen that cause problems in the past. I wonder whether, now that Dantz know the "alternative" registry structure, they could code an SQL agent that will work with it... Do you know what I can look for in my registry to see whather I have the same problem as you? Thanks again, P.
  4. paulockenden

    Can't see SQL container

    That's brilliant news Bill. Like you, the only thing that has ever touched my server is the MS installer and a few MS patches. I'd rather not rebuild my registry if at all possible - what were the other options offered? Thanks, P.
  5. paulockenden

    Can't see SQL container

    Here's the results from ours: 1 ProductName NULL Microsoft SQL Server 2 ProductVersion 524288 8.00.760 3 Language 1033 English (United States) 4 Platform NULL NT INTEL X86 5 Comments NULL NT INTEL X86 6 CompanyName NULL Microsoft Corporation 7 FileDescription NULL SQL Server Windows NT 8 FileVersion NULL 2000.080.0760.00 9 InternalName NULL SQLSERVR 10 LegalCopyright NULL © 1988-2003 Microsoft Corp. All rights reserved. 11 LegalTrademarks NULL Microsoft® is a registered trademark of Microsoft Corporation. Windows is a trademark of Microsoft Corporation 12 OriginalFilename NULL SQLSERVR.EXE 13 PrivateBuild NULL NULL 14 SpecialBuild 49807360 NULL 15 WindowsVersion 143851525 5.0 (2195) 16 ProcessorCount 2 2 17 ProcessorActiveMask 3 00000003 18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM 19 PhysicalMemory 256 256 (267952128) 20 Product ID NULL NULL Only two processors! P.
  6. paulockenden

    Can't see SQL container

    I'm pretty sure that it's just a default instance here - how can I tell? Bill - are you running Standard or Enterprise edition of SQL Server? We're running Enterprise here, and I wondered if that might be the problem... P.
  7. paulockenden

    All Databased not being backed up

    I'm fairly certain that in my case it's a default instance. (How can I tell?) P.
  8. paulockenden

    All Databased not being backed up

    Plywood Bill - I see that you earlier had the same problem as me (SQL container not showing). How did you manage to cure that one? Thanks.
  9. paulockenden

    Can't see SQL container

    Everything is English. P.
  10. paulockenden

    Can't see SQL container

    Quote: Are you running this in a domain environment or as stand alone servers? Do you have SQL set for domain authentication or SQL authentication? I'm running a domain environment with mixed mode SQL authentication. Quote: In the past there were cases (specifically with Windows NT) where some disks would not be visible because they did not have proper permissions. Esentially the admin group did not have access to the volume so Retrospect could not see it. I've tried two different accounts. One set up as per the manual, and also the administrator account. Both of these accounts are able to access the SQL Server using Enterprise manager. Also, on another machine (XP Pro, developer version of SQL) retrospect can see the SQL Server. Quote: Be sure to get Retrospect 6.5.343 from our updates page. It never hurts to have the latest version. That was one of the first things I tried. No luck, I'm afraid. Are you 100% certain that Retro works with SQL Server Enterprise Edition (with its multiple instances etc.) ??? Is there any extra loggin I can switch on to help you guys locate the problem? Thanks for your help. Paul Ockenden Contributing Editor PC pro Magazine
  11. paulockenden

    Removing superceeded backup set members

    Anyone ????
  12. paulockenden

    Can't see SQL container

    OK - done a bit more investigation on this. I actually installed the full Dantz package on that SQL Server, and even locally it still doesn't seem to realise that it's running on an SQL Server. I tried it on another machine running the developer version of SQL Server and it saw it no problem. So there's obviously some setting within my main SQL Server which stop Retro from seeing it. Do you have any ideas? I'm pulling my hair out here. By the way - the server is running SQL Server 2000 Enterprise edition, with a single server instance, and I'm (temporarily) running Retro as Administrator. Adminstrator gets into the SQL Server fine as a login within Enterprise Maganer. Thanks, Paul Ockenden Contributing Editor PC Pro Magazine
  13. paulockenden

    Can't see SQL container

    I already tried forgetting and then re-adding. That didn't fix it. On the XP machine, Retrosepct is running as Administrator. Oh, also should have pointed out that it can see the exchange containers on a different server without any problem... P.
  14. paulockenden

    Can't see SQL container

    Machine A is an SQL Server 2000 (SP3a) running on Windows 2000 server (SP3). It also runs the latest Retro client. Machine B is an XP box running Retro 6.5 - It has an SQL licence (unused). In the volume selector on Machine B I can see machine A, and all of its drives, but I don't see an SQL container. What am I doing wrong? Thanks, P.
  15. Let's say I'd been doing backups for a year, and had a big stack of DVDs or CDs numbered one to a hundred. Obviously, many of these discs may now be completely superceeded by files on subsequent discs, and so can safely be chucked in the bin. Is there any way of getting Retrospect to tell me which discs I can junk? I suppose I could do a test restore to a different place, and then just junk any discs that aren't asked for during that process, but I was hoping that there would be a cleaner way to do it .... Thanks, Paul Ockenden. Contributing Editor - PC Pro Magazine
×