Retailpro 9 BackupRecovery Best Practices

Retail Pro Backup &
Recovery
Best Practices
Retail Pro Backup & Recovery Best Practices
 Overview
This document discusses the backup and recovery elements of a disaster recovery (DR) plan as they
relate to the Retail Pro application.
 Part 1 – Developing a Disaster Recovery (DR) Plan

 The Importance of a Disaster Recovery Plan
 Key Elements of a Disaster Recovery Plan
 Part 2 – Developing a Comprehensive Backup Plan

 The 3-2-1 Backup
 Part 3 – Creating Retail Pro Backup #1

 Understanding Archive Logs & Redo Logs
 Complete & Incremental Backups
 Part 4 – Creating Retail Pro Backup #2

 Copying the First Backup
 Part 5 – Recovering from Backup

 Accessing Technician’s Toolkit Offline
 Full, Complete & Point in Time Recovery Options
 Recovery Validation
 Part 6 – Troubleshooting Backup & Recovery

 Error Copying Archive Log Files
 Part 7 – Miscellaneous Topics

 The Case for Uninterrupted Power Supply
 Other Retail Pro Files to Backup
 Regularly Testing Backups
1 | Page – Retail Pro Backup & Recovery Best Practices

 Part 1 – Developing a Disaster

Recovery (DR) Plan
 The Importance of a Disaster Recovery Plan

A business who does not have a disaster recovery (DR) plan is simply asking for trouble! Murphy's
Law states that anything that can happen, will happen. Computers can become infected with viruses
and malware. Hard drives can break down at any time or arrive with defects. Files can be
accidentally overwritten or deleted. Employees do power off computers improperly. Power outages
and spikes do occur. Buildings do get flooded or burned down. Any one of these things, and
countless other events, could result in a retailer losing business-critical data. And that data loss can
have serious, real-life consequences:
 Lost revenue
 Financial cost
 Regulatory problems
 Damaged brand
 Lost productivity
 Damaged customer relationships
That’s why it is critical for you to have a disaster recovery plan – both to protect the systems and
data your business depends on and to recover from a disaster in a reasonable amount of time.
When crafting a disaster recovery plan, make sure to think about all the locations where critical data
currently resides. For retail organizations, that includes the head office as well as each and every
remote store location. The risks associated with data loss apply as much to individual retail stores as
they do to corporate, maybe even more so.
 Key Elements of a Disaster Recovery Plan

Developing a comprehensive disaster recovery plan is no small task. There is no one “right” type of
disaster recovery plan and there is no single uniform approach. That said, many disaster recovery
plans share these key elements:

 Develop an Emergency Communications Plan and Contact List

• Generate a list of internal and external recovery team contacts
• Generate a list of internal and external contacts who need to be briefed at the onset of
the disaster and receive ongoing updates throughout the event
• Once a disaster event has been declared, alert and mobilize recovery team members to
react and respond to the situation at hand
• During and following the disaster, periodically update relevant parties as necessary
 Define Key Roles and Responsibilities

• Clearly define the key roles and responsibilities for anyone involved in disaster planning
and recovery operations
 Inventory all Hardware and Software Assets

• Complete a detailed inventory of hardware and software applications, including vendor
technical support contact numbers
• Prioritize applications into three tiers - Tier 1 applications are mission-critical apps
needed immediately, Tier 2 applications are needed within a day, and Tier 3 applications
can wait a few days or more
• For each application, also determine how much data loss is acceptable in the event of a
disaster
 Identify and Reduce (or Prevent) a Disaster

• Create multiple copies (backup) of mission-critical data and files
• Regularly test backups for reliability and recoverability
• Use an uninterrupted power supply (UPS)
• Conduct routine inspections of the IT infrastructure
 Identify Potential Threats or Problems That Could Lead to a Disaster

• Use antivirus software and firewalls
• Install server and network monitoring software
• Install fire alarms
 Establish Procedures for System and Data Recovery After a Disaster

• Fix or replace damaged hardware and network components
• Restore or reinstall application software
• Recover mission-critical data
Again, do note that this document will focus on the backup and recovery components of a disaster
recovery (DR) plan as they relate to Retail Pro.

 Part 2 –Developing a

