Joe_Budden
asked on
Isinteg query
Hi
I am practising Eseutil and Isinteg on test databases in Exchange 2007/
I had some questions about Isinteg:
1. I know with Eseutil /p there is the possibility of data loss, is there the chance of dataloss with Isinteg?
2. The command I can see to run is "isinteg -s servername -fix -test alltests". What's the command to run in check only mode so I can see what Isinteg is going to do?
3. Is there a way to run isinteg against a specific database via command line, or can we only run the the command above and then select which DB we want to run against (just covering against accidental damage)
4. Can isinteg be run against recovered databases within an RSG? Will these show up as possible options?
5. I've heard that sometimes Isinteg needs to be run multiple times to fix all errors, how do I know when all errors have completed? No errors left?
I am practising Eseutil and Isinteg on test databases in Exchange 2007/
I had some questions about Isinteg:
1. I know with Eseutil /p there is the possibility of data loss, is there the chance of dataloss with Isinteg?
2. The command I can see to run is "isinteg -s servername -fix -test alltests". What's the command to run in check only mode so I can see what Isinteg is going to do?
3. Is there a way to run isinteg against a specific database via command line, or can we only run the the command above and then select which DB we want to run against (just covering against accidental damage)
4. Can isinteg be run against recovered databases within an RSG? Will these show up as possible options?
5. I've heard that sometimes Isinteg needs to be run multiple times to fix all errors, how do I know when all errors have completed? No errors left?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1. Gundog has given you good advice on all counts
2. Isinteg changes the database as it finds issues on the fly so if interrupted any fixes made will already be applied vs ESEUTIL /P or /D the entire process most finish.
3. I have never seen ISINTEG do any damage to a DB, however, that said ALWAYS backup the database before running any MS or 3rd party utility against a DB since anything can happen, i.e. HS issues, Power outages, and a number of other things so NEVER work with your ONLY copy of a db.
2. Isinteg changes the database as it finds issues on the fly so if interrupted any fixes made will already be applied vs ESEUTIL /P or /D the entire process most finish.
3. I have never seen ISINTEG do any damage to a DB, however, that said ALWAYS backup the database before running any MS or 3rd party utility against a DB since anything can happen, i.e. HS issues, Power outages, and a number of other things so NEVER work with your ONLY copy of a db.
isinteg -s servername -test alltests
4. A little looking up shows no reason that you cant run the commands against the RSG and I dont see why Exchange would treat them differently, if you have test databases to play with then this would be the perfect time to try it out.
( I use a 3rd party backup and restore manager rather than storage groups as we have users being deleted regularly by our helpdesk)