rdxlock_readme.txt Overland Tandberg rdxlock readme for Version Build Major Changes:

Transcription

1 Overland Tandberg rdxlock readme for Version Build Major Changes: RansomBlock feature Enhanced Security Mode (ESM) is mandatory for WORM volumes. Verified Retention Clock (VRC): enhancement of the compliant retention time management in order to improve the support of removable media. WORM volumes can now be taken offline for an extended time period without prolongating the retention periods registered in a volume. After a new installation or an upgrade from versions prior to 2.2.6, a TimeSync Key must be applied subsequently. (for further information read the Administration Guide sections "Verified Retention Clock" and "Post Installation".) ability to install and configure rdxlock without being logged in as local administrator. (for further information read the Administration Guide sections "Installation" and "Setting up a WORM volume".) File system: allow deletion of empty directories. Support of snaplock commit via nfs Improved internals. 2. Supported OS / Filesystem: MS Windows Server 2008 R2 SP2 Standard & Enterprise Edition, 64 bit, Microsoft Failover Cluster Support MS Windows Server 2012 Standard & Enterprise Edition, 64 bit MS Windows Server 2012 R2 Standard & Enterprise Edition, 64 bit, Microsoft Failover Cluster Support MS Windows Server 2016 MS Windows 7, 32 bit, 64 bit MS Windows 8, 32 bit, 64 bit MS Windows 8.1, 32 bit, 64 bit MS Windows 10, 32 bit, 64 bit Itanium based systems are not supported Server Core installations are not supported 3. Overland Tandberg rdxlock system requirements: minimum system requirements: * CPU 1,4 GHz dual core Seite 1

2 * 2GB Ram * 32GB Harddisk for OS * secondary HDD for WORM volume recommended system requirements: * CPU 2,0 GHz dual core * 4GB Ram * 50GB Harddisk for OS * secondary HDD for WORM volume Please see Mircosoft Windows system requirements for details about additional hardware specifications. Please note: consider mentioned system requirements as a basic starting point. Actual system requirements heavily depend on concrete usage scenarios. Therefore you need a sizing based on your fileservers expected workload, which may require much more system ressources. 4. Installation: Administrative rights are required to install, configure or update rdxlock. Run the rdxlocksetup_<versionnumber>.exe to install it. On some Windows OS a "windows logo testing" warning pops up. This can be ignored, press continue. Remark: When installing on Windows 7, Windows 2008 Server or higher you need to be logged in as Administrator or you need to run the installation program using the context menu option Run as administrator. 5. Upgrade: Is only supported from version or higher. Previous versions need a special support, please contact your service provider. Productive volumes need to have the Enhanced Security Mode (ESM) activated, check the known restrictions below before you run the upgrade. rdxlock requires Microsoft Update for Windows 7 and Windows Server 2008 R2. (see "section 10. known issues" for further information) 6. Configuration: please read the rdxlock AdministrationGuide. Seite 2

3 7. MS Cluster systems: rdxlock needs to be installed on every cluster node which will have access to WORM volumes. A volume needs only to be configured as WORM on one cluster node but may be mounted on any cluster node with rdxlock installed. 8. Backup: From a compliance point of view we only advise to use full image backups. File based backup can not guarantee the restore of all worm files. 9. Compatibility Tests: rdxlock was successfully tested in combination with the following 3rd party applications: 9.1. AntiVirus Scanner Symantec AntiVirus Version 12.1 McAfee VirusScan Enterprise 8.7 TrendMicro ServerProtect MS Office 2003/2007/2010: MS Office applications (for reading) 9.3. NFS protocol support rdxlock supports Microsoft Services for Network File Systems (NFS) that is shipped with Windows. 10. Known restrictions: rdxlock is designed for NTFS formatted volumes on primary partitions of basic disks with MBR (master boot record) and GPT (GUID Partition Table) partitioning schema. If rdxlock is configured for a volume residing on a dynamic disk, the Enhanced Security Mode (ESM) will not be supported on that volume. Additionally rdxlock can not be attached to disks which are encrypted by TrueCrypt. rdxlock supports local disks, certified removable devices and certified Seite 3

4 removable media. Shrinking an ESM protected volume is not supported. Adding a mirror to an ESM protected volume is not supported. Read only volumes are not supported. Files, which have Extended Attributes or non rdxlock reparse points attached, can not be set to WORM. Volumes mounted inside a worm volume are not worm protected. 3rd party replication tools were not tested with rdxlock. Some Linux commands (e.g. cp) sets the last access time (beside other times). This is interpreted as retention time for snaplock configured files. In this case a "cp" followed by "chmod w" would not have the default retention time (because the last access was set by the cp). In such situations an explicit "touch a" followed by "chmod w" is required. The Recycle Bin functionality can not be used on WORM volumes, since rdxlock denies the move operation to the recycle bin, when an expired WORM file is selected for deletion. Therefore it is recommended to deactivate the Recycle Bin for the individual WORM volumes to avoid error messages. Files which are existing before setting a volume to WORM need to be manually committed (even if autocommit is enabled). Backing up an image of a single, ESM encrypted partition on a GPT disk is not supported. In this case an image backup of the entire GPT disk must be created including the backup of unused sectors. The replication service user account needs administrative rights including the backup, restore and take ownership privilege. When replicating to a remote share the appropriate share permissions and NTFS security rights must be granted to the service user account. SMB3 protokoll is not yet supported. Deduplication is not supported. 11. Known issues: The rdxlock tab shows for dynamic disks that the ESM module is not installed, even it is installed and running. When the message is displayed that the ESM is not installed, please check both, the ESM installation and if it's not a dynamic disk. Please note that Microsoft has redesigned the Recycle Bin behavior since Windows 7 and Windows 2008 Server. The properties of the Recycle Bin are now tied to user profiles rather than the actual disk. Therefore each user must explicitly switch off the Recycle Bin of the corresponding WORM volumes, when accessing them locally for deleting expired WORM files. On some Windows 7 and Windows 2008 Server versions the SHA 2 code signing support is not available. The rdxlock drivers are signed with SHA 2 and therefore the support is Seite 4

5 mandatory, otherwise the system will blue screen on next boot. Please check Microsoft knowledge base article KB The rdxlock setup tries to detect this situation, disables the rdxlock driver and does not install the enhanced security module. Handling of this situation: Uninstall rdxlock. Update your Windows 7 or Windows 2008 Server Operation System to the current level. Check that the required Microsoft Update has been installed. Install rdxlock with ESM support and reboot. Seite 5