Comprehensive Backup Plan
 The 3-2-1 Backup
A simple and effective backup strategy recommended by many IT professionals is the 3-2-1 Backup!
Simply stated, the 3-2-1 Backup recommends that you have three copies of your data kept on two
different storage types with one copy located offsite.
Let’s break that down!

 Have three copies of your data – When it comes to backups, redundancy is key. At
minimum, you need three copies of your data. Consider the primary data source as one
copy! This means you need at least two additional copies or backups of your data. We
recommend that you use the Retail Pro Technician’s Toolkit to create a backup of the
primary data source. That gives you the first backup. From there, simply make a copy of
the backup. That gives you the second backup. Bottom line, having multiple copies of your
data makes it less likely to lose your data.
 Store the backup copies on two different storage types – Having all three copies of your
data in the same place (whether it’s the same computer or different disks in the same RAID)
is not a good idea. If that storage device fails, all your data is lost. Instead, copies of your
data should be keep on a different media type altogether. Most likely, the primary data
source is located on an internal hard drive. The two backup copies should be stored on
removable storage media – tapes, external hard drives, USB drives, etc. Bottom line, storing
your data on different devices ensure that there is no single point of failure.

Note: To maximize performance during the backup process, initially save the backup to the
same computer as the primary data source and then copy or move (manually or via batch
job) to removable media.
 Keep one backup copy offsite – If all your data is stored in the same physical location, that
data is still vulnerable to catastrophic events (fires, floods, etc.) as well as robberies.
Therefore, we recommend that one backup copy be kept in an offsite location or in the
cloud. The other backup copy can be kept onsite (on removable media) along with the
primary data source, giving you quick and easy access for recovery purposes.
No backup strategy is 100% foolproof, but the 3-2-1 rule ensures that you’ll have a copy of your
data when the unthinkable happens.

 Part 3 – Creating Retail Pro Backup

#1
 Understanding Archive Logs & Redo Logs
Archive logs are vitally important for database recovery. But what exactly are archive logs? To
understand archive logs, you need to first understand redo logs. Redo logs are key database files
that store changes made to the database. Every new sales transaction. Every new or modified
customer record. Every time an item’s description changes. All such database changes are stored in
one of three redo logs, each with a 100MB file size. So what do redo logs have to do with archive
logs? Well, archive logs are basically copies of redo logs.
Let’s take a closer look:
 As changes are made to the database, those changes are first stored in Redo Log 1.
 When Redo Log 1 is full, Redo Log 2 is used to store database changes.
 When Redo Log 2 is full, Redo Log 3 is used to store database changes.
 When Redo Log 3 is full, the system does not create a Redo Log 4.
 Rather, it reuses Redo Log 1. But remember, Redo Log 1 is currently full of data. So before
reusing Redo Log 1, the system copies that data to an archive file, which resides outside the
database. Let’s call this Archive File 1. Now Redo Log 1 is free to store database changes
again.
 When Redo Log 1 is full, Redo Log 2 has to be reused. As before, the system copies any
data currently in Redo Log 2 to another archive file – Archive File 2 – before reuse.
 This process of using and reusing the three redo logs will ultimately result in the creation of
numerous archive logs.

Given their role in database recovery, here are a few best practices relating to archive logs:
 Do Not Disable Archiving – You should never disable the archiving function in Retail
Pro, even when applying a software update (maintenance pack). The only acceptable time to
disable archiving is during the initial data migration to Retail Pro 9. Just make sure to enable
archiving after data migration is complete.
 Store Archive Logs on External Media – Like the backup, archive logs should be stored
on an external storage device. This will prevent the loss of archive logs that have yet to be
backed up. Using the Technician’s Toolkit, you can easily modify the location (log path)
where archive logs should be stored.
Note: To maximize Retail Pro performance, initially save archive logs to the same computer
as the primary data source and then copy or move (manually or via batch job) to removable
media.
 Delete Archive Logs as Needed– Archive logs can easily get out of hand and fill up your
hard drive. For this reason, they should be periodically purged. Ideally, archive logs should
be deleted as part of the Technician’s Toolkit-created backup process. Never delete archive
logs that have not been backed up.

