Jump to content

venom_zx

Members
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About venom_zx

  • Rank
    Occasional forum poster
  1. venom_zx

    Retrospect Can't See It's Own Rdb File?

    hi Richard, just to be sure. i talked about 2 problems: 1. to be able to change the location in the member properties dialog at Configure > Backup Sets > Properties... > Members > Properties and be able to click "OK", i suggested: - using the "Browse" button and then clicking "OK" (instead of typing the location and clicking "OK") after that i've always tried to run the verification again. 2. to stop it from asking the location of each *.rdb file during the verification, i suggested: - go back to Configure > Backup Sets > Properties... > Members - open the Properties (of the member) dialog - CHECK the "This member is lost or damaged" checkbox - close it with "OK" but leave the Backup Set's Properties dialog (the one showing Members tab) open - open the Properties (of the member) dialog again - UNCKECK the "This member is lost or damaged" checkox - close it with "OK" and now also close the Backup Set's Properties dialog (the one showing Members tab) and try the verification again. i've never tried to change the location and do the checking and unchecking in the same step as you seem to be suggesting.
  2. venom_zx

    Retrospect Can't See It's Own Rdb File?

    i wanted to mention that i also just experienced this with retrospect 7.7 multi-server, and found a solution (better late than never). (solution at the bottom) ===How it started=== i made a copy of my backup files (data and catalogs) at my system dedicated to running backups. this was a simple copy from one external usb drive to another (to store off site) and not through retrospect. after this copying, i connected this drive to a different system running a clean install of retrospect. on this system i wanted to add each backup set to verify them. so i did this: Configure > Backup Sets > More > Open > selected a catalog and then changed the drive letter of the "location" to the usb drive's letter (because it's different from my backup system) Configure > Backup Sets > Properties (of added backup set) > Members > Properties (of the member's folder) but retrospect didn't allow me to click ok (it gave the message "this folder can't be used...") but the ok button worked after i used the "Browse" button to select the same location (very strange). ran verification: Tools > Verify Media > clicked the (added) backup set > OK ***this is where the problem occurred*** the verification just started but it imediately asked me to select the location of the member, even though it was already set as mentioned above. giving it the location through the "choices" button only makes it run for a moment and ask for the next file (strangely, the open file dialog contains strange symbols as file types) ===How i solved it=== - Configure > Backup Sets > Properties... (of the backup set) > Members > Properties (of the member) - now CHECK "This member is lost or damaged" - click OK to close this dialog - Properties (of the member) again (to open the dialog you just closed) - now UNCHECK "This member is lost or damaged" - click OK to close this dialog again - now also close the backup set's Properties dialog (the one with the "members" tab) done (media should work now without asking for every single *.rdb file) this has worked everytime for me (restarting/reinstalling retrospect didn't help). the solution doesn't make much sense, so i consider this a bug.
  3. i was testing these drives on another system. i put the 6 year old sata drive back in the original system and the same task works fine again with 0 verification errors ...so go figure. must be the other system (never experienced this before) i still have the question: - how am i supposed to correct checksum mismatches that are detected by a manually doing "Verification Media" ? (retrospect does not seem to copy these files when the Backup Script is run again) greetings
  4. we are using retrospect 7.7.562 i backup using media verification (so md5 checksums) during backup. and checksum mismatches are detected during backup. running the script again seems to result in the mismatches being recopied but even then there are errors, making me have to run the script multiple times (which is a bad sign). i have run a manual "Verify Media" on the Backup Set after i managed to correct the mismatches by running the backup script multiple times. it still detected checksum mismatches. this happens after starting from a new backupset with varying but similar amounts of erros and files. CHKDSK did not find any bad sectors on the Media (6 year old SATA hard disk ) i'm writing to. another IDE hard disk on the same system can run the same Script without problems. the problem is that retrospect did not try to copy them again after the manually started "Verify Media" - why doesn't retrospect re-copy files that were detected as mismatches during the manually "Verify Media"? - how am i supposed to resolve this? - is my Media going bad? i suspect the disk needs to be replaced but i just want to make sure it's not something else. greetings
  5. venom_zx

    1 files were not verified

    i'ts simply a SATA drive that is on the same system as retrospect (yeah i know i have to rearrange this soon). strangely other backup-sets on the same drive don't have this issue. when i posted the second log... i did not realize that it was such an old one. i've had to re-catalog this backup-set once because the catalog became corrupt after a power failure in the building. so the errors may be related to that. - could the "1 files were not verified" message also be related to having repaired the catalog?
  6. venom_zx

    1 files were not verified

    i never used to get this message. this is the Operations log: ================================= + Executing Verify at 10-1-2011 22:34 (Execution unit 1) To Backup Set user0 disk C,D,X... 1 files were not verified 11-1-2011 01:33:12: 1 execution errors Remaining: 16161 files, zero KB Completed: 88342 files, 55.4 GB Performance: 561.6 MB/minute Duration: 02:58:41 (01:17:50 idle/loading/preparing) ================================= Ctrl+L gave me a different operations log i didn't see before: ================================= Trouble reading: "1-user0 disk C,D,X" (237707118), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-user0 disk C,D,X", Can't read to file C:\Machines\user0w\Retrospect\user0 disk C,D,X\1-user0 disk C,D,X\AA017491.rdb, error -1101 (file/directory not found) Trouble reading: "1-user0 disk C,D,X" (237707119), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-user0 disk C,D,X", ... (it goes on like this for a while) Can't read to file C:\Machines\user0w\Retrospect\user0 disk C,D,X\1-user0 disk C,D,X\AA017491.rdb, error -1101 (file/directory not found) Trouble reading: "1-user0 disk C,D,X" (237711946), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-user0 disk C,D,X", Can't read to file C:\Machines\user0w\Retrospect\user0 disk C,D,X\1-user0 disk C,D,X\AA017521.rdb, error -1101 (file/directory not found) Trouble reading: "1-user0 disk C,D,X" (237711947), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-user0 disk C,D,X", Can't read to file C:\Machines\user0w\Retrospect\user0 disk C,D,X\1-user0 disk C,D,X\AA017521.rdb, error -1101 (file/directory not found) Trouble reading: "1-user0 disk C,D,X" (237711948), error -102 (trouble communicating) 16-4-2010 22:56:26: Remaining: 12575 files, zero KB Completed: 98719 files, 181.1 GB Performance: 24.1 MB/minute Duration: 5 09:47:55 (02:05:55 idle/loading/preparing) 2,131 files were not verified 16-4-2010 22:56:27: 4,810,542 execution errors Total duration: 5 10:56:01 (02:39:24 idle/loading/preparing) ================================= could the the storage drive be corrupt?
  7. the verification script i run contains this (error?) "1 files were not verified" in the user manual it says that verification errors will result in the original file being copied again during the next backup. i've tried running another backup but i still receive the same message when i run the verification. i'm assuming that the file no longer exists. - how do i resolve this? - do i have to create a new backup-set and start from scratch? i'm using retrospect 7.5
  8. basically i want daily backups for all my clients. lets take one client for example: - i created a regular backup script for it to backup every day at a specific time there are times that the machine is not running at that specific time so - i created proactive backup that tries to backup **after** the backup is a day old. ===my expectations=== what i expect/want from this is that the client is backed up at a specific time and if that time is missed, then the proactive backup kicks in, constantly trying to create a backup as soon as possible. i also expect the regular backup to keep running at the specified time of day so that the backup time does not start drifting. (i would find it acceptable if the backup ran twice on the same day due missing a backup on the previous day) ===reality=== but what happens is that the proactive backup ignores the time the client's volumes were last backed up by the regular backup script. they don't seem to work together at all from this perspective. is there any way i can achieve daily backups with constant polling for missed backups ? (i'm using retrospect 7.5)
  9. venom_zx

    How to edit selectors with the volume browser?

    so does this mean i should define a volume for every folder i want to backup? (so i can manage them)
  10. hi, im using retrospect 7.5. i have made some selectors by saving the highlights in the volume browser. but now i want to view them and probably make some small changes. but when i try to edit the selectors i cant get to the browser . i only see a window to modify the condition how can i modify selectors using the volume browser?
×