vSphere Replication files persmissions

[egaulue]

Hi community,

Does anyone could tell me what should be the vSphere Replication files permission. I inherit a server and find them strange, here for 2 vms :

-rwxrwxrwx+ 1 root root          0 Oct 21 01:09 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26022.vmxf.343685

-rwxrwxrwx+ 1 root root          0 Oct 27 12:43 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26139.vmx.344025

-rwxrwxrwx+ 1 root root       8684 Nov  5 23:52 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26154.nvram.344064

-rwxrwxrwx+ 1 root root       3861 Nov  5 23:52 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26154.vmx.344062

-rwxrwxrwx+ 1 root root        260 Nov  5 23:52 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26154.vmxf.344063

-rwxrwxrwx+ 1 root root       8684 Nov  6 03:48 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26158.nvram.344070

-rwxrwxrwx+ 1 root root       3861 Nov  6 03:48 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26158.vmx.344068

-rwxrwxrwx+ 1 root root        260 Nov  6 03:48 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26158.vmxf.344069

-rwxrwxrwx+ 1 root root       8684 Nov  6 03:59 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26162.nvram.344082

-rwxrwxrwx+ 1 root root       3861 Nov  6 03:58 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26162.vmx.344080

-rwxrwxrwx+ 1 root root        260 Nov  6 03:59 hbrcfg.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.26162.vmxf.344081

-rw-------  1 root root  251678720 Nov  6 03:58 hbrdisk.RDID-9283b317-5201-4cc9-90b2-a701db07d122.38725.43205958700507-delta.vmdk

-rw-------  1 root root        371 Nov  6 03:48 hbrdisk.RDID-9283b317-5201-4cc9-90b2-a701db07d122.38725.43205958700507.vmdk

-rw-------  1 root root   16797696 Nov  6 03:59 hbrdisk.RDID-9283b317-5201-4cc9-90b2-a701db07d122.38726.186057387861861-delta.vmdk

-rw-------  1 root root        437 Nov  6 03:59 hbrdisk.RDID-9283b317-5201-4cc9-90b2-a701db07d122.38726.186057387861861.vmdk

-rw-------  1 root root      20480 Nov  6 03:59 hbrdisk.RDID-9283b317-5201-4cc9-90b2-a701db07d122.38729.269669847780298-delta.vmdk

-rw-------  1 root root        438 Nov  6 03:59 hbrdisk.RDID-9283b317-5201-4cc9-90b2-a701db07d122.38729.269669847780298.vmdk

-rwxrwxrwx+ 1 root root       6000 Nov  6 03:59 hbrgrp.GID-72683db4-0c88-4b5a-8e58-e534d39f5d62.txt

-rwxrwxrwx+ 1 root root 8589934592 Nov  6 03:47 proxy-flat.vmdk

-rwxrwxrwx+ 1 root root        612 Nov  6 03:47 proxy.vmdk

-rwxrwxrwx+ 1 root root        8684 Oct  1 19:01 hbrcfg.GID-e556ddda-7bcc-4077-9bcd-8ee556ea961a.25635.nvram.342606

-rwxrwxrwx+ 1 root root        5018 Oct  1 19:01 hbrcfg.GID-e556ddda-7bcc-4077-9bcd-8ee556ea961a.25635.vmx.342604

-rwxrwxrwx+ 1 root root         258 Oct  1 19:01 hbrcfg.GID-e556ddda-7bcc-4077-9bcd-8ee556ea961a.25635.vmxf.342605

-rw-------  1 root root 25602117632 Oct  2 23:05 hbrdisk.RDID-2085701a-d1f2-456c-9c38-f028b37aec76.37482.89680821583932-delta.vmdk

-rw-------  1 root root         371 Oct  2 13:15 hbrdisk.RDID-2085701a-d1f2-456c-9c38-f028b37aec76.37482.89680821583932.vmdk

