File servers
DTU Compute IT Support provides a number of filsystems. Some of the more "important" ones are mentioned below.
Contents
List of file systems:
/home/<username> \\nas1.compute.dtu.dk\home|home1|home2|home3|home4\<username>:
Description: Standard UNIX homedirectory. Mountet as x:\ on Windows PC. Every user has exactly one folder on nas1.
Backup frequency: Daily
Live data: yes
Snapshots: yes
\\nas1.compute.dtu.dk\winhome\<username>:
Description: A CIFS-only share mountet as h:\ on Windows PC.Every user has exactly one folder
Backup frequency: Daily
Live data: yes
Snapshots: yes
/project/<projectname> \\comp-nas3.compute.dtu.dk\project\<projectname>:
Description: Areas with greater capacity than HOME but lower backup frequency. Ask DTU Compute ITSupport for a folder.
Backup frequency: Weekly
Live data: yes
Snapshots: yes
/dtu-compute/<projectname> \\comp-nas3.compute.dtu.dk\dtu-compute\<projectname>:
Description: Areas, which is available from both DTU Compute servers as well as from DTU Computing Center cluster machines. Ask DTU Compute ITSupport for a folder.
Backup frequency: None
Live data: yes
Snapshots: yes
/nobackup/<projectname> \\comp-nas3.compute.dtu.dk\nobackup\<projectname>:
Description: Larger disk areas mainly for performing calculation on the linuxgrid. Ask DTU Compute ITSupport for a folder.
Backup frequency: None
Live data: yes
Snapshots: yes
/groups (UNIX servers) \\nas1.compute.dtu.dk\groups:
Description: Files for group based projects
Backup frequency: Daily
Live data: yes
Snapshots: yes
/www/docs (UNIX servers) \\www2.compute.dtu.dk\docs:
Description: Web pages for courses projects etc.
Backup frequency: Daily
Live data: yes
Snapshots: no
/www/home/<username> (UNIX servers) \\www2.compute.dtu.dk\<username>:
Description: Personal www pages. Every user has exactly one folder.
Backup frequency: Daily
Live data: yes
Snapshots: no
\\nas1.compute.dtu.dk\backups\<username>::
Description: A CIFS share for making backup of Windows PC using immbackup.
Backup frequency: Daily
Live data: no(should always be a copy of data found on a local hard drive)
Snapshots: yes
/backup/<username> on userbackup1.compute.dtu.dk:
Description: A share for making backup from linux/Mac PC's using rzyncbackup.
Backup frequency: Daily
Live data: no (should always be a copy of data found on a local hard drive)
Snapshots: yes
\\nas1.compute.dtu.dk\software::
Description: Software for Windows. Mountet as s:\ drive on Windows PC connected to the DTU Compute Windows domain.
Backup frequency: Daily
Live data: yes
Snapshots: yes
\\nas1.compute.dtu.dk\software_mac:
Description: Software for Mac OS
Backup frequency: Daily
Live data: yes
Snapshots: yes
Note: All files are sync'ed daily to a shadow server which ensures that only up to one working day of data are lost in case of a complete failure of comp-nas3.compute.dtu.dk.
Snap shots and how to use them
On all the filesystems hosted on nas1.compute.dtu.dk and comp-nas3.compute.dtu.dk snapshots are made: A snapshot is a read-only copy of a filesystem at specific time. Snapshots does not use ones quota.
Snapshots are taken with different frequency and are accessed depending on the server:
nas1.compute.dtu.dk:
Frequency
Hourly: last 16 snapshots are kept (usually taken on min. 05)
Daily: last 6 are kept (usually taken just after midnight)
Weekly: last 2 are kept (usually taken night between Saturdat and Sunday)
The latest 4 hourly are kept and the last 5 nightly are kept.
How to user them
From a UNIX client:
In the directory where the old file was, change to the folder .snapshot. In this directory there is a number of directories and is directory indicates when the snapshot was taken.
drwx------ 23 root root 4096 Aug 18 08:55 daily.2016-09-28_0010 drwx------ 23 root root 4096 Aug 18 08:55 daily.2016-09-29_0010 drwx------ 23 root root 4096 Aug 18 08:55 daily.2016-09-30_0010 drwx------ 23 root root 4096 Aug 18 08:55 daily.2016-10-01_0010 drwx------ 23 root root 4096 Aug 18 08:55 daily.2016-10-02_0010 drwx------ 23 root root 4096 Aug 18 08:55 daily.2016-10-03_0010 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_0005 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_0105 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_0205 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_0305 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_0405 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_0505 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_0605 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_0705 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_0805 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_0905 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_1005 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_1105 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_1205 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_1305 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_1405 drwx------ 23 root root 4096 Aug 18 08:55 hourly.2016-10-03_1505 drwx------ 23 root root 4096 Aug 18 08:55 weekly.2016-10-02_0015 drwx------ 23 root root 4096 Aug 18 08:55 weekly.2016-09-05_0015
Note the folder .snapshot is not visible, i.e. it will not show in a "ls -la" listning.
If the folder .snapshot does not exist it is because the parent folder was created after the latest snapshot was taken. Also, if only some of the "hourly" and "daily" folders exist it is because the parent folder was not created at the time of the missing snapshot.
Hint: the command find will pr. default search the .snapshot directory the command find . -name some-name is issued. Use the command find * -name some-name instead. This can speed up the process with a factor 10 or better.
From Windows client:
Either like UNIX, i.e. change to a hidden folder ~snapshot and browse to file of interest. Or find the file/folder of interest, take properties of it and look at Previous Versions tab.
comp-nas3.compute.dtu.dk:
Frequency
Nightly: 23:45 Each snapshot i appended with a number corresponding to day of the week (Monday=1, Tuesday=2, ....) and is kept for one week
How to user them
From a UNIX client:
In the directory where the old file was, change to the folder .zfs/snapshot. In this directory there is 9 directories:
drwxr-xr-x 38 hench unixusers 50 Jun 28 08:44 local1 drwxr-xr-x 38 hench unixusers 50 Jun 28 08:44 local2 drwxr-xr-x 38 hench unixusers 50 Jun 28 08:44 local3 drwxr-xr-x 38 hench unixusers 50 Jun 28 08:44 local4 drwxr-xr-x 38 hench unixusers 50 Jun 28 08:44 local5 drwxr-xr-x 38 hench unixusers 50 Jun 28 08:44 local6 drwxr-xr-x 38 hench unixusers 50 Jun 28 08:44 local7 drwxr-xr-x 38 hench unixusers 50 Jun 28 08:44 copied-280608-185052 drwxr-xr-x 38 hench unixusers 50 Jun 28 08:44 copied-280609-065138
The snapshot is named local1 is the snapshot taken Monday night, etc., etc.
Note the folder .zfs is not visible, i.e. it will not show in a "ls -la" listning.
If the folder .snapshot does not exist it is because the parent folder was created after the latest snapshot was taken. Also, if only some of the snaphots folders are missing it is because the parent folder was not created at the time of the missing snapshot.
Hint: the command find will pr. default search the .snapshot directory the command find . -name some-name is issued. Use the command find * -name some-name instead. This can speed up the process with a factor 10 or better.
From Windows client:
Accessing snapshots is currently not supported.
Mounting from stand alone linux
To mount from a stand-alone linux box one can mount using cifs mount (but only when connected to wired network or VPN) or sshfs.
Note: Due to a security setting on the DTU domain controllers, newer linux distributions can only cifs mount with security level set to ntlm, e.g.:
mount -o username=alice,domain=win,sec=ntlm -t cifs //nas3.compute.dtu.dk/nobackup/myproject /mnt/myproject
...