Enabling Archiving (if Disabled):
1. Launch and logon to the Technician’s

Toolkit located here:
…\RetailPro9\TechToolkit.exe
2. Go the “Managing Storage Structure >

Archive Logs” area.
3. Click the “Enable” button

Changing the Archive Storage Location (to External Media):


Archive Logs” area.
2. For the “Log Path” browse to the desire
location
 NOTE: Like a backup, archive files
should be stored on an external
storage device. This will prevent the
loss of archive files that have yet to be
backed up.
 Complete & Incremental Backups

Use the Retail Pro Technician’s Toolkit to quickly and easily backup the primary Retail Pro data
source (i.e. backup number one) to an external storage device. Again, this applies to all Retail Pro
databases located at the head office and remote store locations.
With the Technician’s Toolkit, you can perform two types of backups – Complete or Incremental.
 Complete Backup – With a complete backup, you are essentially backing up the entire
Retail Pro database, including Retail Pro data files and other key database files. This requires
that the database be shut down for a complete backup to be created. For this reason,
complete backups are typically performed outside of normal business hours. As part of the
complete backup, we recommend that you include archive logs as well.

Note: When performing a complete backup, make sure no Retail Pro operation is currently
running – polling/communications, delta builds, etc.
 Incremental Backup – With an incremental backup, you are not backing up data files.
Instead, you are primarily backing up the archive logs. And because archive logs exist
outside of the database, the database does not need to be shut down for an incremental
backup to be created. This gives you the flexibility to create incremental backups during
business hours if desired. Do keep in mind that incremental backups cannot exist alone; for
recovery purposes, complete backups are still required.
To maximize your recovery options, we recommend that you create both Complete and Incremental
Backups on each Retail Pro system. When and how often to perform these backups will depend on
your business. One common practice is to perform a complete backup one day per week (when the
database can be shut down) with incremental backups created in between the weekly complete
backups. Incremental backups can be performed daily or multiple times throughout the day.

Using the Technician’s Toolkit to Manually Create a Complete Backup:

2. Go to the “Backup and Recovery >

Backup > Options” area
3. Specify the following settings:
 Backup Type: Complete
 Automatically start database after
backup is complete: check
 Location: specify the local of the
external storage device
 Set Name: keep default name
 Backup archive logs: check
 Delete archive logs after successful
backup: check
 Compress Backup: optional
 Password protect: optional
4. When ready, click the “Save” button

Backup” area
6. Click the “Start” button
7. Click the “OK” button.

Using the Technician’s Toolkit to Manually Create an Incremental Backup:


Backup > Options” area
3. Specify the following settings:
 Backup Type: Incomplete
 Shutdown database to perform
backup: uncheck
 Location: specify the local of the
external storage device
 Set Name: keep default name
 Delete archive logs after successful
backup: check
 Compress Backup: optional
 Password protect: optional
4. When ready, click the “Save” button

Backup” area
6. Click the “Start” button
7. Click the “OK” button.

Using the Windows Task Scheduler to Schedule Automatic Weekly Complete Backups:
1. Type “Task Scheduler” into the Windows

Search to locate/launch the Task Scheduler
2. Click the “Create Task” link
3. Specify the following General Settings:

 Name: Complete Backup
 Run whether user is logged on or not:
check
 Run with highest privileges: check
 Configure for: Windows 10

4. Click on the “Triggers” tab

5. Click on the “New” button
6. Specify the following Trigger settings:

 Begin the task: On a schedule
 Weekly: check
 Start: 5:00:00 AM
 Recurs: 1 weeks on: Sunday
 Enabled: check
7. Click the “OK” button

8. Click the “Actions” button

9. Click the “New” button
10. Specify the following New Action settings:

 Action: Start a Program
 Program:
C:\RetailPro9\TechToolkit.exe
 Add arguments:
/u:sysadmin /p:sysadmin /m:b
/bstype:c /l:c:\backups
/backuparch:yes /deletearch:yes /s
/startup:none

Command line parameters used to schedule backups using the Technician’s Toolkit:
Programs Location
TechToolkit.exe …\RetailPro9
Parameter Description Allowed Value Example

