Can't back up IIS Metabase, error -1001 (unknown Windows OS error)

[Donna]

Hi,

 

My apologies for a rather long, unfocused posting. We are new to

Retrospect, just having had a disaster with that other product with a

major market share and an Intelligent Data Recovery that isn't. I'd

rather have a simpler system that works but we are having some

problems.

 

Error e-mails

--------

Can't back up IIS Metabase, error -1001 (unknown Windows OS error)

------- Subject: Retrospect notification from W2KSRV1

(11/12/2003)

 

Can't use Open File Backup option for Windows xp (C:) on dmCurrie,

error -1017 (insufficient permissions) -------

 

Does anyone know how to turn off these error messages without turning

off the e-mail notification? We are not even running IIS. The second

one I am told is caused by that machine having a FAT32 file system.

 

We are also getting messages re file and directory not found, on our

Mac backup that we are told are due to having Appleshare IP turned on.

Is there any way around this? It would seem pretty normal to to use

this on MAC's. Does it go away with OS X?

 

My main concern so far with Retrospect is its error handling and

spurious? errors. I am hoping for a system that most of the time gives

me terse summary e-mail messages saying 'Backup OK I backed up X Gigs

on Y systems in Z hours' and then a short time later, 'Verify OK I

verified X Gigs on Y systems in W hours -- all is well'. If there is a

problem it should say for instance 'Verify FAILED: \\system\files\abc

did not match' or 'Backup FAILED: tape error ####' Issues such as log

files that have been written to since the backup should produce a

notation in the log but not generate an e-mail.

 

Can Retrospect be setup to do this? We have a W2K server with LTO tape

and Mac (soon to be OS X), W98 and XP clients.

 

Given our past experience we are also concerned about disaster

recovery. What is people's experience. Our problem came from a C:

drive that was still there but not bootable. We were unable to save

the C: drive and it buggered up the D: drive as well when trying to

restore C:

 

 

Donna Marie Currie

Saunders Book Company

 

 

[natew]

Hi

 

 

 

What version of Retrospect are you running? What OS is the machine being backed up running? In the past I remember seeing Retrospect try to backup the IIS metabase on computers that didn't have one to begin with (i.e. workstations). I believe this has been sorted out now.

 

 

 

Unfortuntately email notification in Retrospect is not very flexible so it is difficult to pick and choose when a message will be sent.

 

 

 

A better way to check success and failure of backups is to use the Reports Watcher feature in Retrospect. It puts your backups into an HTML summary that can be viewed from any interenet broswer. The nice thing is that is gives the stats you were looking for and allows you to review errors more easily than looking at the Retrospect event log.

 

 

 

In regard to Disaster Recovery my personal experience is that it works very well and is pretty simple. If you have a good backup on hand you can count on a good restore. I am a bit biased though

 

 

 

Nate

 

 

 

 

 

 

[dbarclay]

Interestingly enough I have also seen this error:

The backup is of a remote win2k client (6.5.132) on a win2k server (fully patched/updated), by a MSVP Retrospect Backup Server, v 6.5.336 running on a win2k server (fully patched/updated).

 

- 1/8/2004 1:18:56 AM: Copying Drive C (C:) on QWERTY

T-39: MapError: unknown Windows error -2,147,023,838

T-39: W2dbIISMetabaseOp: CoCreateInstance failed, winerr -2147023838, error -1001

Can't back up IIS Metabase, error 1013594816 (unknown)

1/8/2004 1:36:54 AM: Snapshot stored, 84.3 MB

1/8/2004 1:37:44 AM: 1 execution errors

Completed: 19 files, 8,954 KB, with 81% compression

Performance: 0.1 MB/minute

Duration: 00:18:13 (00:01:58 idle/loading/preparing)

 

I am not certain how to correct/resolve this issue - any ideas would be welcome.