Scripted backup gives 1102 Error

[anjohnson]

I have recently purchased Retrospect with a Maxtor USB hard drive. I can successfully make an immediate duplicate from a local drive to the Maxtor but when I setup a script to do the exact same thing automatically it gives a "1102 - drive missing/unavailable" error and stops. There seems to be an error line at the end of the log but the duplicate still works fine. Is this a problem with permissions on the shared local drive? I can find nothing in the help file to setup permissions to access a shared drive.

 

The full log of both a successful immediate backup and a failed automatic one are attached below. Any help would be appreciated.

 

Andrew

 

+ Executing Immediate Duplicate at 20/05/2003 12:59

To volume MI File Store Backup on Backup disk (G:)...

 

- 20/05/2003 12:59:16: Copying MI File Store (F:)

20/05/2003 13:03:55: Comparing MI File Store Backup on Backup disk (G:)

20/05/2003 13:03:57: Execution completed successfully

Completed: 61 files, 276.1 MB

Performance: 117.8 MB/minute (59.3 copy, 16560.9 compare)

Duration: 00:04:41

instIniWriteItem: WritePrivateProfileString failed, error 5

Quit at 20/05/2003 13:08

 

+ Retrospect Express version 5.6.132

Automatically launched at 20/05/2003 13:15

 

+ Duplicate using BCH Lunchtime Backup at 20/05/2003 13:15

Can't access volume MI File Store (F:), error -1102 (drive missing/unavailable)

20/05/2003 13:15:14: Execution incomplete

instIniWriteItem: WritePrivateProfileString failed, error 5

Quit at 20/05/2003 13:15

 

 

[AmyJ]

Does the Maxtor drive get unplugged often? Try going to Automate > Scripts. Highlight your automatted script and click Edit. Go to Sources > Add. Is the Maxtor drive listed twice? If so, highlight one and hit the delete key on your keyboard. You may be prompted to "Really forget xxxx" and click Okay. If you don't see this message, try this with the other listed drive. The goal is to only have one instance of the Maxtor drive listed. Something about the drive may have changed in such a way that Retrospect believes they are it is/was different a different drive. The script may be pointing to the 'old' drive.

 

instIniWriteItem -- This is internal debug logging that is normally suppressed and is nothing to worry about. It does not indicate a problem with the backup.