System Files Clause Samples
The "System Files" clause defines which files or data are considered essential components of a system, typically in the context of software or IT agreements. It usually specifies the types of files included, such as configuration files, executable code, or databases, and may outline how these files are to be managed, accessed, or protected. This clause ensures clarity regarding ownership, maintenance responsibilities, and access rights to critical system elements, thereby reducing the risk of disputes or operational issues related to system integrity and continuity.
System Files. All SQL Server database files and transaction logs (collectively “System Files”), used by an Appliance must reside on either the Appliance or an external storage device (“Supported Equipment”). Notwithstanding the foregoing, System Files do not include LogRhythm archive files.
System Files. All system files, including SQL Server database files and transaction logs, used by an Appliance must reside on either the Appliance or an external storage device purchased from LogRhythm (“Supported Equipment”). If Customer moves the systems files to any equipment not purchased from LogRhythm then (a) this Agreement, including the license to the Software granted in Section 2.1, shall automatically terminate and (b) LogRhythm’s Support Services obligations to Customer shall automatically terminate. Customer will not be entitled to a refund for any fees paid to LogRhythm for such terminations. Notwithstanding the foregoing, system files do not include LogRhythm archive files.
System Files. Common system and program files need not be processed, reviewed or produced. Upon request, the producing Party shall provide an index of the system files excluded from production and the criteria (e.g., non-human readable file, etc.) for not processing the files.
System Files. All SQL Server database files and transaction logs (collectively “System Files”), used by an Appliance must reside on either the Appliance or an external storage device. Notwithstanding the foregoing, System Files do not include LogRhythm archive files. Documentation except as expressly permitted this Agreement; or (f) disclose to any third party the results of any benchmark tests or other evaluation of the Software or LogRhythm UEBA Services. If Customer will utilize the LogRhythm UEBAServices for any purpose other than the detection, mitigation, containment, and eradication of cyberthreats, Customer is responsible for providing notice to, and obtaining consents from, individuals as required by applicable law.
System Files. All SQL Server database f iles and transaction logs (collectively the “System Files”), used by the Hardware must reside on either the Hardware or an external storage device. Notwithstanding the f oregoing, System Files do not include LogRhythm archive files.
System Files. All system files, including SQL Server database files and transaction logs, used by an Appliance must reside on either the Appliance or an external storage device purchased from LogRhythm (“Supported Equipment”). If trademarks, service marks, trade secrets, patents, patent Customer moves the systems files to any equipment not applications, moral rights, contract rights and other proprietary rights.