idsdtapia
2 Bronze

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

Jump to solution

We need to keep the same UNC path for the application.  I was thinking something like EMCopy.

Will the copy process distribute the files over the smaller file systems?

0 Kudos
Rainer_EMC
5 Osmium

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

Jump to solution

only if you tell it to by running multiple emcopy's to different component fs (subdir)

do not underestimate how long it takes to copy 15TB

Do you understand that NMFS does need at least one subdir between the root and the component?

0 Kudos
ScottHolmanBG
1 Copper

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

Jump to solution

How about using symbolic links?

I've a pair of 16 TB file systems that were close to capacity (dedupe has now given me a lot of breathing space), so have been investigating thewhether it is possible to split the file systems into smaller chucks, but still keep the data structure seen by the user.

I tested NFS, but but that would ahve changed the data structure, so a linux bod at the desk next to me suggested symbolic links. the Celerra supports it and I've found them to work perfectly during testing. I replicate the file systems, and tested ndmp backup at the other side. ndmp does not follow the symbolic link, so you'll have to backup each file system individually, and be aware of where to pull restores.

Due to dedupe saving the day (for now) I've not put this into production, but plan to in the future; assuming futher testing is successful.

Is this not an option?

cheers

0 Kudos