Roll Back Plan

IDB TECHNOLOGIES
SOFTWARE RELEASE DEPLOYMENT AND

ROLLBACK PLAN
Document Version 1.0
Prepared by:
Prepare Date:
Email Address:
Software Deployment and Rollback Plan
Table of Contents
1 PURPOSE ....................................................................................................................................................... 3
2 RELEASE SUMMARY ...................................................................................................................................... 3
3 TARGET DEPLOYMENT SUMMARY................................................................................................................. 5
4 BUILD HISTORY .............................................................................................................................................. 5
5 QA APPROVAL ............................................................................................................................................... 6
6 ROLLBACK PLAN ............................................................................................................................................ 7
7 DEPLOYMENT APPROVAL HISTORY ............................................................................................................... 8
Revision History
Date Version Description Author
I D B T E C H N O L O G I E S P R I V A T E L I M I T E D | Page 2 of 8
1 PURPOSE
The Software deployment and rollback plan document to help build master to release latest build to
Production/UAT Server effectively without having any issues after the deployment. All the section to be
filled carefully by each team members or owner of this document without missing any build process. This
evidence document make sure the following process to be completed before signoff by the Stack holders.
 Release Summary
 Target Deployment Summary
 Build History
 QA Approval
 Rollback Plan
 Deployment Approval History
2 RELEASE SUMMARY
All the new features, modifications, change request and issues listed here. It helps the Stack holder what
are all the features going to be updated in the Production/UAT server based on the Build Unique
Identification Number. This release contains the following information.
New Features
SNO DESCRIPTION REF. TICKET ID
Change Request
Issues
3 TARGET DEPLOYMENT SUMMARY

This section helps to understand where and when the deployment going to targeted Production/UAT
server. This process will be applicable only approved by respective Product Stack Holder/Client or
Manager. This summary contains the following information.
BUILD VERSION NO
BUILD CREATED BY
BUILD CREATED DATE & TIME
QA REVIEWED BY
QA DATE & TIME
QA APPROVAL STATUS
TARGET PRODUCTION SERVER

SERVER LOCATION
IP ADDRESS
DEPLOYMENT BY
DEPLOYMENT DATE & TIME
HOURS REQUIRED
BUILD LOCATION
FTP TOOL
4 BUILD HISTORY
The following table represents about the build contained files which need to move target environment.
Listed files are available in the build location as described in the Section 3 of this document. If need any
other build instructions required will be updated in this section.
Application Related Files
SNO FILE NAME PACKAGE/FOLDER/FILE PATH FILE TYPE
Database Files
SNO SCRIPT NAME COMMENTS
5 QA APPROVAL
All the build has to be approved by tester.
Build Version:
Tested Date:
Tested By:
Approval Status:
Notes/Comments:
6 ROLLBACK PLAN
Rollback plan major and crucial part for any release to production environment. Build master should make
sure all the back has to be performed before transferring/copying files to application or database server.
All the necessary back has to be performed before entering into to release process. Here is the check list
for the pre and post deployment process.
 Database Backup
 Database Logs Backup
 Application Server Logs Backup
 Application Folders Backup
 Previous Build Backup from the Web or Application Server
 Email should be triggered to the respective stack holders/product owner/manager
 All the server should be stopped proper and order wise
 File location should verified by the build master
 Rollback file or folder location should be verified by the build master
ROLLBACK FILE/FOLDER LOCATION

SYSTERM/SERVER NAME
BACKUP DATE & TIME
Backup Files
SNO FILE DESCRIPTION COMMENTS
7 DEPLOYMENT APPROVAL HISTORY

All the server release should be approved by the stack holders/product owner and manager.
Date Build Version Approved By Comments

Roll Back Plan

Uploaded by

Copyright:

Available Formats

Roll Back Plan

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Roll Back Plan

Uploaded by

Copyright:

Available Formats

IDB TECHNOLOGIES

SOFTWARE RELEASE DEPLOYMENT AND

2 RELEASE SUMMARY ...................................................................................................................................... 3

3 TARGET DEPLOYMENT SUMMARY................................................................................................................. 5

4 BUILD HISTORY .............................................................................................................................................. 5

6 ROLLBACK PLAN ............................................................................................................................................ 7

7 DEPLOYMENT APPROVAL HISTORY ............................................................................................................... 8

 Target Deployment Summary

 Deployment Approval History

3 TARGET DEPLOYMENT SUMMARY

TARGET PRODUCTION SERVER

Application Related Files

SNO FILE NAME PACKAGE/FOLDER/FILE PATH FILE TYPE

SNO SCRIPT NAME COMMENTS

ROLLBACK FILE/FOLDER LOCATION

SNO FILE DESCRIPTION COMMENTS

7 DEPLOYMENT APPROVAL HISTORY

Date Build Version Approved By Comments

You might also like