# Presentation: 516420

## Gridded Service Backup in IFPS 15

- Technical Information for IFPS and Service Backup Focal Points, ITOs, and Other Interested People

## Before Backup Can HappenThings for Focal Point or ITO to Do

- Place any local tools, procedures, etc. in the **/awips/GFESuite/scvbu/data/databases/*****username***  to have access to familiar tools while performing service backup
- Still make sure you have the necessary versions of text formatters and tools needed to create elements in the SITE directory to be sent to an office backing you up

## Examples of Local Scripts

- Anything called (sed scripts, db calls, etc.) within a product script needs to be in a bundled directory
- Web graphic creation scripts may need to be sent (regionally dependent)
- Scripts to update forecast information on backup site’s webpage (regionally dependent)
**Check the **_[service backup FAQ page](http://www.nws.noaa.gov/mdl/icwf/user_guide_ifps14/faq/svc_backup_faq.htm)_** **
**(**_[www.nws.noaa.gov/mdl/icwf/user_guide_ifps15/faq/svc_backup_faq.htm](http://www.nws.noaa.gov/mdl/icwf/user_guide_ifps15/faq/svc_backup_faq.htm)_**)  **
**for known problems with local scripts and **
**service backup**

## Variables to Use in Scripts

**Use these variables, which automatically change in backup, to avoid problems in scripts **
**$IFPS_LOCALBIN**** **
**$IFPS_DATA**
**$IFPS_XDEF**** – XDefaults file**
**$IFPS_HOME**** - /awips/adapt/ifps**
**$IFPS_LOG**** - /data/logs/adapt/ifps**
**$CDSPORT**
**$CDSHOST**

## Keep in Mind

**You need to resend your configuration data to the central server after any changes are made or after an upgrade**
- The configuration structure changes after a major upgrade, so the latest data needs to be sent to the central server so that your backup site’s IFPS knows what version of IFPS you run
- Sending in your latest changes, to smart tools, local text formatters, etc., allows your backup site to benefit from this information and keeps the products going to the public more consistent

## How to Send Your Configuration Data

- The program bundles up:
- In awips/adapt/ifps on lx1/ds
-    - localbin
-    - data
-    - Xdefaults
- And all static database tables
- (like control constants)
- In /awips/GFESuite/primary on px1
-    - etc/SITE
-    - data/databases/SITE
- To run the program, click on the Configuration Export button on the Config_IFPS menu
- see
**www.nws.noaa.gov/mdl/icwf/user_guide_ifps15/custom/launch_custom.htm#Steps**

## Checking Files

**Date/time last file received**

**File name (xxx.cfg for configuration data and xxxGrd.cfg for the gridded database)**

**Make sure your file sizes are reasonable (3-5 Mb for config files and 1-2 Mb for gridded data) and that the date reflects the last time you sent in a change or new configuration **
**If you have an export fail, you will need to remove    the .exprtMode from /awips/adapt/ifps/bin to do anything else with service backup**

## Importing Configuration Data

**At the backup site, files will be imported into the following directories on the lx on which backup was started: **
**in awips/adapt/ifps **
**	****      ****/localbin/xxx****      /data/xxx****	**** (where xxx is the failed site’s ID)**
**	****     ****/Xdefaults/xxx**
**GFESuite files will be imported onto the px1 (px3 for AK): **
**	****     ****/awips/GFESuite/svcbu/etc/SITE****     /awips/GFESuite/svcbu/data/databases/SITE**

## New Variables

**SVCBU_TRIM_ELEMS **
**The ability will exist to limit the elements sent for backup**
**Available in 15.2 and later **
**In the env file (still in /awips/adapt/ifps/localbin on lx/ds)**
**If set to 1, need to create file, also on lx/ds,  ****/awips/adapt/ifps/svcbu_export_elements.ccc**** which contains a one column list of the GFE elements ****not**** to be sent**
**Derived elements should be in this list as the office performing backup can create them**
**Now only sending 6 hours before current time to 6 hours after day 9 for backup **

## Other New Features

**When exporting an office’s grids back, it is now being written to /data/local (non-NFS mounted) which results in much faster export**
**Internal scripts write the data to the Restore database**

## Before Backup Can Happen

- If GFE formatters are used for zone based products (AFM, ZFP) at the backup office, zone grouping software (i.e. XNOW) needs to be configured for the backup site
- The primary backups of all of your surrounding offices need to be in the ISC_Sites list of a “backup” gfeConfig
- See _[www-md.fsl.noaa.gov/IFPS/14/ISC_List.html](http://www-md.fsl.noaa.gov/IFPS/14/ISC_List.html)_ for instructions and sites which need to be in the list
- Inform the forecasters that this gfeConfig needs to be used when one of your surrounding sites is being backed up

**Notes:**
If you do use xnow in product generation, you will need to swap xnow CCC.GFE_Config and GFE_editareas.CCCNNNXXX files with your backup site. 

## Starting a Backup IFPS in 15

**Backup can now be started on any lx box**
**After forecaster imports config data and grids, they will start backup IFPS as before on that lx or an hp**
**Extra step still applies to the hps**

- Defaults to home domain