Skip to content

Commit 7e78be3

Browse files
authored
Update hpc_policies.md
1 parent 78901b9 commit 7e78be3

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

mkdocs/docs/HPC/sites/hpc_policies.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Users are requested to:
7676
**All user data will no longer be accessible after a user has left university.**
7777

7878

79-
### Possible actions after user left university
79+
### Possible actions after a user left university
8080

8181
When a user does not offload data before leaving university, user data might remain on HPC storage locations without a direct owner.
8282
If access to this data is for some reason still needed (by the former user, promotor, ...), the following actions could be possible:
@@ -90,9 +90,18 @@ Once the voluntary employee contract is in order, HPC staff can then reinstate t
9090
#### Data transfer by HPC staff
9191

9292
As a very last resort measure, HPC staff can initiate a data transfer to another VSC account when requested by a VO moderator or promotor.
93+
Please be aware that this is a non-trivial operation for HPC-UGent staff:
94+
95+
- it is an entirely manual process
96+
- it is error-prone
97+
- it has risks for the storage integrity
98+
Hence our helpdesk staff needs to be able to dedicate sufficient time and focus to complete this task.
99+
93100
This is extremely time consuming and dangerous to the storage integrity.
94101
If user was in a VO, we will assume all the data is owned by the VO (including HOM/DATA direcotires)
95102

103+
104+
96105
We will assume a VO moderator and/or promotor
97106

98107
{% endif %}

0 commit comments

Comments
 (0)