/u Tech Toolkit username /u:<username>
/p Tech Toolkit password /p:<password>
/m Start backup b /m:b
/bstype Backup type c /bstype:c
i
/l Location for backup /l:c:\backups
/backuparch Backup archive logs yes /backuparch:yes
no
/deletearch Delete archive logs after backup is yes /deletearch:yes
complete no
/s Hide Tech Toolkit when running /s
/startup Startup the database after none /startup:none
completing complete backup

 Part 4 – Creating Retail Pro Backup

#2
 Copying the First Backup
Using the Retail Pro Technician’s Toolkit, you’ve created a backup of the primary Retail Pro data
source and saved it on an external storage device. That’s backup number one! For backup number
two, simply make a copy of the first backup and save that copy to another external storage device.
To accomplish this very task, you have many different options:

 Built-in Backup Tools – Though limited in function, both Windows and Mac OS X have
built-in backup tools that can be used to copy your data. Windows 10 includes a File
History feature and Mac OS X includes its Time Machine software.
 Standalone Backup Software – There many software applications out there that will allow
you to copy your data. Most backup software will allow you to schedule backups at regular
intervals or continuously monitor your system for changed or new files to backup.
 Online/Cloud Backup Services – Online backup and syncing services will copy your data
over the internet to be saved on remote servers.
 Batch Job – One old fashioned option to copy your data is to use a batch job.
Whatever you decide to do to create this second backup, it’s critically important to store the backup
offsite. If the backup is stored on an external hard drive, move it offsite and replace it with another
external hard drive. If you’re using an online backup service, that backup is automatically uploaded
to a remote server. Just set it up and forget it. Bottom line, having a copy of your critical data stored
in a separate physical location from the primary data source protects it from theft and damage
caused by catastrophic events.
Now that you understand the importance of having three copies of your data with the one copy
stored offline, you may be wondering – does this apply to all Retail Pro databases? Ideally, all
aspects of the 3-2-1 backup strategy should be applied to all Retail pro systems. That said, creating a
third copy of your data and storing it offsite may not be feasible for all Retail Pro systems. At
minimum, we recommend that the Retail Pro system at head office have a backup copy of the data
stored offsite. At remote store locations, not having a second backup stored offsite is not the end of
the world. Just realize that data recovery attempts at the retail store will be hampered after a
catastrophic or theft-related event.

 Part 5 – Recovering from Backup

 Accessing Technician’s Toolkit Offline
Before you can use the Technician’s Toolkit for recovery purposes, you will need access to exported
security permissions (stored within a DbSec.dat file). This will allow you to logon to the
Technician’s Toolkit while the database is down.
Export Security Permissions (to Access Tech Toolkit Offline):
1. From the Retail Pro home screen, click the

“Employee Mgmt. > Groups” button
2. Select on the “ADMIN” security group

and click the “Form View” button

3. Verify that the “SYSADMIN” user is part

of the “ADMIN” group
4. Click on the “Permissions” tab
5. Select the “TECHTOOLKIT” security

area
6. Click the “Check All > Permissions”
button
7. Click the “Save” button
9. Go to the
“…\RetailPro9\Export\Security” folder
10. Copy the “DBSec.dat” file

11. Paste the “DBSec.dat” file to the

“…\RetailPro9” folder
 Full, Complete & Point in Time Recovery Options

Use the Retail Pro Technician’s Toolkit to quickly and easily restore from backup. There are three
recovery options available – Full, Complete, and Point in Time.
 A Full Recovery – attempts to restore the Retail Pro database as close as possible to the
point of failure, using a combination of data files and archive logs.
 A Complete Recovery – also known as a “From a Complete Backup” recovery, will restore
the Retail Pro database to the state it was in, when the specified complete backup was
performed. This recovery option is less desirable than a Full recovery because any data
created after the specified complete backup is not recovered.
 A Point in Time Recovery – gives you the flexibility to restore the Retail Pro database back
to specified date and time. Typically, a Point in Time recovery is used when a negative event
occurs and you need to recover the database back to a specific time prior to that event. For
example, you accidentally loaded test data into your production system. With Point in Time
recovery, you can restore the system back to a point before the data import took place.
Another common example involves data corruption that may have been occurring for an
extended period of time before its detection. With Point in Time recovery, you can restore
the system back to a point before the data corruption began.

