dynamox
6 Thallium

Re: Nested File System - Pros and Cons - Going Beyond 16TB

Jump to solution

what are your plans in terms of backups ?  Those are pretty big file systems.

0 Kudos
idsdtapia
2 Bronze

Re: Nested File System - Pros and Cons - Going Beyond 16TB

Jump to solution

Checkpoints and Replication.

0 Kudos
idsdtapia
2 Bronze

Re: Nested File System - Pros and Cons - Going Beyond 16TB

Jump to solution

I hate to ask again but will this allow the application to see one UNC path.  Hence, I will be able to replicate my old 15TB system to a new NMFS system that is 40TB (4 File Systems @ 10 TB each).

Can I add additional File Systems or start with numerous smaller file systems?

Thanks,

Damian

0 Kudos
dynamox
6 Thallium

Re: Nested File System - Pros and Cons - Going Beyond 16TB

Jump to solution

you can share root for NMFS so users can connect to:

NMFSRoot

          -----filesystem1

          -----filesystem2

          -----filesystem3

          -----filesystem4

how are you going replicate ? Celerra Replicator ? That will not work, file systems have to be the same size.

0 Kudos
idsdtapia
2 Bronze

Re: Nested File System - Pros and Cons - Going Beyond 16TB

Jump to solution

Once I migrate/replicate all data from the current 15TB File System.  I will then replicate to an exact size NMFS.  However, I would like to replicate the current file system (locally) rather than "copying" the file system.  Can we replicate (local replication) the current file system and then add it as a component of the NMFS?

0 Kudos
dynamox
6 Thallium

Re: Nested File System - Pros and Cons - Going Beyond 16TB

Jump to solution

you want to copy local file system (15TB) to another local file system (10TB) ?  You can user server_archive command to "copy" data from one file system to another if they are different in size. Target file system should have enough capacity though. I don't see why you would not be able to mount an existing file system under NMFS. Component file systems are still independent components, they can be increased is size separately for example.

0 Kudos
Rainer_EMC
5 Osmium

Re: Nested File System - Pros and Cons - Going Beyond 16TB

Jump to solution

you lost me there - I don't understand what you are trying to do

0 Kudos
idsdtapia
2 Bronze

Re: Nested File System - Pros and Cons - Going Beyond 16TB

Jump to solution

My apologies for not being clear.  The end goal is as follows:

Migrate our 15TB file system to a new File System larger than the 16TB limit on Celerra.

I'm envisioning the following (numbers are NOT concrete).  Multiple File Systems in NMFS were I then can copy our current File System.

Something like the following (again NOT concrete):

4-5 File Systems that are 5-8 TB each; combined we will have 25TB to 40 TB.  Start the copy/migration process to ONE NMFS as opposed to ONE component File System.

Does this make sense?

Thanks Again for all your help,

Damian

0 Kudos
Rainer_EMC
5 Osmium

Re: Nested File System - Pros and Cons - Going Beyond 16TB

Jump to solution

If you mean how you get from your current fs to a nmfs than that's easy

you don't have to copy or replicate the data

just create the nmfs and mount your fs underneath it

please take a look at the Managing Volumes and File Systems Manually manual that describes the steps

I would also suggest to try it with a small test fs first to understand that your share will look differently

0 Kudos
Rainer_EMC
5 Osmium

Re: Nested File System - Pros and Cons - Going Beyond 16TB

Jump to solution

In terms of copying you would need to do that on a component level

and if you do want to distribute the data from the current 15gb to several smaller fs then yes it would have to be file-based (host copy, server_archive or ndmpcopy) and slow

if you app can tolerate the new path then the fastest would be to just mount the existing 15gb fs under a nmfs and create some more component fs

or seriously look at the FMA option

0 Kudos