Solved!
Go to SolutionNested File System - Pros and Cons - Going Beyond 16TB
So here's the issue: Our share is currently as 15 TB and reaching MAX size for a Celerra File System. I'm the lucky one that will migrate/replicate this data over to our CX4-960 that is now connected to the same NAS Gateway. Can I create X amount of File Systems such as:
Images1
Images2
Images3
Images4
Each @ 10 TB
Add then together to form a 40 TB File System?
Add the end of the day I only want to access two shares. Will this setup stripe my data across all file systems? Or am I interpreting Nested File Systems incorrectly.
I'm picturing Nested File Systems as Meta-LUNs.
Thanks for all the support,
Damian
926
0
Posted August 20th, 2010 12:00
Hi dynamox
FMA is currently just archiving (the virtualization / migration / namespace was GFV/FVA/FNA which I think are no longer actively sold)
928
0
Posted August 20th, 2010 12:00
Forgive me for asking FMA?
927
1
Posted August 20th, 2010 12:00
EMC (Rainfinity) File Management Appliance
you could use it to move large files that weren't used in the last xx days to another Celerra file system (or Centera or Data Domain or Atmos cloud storage or ...) replacing them with a 8kB stub that looks and works transparently to the client just like before.
In effect keeping your existing fs and share at 15TB but enabling you to make much much more capacity available.
kinda like an HSM system
take a look at the white papers on Powerlink and talk to your local sales team.
Rainer
926
0
Posted August 20th, 2010 12:00
alias23122 != dynamox
Rainer_EMC wrote:
Hi dynamox
FMA is currently just archiving (the virtualization / migration / namespace was GFV/FVA/FNA which I think are no longer actively sold)
926
1
Posted August 20th, 2010 12:00
NMFS
An NMFS allows you to manage a collection of file systems — Component file
systems as a single file system. CIFS and NFS clients see component file systems
as a single share or single export.
File system capacity is managed independently for each component file system.
This means that you can increase the total capacity of the NMFS by extending an
existing component file system or by adding new component file systems.
The number of NMFS or component file systems is limited only to the number of file
systems allowed on a Data Mover. Hard links (NFS), renames, and simple moves
are not possible from one component file system to another.
Please refer to the attached document.
- Sebby Robles.
927
1
Posted August 20th, 2010 12:00
Rainfinity FMA. It sits between the end users and the Celerra, and virtualizes the namespace. One of its features is what you described, nested file systems. Others are replication, migration, facilitating archiving, etc.
926
0
Posted August 20th, 2010 12:00
whether you can use NMFS really depends on your application and the structure of you data
it would have to be able to use multiple subdir's where each subdir is max 16TB
and also be clever enough to distribute the data across them
926
0
Posted August 20th, 2010 13:00
sorry
alias23122 != dynamox
307
0
Posted August 20th, 2010 20:00
what are your plans in terms of backups ? Those are pretty big file systems.
Rainer_EMC
6 Operator
•
8645 Posts
928
0
Posted August 20th, 2010 12:00
no it won't stripe
a nested mount fs is a number of fs mounted und one mount point to that each fs looks like a subdir but you access it through one share
just look at the manual and try it with some small fs
or look at FMA