Ideally, you want to restore the Retail Pro database as close as possible to the point of failure. This
means performing a Full recovery. If a Full recovery is not possible or fails, you may be forced to
recover from a complete backup alone. If you need to restore Retail Pro back to specified date and
time for whatever reason, perform a Point in Time recovery.
Note: Before attempting to recover from backup, make sure to create a cold backup of the Retail
Pro database.
Using the Technician’s Toolkit to Perform a Full Recovery:
1. To create a cold backup, copy all files from

the “…\Oracle\oradata\RproODS”
folder.
2. Copy all archive files available to the

“…\Oracle\oradata\RproODS\archive”
folder
 Archive files located in Incremental
backups created after the Complete
backup
 Archive files created between the last
Incremental backup and the point of
failure (that have not yet been backed
up)

Toolkit (offline mode) located here:

4. Go the “Backup and Recovery >

Recovery” area.
5. Select “Full” as the Recovery Type
6. In the “Backup History” table, click on the
last Complete backup record
7. In the “Recovery Settings” area:
 If different from the backup history
table, browse to the location of the
Complete backup
 Specify the “Target Drive”
8. When ready, click the “Start” button
9. If prompted:
 Copy all archive files to the
“…\Oracle\oradata\RproODS\archi
ve” folder
 Copy the control files (from the cold
backup if available OR from the last
Incremental backup) to the
“…\Oracle\oradata\RproODS”
folder
10. When ready, click the “OK” button
11. Create a new Complete backup
Using the Technician’s Toolkit to Perform a Recover from a Complete Backup:

folder.



Recovery” area.
4. Select “From a Complete Backup” as the
Recovery Type
last Complete backup record
Complete backup

Using the Technician’s Toolkit to Perform a Point in Time Recovery:

folder.
2. Copy all archive files available to the

“…\Oracle\oradata\RproODS\archive”
folder
 Archive files located in Incremental
backups created after the Complete
backup
 Archive files created between the last
Incremental backup and the point of
failure (that have not yet been backed
up)


Recovery” area.
5. Select “Point in Time” as the Recovery
Type
last Incomplete backup record
Complete backup
 Specify the restore date and time
(must be earlier than the last archive
file date/time)

9. If prompted, click the “OK” button
10. If prompted:
ve” folder
11. When ready, click the “Yes” button
12. If prompted:
ve” folder
 Copy the control files (from the cold
backup if available OR from the last
Incremental backup) to the
“…\Oracle\oradata\RproODS”
folder

 Recovery Validation
After recovering from backup, make sure to logon to Retail Pro to perform a high-level systems
check before calling the recovery a success. At minimum, make sure to complete the following
tasks:
 General Systems Check – Logon to Retail Pro to click through the different Retail Pro
modules and areas. Additionally, attempt to create new transactions and customer records
(DO NOT save these test records).
 Communications Check – Access ECM to manually process out. If you are unable to
perform this task, INDEX files and/or DOC_SYNC tables may have been corrupted. To
resolve this issue, you may need to attempt another recovery using an earlier complete
backup or, if performing a Point in Time recovery, using an earlier restore date/time.

 Part 6 – Troubleshooting Backup &

Recovery
 Error Copying Archive Log Files
Because archive logs can easily get out of hand and fill up your hard drive, they should be purged
periodically. This can be done manually or automatically.
 Automatically Deleting Archive Logs – The most convenient way to handle this task is to
allow the Technician’s Toolkit to delete archive logs automatically as part of the complete or
incremental backup process.
For manual backups, make sure to enable the

“Delete Archive logs after successful backup”
setting option before performing the backup.
For scheduled backups, make sure to include the “/deletearch:yes” command line parameter.
Parameter Description Allowed Value Example
/deletearch Delete archive logs after backup is yes /deletearch:yes
complete no
When the purging of archive logs is handled automatically by the Technician’s Toolkit, the
database control file updates each individual archive log’s status to “deleted.”
 Manually Deleting Archive Logs – If you choose to delete archive logs manually or via a
