Best Practice for Creating Strong Passwords
Do Not Do the Following:
- Never use only numbers or words in a password.
- Do Not Use Recognizable Words
- Do Not Use Words in Foreign Languages
- Do Not Use Personal Information (If the attacker knows your identity, the task of deducing your password becomes easier.)
- Do Not Invert Recognizable Words ( Good password checkers always reverse common word, so inverting a bad password does not make it any more secure.)
Do the Following:
- Make the Password At Least Eight Characters Long
- Mix Upper and Lower Case Letters
- Include Non-Alphanumeric Characters
- Pick a Password You Can Remember
While every customer’s infrastructure is unique, here is a diagram illustrating the general layout of the Eclipse cloud/hosted environment:
UniVerse Database Replication
Data replication frequency: typically “real time”
Time to recovery: typically a few minutes
Eclipse customers that want “real time” replication can use UniVerse’s native replication functionality. The software is configured to capture writes to the database and replicate them to a secondary server while preserving the integrity of the database. Recovery is also quick, since the Eclipse software is already up and running on the secondary server. This solution is implemented and supported directly by the database vendor, Rocket Software, so please contact your account manager for more details.
NOTE: these steps must be performed on the same LAN as the device.
- Record the MAC address of the Digi device (located on the label side (bottom) of the unit)
- Manually update the workstation’s ARP table using the Digi device’s MAC using one of the commands below, substituting the new Digi’s IP address and MAC address:
arp -s 192.168.2.2 00-00-9d-22-23-60
arp -s 192.168.2.2 00009d222360
- Ping the Digi device using the IP address just assigned:
If your system is configured to perform an rsync backup as part of the standard snapshot script, simply run the following command:
at now -f /u2/UTILS/bin/snapsave_linux.sh
To schedule the backup at specific date and time, for example at 11PM today, change now to 23:00.
at 23:00 -f /u2/UTILS/bin/snapsave_linux.sh
This script will suspend your database, take snapshots of the database files and create a full tape backup. You will not see any output in your console session, because the script creates a separate log file under /tmp/snapsave.log.
If you have already created the snapshot filesystem, but you want to perform a separate manual tape backup:
rsync -avz --delete --stats /snap/u2/ /mnt/nas/rsync/
If there are no snapshots present, but no users are on the system and you want to perform a manual rsync backup:
rsync -avz --delete --stats /u2/ /mnt/nas/rsync/
How to use the at command
How to use rsync