Beruflich Dokumente
Kultur Dokumente
Ans:-
Technology Risks:-
The Problem:
When budgets are tight, companies may delay their PC replacement
programs in an effort to save money. But the longer those aging PCs
remain in a company’s infrastructure, the more hidden costs escalate —
losses such as lost end-user productivity and downtime. When you factor
in security risks, high maintenance costs, and reduced productivity,
refreshing your client base could actually save your company time and
money — important business goals in any economic climate.
The Problem:
In an attempt to save money, companies large and small occasionally use
business desktop PCs as “servers” by loading server software and adding
more powerful internal components like larger or additional hard drives
and more memory. A desktop PC is designed to serve a single user and
cannot provide the expandability, performance, or dependability that a
server offers.
The Problem:=
The Problem:
The Problem
The Problem:-
Every IT manager wants to limit software images and qualify their PC
platforms using a standardized image. But when it's time to deploy new
PCs, it's never easy. When a vendor makes a hardware change, it can
affect a previously qualified PC platform, and then the software image has
to be updated for the changed PC. After a few such changes on multiple
system components, the cost benefits of PC platform standardization
begin to unravel.
The Problem:-
The Problem:
The Problem:-
The Problem:-
ANS:-
1) How fast and how easy do you want the MySQL Recovery process to
be?
Just like planning any other backup implementation, the most important
consideration is the recovery process. Here are two key recovery
objectives:
Therefore, you will need to determine RPO and RTO for MySQL database
in your environment and implement your backup solution accordingly.
Backup window refers to the time it takes for backups to complete. During
the backup window your MySQL applications will be either offline or
degraded (in performance or functionality or both).
The size of your database and rate of transaction activity will determine
how long your backup window will be. Depending on these factors and the
business requirements of your MySQL based applications you will need to
decide on the scheduling of your backup window. You will also need to
plan on potentially wide gyrations of the backup window duration - e.g. if
some business activity results in a huge number of updates to your
database. Ideally your implementation should also be aware of the
current activity on your database - e.g. if your database is presently
loaded with transactions, your implementation can intelligently postpone
a scheduled backup run for a few hours.
Choosing the right location for backup images is also a critical decision.
Store backups as far away from the original data as possible! You will be
surprised how many DBAs keep the backups on the same RAID as the
original data.
A related decision is where you want to recover your database during the
recovery process. If recovery is initiated after a simple user error, you
may choose to recover the database at its original location. Keep in mind
that hardware failure and disaster might require recovering to a different
host that could have a different location, hardware, operating system, or
version of MySQL. In ideal case, you should have a standby server where
you periodically audit your recovery process.
If you are using MySQL replication for high availability or load balancing, it
can also be leveraged for backup purposes - backups can be performed
on a slave server without effecting the master server.
4) How will you manage your backup process and backed up data?
Appropriate security and access to backup images also plays into the
compliance requirements that your organization may have, which leads
us to the next top consideration.
Ans:-
The FTR (Formal Technical Review) is a software quality assurance activity
with the objectives to uncover errors in function, logic or implementation
for any representation of the software; to verify that the software under
review meets its requirements; to ensure that the software has been
represented according to predefined standards; to achieve software that
is developed in a uniform manner and to make projects more
manageable.
Analysis:-
At the end of each review meeting the decision has to be taken by the
attendees of the FTR (Formal Technical Review) on whether to accept the
product without further modification or to reject the product due to severe
errors or to accept the product provisionally. All FTR (Formal Technical
Review) attendees sign off whatever decision taken. At the end of the
review a review issues list and a review summary is report is generated.
Ans:-
Below is a sample configuration audit checklist (for FCA and PCA). The
Project Managers can use the following checklist as a reference for the
readiness of the audit or even for doing the audit.
Release audit: