Docker excludes

[Richard van Denzel]

Hi All,

Is there a way to exclude docker filesystems? I.e. is it possible to useva
wildcard in exclude.fs?

Richard.

Re: Docker

[Remco Post]

> On 19 Apr 2018, at 14:26, Rhodes, Richard L. <rrho...@firstenergycorp.com> 
> wrote:
> 
> Hi,
> 
> Yesterday I was doing some TSM cleanup.  I found that we had >8000 orphaned 
> filesystems for Linux clients that are all of a form like these:
> 
> ("Days" is days since last backup)
> TSM   Node  DaysFSID Filesystem
> tsm2LITSMA4D    100 633 
> /opt/kubernetes/data/docker/devicemapper/mnt/8659aedb3538a83019159cdb3d00842a4ace85adcd102be4147fa75c0957be60
> tsm2    LITSMA4D100 634 
> /opt/kubernetes/data/docker/devicemapper/mnt/4905b5fb2e596d39f08b6ffc4a8a884a329f98df0b16938b866c31708a7ebe55
> tsm2    LITSMA4D100 635 
> /opt/kubernetes/data/docker/devicemapper/mnt/c40c9bec3b01f0b839778ea2fa06b6b1eb07d9657fe9b41d9d9ecdbded07df32
> tsm2LITSMA5D100 707 
> /opt/kubernetes/data/docker/devicemapper/mnt/fdf32a2dc0048f7b7e9727afecc94d96504632365da88f71cf6509bfd8b08166
> tsm2LITSMA5D100 708 
> /opt/kubernetes/data/docker/devicemapper/mnt/4e17d69255758d1a09f79ee2c9cff06e3c73a852d51d144d28018ebbce9a38dc
> tsm2LITSMA5D100 709 
> /opt/kubernetes/data/docker/devicemapper/mnt/d7b497e5ee74a180f3a2a99c33a2af4ef3dbb57cd02b62b1dfd5cc6544c557d7
> 
> I think this is from an installed application, and we have no inhouse 
> knowledge about Docker.  My guess is that these are container filesystems 
> that the dsmc client swept up
> 
> Questions:
> 
> Should these be backed up?

usually not, docker images are created on the fly when a docker container gets 
activated (deployed). These containers are deployed from a configuration file 
(in your case in kubernetes, a tool to maintain docker containers)

> How would you exclude them since the filesystem name changes all the time?
> 

exclude.fs /opt/kubernetes/data/docker/devicemapper/mnt/* should do the job I 
guess

> 
> Thanks!
> 
> Rick
> 
> 
> 
> --
> 
> The information contained in this message is intended only for the personal 
> and confidential use of the recipient(s) named above. If the reader of this 
> message is not the intended recipient or an agent responsible for delivering 
> it to the intended recipient, you are hereby notified that you have received 
> this document in error and that any review, dissemination, distribution, or 
> copying of this message is strictly prohibited. If you have received this 
> communication in error, please notify us immediately, and delete the original 
> message.

-- 

 Met vriendelijke groeten/Kind Regards,

Remco Post
r.p...@plcs.nl
+31 6 248 21 622

Docker

[Rhodes, Richard L.]

Hi,

Yesterday I was doing some TSM cleanup.  I found that we had >8000 orphaned 
filesystems for Linux clients that are all of a form like these:

("Days" is days since last backup)
TSM   Node  DaysFSID Filesystem
tsm2LITSMA4D100 633 
/opt/kubernetes/data/docker/devicemapper/mnt/8659aedb3538a83019159cdb3d00842a4ace85adcd102be4147fa75c0957be60
tsm2LITSMA4D100 634 
/opt/kubernetes/data/docker/devicemapper/mnt/4905b5fb2e596d39f08b6ffc4a8a884a329f98df0b16938b866c31708a7ebe55
tsm2LITSMA4D100 635 
/opt/kubernetes/data/docker/devicemapper/mnt/c40c9bec3b01f0b839778ea2fa06b6b1eb07d9657fe9b41d9d9ecdbded07df32
tsm2LITSMA5D100 707 
/opt/kubernetes/data/docker/devicemapper/mnt/fdf32a2dc0048f7b7e9727afecc94d96504632365da88f71cf6509bfd8b08166
tsm2LITSMA5D100 708 
/opt/kubernetes/data/docker/devicemapper/mnt/4e17d69255758d1a09f79ee2c9cff06e3c73a852d51d144d28018ebbce9a38dc
tsm2LITSMA5D100 709 
/opt/kubernetes/data/docker/devicemapper/mnt/d7b497e5ee74a180f3a2a99c33a2af4ef3dbb57cd02b62b1dfd5cc6544c557d7

I think this is from an installed application, and we have no inhouse knowledge 
about Docker.  My guess is that these are container filesystems that the dsmc 
client swept up

Questions:

Should these be backed up?
How would you exclude them since the filesystem name changes all the time?


Thanks!

Rick



--

The information contained in this message is intended only for the personal and 
confidential use of the recipient(s) named above. If the reader of this message 
is not the intended recipient or an agent responsible for delivering it to the 
intended recipient, you are hereby notified that you have received this 
document in error and that any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately, and delete the original message.