-rw-------  1 root root       86016 Oct  2 23:05 hbrdisk.RDID-2085701a-d1f2-456c-9c38-f028b37aec76.38136.76332169607217-delta.vmdk

-rw-------  1 root root         436 Oct  2 23:05 hbrdisk.RDID-2085701a-d1f2-456c-9c38-f028b37aec76.38136.76332169607217.vmdk

-rw-------  1 root root  1728159744 Oct  1 20:59 hbrdisk.RDID-4f582faa-8ec8-4213-ae89-eea05ab39ca4.37473.110238378379207-delta.vmdk

-rw-------  1 root root         373 Oct  1 19:01 hbrdisk.RDID-4f582faa-8ec8-4213-ae89-eea05ab39ca4.37473.110238378379207.vmdk

-rw-------  1 root root      106496 Oct  1 21:00 hbrdisk.RDID-4f582faa-8ec8-4213-ae89-eea05ab39ca4.38111.35669527070949-delta.vmdk

-rw-------  1 root root         438 Oct  1 21:00 hbrdisk.RDID-4f582faa-8ec8-4213-ae89-eea05ab39ca4.38111.35669527070949.vmdk

-rw-------  1 root root 18505396224 Oct  2 16:58 hbrdisk.RDID-95ee4aad-9b36-4d1c-a9df-55a21bbfb01f.37475.134374623950577-delta.vmdk

-rw-------  1 root root         371 Oct  2 13:15 hbrdisk.RDID-95ee4aad-9b36-4d1c-a9df-55a21bbfb01f.37475.134374623950577.vmdk

-rw-------  1 root root      126976 Oct  2 16:58 hbrdisk.RDID-95ee4aad-9b36-4d1c-a9df-55a21bbfb01f.38128.98365607422069-delta.vmdk

-rw-------  1 root root         438 Oct  2 16:58 hbrdisk.RDID-95ee4aad-9b36-4d1c-a9df-55a21bbfb01f.38128.98365607422069.vmdk

-rw-------  1 root root 64894398464 Oct  3 21:32 hbrdisk.RDID-aa8346a6-da8f-457c-8b6a-639547a03608.37481.161924784757161-delta.vmdk

-rw-------  1 root root         373 Oct 27 11:48 hbrdisk.RDID-aa8346a6-da8f-457c-8b6a-639547a03608.37481.161924784757161.vmdk

-rw-------  1 root root      126976 Oct  3 21:32 hbrdisk.RDID-aa8346a6-da8f-457c-8b6a-639547a03608.38157.244178800290821-delta.vmdk

-rw-------  1 root root         439 Oct  3 21:32 hbrdisk.RDID-aa8346a6-da8f-457c-8b6a-639547a03608.38157.244178800290821.vmdk

-rwxrwxrwx+ 1 root root       43287 Aug  6 20:36 hbrgrp.GID-e556ddda-7bcc-4077-9bcd-8ee556ea961a.txt

-rw-------  1 root root 42949672960 Oct  1 17:51 SQL_1-flat.vmdk

-rw-------  1 root root         493 Oct  1 17:51 SQL_1.vmdk

-rw-------  1 root root 64424509440 Nov  6 13:11 SQL_2-flat.vmdk

-rw-------  1 root root         494 Nov  6 12:18 SQL_2.vmdk

-rw-------  1 root root 53687091200 Oct  1 15:39 SQL_5-flat.vmdk

-rw-------  1 root root         494 Oct  1 15:39 SQL_5.vmdk

-rw-------  1 root root 64424509440 Oct  1 18:59 SQL-flat.vmdk

-rw-------  1 root root         492 Oct  1 18:59 SQL.vmdk

So what should be those permissions : 777 or 600? Why are they not all the same? Is there a way to change the umask setting?

Regards,

[daphnissov]

If these are files created or managed in any way by vSphere Replication, don't touch them. There's no need to change file permissions or ownership and doing so will likely result in breaking all or part of replication.