batch job, keep in mind that the database control file is not updated to reflect those
deletions. This may ultimately lead to non-critical errors appearing (in the progress window)
when performing complete backups, assuming the backup is configured to include archive
logs.

Again, these errors are benign and will not impact the successful creation of a complete
backup. That said, you can prevent these errors from displaying at all by rebuilding the
control file.
Using the Technician’s Toolkit to Rebuild the Control File:


Control File” area.
3. Click the “Rebuild” button
4. If prompted, click the “OK” button

 Part 7 – Miscellaneous Topics

 The Case for Uninterrupted Power Supply
Power outages and fluctuations can wreak havoc on computers, potentially resulting in data
corruption or even damage to internal hardware components. In fact, over 60% of "system down"
calls reported to the RPI Technical Support team are due to power-related events. To protect your
computer from damage, connect it to an Uninterrupted Power Supply (UPS) system. During power
outages, a UPS will provide enough emergency power for you to save your work and shut down the
computer properly. Many UPS systems will even shut down an unattended operating system
gracefully in the event of an extended power outage or computer power problem. UPS systems will
also level out voltage fluctuations (power surges and dips) that can overheat your computer and
reduce its performance.
The following best practices will ensure that your system is protected in the event of a power failure
or fluctuation:
 One Database, One UPS – Make sure each Retail Pro database is connected to a UPS
system to protect it from power fluctuations and surges.
 Maintain and Test UPS Systems – As part of your disaster recovery plan, it’s important to
periodically check UPS equipment as well. Just because a UPS is up-and-running does not
mean it’s fully operational. Newer UPS systems typically come with monitoring software
that will allow you to check current power status as well as past performance during power-
related events. Some units will automatically perform periodic battery self-tests and notify
you if a battery needs to be replaced. Additionally, make sure to visually inspect each UPS as
well. Look for wear and deterioration. Remove trash or unrelated materials around the UPS
unit to create better airflow. Clean and vacuum the enclosure if necessary.
Bottom line, a UPS unit is an inexpensive investment against the cost of repairing or replacing
damaged hardware, the lost in revenue and productivity associated with downtime, not to mention
the time and cost of data recovery.
 Other Retail Pro Files to Backup

A good set of backups and archive logs will allow you to fully recover the Retail Pro database after a
disaster or system failure. You’ll be able to logon, ring up sales and so on. For many Retail Pro
users, however, the system is still not production ready. That’s because a Retail Pro backup does
not include custom layouts, translations, modified document designs or custom-built reports.

Likewise, communications-related data is also not included in a Retail Pro backup. All this data
resides outside the Retail Pro database. Specifically, they are stored in two folders, which should be
included in your backup plan.
 Retail Pro 9 – Outside of database-related files, this folder stores almost everything else
required by Retail Pro - document designs, layouts, translation files, report files and program
executables. This folder is located here: …\RetailPro9.
 ECM – this folder stores all communications-related files, including station settings, profiles,
security permissions and program executables. This folder is located here: …\ECM.
Because these files change little over time, it’s not necessary to back them up daily and weekly like
you would with Retail Pro data. Making a copy and updating it every few months is fine.
 Regularly Testing Backups

Backups are useless if you can’t recover them. That’s why a good disaster recovery plan includes
regular testing of backups for reliability and recoverability. The last thing you want to see is a
“failed” or “unreadable” message appear onscreen when recovering from backup.

 Restoring to a Nonproduction Server – Build a nonproduction server using the latest

backups and archive files. Not only will this allow you to test your backup files but it’s also
good practice and gives you a chance to audit the recovery script.
 Validating Datafiles Using DBVERIFY – DBVERIFY is an external command-line
utility that performs a physical data structure integrity check on offline or online datafiles,
including those in a backup file. In other words, this utility can be used to determine if
datafiles are corrupt before spending hours restoring them. Though not a replacement to
actually restoring from backup, it’s a good baseline check that can be performed more often.
Using the DBVERIFY Utility to Validate a Datafile:
1. Click the Windows Start Button and enter

“cmd” into the search box
2. From the Command Prompt, change the

directory to where the backup datafiles are
located. For example:
 cd C:\Backups\C20170203121332
3. Enter the following command to check the

