Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by CCC

  1. No, I don't have the open file backup option. But if I have to pay an extra $900 to add that feature and do a proper disaster restore on my one Vista system, then I'll buy something else that does disaster recovery for a much lower cost.
  2. I am running Retrospect SBS Premium. I have just begun backing up my first Vista workstation. I am receiving the following unexpectd errors that are particularly alarming: ... File "C:\Users\Jim\NTUSER.DAT": can't read, error -1020 (sharing violation) File "C:\Users\Jim\ntuser.dat.LOG1": can't read, error -1020 (sharing violation) File "C:\Users\Jim\ntuser.dat.LOG2": can't read, error -1020 (sharing violation) ... File "C:\Windows\ServiceProfiles\LocalService\NTUSER.DAT": can't read, error -1020 (sharing violation) File "C:\Windows\ServiceProfiles\LocalService\ntuser.dat.LOG1": can't read, error -1020 (sharing violation) File "C:\Windows\ServiceProfiles\LocalService\ntuser.dat.LOG2": can't read, error -1020 (sharing violation) File "C:\Windows\ServiceProfiles\LocalService\AppData\Local\lastalive0.dat": can't read, error -1020 (sharing violation) File "C:\Windows\ServiceProfiles\LocalService\AppData\Local\lastalive1.dat": can't read, error -1020 (sharing violation) File "C:\Windows\System32\config\RegBack\COMPONENTS": can't read, error -1020 (sharing violation) File "C:\Windows\System32\config\RegBack\DEFAULT": can't read, error -1020 (sharing violation) File "C:\Windows\System32\config\RegBack\SAM": can't read, error -1020 (sharing violation) File "C:\Windows\System32\config\RegBack\SECURITY": can't read, error -1020 (sharing violation) File "C:\Windows\System32\config\RegBack\SOFTWARE": can't read, error -1020 (sharing violation) File "C:\Windows\System32\config\RegBack\SYSTEM": can't read, error -1020 (sharing violation) This looks to me like the registry is not getting properly backed up. Is that correct? ...Jim Hansen Canyon Country Consulting
  3. We are also having this problem. After spending a week trying to get SQL backup working it is really annoying to have to deal with possibly bogus application log errors daily. Does this error mean there is a problem with my SQL backups or is it a benign error?
  4. I had been getting error -1019 (not enough resources) intermitently when backing up the registry on one workstation since last winter. This summer it became a normal event and I was no longer able to back up the registry under any circumstances. I have 1 GB RAM and 40 GB free HD space, so that was not the issue. Tech support was no help. Another problem recently appeared regarding loss of access to network drives due to insufficient resources that led me to a solution for both problems. It turns out that Trend Micro's SMB messaging suite hogs paged kernel memory and that was the resource that was being exhausted in both cases. The Windows XP default is to allow a PagedPoolSize of 193 MB. Changing the registry key PagedPoolSize (DWORD) in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manger\Memory Mangement" from 0x00000000 to 0xffffffff (8 f's) changes the algorithm to allow the maximum paged pool allocation given other conditions on the machine. This fixed the problem with the registry backup and a few other problems on my system as well. Next I will try it on my SBS 2003 Premium sever to see if it fixes my intermittent problems with VolSnap failures and with backing up IIS Metabase. Sadly, tech support was no help on this issue. They never got back to me to help me debug this problem last July. I hope this helps somebody else!
  5. After using Retrospect for many years on my own peer-to-peer network and on the domain networks of various clients, I recently upgraded my system to SBS 2003 server and a domain. Consequently, I upgraded from Retrospect 5.6 to 6.5 in order to backup SQL and Exchange on SBS. My preferred backup mode is to do a full backup once a week and an incremental ("normal" in Retrospect parlance) backup the other six days, changing the tape once a week. I understand this is not as safe as doing a full backup every day with complicated tape rotation schemes, but it meets my needs for simplicity while providing a reasonably long history. (It also meets the needs of many of my small business clients who have only five to ten workstations and a small staff). I now find that I can not do an incremental backup (Differential or Log) on the SQL Master database. Only a Full backup can be done. But the option for SQL backup style for scripts is set for the whole backup script, not on a per database basis. It would appear then that I must further split my normal backup script so that the Master SQL database is backed up by its own script. This means I must now run a separate script on the first night to do a full backup on all databases, then two separate scripts on the other nights, one to backup the Master database Full and the other to backup the other databases Differential or Log. I searched the documentation, Help, FAQs, Forums and Google news groups and found no information about backing up the SQL Master database in Retrospect. Is this correct: I have to use three spearate scripts to backup of the SQL database incrementally? Or am I missing something?
  6. Thanks for the reply. I was hoping I overlooked something. However, if I understand the way scripts work, it is more than just a pain to set up; it is also wearing on the tapes and drive. I believe the tape is repositioned at the start of each backup script. If this is the case, having to run multiple scripts means multiple tape passes to position at the end of the last set written by the previous script. Multiple scripts also means having to look at multiple log files to verify everything worked OK. Most of my clients are small businesses with only a few staff people. They want a really simple backup scheme that requires a minimum amount of interaction and a minimum amount of supervision on my part. Few of my clients have anybody that can make sense of the Retrospect log. They just want a simple answer to "Did it run OK?" Multiple scripts running every night just makes things worse. I would rather run one script per night. As it stands now, for SBS I have to run three scripts: one for the server system, Exchange, all databases except Master, and most desktop systems that are connected and on 24x7; another for the Master database; and a third for laptops and desktops that may or may not be connected and turned on. It would be nice if we could just set the backup type for each database and run one script.