This commit is contained in:
2021-12-13 00:02:49 +00:00
parent c9dbb15f87
commit b41904a016

View File

@@ -26,56 +26,8 @@ Prioritize anything that stands in the way of beta testing
TODO: NEXT:
## TEST BACKUP AND RESTORE USING GREEN AMS DROPLET FROM HERE WINDOWS BACKUP
this is ultimate test, make sure have attachments etc, do full backup and full restore
document it and build docs for it
1) Downloaded backup from amsterdam server, two files attachments and db, data was migrated from v7 trial on my pc to amsterdam trial52 server
Restoring to windows server here
Manual restore steps
Ensure data folders exist, clear out attachments and backups is currently empty
windows
psql -U postgres --set ON_ERROR_STOP=on AyaNova < C:\temp\xfer\amsbackup\db-20211212195504569.backup
pg_restore -C -d postgres C:\temp\xfer\amsbackup\db-20211212195504569.backup
pg_restore -U postgres -C -c -d postgres C:\temp\xfer\amsbackup\db-20211212195504569.backup
Error on first attempt:
pg_restore: terminated by user
^C
C:\data\code\postgres_14\bin>pg_restore -U postgres -C -c -d postgres C:\temp\xfer\amsbackup\db-20211212195504569.backup
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 4649; 1262 16384 DATABASE AyaNova postgres
pg_restore: error: could not execute query: ERROR: invalid locale name: "C.UTF-8"
Command was: CREATE DATABASE "AyaNova" WITH TEMPLATE = template0 ENCODING = 'UTF8' LOCALE = 'C.UTF-8';
pg_restore: error: could not execute query: ERROR: database "AyaNova" does not exist
Command was: ALTER DATABASE "AyaNova" OWNER TO postgres;
pg_restore: error: reconnection failed: connection to server at "localhost" (::1), port 5432 failed: FATAL: database "AyaNova" does not exist
Linux -> windows error of some kind maybe?? Research that shit
Fix is to create dest db first as I already wrote in instructions but then restore to *that* db, don't make a new one so this is the command line in this scenario:
C:\data\code\postgres_14\bin>pg_restore -U postgres -c -d AyaNova C:\temp\xfer\amsbackup\db-20211212195504569.backup
## FINAL BETA INSTALL EVERYTHING TO CONFIRM DOCS
TODO: FInally, last step before considering installs done is to do a fresh round of all installs following docs and make sure nothing missed or unclear or not working as expected
Not sure, build installers and post them I guess, and back to list, probably time to face the cases amongst other things and triage the stuff added recently
report sample stuff limited to report designer roles and etc
@@ -91,19 +43,9 @@ OUTSTANDING MAJOR AREAS TO BETA
- Features
Installer
Linux
Offer as archive for docker and for bare metal
Do a manual install of both to a clean server and document each step in the manual
Windows
NEED INSTALL GUIDE WITH EACH TARGET TYPE USER
Dummy installer with everything included and static configuration
network admin installer with server files starts with windows or as a service
config edited by hand, expects postgres already installed
zip installer with guidance
Test restore!!! Super important, also document it in manual
Reports (stock)
mostly there but issue with ordering and missing some obvious ones like Customer etc that should have at least *something* there
mostly there but issue with ordering and missing some obvious ones like Customer etc that should have at least *something* there (ask joyce, her judgement maybe not useful?)
trial / seeder system
do not specify by size but rather scenario
we care about size for load testing but don't want to give impression we think HUGE is just a few 10s of thousands of workorders because it's a db issue at a certain point