RE: Arcserve2000 and ISINTEG

[HOLLIDAY, Eric]

Well, we're looking at booting out Arcserve & installing Veritas' NetBackup - it can't come soon enough IMHO.

 

As far as downtime,  I have a 23Gb store (aargh!) on that server.  Never having had to run the -fix option, how long do you think that would take?

 

Eric

 

-----Original Message-----
From: John Matteson [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 22, 2001 3:28 PM
To: MS-Exchange Admin Issues
Subject: RE: Arcserve2000 and ISINTEG

I will assume that you have the Exchange agent installed, activated, licensed by CA and blessed by the local spirit leader.

 

Assuming that you have enough downtime available, I would run ISINTEG -PRI/pub -Fix -TEST ALLTESTS

on the information store to ensure that you have any corruption in the store, at the information store level, corrected.

 

We would have a similar problem with Backup Exec. Running ISINTEG on the information store (until the Fixes came up Zero) would clear the problem. There was no problem during normal message processing, but backups would fail on a regular basis.

 

Also, should you have the time, inclination, money and management approval, get rid of CA and put in a real backup solution, like HP's OmniBack or Backup Exec.

 

John Matteson; Exchange Manager
Geac Corporate Infrastructure Systems and Standards
(404) 239 - 2981
Believe nothing because it is written in books. Believe nothing because wise men say it is so. Believe nothing because it is religious doctrine. Believe it only because you yourself know it to be true. -- Buddha

-----Original Message-----
From: HOLLIDAY, Eric [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 22, 2001 3:20 PM
To: MS-Exchange Admin Issues
Subject: Arcserve2000 and ISINTEG

Environment: Exchange (Enterprise) 5.5 SP4
Hardware: Compaq Proliant ML530 dual Xeon processors, 1Gb RAM, 34Gb RAID 5 array
OS: Windows 2000 server SP2
Backup SW: ArcServe 2000

Problem: We cannot get a good IS backup using ArcServe2000 on three of our eight servers. The error code returned is:
(E8602 Failed to read from database. (DBNAME=Information store.EC=)

Now Here's where it gets interesting - After telling us to run ISINTEG with the -patch option (which didn't fix the problem), CA support is now telling us to run: ISINTEG -PRI -FIX -TEST and ISINTEG -PUB -FIX -TEST. 
Now this sounds pretty bogus to me especially since all three databases are working just fine.  The only time we have a problem is when it come time to backup. 

 Opinions/suggestions?

TIA,
Eric Holliday
Exchange Administrator
Corporate Information Systems
Logistics Management Institute
[EMAIL PROTECTED]

 

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm