
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Automated backup and recovery solution capable of restoring files and databases to a given point in time.
Key assumptions made:
The following instructions work for Alpine Linux
apk add --no-cache ruby ruby-rake ruby-io-console ruby-bigdecimal ruby-json ruby-bundler \
tar gzip zlib zlib-dev dcron tzdata
cat > ~/.gemrc <<EOF
---
gem: --no-ri --no-rdoc
EOF
gem install rtbackup
sudo apt-get install -y ruby ruby-dev zlib1g-dev
sudo gem install rtbackup
Make sure that binary logging is enabled on your mysql server. The following settings
need to be enabled in mysql configuration files. On Debian-based Linux distros this
means editing /etc/mysql/mysql.conf.d/mysqld.cnf
, though Alpine Linux and others will
involve editing /etc/mysql/my.cnf
.
[mysqld]
# ...
# Make sure that you know how to use this setting properly if you're using replication.
server-id = 1
log_bin = /var/log/mysql/mysql-bin # Make sure this matches the
# bin_log setting in your backup_conf.yml file.
Then restart mysql:
sudo service mysql restart
# Make sure you know what the group ownership is, for your web root.
sudo usermod -a -G www-data ubuntu
sudo usermod -a -G mysql ubuntu
Set up a configuration file with the following command:
rtbackup create_config
Now edit ~/.backup_conf.yml
and adjust it to fit your app's needs.
Schedule your backups by running
rtbackup crontab
This will enable the recommended backup schedule:
Full backups are all the same, but their retention periods differ.
Change the schedule by running the command:
crontab -e
See the crontab manual pages or look online for tutorials on how to edit cron schedules.
That's all! Your backups are now scheduled. You may run rtbackup daily
in order to get your first
full backup.
some examples
# Take a full backup and store it in the monthly backups location.
rtbackup monthly
# Take a full backup as normal, but instead of backing up all databases,
# only back up `mydatabase`.
rtbackup daily -d mydatabase
rtbackup daily -f # only back up the files, not the database(s)
rtbackup daily -b # only back up the database(s), not the files
# Take an incremental backup, but load the given configuration file.
rtbackup incremental -c /etc/my_backup_configuration.cnf
rtbackup zones # list all
rtbackup zones america # case insensitive search for zones containing a string
# Restore up to the latest backup data available on s3
rtbackup restore
# Restore up to two days ago at 3pm in the configured
# time zone (see config file).
rtbackup restore --up_to='two days ago at 3:00 PM'
# To make it easier to decide what time your restore point
# should be, you can write the restore point time in any time
# zone and it will be translated to the server's normal time zone.
#
# This way, if the server is in UTC and you're in Singapore, you
# don't necessarily have to do any confusing time maths in order
# to restore back to what time it was before you made a mistake
# and updated a wordpress plugin. ;)
rtbackup restore --up_to='March 28 12:00 PM' --time_zone='Singapore'
NAME
rtbackup
SYNOPSIS
rtbackup (restore|zones) backup_type [options]+
PARAMETERS
backup_type (1 -> symbol(backup_type))
specifies the backup type to perform [incremental | daily | weekly |
monthly]
--config=config, -c (0 ~> config=~/.backup_conf.yml)
load configuration from YAML file
--database=database, -d (default ~> database=all)
Which database to back up, defaults to all non-system databases.
--db_only, -b (default ~> false)
If specified
--files_only=[files_only], -f (de ~> files_only)
Only work with files.
--help, -h
website_backup restore app_name
FAQs
Unknown package
We found that rtbackup demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.