A backup of the Footprints 12 Database is required for a viable recovery. A FootPrints File Systems backup corresponding with the database backup is needed for a full recovery.
For instructions on how to backup see
000011024 How to Backup FootPrints Service Core 12 (for Disaster Recovery purposes)The instructions below can be used to restore on a server that has already had Tomcat appropriately installed and configured.
Please consult the Knowledge Base articles below if Tomcat assistance is needed prior to recovering Footprints 12.
000011063 How to install Tomcat for FootPrints Service Core version 12000010914 How to configure Tomcat for FootPrints Service CoreThese instructions are written for a Windows installation of FootPrints Service Core using a PostgreSQL database. Although the basic process is the same for Linux and PostgreSQL, if assistance is needed, please contact FootPrints Technical Support. If you need Disaster Recovery instructions for Windows/MSSQL, see Knowledge Base Article
00123552 instead.
NOTE: In Footprints 12.1.07 the application name was changed from
FootPrints Service Core to FootPrints. If your installation(s) began at 12.1.0 or later be aware that the installation directory had changed from to X:\Program Files\BMC Software\FootPrints and the default database and database users are renamed to just fpdb001 rather than fpscdb001.
- First a new database will need to be created in PostgreSQL using the following SQL query. Replace the "new_database_name" string with whatever name you choose.
create database new_database_name with encoding='UTF8' owner=postgres connection limit=-1;
- Restore your database backup making sure to update the new_database_name string with the proper name. If errors like ERROR: role "fpscdb002_adm" does not exist are returned, simply end the attempt with CTRL+C and create users that match that fpscdb002 schema as shown in step 3 below, then drop the new database and start at step 1 again. If no such errors occur, skip to step 4.
cd \Program Files\PostgreSQL\9.2\bin\
psql.exe -h localhost -p 5432 -U postgres -d new_database_name -f "C:\Path\To\file\filename.backup or filename.sql" >> "C:\Path\To\file\psql_restore.log"
- If the new installation's database users are different than those used in your existing database, create a new set of users with the following SQL query. Be sure to use the same passwords as those used during the new Footprints installation on this server.
create role fpscdb001_adm with CREATEDB NOCREATEROLE NOCREATEUSER LOGIN PASSWORD 'ucZm93#aF2iXKh';
create role fpscdb001_rpt with NOCREATEDB NOCREATEROLE NOCREATEUSER NOINHERIT LOGIN PASSWORD 'ucZm93#aF2iXKh';
create role fpscdb001_sec with NOCREATEDB NOCREATEROLE NOCREATEUSER NOINHERIT LOGIN PASSWORD 'xRG0#Qi#3NwUQB';
create role fpscdb001_usr with NOCREATEDB NOCREATEROLE NOCREATEUSER NOINHERIT LOGIN PASSWORD 'uwC#7ehS4Pe5nI';
- After the database has been restored, check your "C:\Path\To\file\psql_restore.log" file to ensure no database errors were reviewed during the restoration process.
- In your PostgreSQL server we will need to prepare your restored database for recovery using the SQL Queries below. NOTE: As with the steps above, if your restored database has a different schema than that created with the new installation, please alter these queries accordingly.
-- Step 1 - If new users were needed, then we need to select the appropriate new user as the database owner with the SQL query below.
alter database new_database_name owner to fpscdb001_adm;
-- Step 2 - The following is to reset a required local path in case the new instance isn't installed into the same folder as the original installation. Replace the path with that of your local repository folder.
update fpscdb001_system.cfg_setting_val set string_val = 'C:/Program Files/BMC Software/FootPrints Service Core/repository'
where cfg_setting_id = (select cfg_setting_id from fpscdb001_system.cfg_setting where cfg_setting_const = 'fileStorageLocation');
-- Step 3 - Set encrypted password values to null to prevent decryption related failures as the new installation had created a new encryption key.
UPDATE fpscdb001_system.cfg_setting_val
SET string_val = NULL
WHERE cfg_setting_val_id in (
SELECT csv.cfg_setting_val_id
FROM fpscdb001_system.cfg_setting_val csv
join fpscdb001_system.cfg_setting cs on cs.cfg_setting_id = csv.cfg_setting_id
WHERE
cs.cfg_setting_const like '%password%'
and csv.string_val is not null
and csv.string_val <> '');
- If the restored database uses the same schema name (ex fpscdb001) as the newly installed Footprints instance, skip ahead to step 7. If the schema names are different, we will need to perform a Find/Replace on the content of the files in the X:\Program Files\BMC Software\FootPrints Service Core directory so that all references to the new installation's schema are changed to match that of the schema for the restored database. This Find and Replace can be performed with a third-party application such as Notepad++ or fnr.exe. IMPORTANT: Be sure to create a backup copy of your BMC Software directory before making any of these changes.
- Next we need to manually edit the x:\Program Files\BMC Software\FootPrints Service Core\conf\footprints-environment.properties file to ensure the usernames and TenantID have been updated.
SystemLocaleCode=en_US
SystemLocaleName=English - United States
EncryptionStrength=128
Data0=FA0Y0IksvBRB6T1hcw0v3_veu5Nzv-SJJne3lVKbor7N2bg3TokMIE4dZhpDLPIdk68wZ45vrSe3|M39Hz4C0Yu7OgXHtz0IOrKs37dg43YshjHdIEgvnig39UptO8dB2wdzMatSz3j7faf3Gcq5lAA|
Data1=0i4Fzeu-edELHFKjt3RWUxPuO_OlMdqlDUIuKESImu-f-ilokwI2ROgoAFEYaKWo|
Data2=JR1rYWNscnZiMG5ocDBzc2Q3bWhoZ2xwNGJvNjk4dGwxam1ubWgxb243dGlzbzAzbXEzZmlsbjFo|N2ZmcmhrazA1NGk0YTlpa2pjN2FqdTlpcGkwYTlxZTVlbW8yYWdxOWk|
DatabaseDriverClass=org.postgresql.Driver
DatabaseConnectionUrl=jdbc:postgresql://localhost:5432/fpscdb001
GrantUsers=fpscdb001_usr
DatabaseUserName=fpscdb001_usr
DatabaseUserPassword=LV5GP3N8p9-dS_n99G47nSP4Dgu_x7RKXPyx5V84hABgIsL54nfN6AJXjR3UzFuk|
DatabaseAdminName=fpscdb001_adm
DatabaseAdminPassword=ZtUq2tFfvlWvMWn8Phmooc1YStnyk2_Th9dVMExRE8YznMJM75NnhyRfpcsBjlZ2|
ReportingUserName=fpscdb001_rpt
ReportingUserPassword=AgSf5JYsKxRgu-itO5zPrnLxUCXboin9fTwQ_zx9O8gRnVkFcSp2Q-ASf29EeDU2|
SecureUserName=fpscdb001_sec
SecureUserPassword=evjDXLEE17jfZkQV6XSrBb3j0f6ZOWCYcDyVamc7w4LH1XgJYFJbgxViD4jbpoDv|
DatabaseStaticMappingsLocation=C:\\Program Files\\BMC Software\\FootPrints Service Core/conf/mappings
TenantId=fpscdb001
- Next update the database name in the DatabaseConnectionUrl= entry to that of the restored database. The format of the string after “…:postgresql://” should appear as below.
<hostname>:<port>/<databasename>
- Once the Footprints 12 installation is pointed to the restored database, ensure the Tomcat service is stopped then delete all current Tomcat and Footprints 12 logs before restarting Tomcat against the restored database.
- When the login page displays use the query below to identify the System Admin users. If any are set to FootPrints Internal Authentication they can be used to login now with their normal passwords. Any that use External Authentication methods will not work at this time. If none are able to login, please contact the FootPrints Service Core support team for assistance.
select app_user_id,user_login,delete_date from fpscdb001_system.app_user where app_user_id in
(select app_user_id from fpscdb001_system.app_user_prof_link where user_prof_id in
(select user_prof_id from fpscdb001_system.user_prof where app_role_id in
(select app_role_id from fpscdb001_system.app_role where app_role_name='System Administrator' and is_built_in='1')));
- If you can login successfully you will need to re-enter any external system credentials into Footprints to re-encrypt the passwords using the new installation’s key. This includes:
- LDAP Authentication credentials
- LDAP Address Book credentials
- SQL Address Book credentials
- Any passwords saved in the “Email Settings” administration menu
- Any credentials in the “Integration“ administration menu
- Any SQL Lookup configuration with your item’s Fields list using the “Manage Linked Fields” button
- If the Database Backup was the only backup of your Footprints Service Core data, the application is now ready for use and the backup is complete. You may notice missing file attachments in your records or missing images in your configuration, this is to be expected as they resided in the Footprints Repository folder and these will need to be manually re-added to the system.
- If you had also backed up the FootPrints Service Core Application files as well per our KB Article 000011024 above, stop the Tomcat Service so the files can now be restored.
- In your current installation of FootPrints Service Core 12 locate your installed directory. The KB Article had you backup the Conf and Repository folders. Before restoring them, rename your current folders, DO NOT DELETE THEM.
- Restore your backed up Conf and Repository folders. This may take some time as the repository folder contains all of your ticket attachments for the entire system.
- After the folder restore, copy the two files below from your renamed Conf folder to replace the files in your restored Conf folder.
- footprints-environment.properties
- log4j.properties
- Restart the Tomcat Service once more and login when the FootPrints Entrance Page is presented. If login is successful, Footprints should now be ready for use.
