Differences

This shows you the differences between two versions of the page.

--- cloudappliance/faq [2018_07_30 16:06] – [15 Can I backup the appliance?] jim
+++ cloudappliance/faq [2019_05_29 09:59] – smeadmin
@@ Line 147: / Line 147: @@
-Although Storage Made Easy does not cache any data, if 'resume upload' is enabled for a package files ban be stored on the server whilst uploading (to enable resume to occur) which can fill up the disk space. You can disable this from the package assigned to the users as the appladmin user.\\ \\  You can also increase the disk space for the appliance by following this [[http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1006371|article]].\\ \\  Temporary files are stored at ''%%/var/www/smestorage/public_html/cgi-bin/uploader/tmp%%'' in the event you need to clear the files manually prior to applying the suggested changes.
+Although the File Fabric does not cache any data, if 'resume upload' is enabled for a package files ban be stored on the server whilst uploading (to enable resume to occur) which can fill up the disk space. You can disable this from the package assigned to the users as the appladmin user.\\ \\  You can also increase the disk space for the appliance by following this [[http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1006371|article]].\\ \\  Temporary files are stored at ''%%/var/www/smestorage/public_html/cgi-bin/uploader/tmp%%'' in the event you need to clear the files manually prior to applying the suggested changes.
@@ Line 155: / Line 155: @@
-Each request to S3 and similar storage services carries a timestamp containing the time at which the request was made. S3 and S3 compatible services will refuse to honour a request to read or write a file if the request appears to be too old (older than 15 minutes in the case of S3) or if it is significantly ahead of the current time as known to the storage server.\\ \\ When this happens SME will display an error message. In some cases the error message won’t indicate that a time difference is the cause of the error but, if you see a message inclusive of this text:\\ \\ ''%%The difference between the request time and the current time is too large%%''\\ \\  you can be sure the cause is that the clock on your SME appliance is out of sync with the clock on your storage service.\\ \\  To fix this problem you need only enable the ntpd service, which keeps the clock on your appliance in sync with a clock on a server that is a reliable time keeper:\\ \\ ''%% \# su - root\ \# systemctl enable ntpd.service\ \# systemctl start ntpd.service%%''\\ \\  S3 and S3 compatible services deal exclusively in Coordinated Universal Time (UTC) for the purpose of comparing request times to the current time. This means that the timezone to which your server is set doesn’t matter. As long as the UTC on your appliance is close to correct, your request should be honoured by the storage service.
+Each request to S3 and similar storage services carries a timestamp containing the time at which the request was made. S3 and S3 compatible services will refuse to honour a request to read or write a file if the request appears to be too old (older than 15 minutes in the case of S3) or if it is significantly ahead of the current time as known to the storage server.\\ \\ When this happens SME will display an error message. In some cases the error message won’t indicate that a time difference is the cause of the error but, if you see a message inclusive of this text:\\ \\ ''%%The difference between the request time and the current time is too large%%''\\ \\  you can be sure the cause is that the clock on your SME appliance is out of sync with the clock on your storage service.\\ \\  To fix this problem you need only enable the ntpd service, which keeps the clock on your appliance in sync with a clock on a server that is a reliable time keeper:\\ \\ ''%% \# su - root\ \# systemctl enable ntpd.service\ \# systemctl start ntpd.service%%''\\ \\  S3 and S3 compatible services deal exclusively in Coordinated Universal Time (UTC) for the purpose of comparing request times to the current time. Your appliance time zone should be set to UTC timezone.