I have a project which has about 200GB of media - when there is a corrupt file (and the msm's need to be recreated), it takes about 40 minutes to scan - Is there a way i can reduce this? Perhaps, can I create folders within the room's directory - so for example, the room's folder is Avid2 and thus the folder is Avid2 - Can I create more folders - Avid 2.1, Avid 2.2, etc?

i am running Windows XP with Avid version 7.2

.- I used to have the very same problem like 3 times a week.

1.- You shouldn't have more than 10.000 files by OMFI folder. That means trouble. If you can, delete some.

2.- You can't have more than one OMFI folder per disk/partition. I mean, you can't, even if you want to.

3.- My solution? I partitioned my large Raid (1.5 TB) in several smaller partitions (no larger than 200 Gigs)

4.- If you cant make new partitions, try to delete the precomputes and then rebuild the omfi database, this is temporary but would work.

5.- Delete ALL msm, I mean ALL OF THEM, even in different disks.

6.- Make the small partitions ASAP!!

Does the same apply for MXF?

No, MXF will create a new subfolder when there is un overflow.

These subfolders are called "1", "2"...

raspago:

2.- You can't have more than one OMFI folder per disk/partition. I mean, you can't, even if you want to.

http://www.avid.com/exchange/forums/post/278003.aspx

sep:

raspago:

2.- You can't have more than one OMFI folder per disk/partition. I mean, you can't, even if you want to.

http://www.avid.com/exchange/forums/post/278003.aspx

.- Good info to know in case of emergency, really!!!

 but I prefer prevention (partitions):

http://www.avid.com/onlineSupport/supportcontent.asp?contentID=8082

"- By creating more, yet smaller Drive Partitions, the Avid can more efficiently and reliably maintain its Media Database files, giving overall stability and speed back to the system."

raspago:

"- By creating more, yet smaller Drive Partitions, the Avid can more efficiently and reliably maintain its Media Database files, giving overall stability and speed back to the system."

Avid does not know the difference between a real partition and a "virtual drive"  partition so there is no benefit either way based on that parameter.
If you embrace the concept of one Avid media folder for each project and create that folder before you start a each project you would be amazed at the long term advantages this method can offer.  For local storage Avid systems project based media management and archiving suddenly becomes a breeze. 

If you're on a Unity or ISIS shared storage system, then it will automatically create and track your subfolders for you.  So, it would create your Avid2.1, 2.2, folders etc. 

PS, there is no Avid version 7.2 that will run on WinXP, unless you're talking about Liquid.... then again, if you're talking about Liquid, you're a) in the wrong forum and b) not using OMF or MXF media with msm database files.  I can only guess/assume that you've simply transposed the version numbers and meant to say 2.7, which is a valid MC version that runs on WindowsXP

AndrewAction:

raspago:

"- By creating more, yet smaller Drive Partitions, the Avid can more efficiently and reliably maintain its Media Database files, giving overall stability and speed back to the system."

Avid does not know the difference between a real partition and a "virtual drive"  partition so there is no benefit either way based on that parameter.
If you embrace the concept of one Avid media folder for each project and create that folder before you start a each project you would be amazed at the long term advantages this method can offer.  For local storage Avid systems project based media management and archiving suddenly becomes a breeze. 

.-  BTW. They are not my words, they're Avid's

raspago:

 but I prefer prevention (partitions):

http://www.avid.com/onlineSupport/supportcontent.asp?contentID=8082

Is this still true today, it seems these recommendations are (were) for Meridien systems, I 've heard that in terms of partition this was no longer true, however file amount limit in OMFI folder is still 10 000 !

raspago:

BTW. They are not my words, they're Avid's

Sure. But then Avid have never officially recognised that virtual drives work.
I have used virtual drives for six years now with Avids. No problems at all. Therefore I have no problem recommending them as a solution. Ideal for solving an oversized OMFI MediaFiles folder problems without having to partition a drive.
For me they are ideal for project based media management and archiving.
On a 2 TB raid here I have no partitions but 30 project media folders any of which can be turned into a working virtual drive in less than a minute. Avid sees up to 20 "partitions" at any time on this raid and all of them are under 100GB's so "By creating more, yet smaller Drive Partitions, the Avid can more efficiently and reliably maintain its Media Database files" my Avids are very happy virtual campers.

Action,

let me see if I am understanding you. I too am runing a raid media server and have gotten in the habit of making larger partitions to work from. You feel that it is better to limit partitions to 100 gig? The issue I had run into was that I would run out of drive letter designations so I began making larger partitions to reduce the number of partitions that needed to be mounted at any one time. As my projects get closer to being finished I offten begin to get various errors and bin read errors, do you feel this is due to excessive OMFI folder size and ergo database filesize?

Thanks

I am not recommending any sizes it was just an example of what is heppening here at present.
The advantage I see for your situation would be that you could have a few partitions on your raid for overall managability. Then by using folders as virtual drives you can manage how many drive letter designations you use at any time by only activating the virtual drive function for folders needed for the project you are working on.  These virtual drives are completely dynamic in their size as they are actuallly only folders
Real partitions take up your drive letters regardless of wether you have media on them or not. Virtual drives are fluid for drive letters as you only activate them on a need to use basis.

"I offten begin to get various errors and bin read errors, do you feel this is due to excessive OMFI folder size and ergo database filesize?" could very well be. Touch wood.  I have not had a database error on any Avid here for several years now.

Andrew, your solution with virtual drives sounds great. Could you tell us your workflow and what virtual-drive-software you are using (daemontool??)? I am trying to keep the system as clutter-free as possible, so I wonder if the virtual-drive running software in the background would compromise resources. Also, are you using MXF or OMFI? It seems the former is more recommandable for larger projects.

Thanks.

Isn't the 10000 file count a windows limitation?