* * * READ ME * * *
                     * * * Veritas Access 7.4.1.0 VA* * *
                      * * * SDFS RELEASE 7.4.1.0 * * *
                             RELEASE Date: 2018-07-06

This document provides the following information:

   * RELEASE NAME
   * OPERATING SYSTEMS SUPPORTED BY THE RELEASE
   * BASE PRODUCT VERSIONS FOR THE RELEASE
   * SUMMARY OF INCIDENTS FIXED BY THE RELEASE
   * DETAILS OF ISSUES FIXED IN THE RELEASE
   * KNOWN ISSUE IN THE RELEASE
   * INSTRUCTIONS

RELEASE NAME
----------
Veritas Access 7.4.1.0 RELEASE for sdfs 7.4.1.0


OPERATING SYSTEMS SUPPORTED BY THE RELEASE
----------------------------------------
RHEL7 x86-64


BASE PRODUCT VERSIONS FOR THE RELEASE
-----------------------------------
   * Veritas Access 7.4.1.0 VA
   

SUMMARY OF INCIDENTS FIXED BY THE RELEASE
---------------------------------------
RELEASE ID: 7.4.1.0-sdfs
*   3953510 Defect created to track sdfs 7.4.1.0 rpm


DETAILS OF ISSUES FIXED IN THE RELEASE
---------------------------------------
   * Updated log4j to log4j2.


INSTRUCTIONS
--------------
1. Here is the md5sum of the RPM.
-bash-4.2$ md5sum sdfs-7.4.1.0-1.x86_64.rpm
61535e60e97ba99a9f95738e25be414d  sdfs-7.4.1.0-1.x86_64.rpm
-bash-4.2$ cksum sdfs-7.4.1.0-1.x86_64.rpm
527467238 108343884 sdfs-7.4.1.0-1.x86_64.rpm
-bash-4.2$

2. Changing log levels from the volume.xml will not be effective any longer.
You are required to update the “/etc/sdfs/log4j2.xml” file.
To change the log level, edit the “/etc/sdfs/log4j2.xml” file. 
Under the “Loggers” section, search for Logger name="sdfs" and set the level
 to an appropriate value.
Example:
	<Loggers>
		<Logger name="sdfs" additivity="false" level="debug">
			<appender-ref ref="sdfsLog" />
			.
			..
The following log levels are available: "trace", "debug", "info", "warn", "error" and "fatal".

You can find more details about log42.xml parameters at 
https://logging.apache.org/log4j/log4j-2.2/manual/configuration.html

3.	When you are upgrading to sdfs7.4.1 from an earlier version:
	-If you are an existing customer and have backups with previous sdfs 
versions (earlier than  7.3.1.2) , you need to set the xml param “dist-layout” to false 
in extended config volume.xml before mounting the sdfs volume.
	-If you are an existing customer and have taken backup with sdfs7.3.1.2 and 
later versions without setting the “dist-layout” to false, and if there is a problem 
with restore, you need to unmount the sdfs volume, set “retry-layout” to true in volume.xml 
and remount sdfs volume before you start restore.
Note: “dist-layout” value is true by default.
	-If you are new customer, no modification is required.

Sample Snip from volume.log:
<extended-config allow-sync="false" block-size="30 MB" data-appendix=".data" 
delete-unclaimed="true" disableDNSBucket="false" dist-layout="true" retry-layout=”true” 
glacier-archive-days="0" io-threads="16" local-cache-size="10 GB" map-cache-size="200" 
read-speed="0" refresh-blobs="false" retry-layout="true" simple-metadata="true" simple-s3="true" 
sync-check-schedule="4 59 23 * * ?" sync-files="true" upload-thread-sleep-time="10000" 
use-basic-signer="true" write-speed="0">


OTHERS
------
NONE