Visit Our UNIX and Linux User Community

Top Forums Web Development Some Typical Discourse Docker (Standalone) Rebuild, Restore and Update Times Post 303045708 by Neo on Friday 10th of April 2020 12:40:31 AM
Old 04-10-2020
Some Typical Discourse Docker (Standalone) Rebuild, Restore and Update Times

Just some notes on some typical tasks for Discourse and how long they take:

Restore Postgres DB (Linux Ubuntu, 8 Core 32 GB RAM)

# time ./restoreneo     // simple script that does a command line restore
cd /var/www/discourse
discourse enable_restore
Restore are now permitted. Disable them with `disable_restore`
begin neo restore

Marking restore as finished...
Notifying 'system' of the end of the restore...
Restore done.
discourse disable_restore
Restore are now forbidden. Enable them with `enable_restore`

real	9m58.273s
user	2m20.157s
sys	1m26.850s

Rebuild Discourse Docker standalone app which is already installed (MacOS MacPro (Last 2013) 12-Core, 64GB RAM)

# ./launcher rebuild app

WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed

Please be patient


real	7m18.784s
user	0m1.694s
sys	0m1.116s

This User Gave Thanks to Neo For This Post:

5 More Discussions You Might Find Interesting

1. AIX

Restore previous update w/o multibos

Hi All, How do I restore previous state if my current update failed w/o multibos? Is that possible? Thanks in advance for any idea. (3 Replies)
Discussion started by: itik
3 Replies

2. Shell Programming and Scripting

rebuild/update fuppes database if files are added/removed from directory

The title says it all. I have a upnp server running fuppes that is connected to my xbox360. In order to see the files on the xbox360 i have to manually update and rebuild the database anytime i add or remove files. I have tried cron jobs to do it every 20 min which works, but if I am streaming... (0 Replies)
Discussion started by: tr6699
0 Replies

3. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Two

OK. Like we all do, we learn a lot from tests, test migrations, and so forth. Today, I started from scratch on test migration 2, armed with a lot more knowledge, The main differences are as follows: Installed discourse plugin ruby-bbcode-to-md before starting the install Modified... (30 Replies)
Discussion started by: Neo
30 Replies

4. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Four

Test Build 4 on New Server, with changes identified in discourse test builds 2 and 3, primarily: Insuring ruby-bbcode-to-markdown is enabled. Removing line breaks from ICODE to markdown in migration script. Added vbpostid to posts in discourse to setup migrating vb "thanks" to discourse... (28 Replies)
Discussion started by: Neo
28 Replies

5. What is on Your Mind?

Update on vB3 Migration to Discourse - Issues and Status of BBCode Transformations

We "completed" the migration of this vB3 site to Discourse a number of days ago. However, deeper testing by @Scrutinizer and @MadeInGermany revealed that a lot of text was mangled in the migration. We traced these bugs to two issues: A minor bug in the Ruby vbulletin.rb migration script... (19 Replies)
Discussion started by: Neo
19 Replies
VGCFGRESTORE(8) 					      System Manager's Manual						   VGCFGRESTORE(8)

vgcfgrestore - restore volume group descriptor area SYNOPSIS
vgcfgrestore [-b|--backup_number VolumeGroupBackupNumber] [-d|--debug] [-f|--file VGConfPath] [-l[l]|--list [--list]] [-h|--help] [-i|--ignore_size] [-n|--name VolumeGroupName] [-o|--oldpath OldPhysicalVolumePath] [-t|--test] [-v|--verbose] [PhysicalVolumePath] DESCRIPTION
vgcfgrestore allows you to restore the volume group descriptor area from backup files in /etc/lvmconf or from VGConfPath to the given Phys- icalVolumePath. The default backup file is /etc/lvmconf/VolumeGroupName.conf. This command DOES NOT restore data contained in logical volume(s), only the LVM configuration metadata! OPTIONS -b, --backup_numberVolumeGroupBackupNumber Restore from the specified backup number. Use together with option -n which gives the name of the volume group. See examples below. -d, --debug Enables additional debugging output (if compiled with DEBUG). -f, --file VGConfPath Restore from the specified path. Useful for selection of specific backups in the backup history or for copies of VGDA backups. -i, --ignore_size Restore though the size of the physical volume doesn't match the one in the backup. -l, --list Display volume group information contained in the backup file. If given twice, the physical and logical volume information con- tained in the backup file is also shown. -h, --help Print a usage message on standard output and exit successfully. -n, --name VolumeGroupName Do a restore for this volume group name. -o, --oldpath OldPhysicalVolumePath If the path to the physical volume has changed between backup time and restore time, this option enables you to choose the corre- sponding physical volume path in the backup file. -t, --test Do a test run reading the volume group backup WITHOUT trying to restore it -v, --verbose Give verbose runtime information about vgcfgrestore's activities. --version Output the version number and exit successfully. Examples To display information like with "vgdisplay vg00" stored in the backup file /etc/lvmconf/vg00.conf: vgcfgrestore -n vg00 -l To restore the VGDA of vg00 from the alternative backup file /tmp/vg00-old to physical volume /dev/sdn1: vgcfgrestore -f /tmp/vg00-old -n vg00 /dev/sdn1 To restore the VGDA of vg00 from the alternative backup file /etc/lvmconf/vg00.conf.5.old to physical volume /dev/sda5 : vgcfgrestore -n vg00 -b 5 /dev/sda5 DIAGNOSTICS
vgcfgrestore returns an exit code of 0 for success and > 0 for error: 1 no physical volume on command line 2 invalid physical volume name 3 volume group is active 4 error doing restore to physical volume 5 backup is invalid for this volume group 6 volume group is inconsistent 7 physical volume doesn't belong to volume group backup 8 error reading physical volume 9 error getting size of physical volume 10 error writing VGDA to physical volume(s) 11 error removing special files of volume group 12 error setting volume group into lvmtab 13 error doing backup 95 driver/module not in kernel 96 invalid I/O protocol version 97 error locking logical volume manager 98 invalid lvmtab (run vgscan(8)) 99 invalid command line SEE ALSO
lvm(8), vgcfgbackup(8), vgcreate(8) AUTHOR
Heinz Mauelshagen <> Heinz Mauelshagen LVM TOOLS VGCFGRESTORE(8)

Featured Tech Videos

All times are GMT -4. The time now is 05:37 PM.
Unix & Linux Forums Content Copyright 1993-2021. All Rights Reserved.
Privacy Policy