cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
804
Views
0
Helpful
6
Replies

Unity 4.05 - question about Migrate Subscriber Data tool

maratimer_2
Level 1
Level 1

We just had our main unity server go down, one of 8 in a dialing domain. I am looking at the D: Drive which normally has about 70 GB of free disk space and noticed it was full - issue found.

The reason the disk is full is because under the D:\CommServer\Utilities\Migrate Subscriber Data Tool folder, the LOGS folder has four files in it, two which are 26k and the other two are 35 GB each both dated yesterday....obviously what filled the disk.

My question is where did these come from and how did they get so big? There may have been a dozen mailboxes moved yesterday in the exchange environment using thier own tools, but we have not run this tool once.

Any suggestions? Will also be opening a TAC ticket but wanted to look for suggestions here also. Thanks.

1 Accepted Solution

Accepted Solutions

Try opening a command line and using the command 'type MigrateSubscriberData_20061004_105144.log | more'. I don't have a 35 gib file to test on so I could only find a 650Mb file to use but I'm thinking that the type command doesn't load the entire file but rather reads it as necessary. I just want to see if it looks like a legitimate MSD log.

And yes, if these are legitimate MSD logs they would only be created when MSD is run.

View solution in original post

6 Replies 6

smilliga
Level 1
Level 1

What are the file names of those four files?

MigrateSubscriberData_20061004_104134 (26kb)

MigrateSubscriberData_20061004_105133 (26kb)

MigrateSubscriberData_20061004_105144 (35GB)

MigrateSubscriberData_20061004_105201 (35GB)

MigrateSubscriberData_20061004_105352 (26kb)

Any ideas what happened?

If these logs are indeed MSD logs then MSD was run at some point. Send me (smilliga at cisco dot com) this one: MigrateSubscriberData_20061004_105133 and maybe type out the first page of contents from one of the large ones. The fact that both of the large ones were created just 15 seconds apart, first at 10:51:44 and the second at 10:52:01 leads me to believe something else created those files. I'm a firm believer in diagnostics but creating 35 gigs worth in under 15 seconds seems highly unlikely.

Thanks, will send the files as requested. We have had traces running for the TSP diagnostics only on that server, nothing else that I am aware of to date. Thanks for a quick reply.

I wont be able to open the 35GB files, or copy them over the network - its too large to open, even on our big unity server with 4 GB RAM and 150 GB disk...any other ideas?

Otherwise, i will only be able to send the 26k one which I suspect wont help much..so you are saying the fact that the log files are there points to the actual tool being run?

Try opening a command line and using the command 'type MigrateSubscriberData_20061004_105144.log | more'. I don't have a 35 gib file to test on so I could only find a 650Mb file to use but I'm thinking that the type command doesn't load the entire file but rather reads it as necessary. I just want to see if it looks like a legitimate MSD log.

And yes, if these are legitimate MSD logs they would only be created when MSD is run.

Thanks, they are on the way - yes, it looks like a valid file..interesting stuff.