<div dir="ltr"><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I am a proponent of mass data backup. Running Spider in a Linux Virtual box, what is the best way to back up these files? I have used the Clone function in Virtual box to clone the virtual machine. Is there a better way to do this?</div><br clear="all"></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"> <br><b>Regards,<br><br>Anthony </b><div><b> N2KI</b><br><br><br><br><br><br><br><br></div></div></div></div><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Feb 6, 2025 at 9:12 AM Kin via Dxspider-support <<a href="mailto:dxspider-support@tobit.co.uk">dxspider-support@tobit.co.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
As I see no one has answered you, I would say something like this:<br>
<br>
<br>
*Best practices guide for DXCluster network sysops*<br>
<br>
1. Keep the node updated<br>
Always make sure to use the latest stable version of the software.<br>
<br>
2. Perform regular backups<br>
Save copies of configuration files, logs, and databases to ensure recovery<br>
in case of failure.<br>
<br>
3. Monitor the node's status<br>
Keep track of CPU and memory usage, as well as active connections with nodes<br>
and users.<br>
<br>
4. Maintain good communication with neighboring nodes and the community<br>
If you detect connection problems, packet losses, or inappropriate network<br>
usage, notify sysops for a quick resolution. Collaboration is key to the<br>
system’s stability.<br>
<br>
5. Manage network traffic responsibly<br>
Avoid forwarding unnecessary packets that may overload the network.<br>
Configure spot and announcement traffic correctly to avoid duplications,<br>
loops, or congestion.<br>
Perform periodic checks to ensure the proper functioning of node<br>
interconnections.<br>
<br>
6. Configure filters and access permissions correctly<br>
Define clear access rules and permissions to avoid unwanted or malicious<br>
connections, both for users and nodes.<br>
Protect node interconnections through authentication.<br>
<br>
7. Inform the community<br>
It’s important to share details about your node, such as installation type,<br>
node type, access data, sysop contact, and any other relevant information<br>
for the network.<br>
Similarly, report any anomalies, malfunctions, abuse, or hijacking attempts<br>
you detect on the network.<br>
<br>
8. Stay informed and participate in the community<br>
Follow the changes, improvements, and proposals related to the network and<br>
your node software. Use support and communication forums as a valuable tool<br>
to improve the service.<br>
<br>
9. Have a global vision before acting<br>
Before making modifications to your node, analyze how they could affect the<br>
network as a whole. Think not only about your node but also about the global<br>
impact of changes.<br>
<br>
10. Limit misuse of spots and announcements<br>
Avoid excessive use of auto spots and announcements, and help keeping the<br>
network free from insults, threats, political or religious content.<br>
<br>
11. Experiment in closed environments<br>
If you want to try new configurations or developments, do it first in an<br>
isolated environment to avoid affecting the DXCluster network.<br>
<br>
12. Act always within the ham radio ethics<br>
Respect the rules and principles of amateur radio, promoting cooperation and<br>
the good use of shared resources selflessly.<br>
<br>
<br>
But the above does not exist, it is not written, it is a product of my<br>
limited experience with network clusters and a few decades working in<br>
network environments.<br>
<br>
Kin EA3CV<br>
<br>
<br>
-----Mensaje original-----<br>
De: Dxspider-support <<a href="mailto:dxspider-support-bounces@tobit.co.uk" target="_blank">dxspider-support-bounces@tobit.co.uk</a>> En nombre de<br>
Gregor Surmann via Dxspider-support<br>
Enviado el: miércoles, 5 de febrero de 2025 3:49<br>
Para: The DXSpider Support list <<a href="mailto:dxspider-support@tobit.co.uk" target="_blank">dxspider-support@tobit.co.uk</a>><br>
CC: Gregor Surmann <<a href="mailto:gs@funil.de" target="_blank">gs@funil.de</a>><br>
Asunto: [Dxspider-support] List of actions to do<br>
<br>
Hello guys!<br>
<br>
I may be, somehow, slightly confused about what I should do or not do to<br>
comply with the (unwritten or written) rules to keep my DO5SSB-2 node<br>
running and alive.<br>
<br>
I would prefer some short words or a list of things that I should<br>
check/change/improve/etc. Could you provide some information, please?<br>
<br>
Also my answers may be delayed, as I work full time.<br>
<br>
Thank you all in advance!<br>
<br>
73 de Gregor, DO5SSB<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@tobit.co.uk" target="_blank">Dxspider-support@tobit.co.uk</a><br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer" target="_blank">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@tobit.co.uk" target="_blank">Dxspider-support@tobit.co.uk</a><br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer" target="_blank">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</blockquote></div>