emcmagic
3 Argentium

file systems on Data Domain?

I am a kind of confused by file systems on Data Domain.

'nfs show clients' is to list "paths". Aren't they file systems as well ? If they are not FS, then how can they be exported to clients?

OR, DD has only one file system, and all "paths" are creaed on the same file system? In regular Unix file system, nfs exports "file system" to clients,

based on 'df' command below, df is supposed to show all file systems, so, are both /data and /ddvar file systems?

# df

Active Tier:

Resource           Size GiB    Used GiB   Avail GiB   Use%   Cleanable GiB

----------------   --------   ---------   ---------   ----   -------------

/data: pre-comp           -   2017644.0           -      -               -

/data: post-comp   218428.5    168477.0     49951.5    77%          7891.5

/ddvar               132.9         8.8       117.3     7%               -

----------------   --------   ---------   ---------   ----   -------------

As you can tell, I am kind of confused...

Appreciate your help.

Tags (2)
0 Kudos
17 Replies
ble1
6 Indium

Re: file systems on Data Domain?

DDOS has single file system.  You share path which you mount as machine:/path to your NFS client.

emcmagic
3 Argentium

Re: file systems on Data Domain?

Great! Your message cleared up one big question in my mind.

Then if you look back "df" output, what are /data and /ddvar respectively? are they just two different paths on the same file system? what are differences between them?

Thank you!

0 Kudos
ble1
6 Indium

Re: file systems on Data Domain?

/data is where you data end -  you should not touch that one.

/ddvar is interesting if you wish to access logs.

I usually do not allow any access to any of those   Going back to nfs show clients, you will most likely have:

/data/col1/<backup server hostname> 

If you use AFTD (or DDBoost), this will be mtree where you backups go (and this is already part of /data from df).

0 Kudos
dynamox
6 Thallium

Re: file systems on Data Domain?

/ddvar is a local file system, built on top of internal drives. While /data is another file system built on top of drives in external DAEs.

/dev/dd_dg00p15 on / type ext3 (rw,noatime)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

devpts on /dev/pts type devpts (rw,gid=5,mode=620)

/dev/dd_dg00p14 on /ddr type ext3 (rw,noatime)

/dev/dd_dg00p13 on /ddr/var type ext3 (rw,noatime)

0 Kudos
ble1
6 Indium

Re: file systems on Data Domain?

dynamox wrote:

/ddvar is a local file system, built on top of internal drives. While /data is another file system built on top of drives in external DAEs.

True only for boxes with external enclosures - low end models share it, right?

0 Kudos
dynamox
6 Thallium

Re: file systems on Data Domain?

don't have low end models but i suspect it's not sharing drives with /data  ..must be using separate drives.

0 Kudos
ble1
6 Indium

Re: file systems on Data Domain?

Could be.  Not sure how it is there.  I have DD160 at small location and I remember it is headless system with single spare for all disks inside which all at the time I checked were identical.

0 Kudos
emcmagic
3 Argentium

Re: file systems on Data Domain?

I have 4 drives in enclosure 1, and assuming they are local drives. the other 155 drives in enclosure 2 and 3 and assuming they are in DAEs, as dynamox indicated.

Now, what commands to confirm /ddvar is on 4 internals and /data is on other drives?

So, do we have 2 file systems total here, one is /ddvar and the other /data?

dynamox, what command you used to list all entries that are supposed to be in /etc/fstab, ex, /dev/dd_dg00p15 in your message?

0 Kudos
ble1
6 Indium

Re: file systems on Data Domain?

Those 4 drives are head. The others are where you data lives.

You can run command like df if you exit to shell, but this is not something allowed for general public.  There is no need for you to check this as this is standard rollout by DDOS and it is as that and no other way.  To be brutally honest, you are wondering about wrong things here.  DD is supposed to be black box in terms of internal setup and customers are restricted in what they can run themselves.  Even if you see how it is done (eg. during webex), doing it yourself might cost you loss of support so no need to go there.