4
ReFS Berechtigungen
Eine Einsteigerfrage zu ReFS.
Wie verhält sich das mit vorhanden NTFS Berechtigungen (Active Directory)?
Sind die Berchtigungen kompatibel oder sogar identisch? Wenn man beispielsweise robocopy /SEC verwendet, erhält man dann ein identisches Ergebnis wie auf einem NTFS Volume?
Wie verhält sich das mit vorhanden NTFS Berechtigungen (Active Directory)?
Sind die Berchtigungen kompatibel oder sogar identisch? Wenn man beispielsweise robocopy /SEC verwendet, erhält man dann ein identisches Ergebnis wie auf einem NTFS Volume?
Auf Facebook teilen
Auf Twitter teilen
Auf Reddit teilen
Auf Linkedin teilenBitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben
Content-ID: 5304180089
Url: https://administrator.de/contentid/5304180089
Ausgedruckt am: 23.11.2024 um 09:11 Uhr
4 Kommentare
Neuester Kommentar
Vielen Dank für diesen aufwändig erstellten Beitrag. Doch wo in diesem Artikel wird meine Frage beantwortet?
Die wesentlichen Dingen funktionieren, auch dein Robocopy /SEC.
https://www.ntfs.com/refs-features.htm
https://www.ntfs.com/refs-features.htm
Removed Features
Some NTFS features are not implemented in ReFS. These include object IDs, 8.3 filename, NTFS-compression, Encrypting File System (EFS), transactional NTFS, hard links, extended attributes, and disk quotas. In addition, Windows cannot be booted from a ReFS volume. Dynamic disks with mirrored or striped volumes are replaced with mirrored or striped storage pools provided by Storage Spaces; however, automated error-correction is only supported on mirrored spaces. Data deduplication was missing in early versions of ReFS. it was implemented in v3.2, debuting in Windows Server v1709. Support for alternate data streams was initially not implemented in ReFS. In Windows 8.1 64-bit and Server 2012 R2 the file system reacquired support for alternate data streams, with lengths of up to 128K, and automatic correction of corruption when integrity streams are used on parity spaces. ReFS had initially been unsuitable for Microsoft SQL Server instance allocation due to the absence of alternate data streams.
Some NTFS features are not implemented in ReFS. These include object IDs, 8.3 filename, NTFS-compression, Encrypting File System (EFS), transactional NTFS, hard links, extended attributes, and disk quotas. In addition, Windows cannot be booted from a ReFS volume. Dynamic disks with mirrored or striped volumes are replaced with mirrored or striped storage pools provided by Storage Spaces; however, automated error-correction is only supported on mirrored spaces. Data deduplication was missing in early versions of ReFS. it was implemented in v3.2, debuting in Windows Server v1709. Support for alternate data streams was initially not implemented in ReFS. In Windows 8.1 64-bit and Server 2012 R2 the file system reacquired support for alternate data streams, with lengths of up to 128K, and automatic correction of corruption when integrity streams are used on parity spaces. ReFS had initially been unsuitable for Microsoft SQL Server instance allocation due to the absence of alternate data streams.