“Users01.dbf” datafile
 dbv file=users01.dbf

4. Looked for any “failed” results that may

indicate data corruption

DISCLAIMER
In spite of what this document advises, recommends or purports, and all of our mutual best efforts to the contrary, you
may still wind up losing your data or experiencing some form of data corruption. And, while we are available to try to
help you recover your data using our best efforts and possibly at significant cost to you, you may still wind up losing
your data. Please remember that your system is yours to manage and defend/protect, and you are ultimately responsible
for it, your data, and your operations. In any event, RPI is not responsible for any loss or corruption of your data, or for
any damages - incidental, consequential or otherwise - which might result from such loss, including but not limited to
loss of business, sales, profits, customers, good will, or any other damages whatsoever at law or in equity.
Copyright © 2017 All rights reserved. Retail Pro University and Retail Pro International, LLC.

Retailpro 9 BackupRecovery Best Practices

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Retailpro 9 BackupRecovery Best Practices

Hochgeladen von

Copyright:

Verfügbare Formate

Retail Pro Backup &

 Part 1 – Developing a Disaster Recovery (DR) Plan

 Part 2 – Developing a Comprehensive Backup Plan

 Part 3 – Creating Retail Pro Backup #1

 Part 4 – Creating Retail Pro Backup #2

 Part 5 – Recovering from Backup

 Part 6 – Troubleshooting Backup & Recovery

 Part 7 – Miscellaneous Topics

1 | Page – Retail Pro Backup & Recovery Best Practices

 Part 1 – Developing a Disaster

 The Importance of a Disaster Recovery Plan

 Key Elements of a Disaster Recovery Plan

2 | Page – Retail Pro Backup & Recovery Best Practices

 Develop an Emergency Communications Plan and Contact List

 Define Key Roles and Responsibilities

 Inventory all Hardware and Software Assets

 Identify and Reduce (or Prevent) a Disaster

 Identify Potential Threats or Problems That Could Lead to a Disaster

 Establish Procedures for System and Data Recovery After a Disaster

3 | Page – Retail Pro Backup & Recovery Best Practices

 Part 2 –Developing a

Let’s break that down!

4 | Page – Retail Pro Backup & Recovery Best Practices

5 | Page – Retail Pro Backup & Recovery Best Practices

 Part 3 – Creating Retail Pro Backup

Let’s take a closer look:

6 | Page – Retail Pro Backup & Recovery Best Practices

7 | Page – Retail Pro Backup & Recovery Best Practices

Enabling Archiving (if Disabled):

1. Launch and logon to the Technician’s

2. Go the “Managing Storage Structure >

8 | Page – Retail Pro Backup & Recovery Best Practices

Changing the Archive Storage Location (to External Media):

1. Launch and logon to the Technician’s

1. Go the “Managing Storage Structure >

 Complete & Incremental Backups

9 | Page – Retail Pro Backup & Recovery Best Practices

10 | Page – Retail Pro Backup & Recovery Best Practices

Using the Technician’s Toolkit to Manually Create a Complete Backup:

1. Launch and logon to the Technician’s

2. Go to the “Backup and Recovery >

5. Go to the “Backup and Recovery >

7. Click the “OK” button.

11 | Page – Retail Pro Backup & Recovery Best Practices

Using the Technician’s Toolkit to Manually Create an Incremental Backup:

1. Launch and logon to the Technician’s

2. Go to the “Backup and Recovery >

5. Go to the “Backup and Recovery >

7. Click the “OK” button.

12 | Page – Retail Pro Backup & Recovery Best Practices

1. Type “Task Scheduler” into the Windows

2. Click the “Create Task” link

3. Specify the following General Settings:

13 | Page – Retail Pro Backup & Recovery Best Practices

4. Click on the “Triggers” tab

6. Specify the following Trigger settings:

14 | Page – Retail Pro Backup & Recovery Best Practices

8. Click the “Actions” button

10. Specify the following New Action settings:

11. Click the “OK” button

15 | Page – Retail Pro Backup & Recovery Best Practices

12. Click the “OK” button

Parameter Description Allowed Value Example

16 | Page – Retail Pro Backup & Recovery Best Practices