Question

1.When is one big file server preferable to several smaller ones? Identify the volume types? You are deciding which file system to use. You need NTFS permission system support.
You don’t presently need encryption or compression, but might at a later date. What file system is your best choice?

# Note - No plagiarism please

Answer 1

Dear Student I understand the following questions you have asked and you may also be knowing about answering this question might be a bit tricky.Please go through the following paragraphs given below and try to interpret.This will surely resolve all your queries and you will not face any issues.

The short answer is that everything relies upon your application and what is running on the worker:

Having more workers enables you to deal with worker disappointments all the more without any problem. In the event that you have 10 workers and one bombs chances are nobody will see on the off chance that you have it effectively arrangement. What do you do in the event that you simply have one monstrous worker and it begins smoking?

In case you're in a circumstance where you're running different workers you presumably have the spending plan to place them all in a private rack behind a switch. For this situation the between worker network doesn't add to your month to month transmission capacity.

A few applications are difficult to scale out, for instance a few information bases in certain circumstances. For this situation it is simpler to scale up for some time before considering to scale out.

Worker cost is a major factor in concluding if to scale up. At the point when you're leasing a greater worker starts to cost significantly more than at least two more modest workers so it bodes well proportional out. This might be to a lesser extent a factor in the event that you really purchase/construct your own workers and use colocation administrations.

I hope this answers your first subpart of the gven question.

Now lets move ahead and solve the next subpart.

NTFS (NT File System) is a restrictive journaling document framework created by Microsoft.[1] Starting with Windows NT 3.1, it is the default record arrangement of the Windows NT family.[9]

NTFS has a few specialized enhancements over the document frameworks that it supplanted – File Allocation Table (FAT) and High Performance File System (HPFS) –, for example, improved help for metadata and progressed information structures to improve execution, unwavering quality, and circle space use. Extra augmentations are a more detailed security framework dependent on access control records (ACLs) and document framework journaling.

NTFS is upheld in other work area and worker working frameworks also. Linux and BSD have a free and open-source NTFS driver, called NTFS-3G, with both peruse and compose usefulness. macOS accompanies read-just help for NTFS; its compose uphold for NTFS is precarious, so of course record composing is handicapped.

Now Lets move ahead to final subpart C so that it clears all your tricky questions.

If you need the drive for a Windows-just climate, NTFS is the most ideal decision. On the off chance that you have to trade documents (even every so often) with a non-Windows framework like a Mac or Linux box, at that point FAT32 will give you less agita, as long as your record sizes are more modest than 4GB

Dear student I hope all your questions have been answered and you have improved your knowledge on the given topic.Be Assured and feel free to ask any questions.Thanks a lot!