Smart Data Backup Management System
Smart Data Backup Management System
1. INTRODUCTION
1. INTRODUCTION
We know, most people in the Internet have a flat rate and they have hard disk
much bigger than they ever use them. If you don't work with video application,
it‘s really hard to fill modern Tera byte hard disks. we think, it may be a very
good idea to implement a Backup system based on Network. You split your
Hard disk in two Partitions. The working Partition and a two times bigger one
to have space for the backup of other people via Network.
All you need is a program, who backups your files to the free net. Because of
the content related key and encryption, Network stores equal content to the
same location. This creates a lot of space be avoiding the infinite duplication
of common content like windows or other dat a applications and operating
systems. This space can be used to store different versions of file who are user
specific and under evolution. Also need is some additional forward error
recover, called save set envelope, to keep the probability below a define d
value.
The private files are secure, because the content has key is better than every
content encryption password. Only if the file is known, it is possible by the
neighbor peers to recognize the presents of this file during backup. This
problem may be solved by the onion routing at the lead in of Network
requests. The directories are also stored with the content related key and
encryption system, so identically directories within distributed software are
also stored on same locations. The main Dataset of the Backup system to
needed start a recovery will be stored local on the computer and additional
under a KSK who contains data to handle to an USK. This KSK must be a
derivate build from a long user password, to create the opportunity to recover
every time the whole hard disk with nothing more than a new computer and the
knowledge of the master password.
2. SYSTEM ANALYSIS
2. SYSTEM ANALYSIS
System analysis is required to build and verify an effective
system. It is the process of gathering and interpreting data and facts,
diagnosing problems and using the information to recommend improvements to
the system. In the development of software, structural analysis, information is
collected from the existing d ocuments.
The smart data backup server has the facility to take secured backups
of the systems in the network. This application will enable the clients to
schedule their backup and take urgent backup of only the required files when
needed. The encryption property of the Smart - Data Backup server ensures
security of the data. Also the clients can have a detailed report o f the backups
As with all computer system, there is always the potential for hardware
malfunctions such as hard disk failures. Often, such maintenance is required
due to the accidental and sometimes even deliberate modification or deletion
of files on a system by its users. In some cases, such alterations can be undone
easily, while in others, the only remedy is to reinstall a system from scratch.
Why Backups?
– Motherboard failure
– Virus attack
Client and Server must have an active connection at schedule time for
proper data backup.
The programs permit you (or the system administrator) to manage backup,
recovery, and verification of computer data across a network of computers of
different kinds. In technical terms, it is a network Client/Server based backup
program. The Backup System is relatively ea sy to use and efficient, while
offering many advanced storage management features that make it easy to find
and recover lost or damaged files. Due to its modular design, Backup System
is scalable from small single computer systems to systems consisting of
hundreds of computers located over a large network.
Advantages:
1. Scheduling
2. Reports
3. Verification
4. Security
The system protect against every kind of data loss. This are
Alternative solutions:
HARDWARE SPECIFICATION
Memory 2 GB RAM
DVD-RW 52 X
Client System
SOFTWARE SPECIFICATION
Client System
FEATURES OF JAVA
JAVA
Java was designed to not only be cross -platform in source form like C,
but also in compiled binary form. Since this is frankly impossible across
The term Java actual refers to more than just a particular language like C or
Pascal. Java encompasses several parts, including:
A high level language – the Java language is a high level one that at
a glance looks very similar to C and C++ but offers many u nique
features of its own.
Java byte code - a compiler, such as Sun's javac, transforms the Java
language source code to byte code that runs in the JVM.
Simple
There are various features that make the java as a simple language.
Programs are easy to write and debug because java does not use the pointers
explicitly. Java provides the bug free system due to the strong memory
management. It also has the automatic memory allocation and deallocation
system.
Platform Independent
Object Oriented
Inheritance: It is the process of creating the new classes and using the
behavior of the existing classes by extending them just to reuse the existing
code and adding the additional features as needed.
Robust
Java has the strong memory allocation and automatic garbage
collection mechanism. It provides the powerful exception handling and type
checking mechanism as compare to other programming languages. Compiler
checks the program whether there any error and interpreter checks any run
time error and makes the system secure from crash. All of the above fea tures
make the java language robust.
Distributed
The widely used protocols like HTTP are developed in java. Internet
Programmers can call functions on these protocols and can get access the files
from any remote machine on the internet rather than writing codes on their
local system.
Portable
The feature Write-once-run-anywhere makes the java language
portable provided that the system must have interpreter for the JVM. This
feature makes the java as a portable language.
Dynamic
While executing the java program the user can get the required files
dynamically from a local drive or from a remote server thousands of miles
away from the user just by connecting with the Internet.
Secure
Java does not use memory pointers explicitly. All the programs in java
are run under an area known as the sand box. Security manager determines
the accessibility options of a class like reading and writing a file to the local
disk. Java uses the public key encryption system to allow the java
applications to transmit over the internet in the secure encrypted form. The
byte code Verifier checks the classes after loading. Array index limit
checking. Code pathologies reduced by
Performance
Java uses native code usage, and lightweight process called threads.
In the beginning interpretation of byte code resulted the performance slow
but the advance version of JVM uses the adaptive and just in time
compilation technique that improves the performance.
Compiler/Interpreter Combo
1. No memory pointers
2. No preprocessor
Multithreaded
As we all know several features of Java like Secure, Robust,
Portable, dynamic etc; you will be more delighted to know another feature of
Java which is Multithreaded.
Interpreted
We all know that Java is an interpreted language as well. With an
interpreted language such as Java, programs run directly from the source
code.
The interpreter program reads the source code and translates it on the
fly into computations. Thus, Java as an interpreted language depends on an
interpreter program.
Built-in Networking
Java was designed with networking in mind and comes with many
classes to develop sophisticated Internet communication s.
Architecture Neutral
Windows XP is known for its improved stability and efficiency over the
9x versions of Microsoft Windows. It presents a significantly redesigned
graphical user interface, a change Microsoft promoted as more user-friendly
than previous versions of Windows. New software management capabilities
were introduced to avoid the "DLL hell" that plagued older consumer -oriented
9x versions of Windows. It is also the first version of Windows to use product
activation to combat software piracy, a restriction that did not sit well with
some users and privacy advocates. Windows XP has also been criticized by
Department of Computer Science, ASIET 17
Smart Data Backup Management System
3. SYSTEM DESIGN
3. SYSTEM DESIGN
Database Design
Level - 0
Level - 1
Level - 2
Level - 3
Dataflow Diagram
Arrows
Circles
Open-ended boxes, and
Squares
The following seven rules govern construction of Data Flow diagrams (DFD):
fig.6: Restore
fig.7: Decompress
SERVER CONFIGURATION
USER ACCOUNT
REPORT
Modules
d) FTP Server
b) Data Compression
Backup scheduling
d) Recover y management
e) Report (backup/Recovery)
c) Data Replication
This creates the duplicates of files needed for ensuring the
security from data loss. This data can be maintained in the client
system near the original data or can be transferred to the server
and can be even maintained in secondary storage devices.
d) FTP Server
This module follows File Transmission Protocol for the easy
transfer of files from the server system to the connected client
and vice versa. This overcomes complex procedures and the
transmission delay of using other protocols.
g) Data Compression
Before transferring the files to the central server it is
compressed to reduce the storage space. Thus even bulk of
data can be easily transferred and saved in a minimum storage
space.
i) Backup scheduling
Defines a schedule for each backup packs by setting the week,
day, date and time for the backup. The information such as
which files are needed for backup, when the backup process
will start, and where to store the files are received
dynamically from the user and saved as xml file.
j) Recover y management
Data recovery module is used to recover the lost or damaged
data from the central server when needed. The data be restored
in the compressed format or we can decompress the data and
download.
k) Report (backup/Recovery)
This module generates the reports about backup and recovery
.it also provide information about the regi stered client systems
and the types of data, date and time of backup created by
them.
Login
Register
Configuration
Backup
Restore
Decompress
4. TEST REPORT
4. TEST REPORT
SYSTEM TESTING
Software testing is a critical element of software quality assurance and
represents the ultimate reviews of specification, design and coding. Testing
present an interesting anomaly for the software. Testing is vital to the success
of the system. Errors can be injected at any stage during development. System
testing makes a logical assumption that if all the parts of the system are
correct, the goal will be successfully achieved. During testi ng, the program to
be tested is executed with set of test data and the output of the program for the
test data is evaluated to determine if the programs is performing as expected.
A series of testing are performed for the proposed system before the system is
ready for user acceptance testing. The testing steps are:
Unit Testing
Integration Testing
Validation testing
Output Testing
Acceptance Testing
Unit Testing
Unit testing focuses verification effort on the smallest unit of the
software design, the module this is known as module testing. Since the
proposed system has modules the testing is individually performed on each
module. Using the details design description as a guide, important control
paths are tested to uncover errors within the boundary of the module. This
testing was carried out during programming stage itself. In this testing step
each module is found to be working satisfactorily as regards to the expected
output from the module.
Integration Testing
Data can be test across an interface; one module can have adverse effect
on another, sub function when combined may not produced the desired
Validation Testing
Validation testing can be defined in many ways, but a simple definition
is that validation succeeds when the software functions in manner that is
reasonably expected by the customer. Software validation is achieved through
a series of black box tests that demonstrate conformity with requirement. After
validation test has been conducted, one of two conditions exists.
Output Testing
After performing the validation testing, the next ste p is output testing
of the proposed system, since no system could be useful if it does not produce
the required output in the specific format. The output generator or displayed
by the system under consideration is tested by asking the users about the
format required by them. Here the output is considered in two ways: One is on
screen and the other is printed format. The output format on the screen is
found to be correct as the format was designed in the system design phase
according to the user needs. As fa r as hardcopies are considered it goes in
terms with the user requirement. Hence output testing does not result any
correction in the system.
Acceptance Testing
User acceptance of the system is key factor for the success of any system.
The system under consideration is tested for user acceptance by constantly
keeping in touch with prospective system and user at the time of developing
and making changes whenever required
IMPLEMENTATION
Implementation is the stage of the project when the theoretica l design is
turned into a working system. If the implementation stage is not properly
planned and controlled, it can cause chaos. Thus it can be considered to be the
most crucial stage in achieving a successful new system and in giving the
users confidence that the new system will work and be effective .
After the implementation phase is completed and the user staff is adjusted
to the changes created by the candidate system, evaluation and maintenance
begin. The importance of maintenance is to continue to bring the new system
to standards.
Implementation planning
Education and training
System training
White-Box testing
White-box testing is a test case design method that uses the control
structure of the procedural design to derive test cases. White -box testing of
software is predicted on close examination of procedural detail.
Black-Box testing
The black-box testing focuses on the functional requirements of the
software. It helps to find out errors in incorrect or missing functions, interface
errors, errors in data structures, performance errors and initialization and
termination errors. The black-box testing is applied during the later stages for
the functional requirement evaluation.
Testing strategy
Unit testing
Condition Testing
Loop Testing
Integration Testing
When the modules of the system are combined together to form the
whole system, there will be the problem of interfacing. Integration testing is a
systematic testing technique for constructing the program structure while
conducting tests to uncover errors associated with interfacing.
Validation Testing
Output Testing
After performing the validation testing, the next step is output testing of
the proposed system since no system could be useful if it does not produce the
Here, the output is considered into ways: one is on the screen and the
other is printed format. The output format on the screen is found to be correct
as the format designed according to the user needs. For the hard copy also, the
output comes out as specified by the user. Hence output testing doesn‘t result
in any connection in the system.
User acceptance testing of a system is the key factor for the success of
any system. The System under consideration is tested for user acceptance by
constantly keeping in touch with the prospective system users at time of
developing and making the Digital Watermarking System.
The testing of the software began along with coding. Since the design was
fully object-oriented, first the interfaces were developed and tested. Then unit
testing was done for every module in the software for various inputs, such that
each line of code at least once executed. After all modules w ere coded the
integration test were carried out. Some minor errors were found in the output
at the earlier stage and each of them was corrected. In the implementation of
user interface part no major errors were found. After the software was
completely developed, the testing was done. The output of the were correct
and accurate during the time of demonstration after that no errors were
reported.
IMPLEMENTATION
System implementation is the final phase i.e., putting the utility into
action. Implementation is the state in the project where theoretical design
turned into working system. The most crucial stage is achieving a new
successful system and giving confidence in new system that it will work
efficiently and effectively. The system is imp lemented only after thorough
checking is done and if it is found working in according to the specifications.
User Training
Thus the users are trained to operate the developed system. Both the
hardware and software securities are made to run the developed systems
successfully in future. In order to put new application system into use,
preparation of user and system documentation, conducting user training with
demo, test run for some period to ensure smooth switching over the system are
to be prepared
Test Report
Once the user enters into his home page he can search for the products
and can view his history and the recent visited links these functions were
tested for their functionality and was found to be working according to the
specifications, provision for user to edit his password is also provided.
5. CONCLUSION
5. CONCLUSION
Disasters both natural and human-caused can threaten your precious files
at any time: a fire, power surge, or leaking pipe could fry your system. Even
without suffering a calamity, there are plenty of other threats to locally stored
data—hard drive failure, accidental erasures, or a lost or stolen laptop could
make you a victim of data loss. By data, here, we mean things like your
irreplaceable family photos, videos, and music as well as documents .
Secure Network Backup System, securely store your files away from your
premises at on-site/off-site server locations, your data will stay intact and
available even if your local disks are stolen or your premises suffer some
disaster. With more and more emphasis on "cloud computing," i t only makes
sense that backup should take advantage of this hot trend in technology.
6. FUTURE SCOPE
6. FUTURE SCOPE
7. REFERENCE
7. REFERENCES