Knowledgebase
Please follow these steps to change the location of the index:
- Stop the "SpaceObServer Data Central" service.
- Find out the current index location. You can see it in the settings > Index Service. The default value is "C:\ProgramData\JAM Software\SpaceObServer\Indices"
- Move everything from that path to the new location, e.g: "D:\SpaceObServer\IndexStorage\".
- Open the "appsettings.json" file (located in "C:\Program Files\JAM Software\SpaceObServer\IndexServer") in an editor, enter "D:\SpaceObServer\IndexStorage\" as "Base Directory", and save.
- Start the "SpaceObServer Data Central" service.
We have a few pages in our manual that describe how to get SpaceObServer connected to SharePoint:
1. Description of the SharePoint scan target
2. Description of multi-factor authentication (MFA/2FA)
In the scan dialog, "Server name" is the URL to the SharePoint, "Path" is the optional subpath on your SharePoint you want to scan, "User name" and "Password" are the fields where you put in your credentials. Alternatively, you can log in using a certificate.
Yes, the SpaceObServer data can be integrated by accessing the database using the database connectors offered in PowerBI. Examples for this can be found in the installation directory of SpaceObServer under 'C:\Program Files\JAM Software\SpaceObServer\Demos\PowerBI' along side a documentation on how to use it.
Due to how the data is structured in the database and how PowerBI uses data there are some limitations on what can be achieved. These are also explained in the documentation.
This error is caused by an operation that is part of the deduplication process and tries to consolidate the different permissions of the duplicates.
Hardlinks all share the same permission settings, so the deduplication process tries to ensure that access rights that a user previously had will still apply after a deduplication.
Here's an example:
Assuming you deduplicate two duplicates "file A" and "file B".
File A has "read only" access for user X
File B has "read and write" access for user X
File B will be replaced by a hardlink that points to File A
The "larger" set of access rights from File B has to be applied to File A as well
In summary: When one of the files is replaced with a hard link to the other, the process will try to merge the permissions of the underlying data. In the example above, the consolidated access rights would be "read and write" for user x.
However, this operation is only successful, if the current user is allowed to change access rights for that particular file, or for files in the current folder. It is important to keep in mind that having the access right to change or write a file does not automatically include the access right to change the permission settings of that file.
If you receive an error message "Failed to merge permissions: Access is denied", then this means your current user is not allowed to change these permission settings and no deduplication will be performed for this set of duplicates.
This can be the case either if he does not have an "Allow" entry for the operation "Change permissions", or if an explicit "Deny" entry exists for that. It is also important to note that a "Deny" entry will always overrule an "Allowed" entry, if both are set.
There can be several possible causes:
- The last indexing run took place before the file was created or modified, so the current content of that file isn't yet in the index.
- The indexing service may not have had sufficient permissions to access the file.
- The file's type isn't (yet) supported - see https://knowledgebase.jam-software.com/7719
- The file is invalid, corrupted or otherwise unreadable.
- DataCentral ran into a problem when extracting the file (for example, because it's too large or has an unexpected structure).
- DataCentral does not index files that have any of these attributes: Hidden, Temporary, NotContentIndexed
- If the file was indexed successfully, but UltraSearch still doesn't find your search term, it might be due to the term itself - or it could be that less important content (for example, HTML tag names) isn't included in the index.
No, DataCentral does not transfer any sensitive data out of your company network. All data is stored in an on-premises database on your premises.
No cloud services are required or used when using DataCentral.
DataCentral has access control implemented.
Although, there might be files indexed that are not accessible by some users, DataCentral automatically only delivers search results the specific UltraSearch user has access to.
No. There are no built-in limitations regarding amount of files/data. However infrastructure and SQL server may impose limits. The number of scanned elements therefore has an impact on the speed of creating reports. Some reports might scale worse than others depending on the number of files scanned. We expect up to 500 mio files per scan to work given that the SQL server has sufficient resources and the connection to the storage system is good with low latency.
When dealing with very large folders/drives, the infrastructure SpaceObServer is hosted on could cause performance bottlenecks. Please find our recommendations here.
Usually, you need 1 license to run SpaceObServer and DataCentral on a server + n licenses of UltraSearch Professional for n people that can search the DataCentral indexes.
The amount of data in the indexes and the number of searches is unlimited.
The size of the index varies and depends on many factors:
- the number of actually indexable files (xlsx and txt are indexable... exe, images & videos are not)
- the size of the files
For an average drive, the required space ranges between less than 0.01% of the target to 1%.
For a very high ratio of textual content, up to 30% of the target size might be necessary, but this is quite rare.
Need further help getting started?
You did not find what you were looking for? Please contact us so we can provide an answer to your question.
Contact Form