Integration Security of Information System - Myassignmenthelp.Com

Question: Discuss about the Integration Security of Information System. Answer: Introduction SQL server backup component available in database servers is essential as it safeguards and protects vital data and information that is stored in SQL server databases. To reduce the risks of a disastrous data losses, a database admin needs to back up their databases to reserve changes and updates to the data on a consistent basis. A well-thought-out and a well-organized SQL server backup strategy will make sure that you can protect your data from loss due to a variety of failures. A database administrator will need to carefully test their selected strategies and do the backing up of thee data that would help the administrator to keep track of the data and avoid the risk of losing important information from the database. SQL-SERVER BACKUP HISTORY AND HEADER FILES SQL server backup history tables The primary purpose of a backup history table is to store backup metadata in the system database. The following is a table showing sample history tables and their description. History table Description the backupfile This table will contain log files that are backed up Backupfilegroup Contains file group in a backup set backupmediafamily Has a row for each media file backup set Comprises rows for each backup set Backupmediaset Comprises rows for each backup mediaset Table 1: description of history tables Transact-SQL codes used to access backup history These are restored information words or lines used when one wants to access the data or information that is located in a given backup history table. It is critical to note that most of these statements will require CREATE DATABASE permissions (MikeRay et al., 2018). This is necessary to ensure that your backup files and the backup information are adequately protected from unauthorized access. Below is a table showing some of these Transact-SQL statements and their explanations. Backup and media header files The difference between a backup header and a media header file is that media header requires the retrieval of info from the start of the tape while the backup header file requires one to scan the whole tape looking at the header of every backup set that is available. Back up-header info When you view the backup header, you will find information about all the SQL server and the non-SQL server backup sets on that specific media. The backup header contains the following information: Types of backup devices used The kind of backup, g. a transactional file Backup start and stop date information All the above information is essential when one is trying to determine which backup set they will select for restoring. Media-header info When you view the media header, you will find information about the media itself instead of info about the backups. The media header contains the following information: Media name Description Name of the software (the software that created the media file) The date the media file was written The Backup set to restore The information available in the backup header is the one that will help you identify which backup set you will restore. The database management system will number each backup set as shown in figure 1. The numbering will aid you in selecting the exact backup set that you want to restore based on its position on the media. Backup Verification Backup verification is not a mandatory requirement but a precious database management practice. This process certifies that the backup is physically intact, readable and without errors. Verification will ensure that all backup files can be easily restored in the event that a database restore is necessitated. In addition to verifying the state of the data stored, if the backup file were generated with checksums, the verification can provide a good clue of the reliability of the data on the backup. SQL SERVER BACKING UP Why carry out SQL server backups? Backing up data is the only sure way of recovering the data in case it any data losses occurs. For this reason, SQL server databases need to be backed up, test restore procedures run on those backups and storing the backups in a safe and secure off-site location. You back up your data, to caution yourself from the below things: Human errors This might result from, for instance, a user dropping a table Hardware failures an excellent example of this is a damaged disk drive or even a permanent loss of the SQL server. Media failure Natural disaster a natural disaster, for instance, an earthquake can occur destroying your premises. It is advisable to have multiple backups located in different regions. Backups are beneficial for routine administrative practices such as database mirroring and archiving. SQL Server Backup Strategies Backup processes should be tailored to a precise environment and must be able to work within a given set of resources and constraints. For a reliable method, one requires to have a best laid down backup strategy which can guarantee maximum data accessibility and minimum data losses during the backup process. It is crucial that the database and the backup files be stored on separate storage media as this ensures that if the device that contained the database files gets corrupted or fails, your backup files will still be available. The practice of separating database files and backup files also improves the input and output action for both the production use of the database and the writing of backup data. A backup strategy contains both the backup portion and the restore portion. The backup portion This part of the strategy contains information that: Defines both the type and the backup frequency How backups will be tested How and where backups will be stored This might extend to include security considerations The nature and speed of the hardware that is required for the backups It is a great exercise to always document all the backup procedures and keep a copy in a hardcopy format. Careful planning, implementation, and testing are mandatory for one to develop an adequate backup strategy. Testing is a critical part of strategy creation as it ascertains and confirms that your approach works. Some of the critical factors that one need to carefully consider while coming up with backup strategies. They include: Organizational production goals these incorporate the goals that the organization has for its databases and its policies when dealing with data security, data loss, etc. The nature of the database - this includes the size of the database, the structure and nature of the data stored, the usage patterns its data requirements, etc. Resource constraints this extends to include, hardware, a human resource available, space for storing backup media, physical security of the stored media among many others. Designing your backup strategy After you select the recovery model that is best suited for your business needs, then you have to implement the backup strategy. For you to optimize your strategy then you need to consider a number of the following factors Hours that applications need to access the database if you have off-peak period, then this is the best time to schedule full backups. How often do your database updates and modifications occur? Will the modifications happen to a small or a big part of the database? How much of space do complete SQL database backup require? Scheduling backups This is the intermediate procedure once you decide on your backup strategy. You have to define how frequently you need to carry out backups, the nature and types of backups that your organization requires among other things as described in your backup strategy or your organizations data policies. Once this is done, then you will be needed to schedule regular backups to ensure that you dont lose any data for many reasons. Testing your backups We cannot say that you have a reliable and efficient backup strategy if its not tested and working. It is to be made sure to test a copy of the database for all types of backups that you are anticipating to be using. It is a worthwhile and recommended practice to document all procedure that you carry out given every detail of the restoration process. These features should include database names, their locations, and even the time it will take to complete these operations. Case study for the report The database is to be comprised of 22 tables. The details of the tables that the database comprises is provided below: CLIENT ( ClientNo, ClientName, ClientAddress, ClientPhone, ClientEmail) CORPORATE_CLIENT (ClientNo, CorporationName, BusinessArea) INDIVIDUAL_CLIENT (ClientNo, PropertyOwner) BUSINESS ( ABNNumber, BusinessName, ContactName, ContactNumber, ContactEmail, BusinessAddress) FREELANCER_BUSINESS (ABNNumber, EliteMemberID) CORPORATE_BUSINESS (ABNNumber) JOB( JobID,JobDescription,UrgencyLevel,JobAddress,Postcode, SelectedBusinessABNNumber, IndustryID) CONTRACT_JOB (JobID, StartDate, EndDate, CorporateClientNo) EQUIPMENT( EquipmentID, EquipmentName, EquipmentStatus, EFlag, MFlag, InspectionDate) INDUSTRY ( IndustryID, IndustryTitle, UnionID) TRADE_UNION ( UnionID UnionTitle, UnionContactName, UnionContactNumber, UnionEmail, UnionAddress, EliteMemberID ) SUBURB (Postcode, SuburbName) INVOICE ( InvoiceNo, Amount, JobID) REVIEW ( ReviewID, ReviewDate, ReviewRating, ReviewText, JobID) SEMINAR (SeminarID , SeminarTitle, SeminarDataTime, SeminarVenue) EQUIPMENT_HIRE (ClientNo, EquipmentID, PickUpDate, DropOffDate) QUOTATION (JobID, ABNNumber, QuoteAmount, QuoteStatus) BUSINESS_INDUSTRY (ABNNumber, IndustryID) ADJACENT_SUBURB (PostCode, AdjacentPostCode) ELITE_MEMBER ( EliteMemberID) SEMINAR_ATTENDIES (EliteMemberID, SeminarID SQL server database backup: The screenshots of the backup procedure for the database has been provided below. Both the instances of the GUI and the command prompt has been provided. The GUI used for the process is the Microsoft SQL Server. The step by step back up process for the database is provided below. Right click on the created database is done and then backup database option is selected. The dialog box provided in the screenshot below appears. The page type general is selected. The database is being selected. The recovery model is set to simple. The backup type is set to full. The back up set name is already provided and set description is provided by the user. The back set expiry time is set to 0 days and hence the backup will never expire. Next the destination folder of the backup is set on the disk. Hence, the backup of the data is completed. Database backup with RMAN: In addition to the GUI the backup procedure with the RMAN is show below. The first step is checking the previous back up. backup database command is used. The compiler displays that there is no previous backup and hence, the there is a failure to connect to the database. Connect target ServiceManager/tiger; command is used The database: ORCL is connected After the connection to the database is done the backup command is to be run again. The compiler returns the error that the database is in no Archive mode. Hence, it was required to stop the back up immediately. Shutdown immediate command was run on the command prompt. The database was closed, the database was dismounted and the oracle instances were closed. The Startup mount command was run. The database was connected to the target instance. The oracle instances was connected and the database was mounted. Show all command was used. The configuration parameters for the database was show to the user. Finally, the backup database command was run and back up was succesfull. list backup command is used in the system. The list of all the backup is provided below. References Boiko, A., Shendryk, V. (2017). System Integration and Security of Information Systems.Procedia Computer Science,104(ICTE 2016, Riga Technical University, Latvia), 35-42. doi:10.1016/j.procs.2017.01.05 Renshaw, A. A., Gould, E. W. (2015). Extended laboratory information system downtime: Implementing a backup laboratory information system in the cytology laboratory. Cancer cytopathology, 123(1), 5-6. Xu, Q., Zhao, L., Xiao, M., Liu, A. and Dai, Y., 2015. YuruBackup: a space-efficient and highly scalable incremental backup system in the cloud. International Journal of Parallel Programming, 43(3), pp.316-338.