Jump to content

oslomike

Members
  • Posts

    158
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by oslomike

  1. Thanks Mayoff, I appreciate you taking the time to reply. I understand that you don't have the resources to hang out on the forums. In my case, I'm running version 8 and it seems my "deferred" problem is basically the same, but actually a lot more involved than what you're describing. I'm experiencing that all scheduled scirpts get set to deferred and then stop working altogether. Is there a patch for v8? The KB page didn't adress any versions as far back as v8.
  2. David, Thanks for the detailed email. I've tried deleting the Schedules of the scripts, but not the scripts themselves, and that didn't change anything. Scripts still don't run. Under the Activities Tab/Scheduled, there are a bunch of scheduled scripts that are all set to deferred, which seem to be stuck. You can't delete them. Is the same issue others are having? BTW, I'm on Retrospect v8. I know it's old but it's been reliable up until now. I'll have to dig deeper.
  3. Hi David, Thanks for the reply. I understand. There must be something else wrong because I can't even delete the scheduled scripts that are set as deferred. I will do as you suggest and make all new scripts and see if that helps. Thanks again!
  4. Hello Mayoff, Just wanted to chime in here because I too am suddenly experiencing the "deferred" bug. I have an older version of Retrospect v8 that has been working for years without this bug, but suddenly all my scripts get deferred and DO NOT run. I have a long list of deferred scripts in the "scheduled" window. Just checked again this morning and I confirmed that normal scripts stopped running. Any ideas on how I can get the program back to normal again?
  5. Hi Nigel, I've been bad at RAID erase/restore maintenance. That'll be my next thing to try. Re your question about my restore test. I was attempting to restore to a different disk. Re the question about "write exclusive" mode, not other machine on the network is authorized to mount any disk "write exclusive" except for this particular backup machine. When you setup the disks using SANmp, you use the admin program to make users and give them permissions. So, all the client SANmp programs which every machine is running, allows you to mount a disk either Read only or Read/Write, and only one machine is ever allowed to be connected Read/Write. Thanks for the help!
  6. Hi Lennart, SAN doesn't offer any software to repair permissions. It has a Repair mode where you mount the disk exclusive and then you can run disk warrior. When I enter repair mode and mount the disk in question, I'm using an older operating system that still has Disk Utility and the option to repair permissions, BUT that option isn't available when I run the disk. Maybe because it doesn't contain any files installed by the OS?? So, back to the option of reformatting the disk and doing a full restore. Unless there is more things to try. Thanks again!
  7. Hi Nigel! That's exactly correct. We mount the disk on the desktop mac that is connected to the LTO-5 which also runs Retrospect. The Retrospect logs show nothing of any specific folder or file. It has a problem with the disk itself for some reason. So no matter what backup I do, I'll get this error. As you can see below, a log from a recent backup, the error comes first. Yet, it backs up 8GB worth of files. Disk Warrior didn't help at all. It found a minor error in the directory and repaired it but Retrospect shows the same error. It looks like I have to erase the disk and restore it. Thanks for the insight and help!! - 10/20/18 2:28:41 AM: Copying Kåres Disk > !Can't read state information, error -1101 ( file/directory not found) 10/20/18 2:33:24 AM: Execution incomplete Completed: 517 files, 8 GB Performance: 2,147 MB/minute Duration: 00:04:42 (00:00:52 idle/loading/preparing)
  8. Hello again, I'd like to figure out how to make the disk be seen normally by Retrospect. Is there a way to redefine the disk? It's confusing because it just shows automatically and there is no removing it other than unmounting the disk. I'd sleep better if I could find a workaround to getting things to backup without errors. (Reinstall the program? Rebuild the catalog? Reformat the disk itself?) Any last thoughts? Lennart, you're always a big help. Thank you! It had to be said. ?
  9. So, I went to restore files and folders I was able to select the disk but it had a "yellow exclamation sign" on the disk. I was able to see my test folder was there. So I guess it's getting backed up but the application is showing misleading information and probably isn't doing something correctly. At least I feel a bit better now. I only wish I could get to be totally back to normal. Thanks Lennart!! BTW, Does it not work to search for a folder name?
  10. OK. I tried to do a search restore for a specific folder that created as a test, and after the backup was finished, the folder wasn't found in the search of the catalog. So, it might be backed up, but I don't see how I can ever retrieve it. Is it possible to tell Retrospect to forget a local disk and then re-add the disk somehow? I just can't seem to figure out what caused this disk to suddenly get these errors. EVERYTHING in the console looks normal, except that the disk in question looks like it's never been backed up. BTW, I'll have to see if there is something that needs repairing on the disk. Disk Warrior didn't find anything. I've run out of ideas. Anyone else?
  11. thanks Lennart, Do you think that the 3.1 GB of files that were copied are cataloged anywhere as having been backed up? I'm just trying to figure out if I can ignore the error when there are in fact files beingn copied. I'll probably have to do a test and see what's getting backed up and what's possible to restore. Could it be that an entire disk (ie snapshot) wouldn't restore properly, but search results for specific files/folders would be found and be possible to restore? thanks
  12. Last clue: The retrospect Sources window shows the disk in question as never having been backed up. I'm not sure what the 3.1 GB of files was. Now, I'm more confused that I was before. ?
  13. If it helps, this is the whole log from this one disk: - 10/12/18 2:30:49 AM: Copying Kåres Disk > !Can't read state information, error -1101 ( file/directory not found) 10/12/18 2:33:14 AM: Execution incomplete Completed: 267 files, 3.1 GB Performance: 1,873.1 MB/minute Duration: 00:02:24 (00:00:40 idle/loading/preparing) So, it looks like it backed up 3.1 GB of files. In the log for the other disks, the second text line states "snapshot stored" ; an example: 10/12/18 1:49:06 AM: Snapshot stored, 9.1 MB Since this is missing on this disk that has the error, could the problem be the catalog?
  14. Thanks for all the tips! I haven't figured it out, but I did get a different error this morning in the log: > !Can't read state information, error -1101 ( file/directory not found) Is this the same error?
  15. BTW, does the latest Retrospect version help with these problems?
  16. Hi Lennart! thanks for the fast reply. The disks are mounted using SANmp which is a shared SAN front end (mounted Read Only). It's made by Studio Network Solutions and has been running great for over 10 years with this setup. It's just this one disk now seems to be seen in Retrospect, but when it comes to backing it up, it says that the disk can't be found. Is there a way to trick the program to see the drive? BTW, I have about 12 other disks mounted this exact way (Read Only) and they are all working perfectly with Retrospect. It's just the one. Would Disk Warrior be an option to try? Again, thanks!
  17. Suddenly I'm getting this error on a disk that has never had problems before. The disk is seen by Retrospect and it shows up as ready for a scheduled backup, but when a script runs to back it up, OR I try to do a manual backup of this disk, I get this error. I can't figure it out. Anybody have this happen before? Thanks in advance.
  18. I had an LTO-5 drive sheer off the leader pin so it's definitely gone. There might also be some damage to the tape itself but I'll try to re-pin it. I was mostly concerned about how much leader retrospect or the drive puts on a tape before writing data. Anyone know? Thanks
  19. Hello, I was wondering if anyone knows if it works to repair a leader pin on an LTO-5 tape and still have it readable by Retrospect? The leader pin repair kit states that the first meter of tape is just leader. If I cut off a few centimeters of tape at the end, will I cut off data? Could there be internal damage to the cartridge that I can't see? thanks mike
  20. Hello, I have a catalog sets that are upwards of close to 5gigs. Is there any danger in that? I have three quite large backup sets that are basically switched back and forth all week long so that there are always three sets of data. But I haven't been paying attention to the size of the catalog files until now. Is there any danger in letting them get this big? I should probably make them smaller simply to make searching for retrieval a lot faster, but then when I make a new set it will burn through about 5TB o the first backup. Are there any common practices that are smart in this situation? Thanks! Mike
  21. Hello, When trying to rebuild a v6 catalog in the v8 program, Retrospect v8 sees the AIT-2 tape drive but when I put in a tape, the Device window shows that the tape drive is still empty. Any ideas why this would be like this? On this one machine that I use for backups, I have connected at the same time an Exabyte Mammoth LT, a Sony AIT-2 drive and a HP LTO-5. Is that I have too many storage devices connected and I am only allowed to have one with the single license I have? OR is there some other reason why it wouldn't read a header from a v6 tape? I thought I read somewhere that v8 should be able to recatalog a v6 storage set. Maybe I'm wrong here. Any thoughts? Thanks mike
×
×
  • Create New...