Recomendados [file Archive]
By default, Personal Folders (.pst) and offline Outlook Data File (.ost) files are in Unicode format in Microsoft Outlook 2010 and Outlook 2013. The overall size of .pst and .ost files has a preconfigured limit of 50 GB. This limit is larger than the limit for Unicode .pst and .ost files in Outlook 2007 and Outlook 2003.
Recomendados [file archive]
The new Outlook file size limit of 50 GB can be increased or decreased by making changes to the Windows registry. For more information, see How to configure the size limit for both (.pst) and (.ost) files in Outlook.
The default .pst file size limit in Outlook 2007 and in Outlook 2003 is 20 GB. If you are using a computer that has Outlook 2007 or Outlook 2003 installed, and you want to access a Unicode .pst file that was created in Outlook 2010 or later, you may have to reduce the size of the .pst file if the file size is at or near 20 GB. If the file size is greater than 20 GB, you will be unable to open the .pst file.
The archive process in Outlook 2010 and Outlook 2013 uses the Modified date on messages to determine the age of the item, but the archive process may not archive as many messages as expected. For more information, see How to change the criteria that Outlook 2010 and Outlook 2013 use to archive different item types.
We welcome queries from researchers about appropriate file formats for working and preservation, particularly early in the research process. If you are unsure of the suitability of your file formats for the data you want to deposit with the UK Data Service, please get in touch.
Apache NiFi can run on something as simple as a laptop, but it can also be clustered across many enterprise-class servers. Therefore, the amount of hardware and memory needed will depend on the size and nature of the dataflow involved. The data is stored on disk while NiFi is processing it. So NiFi needs to have sufficient disk space allocated for its various repositories, particularly the content repository, flowfile repository, and provenance repository (see the System Properties section for more information about these repositories). NiFi has the following minimum system requirements:
The binary build of Apache NiFi that is provided by the Apache mirrors does not contain every NAR file that is part of the official release. This is due to size constraints imposed by the mirrors to reduce the expenses associated with hosting such a large project. The Developer Guide has a list of optional Maven profiles that can be activated to build a binary distribution of NiFi with these extra capabilities.
The next step is to download a copy of the Apache NiFi source code from the NiFi Downloads page. The reason you need the source build is that it includes a module called nifi-assembly which is the Maven module that builds a binary distribution. Expand the archive and run a Maven clean build. The following example shows how to build a distribution that activates the graph and media bundle profiles to add in support for graph databases and Apache Tika content and metadata extraction.
For the partitions handling the various NiFi repos, turn off things like atime.Doing so can cause a surprising bump in throughput. Edit the /etc/fstab fileand for the partition(s) of interest, add the noatime option.
Antivirus software can take a long time to scan large directories and the numerous files within them. Additionally, if the antivirus software locks files or directories during a scan, those resources are unavailable to NiFi processes, causing latency or unavailability of these resources in a NiFi instance/cluster. To prevent these performance and reliability issues from occurring, it is highly recommended to configure your antivirus software to skip scans on the following NiFi directories:
NiFi provides several different configuration options for security purposes. The most important properties are those under the"security properties" heading in the nifi.properties file. In order to run securely, the following properties must be set:
In order to facilitate the secure setup of NiFi, you can use the tls-toolkit command line utility to automatically generate the required keystores, truststore, and relevant configuration files. This is especially useful for securing multiple NiFi nodes, which can be a tedious and error-prone process. For more information, see the TLS Toolkit section in the NiFi Toolkit Guide. Related topics include:
Username/password authentication is performed by a 'Login Identity Provider'. The Login Identity Provider is a pluggable mechanism forauthenticating users via their username/password. Which Login Identity Provider to use is configured in the nifi.properties file.Currently NiFi offers username/password with Login Identity Providers options for Single User, Lightweight Directory Access Protocol (LDAP) and Kerberos.
The nifi.authorizer.configuration.file property specifies the configuration file where authorizers are defined. By default, the authorizers.xml file located in the root installation conf directory is selected.
The authorizers.xml file is used to define and configure available authorizers. The default authorizer is the StandardManagedAuthorizer. The managed authorizer is comprised of a UserGroupProviderand a AccessPolicyProvider. The users, group, and access policies will be loaded and optionally configured through these providers. The managed authorizer will make all access decisions based onthese provided users, groups, and access policies.
Another option for the UserGroupProvider are composite implementations. This means that multiple sources/implementations can be configured and composed. For instance, an admin can configure users/groups to be loaded from a file and a directory server. There are two composite implementations, one that supports multiple UserGroupProviders and one that supports multiple UserGroupProviders and a single configurable UserGroupProvider.
Here is an example composite implementation loading users and groups from LDAP and a local file. Group membership will be driven through the member attribute of each group. The users from LDAP will be read only while the users loaded from the file will be configurable in UI.
In this example, the users and groups are loaded from LDAP but the servers are managed in a local file. The Initial Admin Identity value came from an attribute in a LDAP entry based on the User Identity Attribute. The Node Identity values are established in the local file using the Initial User Identity properties.
If you are upgrading from a 0.x NiFi instance, you can convert your previously configured users and roles to the multi-tenant authorization model. In the authorizers.xml file, specify the location of your existing authorized-users.xml file in the Legacy Authorized Users File property.
After you have edited and saved the authorizers.xml file, restart NiFi. Users and roles from the authorized-users.xml file are converted and added as identities and policies in the users.xml and authorizations.xml files. Once the application starts, users who previously had a legacy Administrator role can access the UI and begin managing users, groups, and policies.
NiFi supports encryption of local repositories using a configurable Key Provider to enable protection of informationon the filesystem. Repository encryption configuration uses a version number to indicate the cipher algorithms, metadataformat, and repository implementation classes. This approach provides a generalized method for configuration without theneed to customize each repository implementation class.
Repository encryption incurs a performance cost due to the overhead of cipher operations. Filesystem encryption at theoperating system level provides an alternative solution, with different performance characteristics. For deploymentswhere filesystem encryption is not configured, repository encryption provides an enhanced level of data protection.Due to increased performance requirements, more computing resources may be necessary to achieve sufficient throughputwhen enabling repository encryption.
Repository encryption supports access to secret keys using standard java.security.KeyStore files.See Secret Key Generation and Storage using Keytool for details on supported KeyStore types, as well as examples ofgenerating secret keys.
On a JVM with limited strength cryptography, some PBE algorithms limit the maximum password length to 7, and in this case it will not be possible to provide a "safe" password. It is recommended to install the JCE Unlimited Strength Jurisdiction Policy files for the JVM to mitigate this issue.
Configuring each Sensitive Property Provider requires including the appropriate file reference property in bootstrap.conf. The default bootstrap.conf includes commented file reference properties for available providers.
This provider uses AWS Key Management Service for decryption. AWS KMS configuration properties can be stored in the bootstrap-aws.conf file, as referenced in bootstrap.conf. If the configuration properties are not specified in bootstrap-aws.conf, then the provider will attempt to use the AWS default credentials provider, which checks standard environment variables and system properties.
This provider uses AWS Secrets Manager Service to store and retrieve AWS Secrets. AWS Secrets Manager configuration properties can be stored in the bootstrap-aws.conf file, as referenced in bootstrap.conf. If the configuration properties are not specified in bootstrap-aws.conf, then the provider will attempt to use the AWS default credentials provider, which checks standard environment variables and system properties.
Azure Key Vault configuration properties can be stored in the bootstrap-azure.conf file, as referenced in thebootstrap.conf of NiFi or NiFi Registry.The provider will use theDefaultAzureCredentialfor authentication.The Azure Identity client librarydescribes the process for credentials resolution, which leverages environment variables, system properties, and fallsback toManaged Identityauthentication. 041b061a72