I just tried to restore from this morning's backup of an instance which is stuck at v1.8.0.beta2 +3 due to linode not having aufs.
i exported, setup a new box from scratch on DO, and followed the easy-setup.
I'm getting this error on restore: function restore.follow_boards() does not exist
RDB: 0 MB of memory used by copy-on-write
2071:M 11 Mar 23:10:20.169 * Background saving terminated with success
2017-03-11 23:14:55 UTC [7677-1] discourse@discourse LOG: duration: 5757.878 ms statement: COPY email_logs (id, to_address, email_type, user_id, created_at, updated_at, reply_key, post_id, topic_id, skipped, skipped_reason, bounce_key, bounced, message_id) FROM stdin;
2017-03-11 23:14:55 UTC [7677-2] discourse@discourse LOG: duration: 227.202 ms statement: COPY incoming_emails (id, user_id, topic_id, post_id, raw, error, message_id, from_address, to_addresses, cc_addresses, subject, created_at, updated_at, rejection_message, is_auto_generated, is_bounce) FROM stdin;
2017-03-11 23:14:58 UTC [7677-3] discourse@discourse LOG: duration: 2462.389 ms statement: COPY post_search_data (post_id, search_data, raw_data, locale) FROM stdin;
2017-03-11 23:15:01 UTC [7677-4] discourse@discourse LOG: duration: 2777.890 ms statement: COPY posts (id, user_id, topic_id, post_number, raw, cooked, created_at, updated_at, reply_to_post_number, reply_count, quote_count, deleted_at, off_topic_count, like_count, incoming_link_count, bookmark_count, avg_time, score, reads, post_type, vote_count, sort_order, last_editor_id, hidden, hidden_reason_id, notify_moderators_count, spam_count, illegal_count, inappropriate_count, last_version_at, user_deleted, reply_to_user_id, percent_rank, notify_user_count, like_score, deleted_by_id, edit_reason, word_count, version, cook_method, wiki, baked_at, baked_version, hidden_at, self_edits, reply_quoted, via_email, raw_email, public_version, action_code, image_url) FROM stdin;
2017-03-11 23:15:03 UTC [7677-5] discourse@discourse LOG: duration: 2442.106 ms statement: COPY scheduler_stats (id, name, hostname, pid, duration_ms, live_slots_start, live_slots_finish, started_at, success) FROM stdin;
2071:M 11 Mar 23:15:03.945 * 10000 changes in 60 seconds. Saving...
2071:M 11 Mar 23:15:03.946 * Background saving started by pid 7697
7697:C 11 Mar 23:15:04.159 * DB saved on disk
7697:C 11 Mar 23:15:04.160 * RDB: 1 MB of memory used by copy-on-write
2071:M 11 Mar 23:15:04.246 * Background saving terminated with success
2017-03-11 23:15:04 UTC [7677-6] discourse@discourse LOG: duration: 665.042 ms statement: COPY stylesheet_cache (id, target, digest, content, created_at, updated_at) FROM stdin;
2017-03-11 23:15:05 UTC [7677-7] discourse@discourse LOG: duration: 269.258 ms statement: COPY topic_users (user_id, topic_id, posted, last_read_post_number, highest_seen_post_number, last_visited_at, first_visited_at, notification_level, notifications_changed_at, notifications_reason_id, total_msecs_viewed, cleared_pinned_at, id, last_emailed_post_number, liked, bookmarked) FROM stdin;
2017-03-11 23:15:07 UTC [7677-8] discourse@discourse LOG: duration: 2797.576 ms statement: COPY unsubscribe_keys (key, user_id, created_at, updated_at, unsubscribe_key_type, topic_id, post_id) FROM stdin;
2017-03-11 23:15:08 UTC [7677-9] discourse@discourse LOG: duration: 412.867 ms statement: COPY uploads (id, user_id, original_filename, filesize, width, height, url, created_at, updated_at, sha1, origin, retain_hours) FROM stdin;
2017-03-11 23:15:13 UTC [7677-10] discourse@discourse LOG: duration: 4391.470 ms statement: ALTER TABLE ONLY unsubscribe_keys
ADD CONSTRAINT digest_unsubscribe_keys_pkey PRIMARY KEY (key);
2017-03-11 23:15:14 UTC [7677-11] discourse@discourse LOG: duration: 971.790 ms statement: ALTER TABLE ONLY email_logs
ADD CONSTRAINT email_logs_pkey PRIMARY KEY (id);
2017-03-11 23:15:14 UTC [7677-12] discourse@discourse LOG: duration: 307.735 ms statement: ALTER TABLE ONLY scheduler_stats
ADD CONSTRAINT scheduler_stats_pkey PRIMARY KEY (id);
2017-03-11 23:15:15 UTC [7677-13] discourse@discourse LOG: duration: 219.281 ms statement: CREATE INDEX idx_search_post ON post_search_data USING gin (search_data);
2017-03-11 23:15:16 UTC [7677-14] discourse@discourse LOG: duration: 1010.045 ms statement: CREATE INDEX index_email_logs_on_created_at ON email_logs USING btree (created_at DESC);
2017-03-11 23:15:17 UTC [7677-15] discourse@discourse LOG: duration: 717.264 ms statement: CREATE INDEX index_email_logs_on_message_id ON email_logs USING btree (message_id);
2017-03-11 23:15:18 UTC [7677-16] discourse@discourse LOG: duration: 1154.586 ms statement: CREATE INDEX index_email_logs_on_reply_key ON email_logs USING btree (reply_key);
2017-03-11 23:15:19 UTC [7677-17] discourse@discourse LOG: duration: 1224.742 ms statement: CREATE INDEX index_email_logs_on_skipped_and_created_at ON email_logs USING btree (skipped, created_at);
2017-03-11 23:15:21 UTC [7677-18] discourse@discourse LOG: duration: 1744.452 ms statement: CREATE INDEX index_email_logs_on_user_id_and_created_at ON email_logs USING btree (user_id, created_at DESC);
2017-03-11 23:15:22 UTC [7677-19] discourse@discourse LOG: duration: 401.306 ms statement: CREATE INDEX index_unsubscribe_keys_on_created_at ON unsubscribe_keys USING btree (created_at);
2017-03-11 23:15:22 UTC [7677-20] discourse@discourse LOG: duration: 148.865 ms statement: CREATE UNIQUE INDEX index_uploads_on_sha1 ON uploads USING btree (sha1);
2017-03-11 23:15:22 UTC [7677-21] discourse@discourse ERROR: function restore.follow_boards() does not exist
2017-03-11 23:15:22 UTC [7677-22] discourse@discourse STATEMENT: CREATE TRIGGER auto_follow AFTER INSERT ON users FOR EACH ROW EXECUTE PROCEDURE restore.follow_boards();
root@discuss:/var/discourse#
The old instance is still fine.. it's just out of date. Any tips on restoration?
)
**
