How to Manage DG Micro Assets on Linux

Plan the DG Micro directory structure

Organizing your Linux file system for DG Micro assets requires a clear separation of concerns. A flat directory becomes unmanageable quickly as raw sensor data, processed models, and system logs accumulate. Establishing a hierarchical structure early prevents permission errors and simplifies backup routines for distributed generation data.

Create a dedicated base directory, such as /var/lib/dg-micro. Inside this root, establish three distinct subdirectories: raw, processed, and logs. The raw folder stores unmodified input from sensors or controllers. The processed directory holds cleaned data or generated reports. The logs folder captures system events, ensuring that verbose debugging output does not clutter your primary data storage.

This separation allows you to apply specific permissions to each folder. For instance, the raw directory might require write-only access for automated scripts, while processed data could be readable by analytics tools. Keeping logs separate ensures that disk space monitoring remains accurate, preventing log rotation issues from interfering with asset storage.

Set permissions for DG Micro files

Configuring secure access controls is the first line of defense for your DG Micro assets. By default, Linux systems may leave configuration files readable by any user on the network. This exposure allows unauthorized users to view sensitive topology data or modify critical settings, potentially destabilizing the entire microgrid.

We will use chmod to restrict file permissions and chown to assign ownership to the correct system user. This ensures that only the DG Micro service account and root administrators can interact with the core files.

1

Identify the DG Micro user and group

Before changing permissions, confirm the user account running the DG Micro service. This is typically a dedicated user like dgmicro or dg-service. You can verify this by checking the process owner:

Unknown component: br

Unknown component: br

ps aux | grep dg-micro

2

Restrict file permissions with chmod

Use chmod to remove read, write, and execute access for "group" and "others". For most configuration files, 600 (owner read/write only) is the standard secure setting. For executable scripts, 700 is appropriate.

Unknown component: br

Unknown component: br

chmod 600 /etc/dgmicro/*.conf

3

Assign ownership with chown

Ensure the files are owned by the DG Micro user identified earlier. This prevents other system users from accidentally modifying or deleting assets even if permissions are misconfigured.

Unknown component: br

Unknown component: br

chown dgmicro:dgmicro /etc/dgmicro/*

4

Verify the changes

Run ls -l on the directory to confirm that only the owner has read/write access. The output should show -rw------- for config files, ensuring no other user can access the DG Micro data.

Previous

1234

Next

These steps lock down the file system layer, complementing network-level security. Regularly audit these permissions, especially after software updates, to maintain a secure DG Micro environment.

Automate DG Micro file backups

Backing up distributed generation (DG) Micro assets requires a strategy that balances frequency with storage efficiency. Since these systems often run on Linux, you can leverage rsync for incremental transfers and cron for scheduling. This combination ensures your configuration files, logs, and critical data are preserved without consuming excessive disk space or network bandwidth.

The goal is to create a silent, reliable pipeline that runs in the background. We will set up a local backup directory, configure rsync to mirror only changed files, and schedule the task to run during off-peak hours.

1

Create the backup destination directory

Establish a dedicated directory for your backups. Use mkdir -p to create the path, ensuring parent directories are created if they do not exist. A common convention is /var/backups/dg-micro or a separate mount point if available.

sudo mkdir -p /var/backups/dg-micro

Set appropriate permissions so that only the root user or the specific service account can write to this directory. This prevents unauthorized modifications to your backup archive.

2

Test the rsync command locally

Before automating, verify the transfer works manually. Use rsync with the -av flags (archive mode and verbose) to copy your DG Micro configuration and data files to the destination. This ensures symlinks, permissions, and timestamps are preserved.

rsync -av /path/to/dg-micro-data/ /var/backups/dg-micro/

Check the output to confirm all files were transferred. If you are backing up remote assets, you can replace the local source path with an SSH-based path (e.g., user@remote:/path/to/data/).

3

Schedule the task with cron

Open the crontab editor for the root user (or the user running the backup service) using crontab -e. Add a new line to schedule the rsync command. For daily backups at 2:00 AM, the entry would look like this:

0 2 * * * /usr/bin/rsync -av /path/to/dg-micro-data/ /var/backups/dg-micro/ >> /var/log/dg-backup.log 2>&1

The >> appends output to a log file, allowing you to audit successful runs or troubleshoot errors. Redirecting stderr (2>&1) ensures error messages are also captured in the same log.

4

Verify log outputs and retention

After the first scheduled run, check /var/log/dg-backup.log to confirm the process executed without errors. Review the backup directory to ensure the file structure matches the source.

Implement a retention policy to prevent the backup drive from filling up. You can add a cleanup step in the cron job or use find to delete backups older than 30 days:

find /var/backups/dg-micro -type f -mtime +30 -delete

This keeps your backup storage lean while maintaining a sufficient history for recovery.

Previous

1234

Next

Pre-Flight Checklist

Monitor DG Micro processes and logs

Tracking the health of distributed generation assets requires a clear view of system activity. On Linux, this means keeping a close eye on the processes running your DG Micro services and the logs they generate. This section covers the essential commands to verify service status and analyze performance data.

Verify service status with systemctl

The first step is confirming that your DG Micro services are active and running. Use systemctl to check the status of specific units. This command provides a quick overview of uptime, recent start/stop events, and any immediate errors.

systemctl status dg-micro-core.service
systemctl status dg-micro-monitor.service

If a service is inactive or failed, the output will show the exit code and the last few lines of the journal. This immediate feedback loop helps you identify if a crash occurred during startup or if the service stopped unexpectedly.

Analyze logs with journalctl

For deeper insights, journalctl is your primary tool. It aggregates logs from the system journal, allowing you to filter by service, priority, and time. This is particularly useful for tracking performance spikes or error patterns over time.

To view logs for a specific service from the last 24 hours, use:

journalctl -u dg-micro-core.service --since "24 hours ago"

You can also filter by log level to focus on warnings or errors:

journalctl -u dg-micro-core.service -p warning

Check process resource usage

Monitoring CPU and memory usage is critical for ensuring your DG Micro processes don’t consume excessive resources. Use top or htop to view real-time process statistics. Look for processes with high CPU percentages or memory usage, which might indicate a memory leak or a bottleneck.

For a more automated approach, you can use ps to list processes sorted by memory usage:

ps aux --sort=-%mem | grep dg-micro

This command filters the process list to show only DG Micro-related processes, sorted by memory consumption. This helps you quickly identify if any single process is consuming an disproportionate amount of resources.

Automate log rotation and retention

Logs can grow quickly, especially in high-traffic microgrid environments. Ensure journald is configured to rotate logs and limit disk usage. Edit /etc/systemd/journald.conf to set SystemMaxUse and MaxRetentionSec.

[Journal]
SystemMaxUse=500M
MaxRetentionSec=1week

After updating the configuration, restart the journald service to apply changes:

systemctl restart systemd-journald

This ensures that logs are automatically rotated and old entries are discarded, preventing disk space issues while retaining recent history for troubleshooting.

Managing DG Micro Assets on Linux

This section addresses frequent questions about handling distributed generation assets on Linux systems. The focus is on security, automation, and file management for DG Micro infrastructure.