Epicor Eagle Verifying Secure Data Backup

Transcription

1 EPICOR EAGLE VERIFY ING SECURE DATA BACKUP PA-DSS IMPLEMENTATION GUIDE Epicor Eagle Verifying Secure Data Backup EL8022

2 This manual contains reference information about software products from Epicor Software Corporation. The software described in this manual and the manual itself are furnished under the terms and conditions of a license agreement. The software consists of software options that are separately licensed. It is against the law to copy the software on any medium, or to enable any software options, except as specifically permitted under the license agreement. In addition, no part of this manual may be copied or transmitted in any form or by any means without the prior written permission of Epicor Software Corporation. From time to time, Epicor makes changes to its software products. Therefore, information in this manual is subject to change, and the illustrations and screens that appear in the manual may differ somewhat from the version of the software provided to you. Created by Learning Products and Education Copyright: 2011 Epicor Software Corporation. All rights reserved. Epicor, the Epicor stylized logo design, and Eagle are registered trademarks, and Epicor Eagle is a trademark, of Epicor Software Corporation. All other trademarks are property of their respective owners. Epicor Software Corporation Southfront Road Livermore, CA Document No. EL8022 Publication Date: December 2011 EL8022 Verifying Secure Data Backup 2

3 Table of Contents Introduction... 4 Setting Up the Jobs in Storage Policy Copy Report (JISPC)... 4 Displaying the JISPC Report... 4 Interpreting the JISPC Report... 5 EL8022 Verifying Secure Data Backup 3

4 Introduction Overview of Secure Data Backup (SDBU) Offsite backups are also known as a Secure Data Backup or SDBU, and are scheduled to run automatically on a nightly basis. To verify that a SDBU ran successfully on any given night, you can check the Jobs in Storage Policy Copy Report, which is described in detail in this document. You can run onsite backups and restores on demand, as many times as needed, just as you always could. You will continue to use the exact set of utilities that you have always used for onsite backups (BACKUP, RESTORE, MBC, and Shutdown/SEQ). In MBC, you can turn on or turn off local CD/Tape backups. End-of-Year Procedure Your end-of-year procedure is the same as it was in the past. When you type BACKUP, the system checks the configuration in MBC and then runs a backup accordingly. Typically, the BACKUP command is set up to back up to DVD/tape as well as to the backup appliance; however, if you disabled local backups to tape/dvd and are only running backups to the backup appliance, you may want to set up a DVD/tape backup for the last day of the year for extra protection. Setting Up the Jobs in Storage Policy Copy Report (JISPC) As an Eagle SDBU customer, you are probably already familiar with how to view the status of your most recent local backup using MBC. The Jobs in Storage Policy Copy Report (JISPC) provides information about the subsequent operation that transmits a copy of your backup data to a server in Epicor s Data Center. If you would like to have the option of viewing this daily report, you must inform your Local Platform Specialist (LPS). He or she will in turn notify one of our SDBU backup monitors, who will schedule a daily report to run at 8:30am in your time zone. The report will be automatically downloaded in html format to the local SDBU appliance, and an LPS can assist with creating a shortcut on your PC s desktop that will allow you to display the report each day with the click of a mouse. Displaying the JISPC Report 1. Click the shortcut that your LPS set up on your desktop. 2. When the report index displays, click latest_report.html to view the latest report, or click older reports for a historical perspective. Currently, there are a maximum of 30 reports retained on the SDBU appliance for viewing. EL8022 Verifying Secure Data Backup 4

5 Interpreting the JISPC Report Overview Note that any time stamps reported on the JISPC are always in the Epicor Data Center s time zone, which is Central Time. There are two basic sections on the JISPC report: The top section (Primary Copy) concerns the local backup to the SDBU appliance only, while the bottom section (GlobalDash Copy) concerns the off-site copy only. Interpreting the Local Backup to the SDBU Appliance (Primary Copy) Below is a description of the important columns of the local backup section of the JISPC. Job ID (Status) Every job has a Job ID. A status of (A) is desirable because this means the backup completed successfully and the data is currently available for restore. The D footnote to the (A) means that this data was also deduplicated. Client Any machine that is being backed up has a Client Name. The naming convention for your reports includes your customer account number appended with _eagle. Agent This column illustrates the type of Agent that is used to perform the backup. If the client is an Eagle server, then Linux FS is the Agent. If the client is a Windows PC, the Agent would be Win FS. Backup Type (Cycle/Seq. No) The backup type will be either INCR for incremental or FULL. Your backups are set up on a weekly cycle, and each cycle goes through seven sequence numbers. One FULL backup type will be seen during each cycle. EL8022 Verifying Secure Data Backup 5

