Randallkinard: // via Wikitext Extension for VSCode

2024-11-07T16:25:29Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 11:25, 7 November 2024
Line 275:		Line 275:
	# Press the ellipsis button at the end.		# Press the ellipsis button at the end.

	You've now successfully copied one Grooper Repository from one server to another and connected to it. Next, we're going to open up Grooper and verify we've done our job correctly.		You've now successfully copied one Grooper Repository from one server to another and connected to it. Next, we're going to open the Grooper site and verify we've done our job correctly.

	~~[[File:2022-backup-restore-repo-30.png]]~~

	{\|class="attn-box"		{\|class="attn-box"

Randallkinard: final edits for 2024 // via Wikitext Extension for VSCode

2024-11-07T16:24:18Z

final edits for 2024 // via Wikitext Extension for VSCode

← Older revision		Revision as of 11:24, 7 November 2024
Line 12:		Line 12:
	# Copy the Grooper File Store from the source server to the target server.		# Copy the Grooper File Store from the source server to the target server.
	# Change the Primary File Store's path to copied File Store's location by updating the File Store object in the Tree Node table in SQL Server Management Studio.		# Change the Primary File Store's path to copied File Store's location by updating the File Store object in the Tree Node table in SQL Server Management Studio.
	# Create a new Grooper Repository connection on the target server, connecting to the restored Grooper Database on the target server in Grooper ~~Config~~.		# Create a new Grooper Repository connection on the target server, connecting to the restored Grooper Database on the target server in Grooper Command Console.
	# Verify objects and files are accessible in new Grooper Repository connection.		# Verify objects and files are accessible in new Grooper Repository connection.

Line 28:		Line 28:
	'''''FIRST AND FOREMOST! DO NOT CONTINUE UNTIL READING THE NEXT LINE'''''		'''''FIRST AND FOREMOST! DO NOT CONTINUE UNTIL READING THE NEXT LINE'''''

	Ensure all Grooper services running on the source server are '''''stopped~~''''' and any Grooper applications (Grooper Design Studio, Grooper Config, etc) are '''''closed~~'''''.		Ensure all Grooper services running on the source server are '''''stopped'''''.

	On the source server, open Microsoft SQL Server Management Studio.		On the source server, open Microsoft SQL Server Management Studio.
Line 39:		Line 39:
	# Expand the '''Databases''' folder.		# Expand the '''Databases''' folder.
	# Right-click the Grooper Database you wish to back up.		# Right-click the Grooper Database you wish to back up.
	#* In this case, the database I want to back up is named "2022DB". This is the name I gave when originally creating the Grooper Repository in Grooper ~~Config~~.		#* In this case, the database I want to back up is named "2022DB". This is the name I gave when originally creating the Grooper Repository in Grooper Command Console.
	# Select ''Tasks''		# Select ''Tasks''
	# Select ''Back Up...''		# Select ''Back Up...''
Line 261:		Line 261:

	== 5. Create a Grooper Repository Connection ==		== 5. Create a Grooper Repository Connection ==
	All that is left is to create a new Grooper Repository connection to the Grooper Database and File Store, just like we would connect to any other Grooper Repository using Grooper ~~Config~~.		All that is left is to create a new Grooper Repository connection to the Grooper Database and File Store, just like we would connect to any other Grooper Repository using Grooper Command Console.

	Open Grooper ~~Config~~.		Open Grooper Command Console.

			Use the following command:
			<pre>connections add <server> <database> [user] [password]</pre>
			Portions of the command in angled brackets are required, while portions in square brackets are not.
			* You will need to replace <code><server></code> with the appropriate hostname of your Grooper server.
			* You will need to replace <code><database></code> with the appropriate database name of your Grooper database.
			* <code>[user]</code> and <code>[password]</code> are only needed if you are passing explicit user credentials for authentication.

	# Select the '''''Repositories''''' property.		# Select the '''''Repositories''''' property.
	# Press the ellipsis button at the end.		# Press the ellipsis button at the end.

	~~[[File:2022-backup-restore-repo-26~~.~~png]]~~		You've now successfully copied one Grooper Repository from one server to another and connected to it. Next, we're going to open up Grooper and verify we've done our job correctly.

			[[File:2022-backup-restore-repo-30.png]]

	~~# Press the ''Add'' button to add a new Grooper Repository connection.~~		{\|class="attn-box"
	~~# Enter the '''''Server Name'''''.~~		\|-
	~~#* In our case, the SQL instance on our local/target server.~~		\|⚠
	~~# Enter the '''''Database Name'''''.~~		\|
	~~#* This is the name of the database we restored from the backup file.~~		At this point be sure to refresh the App Pool in IIS for the Grooper website on your Grooper web server.
	~~# Press the ''Test Connection'' button.~~		\|}

	~~[[File:2022~~-~~backup-restore-repo-27.png]]~~


	~~If you restored the database correctly, you will see a~~ "~~Connection Successful!" message appear.~~
	~~#<li value=5> Click ''OK'' to continue.~~

	~~[[File:2022~~-~~backup-restore-repo-28.png]]~~


	~~#<li value=6> Select ''OK''~~ to ~~finish setting up~~ the ~~connection.~~

	~~[[File:2022-backup-restore-repo-29.png]]~~


	~~#<li value=7> Select ''Save'' to finalize.~~
	~~#* FYI: If you want~~ the ~~new~~ Grooper ~~Repository connection to be the default one, you can make it so using the '''''Default Repository''''' property~~ on ~~this screen.~~

	~~You've now successfully copied one~~ Grooper ~~Repository from one~~ server ~~to another and connected to it~~. ~~Next, we're going to open up Grooper Design Studio and verify we've done our job correctly.~~

	~~[[File:2022-backup-restore-repo-30.png]]~~

	== 6. Verify Connection ==		== 6. Verify Connection ==
Line 312:		Line 299:


	If you're able to switch to the Grooper Repository or otherwise load it in Grooper ~~Design Studio~~ ''at all'' that's a good first sign. If you get an error message, likely the database backup was corrupted and you'll need to start all over at step 1.		If you're able to switch to the Grooper Repository or otherwise load it in Grooper ''at all'' that's a good first sign. If you get an error message, likely the database backup was corrupted and you'll need to start all over at step 1.

	Another good test is to select objects in the repository and verify their properties are loaded as expected.		Another good test is to select objects in the repository and verify their properties are loaded as expected.
	# Here, we've selected a '''Content Model''' in the Node Tree.		# Here, we've selected a '''Content Model''' in the Node Tree on the "Design" page.
	# It loads the '''Content Model's''' properties with no error and configured as they were on the source server.		# It loads the '''Content Model's''' properties with no error and configured as they were on the source server.
	#* This is another good sign there's nothing wrong with the Grooper Database backup.		#* This is another good sign there's nothing wrong with the Grooper Database backup.
Line 322:		Line 309:


	Next, we need to verify there's nothing wrong with our Grooper Repository's File Store. For that, we'll need to select an object in the Node Tree that has something in the file store associated with it, like a document or page in a '''Batch'''.		Next, we need to verify there's nothing wrong with our Grooper Repository's File Store. For that, we'll need to select an object in the Node Tree of the "Design" page that has something in the file store associated with it, like a document or page in a '''Batch'''.
	# Here, we've selected a test '''Batch''' in the Node Tree.		# Here, we've selected a test '''Batch''' in the Node Tree.
	# I can see page object's thumbnails loaded and select a page object in the '''Batch'''.		# I can see page object's thumbnails loaded and select a page object in the '''Batch'''.

Randallkinard: initial adjustments for 2024 // via Wikitext Extension for VSCode

2024-11-06T19:26:57Z

initial adjustments for 2024 // via Wikitext Extension for VSCode

Show changes

Randallkinard at 17:45, 6 November 2024

2024-11-06T17:45:45Z

Show changes

Randallkinard at 20:14, 27 August 2024

2024-08-27T20:14:43Z

← Older revision		Revision as of 15:14, 27 August 2024
Line 1:		Line 1:
	{{~~Migrated2023~~}}		{{Migrated}}
	{{2023:{{PAGENAME}}}}		{{2023:{{PAGENAME}}}}

Dgreenwood: Dgreenwood moved page Backup and Restore Grooper Repository (Concept) to Backup and Restore Grooper Repository over a redirect without leaving a redirect

2024-04-18T19:50:01Z

Dgreenwood moved page Backup and Restore Grooper Repository (Concept) to Backup and Restore Grooper Repository over a redirect without leaving a redirect

← Older revision	Revision as of 14:50, 18 April 2024
(No difference)

Randallkinard: Randallkinard moved page Backup and Restore Grooper Repository to Backup and Restore Grooper Repository (Concept): new naming convention

2024-04-17T14:40:41Z

Randallkinard moved page Backup and Restore Grooper Repository to Backup and Restore Grooper Repository (Concept): new naming convention

← Older revision	Revision as of 09:40, 17 April 2024
(No difference)

Dgreenwood: Removed redirect to Backup and Restore Grooper Repository - 2023

2023-12-22T14:56:01Z

Removed redirect to Backup and Restore Grooper Repository - 2023

← Older revision		Revision as of 09:56, 22 December 2023
Line 1:		Line 1:
	~~#REDIRECT [[Backup and Restore Grooper Repository -~~ 2023]]		{{Migrated2023}}
			{{2023:{{PAGENAME}}}}

Randallkinard: Changed redirect target from Backup and Restore Grooper Repository - 2022 to Backup and Restore Grooper Repository - 2023

2023-11-08T19:37:34Z

Changed redirect target from Backup and Restore Grooper Repository - 2022 to Backup and Restore Grooper Repository - 2023

← Older revision		Revision as of 14:37, 8 November 2023
Line 1:		Line 1:
	#REDIRECT [[Backup and Restore Grooper Repository - ~~2022~~]]		#REDIRECT [[Backup and Restore Grooper Repository - 2023]]

Randallkinard: Randallkinard moved page Backup and Restore Grooper Repository to Backup and Restore Grooper Repository - 2022

2023-11-08T19:26:32Z

Randallkinard moved page Backup and Restore Grooper Repository to Backup and Restore Grooper Repository - 2022

New page

#REDIRECT [[Backup and Restore Grooper Repository - 2022]]

Backup and Restore Grooper Repository - Revision history