Etc Maintaining files in the second category on the fastest file servers is expensive and maintenance heavy. If these could be automatically moved off to another server shortly after appearing on the file server, IT Departments could spend less time per day backing up data and spend less money by purchasing less costly storage solutions. In especially organized companies, the IT department may mandate that the different categories of files should be stored in separate directories to make it possible to automatically move off the non-business critical files after they have been on the server for a few days. However, once a file is moved from one directory to another, the file automatically falls under the policy on that directory, which may be incorrect and cost the company money. The File Classification Infrastructure can allow an administrator to classify files based on their location and ensure that those classifications stay attached to the individual files. A File Management Task can then be utilized to move files to the secondary server. For this scenario, the administrators set up the following directories to make this possible: C:\Server 2008 R2 Labs\File System Classification Infrastructure\Data\High_often: files that are necessary for business and change often C:\Server 2008 R2 Labs\File System Classification Infrastructure\Data\High_rare: files that are necessary for business and change rarely C:\Server 2008 R2 Labs\File System Classification Infrastructure\Data\Low: files that are not necessary for business Part 1: Only Business Critical Files on Primary Storage In FSRM, expand Classification Management and select Classification Properties: Figure Click Create Property in the Actions pane. Figure Note: This opens the Create Classification Property Definition dialog box: In the Property name text box, type the name Business Need for the property. In the Property Type drop-down menu, select Ordered List from the list. Enter the following entries into the Value column below the Property Type dropdown: High often
Etc Maintaining files in the second category on the fastest file servers is expensive and maintenance heavy. If these could be automatically moved off to another server shortly after appearing on the file server, IT Departments could spend less time per day backing up data and spend less money by purchasing less costly storage solutions. In especially organized companies, the IT department may mandate that the different categories of files should be stored in separate directories to make it possible to automatically move off the non-business critical files after they have been on the server for a few days. However, once a file is moved from one directory to another, the file automatically falls under the policy on that directory, which may be incorrect and cost the company money. The File Classification Infrastructure can allow an administrator to classify files based on their location and ensure that those classifications stay attached to the individual files. A File Management Task can then be utilized to move files to the secondary server. For this scenario, the administrators set up the following directories to make this possible: C:\Server 2008 R2 Labs\File System Classification Infrastructure\Data\High_often: files that are necessary for business and change often C:\Server 2008 R2 Labs\File System Classification Infrastructure\Data\High_rare: files that are necessary for business and change rarely C:\Server 2008 R2 Labs\File System Classification Infrastructure\Data\Low: files that are not necessary for business Part 1: Only Business Critical Files on Primary Storage In FSRM, expand Classification Management and select Classification Properties: Figure Click Create Property in the Actions pane. Figure Note: This opens the Create Classification Property Definition dialog box: In the Property name text box, type the name Business Need for the property. In the Property Type drop-down menu, select Ordered List from the list. Enter the following entries into the Value column below the Property Type dropdown: High often
File-System-Classification-Infrastructure.docx