6 Start Time/End Time Remember that the start and end times on the report are currently listed in Central time. Size of Application (Compression Rate) The Size of Application (in the example above, the size is 8.41GB) reflects the amount of data that was gathered by the backup agent on the client and transported over the network to the SDBU appliance. This figure will vary daily. On a day where a FULL backup has been performed, the figure will be substantially higher. On days where incremental backups are performed, the figure will in general be lower, because the only data gathered for transport over the network consists of files that have been altered since the prior incremental backup. The compression rate figure reflects the extent to which the data was able to be compressed prior to being deduplicated. The compression operation is important, and compression alone accounts for much of the space savings on the hard disk of the SDBU appliance. In the example above, a compression rate of 29.39% means that after compression, the equivalent of 29.39% of the Size of Application was then passed to the de-duplication engine. In the example above, the equation the system uses is.2939 x 8.41GB = 2.47GB. Thus, 2.47GB was passed to the de-duplication engine. The smaller the Compression Rate percentage, the more effective the compression was. Data Transferred on Network This column reflects how much data was sent over the LAN from the client to the SDBU appliance during the backup operation. Backups may be configured such that data compression takes place at either the client, or at the SDBU appliance itself. Logically, if data compression takes place at the client, then this figure will typically be smaller than the figure in the Size of Application column described earlier. The data was collected, compressed, and then sent across the network to the SDBU appliance. On the other hand, if data compression takes place at the SDBU appliance, then this figure will typically be equivalent to the figure in the Size of Application column. The data was collected, sent across the network to the SDBU appliance, and then compressed. Data Written This figure reflects the amount of data written to disk at the SDBU appliance, after both compression and de-duplication of the data have taken place. Data Verification This column will say Not Picked because this feature is currently not enabled. Retain Data Until A seven day/ one-cycle retention policy is the standard, and that is reflected here. To Be Copied To This column is important, and relates to the off-site copy. Normally, the text Already Copied is what you will see in this column. Already Copied means just what it says: This data was Already Copied off-site. If it hadn t been copied off-site yet, the name of the associated secondary copy, GlobalDash, would appear in the column. Typically, the off-site copy operation should be done by the time this report is run and downloaded to the SDBU appliance, but this will not be true in all cases. If for some reason the Data Written figure of the backup was unusually high, then the off-site copy of all t new, unique data may take a substantial amount of time and still be running as of the next day s business. EL8022 Verifying Secure Data Backup 6

7 Interpreting the Offsite Backup (GlobalDash Copy) Below is a description of the important columns of the offsite backup section of the JISPC. Note that the first 10 columns are identical to the local backup section, and all but the Job ID column contain the exact same information. This is normal. In the Job ID column, note the additional footnote E next to the (A). This means that the data was encrypted, which is correct because the data is encrypted for transmission over the internet to the Epicor Data Center. The Data Written figure in this section would typically be similar, but not exactly identical, to the Data Written figure in the local backup report. The Copied Time indicates the time at which the copy off-site completed. Below is an example of what the JISPC report would look like if it were run AFTER the local backup (Primary Copy) had completed, but BEFORE the off-site (GlobalDash) copy had completed. Note the color coding, which is present on every report. A key for the color coding is located at the bottom of the report screen. Note the following differences between the two sections of the report: In the Primary Copy section, the To Be Copied To column does NOT say Already Copied. In the GlobalDash section, in the Job ID (Status) column, there is an (N), which means the data is Not Available in this copy. Note that the entire row is color-coded differently in the GlobalDash section. The pink coloring also signifies Data Not Available (as per the key at the bottom of the report). EL8022 Verifying Secure Data Backup 7

8 In the GlobalDash section, also note the Data Written value of zero, and the Copied Time is N/A. The Watchdog staff at the Epicor Data Center should be aware of any instance where your off-site copies are behind schedule and advise you accordingly. However, if for some reason you are not contacted and notice this condition yourself over a couple of consecutive days, please open an isupport ticket. EL8022 Verifying Secure Data Backup 8