Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
2
1.1 RMsis Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1 Requirements Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 RMsis User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1 Introduction and Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1.1 Menus, Keyboard and Mouse Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1.2 Requirement Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1.3 Roles and Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.2 Capturing and Analyzing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.2.1 Requirement Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.2.2 Requirement Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.3 Requirements Traceability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2.4 Reverse Traceability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.4.1 Artifact Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.4.2 Artifact Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.5 Release Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.5.1 Release attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.5.2 Release operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.6 Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2.7 User administration by Requirement Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3 RMsis Installation and Upgrade Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.1 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.3 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.4 Application Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3.5 Database Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3.6 Deployment of RMsis Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3.7 License activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3.8 Upgrading Existing RMsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3.9 Trouble Shooting and FAQ's . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4 RMsis Administrator's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.4.1 RMsis administration by JIRA admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.4.2 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.4.2.1 MSSQL Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.4.2.2 MySQL Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
RMsis Documentation - 1.0 Release
This is Home Page for the RMsis 1.0 release. You can access documents / articles using the LHS navigation pane.
Requirements Manager
Requirements Manager is a role, generally performed by a person who "owns" the requirements in a project. Requirements Manager may be
assisted by a team, who may own some of the roles.
In this section, we will explain certain end use scenarios, applicable to this role and how RMsis can be used in these scenarios.
Mouse
Right click on any cell/element shows possible operations in context of that cell/section.
Clicking on a cell opens cell in editable mode if user is having permissions.
Clicking on link of any artifact shows details about that artifact.
Keyboard
Esc key is used for cancelling any operation/action.
Tab key is used navigate on next available control.
Requirement Categories
RMsis provides functionality to manage requirements under two categories:
Unplanned Requirements: This is the collaboration space, where all the users can create/edit requirements and comment on them.
Requirement Manager can move requirements from this category to "Planned Requirement" category and assign them various
attributes/release.
Planned Requirements: This list is used by Requirement Manager to analyze requirements and assign them to specific releases. It is
recommended that only 1 manager should have write access to the "Planned Requirements", even though RMsis can be configured to
provide write access to other category of users as well.
Team Member
Can contribute requirement(s)
Reviews the requirement(s)
Refers to the requirements for other downstream activities.
Customer
Has limited RW access, as defined by the administrator.
Can contribute requirement(s)
These users can map into various designations / roles for your specific context. Some examples of this mapping are enumerated below:
Project Manager / Agile (Scrum) Product Owner, who is generally responsible for consolidating, analyzing and allocating
Project Lead team requirements.
Team Member Agile (Scrum) Scrum Master will be a part of the team and will be allocated a set of requirements (as sprint
teams backlog) by the Product Owner.
Requirement Manager can create/edit requirement under "Planned Requirements" and assign values to their attributes.
Any user (if permitted by Admin) can create requirement under "Unplanned Requirements". If found suitable, these can be moved to
"Planned Requirements" by Requirement Manager.
Fig – 1 : Requirement Management Screen
Requirement Attributes
A requirement has following attributes:
Req. Id: A unique identification of the requirement. This field is non editable.
Requirement: This is a brief description of the requirement.
Attachments: Any number of documents can be attached to the requirement. For attaching a document against a requirement, just click
on "Attachments" column ( ) and row corresponding to the requirement. After a panel appears, click on "Attach new document" to
attach the document.
Depends on: Requirement dependency can be created by clicking the cell corresponding to the requirement in "Depends On" column.
After clicking on this column, a panel will appear. Check the requirements on which dependencies needs to be created. RMsis checks for
and prevents cyclic dependencies.
Fig – 2 : Requirement Dependency Screen
Requirement Operations
The following operations can be performed on "Planned Requirement" table:
Edit Requirement: A requirement can be edited simply by clicking on it OR by clicking its ID.
Delete Requirement: A requirement can be deleted by clicking on context menu item "Delete Requirement".
Caution! if a parent requirement is deleted, then all of its children will also be deleted.
Select Requirement: A requirement can be selected by clicking on first column of the requirement.
Indent Requirement: A requirement can be indented in the following two ways:
First select a requirement and then click on indent button to indent it.
By selecting context menu item "Indent Requirement".
Outdent Requirement: A requirement can be outdented in the following two ways:
First select a requirement and then click on outdent button to outdent it.
By selecting context menu item "Outdent Requirement".
Paste Requirement: A requirement can be cut from the unplanned requirements table and then pasted into the planned requirements
table either:
by selecting context menu item "Paste Requirement above" or "Paste requirement below".
or by selecting a requirement from planned requirements table and then choosing "Paste Requirement above" or "Paste
Requirement below" from the dropdown "More Actions" in the planned requirements section.
Expand Requirement: A parent requirement can be expanded by clicking on expand button associated with the requirement text but if
you want to expand all the requirements then click on "Expand All" button.
Collapse Requirement: A parent requirement can be collapsed by clicking on collapse button associated with the requirement text but if
you want to collapse all the requirements then click on "Collapse All" button.
Move Requirement from Unplanned to planned: A requirement can be moved from "Unplanned Requirements" section to "Planned
Requirements" section by selecting requirement and right clicking on it. After right click, a menu appears and requirement can be moved
to planned section by selecting "Move to Planned Requirements" section.
Filters: Requirements can be filtered on various attributes like "Release ID", "Priority", "Criticality", "Feasibility", "Status" etc. Filter
selection performs an OR operation within a given column and performs AND operation across columns.
Export Requirements (PDF/Word): Requirements can be exported to PDF/Word document by clicking icons shown on top right corner.
Important Notes:
If you are unable to perform any operation on this table, then please confirm with your administrator / manager that you have the required
credentials to perform that operation.
Context Menu is accessible by right clicking on any table row. Operations defined in context menu will be performed on that row.
The fields categories, estimated effort, technical risk, release id, priority, criticality, feasibility, status for a parent requirement are non
editable.
Requirements Traceability
Requirement Manager can link/unlink JIRA issues/bugs/tasks with a given requirement and can check traceability in real time.
To link an artifact to a requirement, just click on of that row. After a panel appears containing:
Linked Artifacts table showing artifacts linked with this requirement. To unlink an artifact, just click on .
Link New Artifacts table showing artifacts not linked with this requirement. To link an artifact, just click on , that artifact will be
automatically moved to linked artifact table.
Color coding of table cells is done according to the status of the artifacts.
Red Color: if number of ("Resolved" and "Closed") artifacts are less than 50% of total attributes associated with requirement.
Yellow Color: if number of ("Resolved" and "Closed") artifacts are more than 50% and less than 100% of total attributes associated with
requirement.
Green Color: If all artifacts are either "Resolved" OR "Closed".
Requirement traceability table can be exported to PDF/word by clicking icon on top right corner.
Reverse Traceability
Using RMsis, Requirement Manager can easily track requirements associated with a given issue. This feature is helpful to know associatively of
JIRA issue(s) with given requirement(s).
Artifact Attributes
An artifact has the following attributes:
Jira Reference: This field specifies unique key (Jira reference id) of the artifact.
Summary: This field specifies brief summary description of the artifact.
Artifact Type: This field specifies type of the artifact. Artifact types are automatically synchronized with issue types in Jira.
Priority: This field specifies priority of the artifact. Possible values are "Blocker", "Critical", "Major", "Minor" or "Trivial".
Status : This field specifies status of the artifact. Possible values are "Open", "In Progress", "Reopened", "Resolved" or "Closed".
Requirements: This field shows the requirement ids which are linked with this artifact.
Artifact Operations
The following operations can be performed:
Add Artifact: An artifact can be created by clicking on "Add Artifact" button. A Jira issue panel will be opened to create a new Jira issue.
Artifact table will be automatically updated after closing the Jira issue panel.
Edit Artifact: An artifact can be edited by clicking in "Jira Reference" column. A Jira issue panel will be opened to edit that Jira issue.
Artifact table will be automatically updated after closing the Jira issue panel.
Link Requirements: An artifact can be linked to one or more requirements. A requirement can be linked to an artifact by clicking on
"Requirements" column for an artifact row. After a panel appears, check on the requirement rows to link requirements.
Filters: JIRA issues can be filtered on "Artifact Type", "Priority" and "Status".
Export Releases (PDF/Word): JIRA issues can be exported to PDF/Word document by clicking icons shown on top right corner.
Fig – 7 : Requirement Reverse Traceability Screen
Release Planning
Requirement manager can plan releases on the "Release" tab.
Release attributes
A release has the following attributes:
Release operations
Following operations can be performed on releases:
Create Release: A new release can be created by clicking on the last row of the table under the "Project Release Name" column labeled
"< Enter new release >".
Edit Release: A release can be edited simply by clicking on it.
Delete Release: A release can be deleted by clicking on context menu item "Delete Release". However, if a release is associated with
requirements, then it will not be deleted.
Filters: Releases can be filtered on "Release Status".
Export Releases (PDF/Word): Releases can be exported to PDF/Word document by clicking icons shown on top right corner.
Fig – 5 : Requirement Release Screen
Filters
RMsis implements filters with some common characteristics, described below:
The filter drop-down can be closed by clicking on the (now changed) icon.
Assign Role to a User: To assign role to a user, click on "Roles" column and row corresponding to the user. After a panel appears,
check on the desired role and close.
Un-assign Role to a User: To un-assign role to a user, click on "Roles" column and row corresponding to the user. After a panel
appears, un-check the desired role and close.
Fig – 8 : User Management Screen
Users who would like to install and configure RMsis (Requirement Management Extension for JIRA)
Users who would like to upgrade existing RMsis.
Assumptions
In this document, it is assumed that the readers are aware of JIRA and its basic configuration. For detailed information about JIRA, please refer (
JIRA documentation).
Terminology
Following table describes the terms used in this document.
Term Description
Admin Person who is responsible for installation and configuration of RMsis for JIRA.
RMsis web application Requirement management product from Optimizory. Typically it's implementation is available as rm.war file.
RMsis JIRA plugin JIRA plugin for RMsis application. Typically this plugin is available as jira-rmsis-x.x.jar.
System Requirements
Hardware
RMsis can be installed on any server/machine where JIRA is installed. You would need a server class machine, as suggested by Atlassian for
JIRA.
Software
JIRA JIRA 4.0, 4.1, 4.2, 4.3 or later. Please refer JIRA Installation and Upgrade Guide
Java Platform Sun/Oracle JDK / JRE 1.6 (update 10 or higher). Please refer JAVA environment setup
Application Servers Apache Tomcat 6.0 OR later
Application Structure
RMsis Application Structure
Latest version of RMSis can be downloaded from http://cart.optimizory.com/rmsis. The compressed downloaded file contains following files:
Database Setup
Database Creation
MySQL
1. Open a unix terminal or a windows command prompt whichever is relevant to you. And login to MySQL database using the command line
client that is shipped with the MySQL. Use "root" (administrator) credentials to login.
2. Create a database to store RMSis data. Use any name for it. Example - "rmsis".
3. Create a database user and assign permissions to this user to access the database created above.
4. Exit MySQL
1. Create a database for RMsis (e.g. rmsis). Note that the collation type must be case insensitive, e.g.: 'SQL_Latin1_General_CP437_CI_AI'
is case insensitive. If it is using your server default, check the collation type of your server.
2. Create a database user which RMsis will connect as (e.g. rmsisuser). Note that rmsisuser should not be the database owner, but should
be in the db_owner role.
3. Create an empty 'schema' in the database (e.g. rmsisschema) for the RMsis tables. Please note that a 'schema' in SQL Server 2005 is a
distinct namespace used to contain objects, and is different from a traditional database schema. It is not required to create any of RMsis
tables, fields or relationships (RMsis will create these objects in empty schema when it starts for the first time). Read more on SQL
Server 2008 schemas in the relevant Microsoft Documentation (http:/msdn2.microsoft.com/en-us/library/ms190387.aspx).
4. Ensure that the user has permission to connect to the database, and create and populate tables in the newly-created schema.
5. Ensure that TCP/IP is enabled on SQL Server and listening on the correct port (the port is 1433 for the default instance of SQL Server).
Read the Microsoft documentation for information on how to enable a network protocol (TCP/IP) and how to configure SQL server to
listen on a specific port.
6. Ensure that SQL Server is operating in the appropriate authentication mode. By default, SQL Server operates in 'Windows Authentication
Mode'. However, if user is not associated with a trusted SQL connection, i.e. 'Microsoft SQL Server, Error: 18452' is received during
RMsis startup, it is required to change the authentication mode to 'Mixed Authentication Mode'. Read the Microsoft documentation on
authentication modes and changing the authentication mode to 'Mixed Authentication Mode'
7. Turn off the SET NOCOUNT option. Open SQL Server Management Studio and navigate to Tools -> Options -> Query Execution -> SQL
Server -> Advanced. The following screenshot displays the configuration panel for this setting in MSSQL Server 2005/2008. Ensure that
the SET NOCOUNT option is not selected:
8. Copy SQL server driver to application server.
9. Download the SQL Server JDBC driver (v1.2.3) from JTDS.
10. Add the SQL Server JDBC driver jar (jtds-1.2.3.jar) to the <Tomcat install>/lib/ directory.
Deployment of RMsis Application
Application Deployment
For Windows
c:\> .\setup.bat
4. System will ask to enter RMsis configuration directory. Please enter the full absolute path of configuration directory (created in step 2).
5. Go to RMsis configuration directory and open jdbc.properties file. Enter your database configuration.
6. Go to RMsis configuration directory and open mail.properties file. Enter your mail configuration.
7. Deploy rm.war to your application server (Tomcat). This can be done by copying rm.war to your <CATALINA_HOME>\webapps\ folder.
Note:
For Linux
$ chmod +x setup.sh
$ ./setup.sh
4. System will ask to enter RMsis configuration directory. Please enter the name of configuration directory (created in step 2).
5. Go to RMsis configuration directory and open jdbc.properties file. Enter your database configuration.
6. Go to RMsis configuration directory and open mail.properties file. Enter your mail configuration.
7. Deploy rm.war to your application server (Tomcat). This can be done by copying rm.war to your <CATALINA_HOME>/webapps/ folder.
For Windows
2. Shutdown JIRA and restart it. It will install rmsis JIRA plugin.
For Linux
$ cp jira-rmsis-x.x.jar <JIRA_HOME>/plugins/installed-plugins
2. Shutdown JIRA and restart it. It will install rmsis JIRA plugin.
1. After this stage, the Database should be created and RMsis should run normally.
2. Now, you should be able to see the "License Activation Screen".
At this stage RMsis application is installed and can be activated after providing license to the application.
Note : The application's (JIRA / RMsis) startup sequence is not important.
License activation
After installation of RMsis, "RMsis" link will appear on JIRA menu bar.
The screen shows the system code for this RMsis instance. To generate license key, click on "RMsis Evaluation License Key" or log on to
http://cart.optimizory.com/rmsis and input your system code to generate License Key.Enter the license key in text box.
1.
1. Take backup of existing database.
2. MySQL
If http://www.example.com is host, & tomcat server is running on port 8080 of this host; then RMsis base url(i.e. host ID) will be
http://example.com:8080/rm/. RMsis base url may be different according to your deployment scenario.
If you get an error, which log files should you share with us?
*Application Server Logs:*These logs files are generally located in logs folder of your application server. e.g. In case of Apache Tomcat, it
is located in <CATALINA_HOME>/logs/ folder.
JIRA Logs: These are located at <JIRA_HOME>/logs/ folder.
RMsis Logs: These are located at <RMSIS_HOME>/logs/ folder.
Is the system code for RMsis same as the one for JIRA?
Common Issues
I have JIRA running on another server and I am getting one of the following errors:
Caution: If your system is already in use, please backup the database before trying out any fix.
Listener Error
You may have multiple JIRA plugins installed in the system. To resolve this issue : -
Shutdown JIRA and remove previous versions of jira-rmsis plugin from JIRA_HOME/plugins/installed-plugins/ directory
Restart JIRA again
I am getting the following error after clicking on RMsis. Error : RMsis is already connected to JIRA instance "XXXX-XXXX-XXXX-XXXX".
In order to use RMsis for both JIRA instances simultaneously, different RMsis instance and license keys would be required.
This is because RMsis may not have permission to create / write a file in RMsis logs directory. You need to provide write permission to
<RMSIS_HOME>/logs/ and will have to restart RMsis.
This problem has been fixed in Version 0.70 of RMsis. Please upgrade, if you are facing performance problems with each user login.
I am getting the following error during setup; jar:command not found / 'jar' is not recognized as an internal or external command
Please check that you have JDK installed (Java development kit). If you have not installed JDK then install it and set the JDK path as follows:
Support
For any queries or unresolved issues, you can reach out to our support team support@optimizory.com and we will ensure a prompt response to
your problem.
User Management: RMsis admin can assign users based on number of users for which license is purchased (by enabling check-box).
This table automatically shows all JIRA users in given system where RMsis is installed.
Role Management: RMsis administrator can assign/un-assign permission to a given role by enabling/disabling check boxes.
Project Management: RMsis administrator can see all projects and assign/unassign users in those projects. This table automatically
syncs with JIRA.
MySQL
Backup and restore of MySQL should be done using the utilities that come packaged with MySQL. This section briefly describes the process.
more...
MSSQL
This section briefly describes how to backup and restore MSSQL database using the SQL Server Management Studio.
more...
Backup
1. After connecting to the appropriate instance of the Microsoft SQL Server Database Engine, in Object Explorer, click the server name to
expand the server tree.
2. Expand Databases, and depending on the database, either select a user database or expand System Databases and select a system
database.
3. Right-click the database, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.
4. In the Database list box, verify the database name. You can optionally select a different database from the list.
5.
5. You can perform a database backup for any recovery model (FULL, BULK_LOGGED, or SIMPLE). In the Backup type list box, select
Full.
6. For Backup component, click Database.
7. Either accept the default backup set name suggested in the Name text box, or enter a different name for the backup set.
8. Optionally, in the Description text box, enter a description of the backup set.
9. Specify when the backup set will expire; a value of 0 days means that the backup set will never expire.
10. Choose the type of backup destination by clicking Disk or Tape. To select the paths of up to 64 disk or tape drives containing a single
media set, click Add. The selected paths are displayed in the Backup to list box.
To remove a backup destination, select it and click Remove. To view the contents of a backup destination, select it and click Contents.
Restore
1. After you connect to the appropriate instance of the Microsoft SQL Server Database Engine, in Object Explorer, click the server name to
expand the server tree.
2. Expand Databases. Depending on the database, either select a user database or expand System Databases, and then select a system
database.
3. Right-click the database, point to Tasks, and then click Restore.
4. Click Database, which opens the Restore Database dialog box.
5. On the General page, the name of the restoring database appears in the To database list box. To create a new database, enter its name
in the list box.
6. In the To a point in time text box, either retain the default (Most recent possible) or select a specific date and time by clicking the browse
button, which opens the Point in Time Restore dialog box. For more information, see How to: Restore to a Point in Time (SQL Server
Management Studio).
7. To specify the source and location of the backup sets to restore, click one of the following options:
a. From database
b. Enter a database name in the list box.
c. From device
Click the browse button, which opens the Specify Backup dialog box. In the Backup media list box, select one of the listed device
types. To select one or more devices for the Backup location list box, click Add.
After you add the devices you want to the Backup location list box, click OK to return to the General page.
8. In the Select the backup sets to restore grid, select the backups to restore. This grid displays the backups available for the specified
location. By default, a recovery plan is suggested. To override the suggested recovery plan, you can change the selections in the grid.
Any backups that depend on a deselected backup are deselected automatically.
Backup
Backup should be taken using the mysqldump utility. Following is the syntax of command.
Restore
Backup taken using mysqldump is an SQL dump. You can restore the database using any MySQL client. Following is the command syntax for
the CLI mysql client.