Backing up any needed CA Service Desk Manager (CA SDM)files prior to update and customization

book

Article ID: 36493

calendar_today

Updated On:

Products

SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Introduction

A common ask when making a change in CA Service Desk Manager (CA SDM) is to backup a given file.  There are various approaches to this task.  A frequent tactic would be to copy/paste the same file in place, creating a duplicate of the same file in the same location.  However, this introduces the possibility of a file conflict during later operations, such as pdm_publish or pdm_configure, and possible corruption of the CA SDM environment. 

Instructions

The recommended approach when backing up an individual file before directly manipulating it is to copy a given file that is being backed up and pasting it in a location outside of the CA Service Desk Manager directory.

An approach that is frequently used, creating a duplicate file in the same location with either an alternate extension or a string to identify it as a copy (i.e. "Copy of wsp_schema.sch") is not an advisable method. 

The reason is that there are components in CA SDM that may process a duplicate file in its operations, causing a conflict of existing content that should take precedence.

Example:

Environment

Release: SDMU0M99000-14.1-Service Desk Manager-Full License
Component: