Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 229
  • Last Modified:

Exchange 2003: DB on different LUN has disapeared

I created a temp db on my Exchange 2003 server in order to move users temporarily out of a massive DB that needs to be reinitialized.  The DB is on a different LUN than my other db's (all on separate drives, NAS).

Upon creating a dummy user and setting its mailbox to reside on this new db, the DB has just up and disapeared out of Exchange server manager.  The two db files were created on the server but the DB does not appear.

I have not rebooted this server as it is a considered a high-availability box but I have an upcoming maintenance window coming up that I would like to troubleshoot this issue.

Any advice or suggestions are welcomed.
0
WytLytnyn
Asked:
WytLytnyn
  • 5
  • 3
1 Solution
 
WytLytnynAuthor Commented:
Would restarting the IS possibly fix this?
0
 
MegaNuk3Commented:
Is it a cluster? Has that drive been added to both nodes?

Are you looking from the ESM that originally created that DB?

It might be worth looking for the DB in ADSIEdit, if it's not there then you may have AD replication problems or one of your helpful colleagues has removed the 'temp' DB
0
 
WytLytnynAuthor Commented:
Thanks for the response, MegaNuk3.

It is not part of a cluster.  I'm not looking through the original ESM.

I'm querying the other admins right now but I doubt they'd pull something that uncool or stupid.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
WytLytnynAuthor Commented:
I've gone back to the ESM on the server and it still does not show.

Would it be logical to assume that I could recreate the DB through the setup process and point the DB to the log files already created?
0
 
MegaNuk3Commented:
Yep, create a new one in ESM and point it at the existing file location
0
 
WytLytnynAuthor Commented:
Found that the database had been renamed by another admin.

One of the things that I did notice when trying to figure the whole situation out was the fact that the database files both showed a current timestamp for last accessed which told me that the DB was in use and that the server was seeing the LUN/DB/et. al.

Thanks to the others for their input.  Sorry I didn't have a "real" technical issue.
0
 
MegaNuk3Commented:
Thanks for the update, feel free to close the question.
0
 
WytLytnynAuthor Commented:
Discovered that there was no real technical issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now