Veritas Backup Exec restore process is very simple and one click job to restore any data from all types of storage devices like Disk, Tape, Dedup and other devices.
There are certain things we need to keep in mind while trying to restore files and folders in Veritas Backup Exec. The data restore process depends upon the the type of storage devices used during backup. For example if a Disk storage was used then you can simply restore from below options:
You go to Backup and Restore Tab > right click the server where you want to perform the restore> click Restore and follow instruction to complete the restore process.
Also in case Disk store you don’t need to run Inventory and Catalog because storage is not kept offline. You can restore from a disk storage in simple way.
But if the data needs to be restored from a Tape Library / Tape drive then you must run Inventory and Catalog because catalog needs to be updated for populate all the data available in tape so that you can make your restore selection or you can choose which file you need to restore. We’ll discuss in detail about the restore process in the next post.
Lets check how the restore process actually works in Veritas Backup Exec.
Once you right click on a server to restore the data then submit the restore job then it executes the restore. Then restore is initialized and dispatched to BE Engine and Bengine takes over.
Then BE Engine retrieves the restore job and tries to find out storage device associated with it. Once the storage device which was used in backup job is located to restore the requested data in the restore job it reads the file and transfer the data to remote agent to write the data to the destined server / remote agent server.
Post writing the data to the server which was in restore job selection list, the storage device / storage media is released to its original location. For example if tape cartridge was used then the tape is released and sent back to its slot in the tape library.
The restore job status was reported to backup database and logs are generated as well. It also reports if the status of restore job if it was successful or failed. Now the restore job ends. You can see the restored data to its location where the restore job was pointed to be saved / written.
Here we’ll discuss the backup process and functionality of Veritas Backup Exec.
Veritas Backup Exec has a mechanism which takes place during backup and restore process. We’ll discuss below starting from backup job till the job finishes. Here is the process flow of the backup job.
First of all you need a server for backup and it could be the Backup Exec server (media server) itself or any remote agent server which you have already added. Then you create a backup job job and selection the storage device which could be disk / tape / dedup etec.
Post creating the backup job when it starts either the schedule or manual backup it gets executed. Then backup is initialized and checked the entire backup configuration and identifies the initiator and the target devices which includes sources server and destination storage devices and types of backup. Once the job is initialized it is dispatched to Backup Exec job engine (BE engine) and then BE engine takes over the backup operation.
Then it tries to locate the storage devices involved in the backup job. It also ensures that storage device is healthy and ready to perform backup operation.
Then it tried to establish a control connection which ensure that backup job is ready to give commands to storage device for data writing. Then it prepares and decides to pick up storage device like tape if tape library. If disk storage then it creates a media inside the disk storage to write the data.
Now it checks the backup selection list and excludes the files and folders which are not part of the backup. Then it takes a snapshot of the backup selection list and transfers the snapshot in form of data to the storage device to perform the writing.
Once the backup data is written to the storage device, the backup process performs a verification job post writing the data to ensure it all the data present in the selection list are have been written and are healthy and restoreable as well.
Post backup job completion the storage device which was mounted for data writing is released. Then database is updated. It also creates an index of the written data which is a catalog of data which has been backed up for future use. Then it reports that job status whether it failed or succeeded.
Post every operation being performed two log files are also created – Job history and Job log which actually has the detailed information of operation performed. Finally the backup job ends.
Here we’ll discuss Backup Exec 20.5 Installation step by step. It is important to keeps in mind the prerequisites while installing Backup Exec 20 to better performance.
While installing Backup Exec 20 we need to ensure that we meet it’s minimum system requirement for smooth performance and stability that includes hardware, software and other requirements.
Backup Exec server (Media Server) can be installed on 64 bit operating system only. It can not be installed on any windows core operating system like Windows Server 2008/2012/2012R2/2016. However, only remote agent can be installed on windows core operating system.
Backup Exec can not be installed on windows 2008 SQL or SQL express which is Read Only Domain Controller (RODC) role. In order to use SQL / SQL express it requires the local user account which Read Only Domain Controller does not allow. However if Backup Exec is installed on RODC server then remote SQL instance can be used for Backup Exec Database.
Remote Agent for windows also can not be installed on deduplication volume or ReFS volume.
Below are the additional requirement:
-Internet explorer 9 or later
-Intel 64, Xeon (64bit), AMD64, or compatible processor
-Screen resolution 1024 x 768
-SQL Express 2014 SP2 default instance for Database repository
-Minimum RAM 1 GB, recommended 2 GB or more
– 1.26 GB of Disk space for typical installation
-1.91 GB of Disk space for all options installation
Note: Disk space requirement depends upon the features, options and configuration being used. Additional space would also be required for Database, Catalogs and SQL Express.
Other hardware requirement include NIC card or Virtual network card, CD/DVD drive and a mouse
You can use storage device for data storage which are Disk storage (internal / external) / stand alone tape drive / Robotic Tape Library / Removeable storage devices and non – removeable hard drives.
Note: Backup exec included one tape drive with a robotic tape library by default however tape library with more than one tape drive, Backup Exec Library Expansion Option license is required.
Before we start the installation of Backup Exec 20 we need to download the ISO image from Veritas website. If you have a CD/DVD drive then you can burn the ISO image to a cd/dvd and then insert it for installation. If you don’t have the cd/dvd drive in the server then you can use a third party software like Daemon and mount the ISO image as virtual drive for installation.
You can also mount the ISO image as a virtual drive if you are installing it on Vmware / hyper-v virtual machine:
Once you mount the ISO then you can click Open AutoPlay or Open
Post opening the virtual drive you find below option and click Browser for to start the installation
Then the next screen comes up like below. You can click for Getting started, Pre-instalation or Install Products if you want to know about these option.
To start installation you can click Installation option left side and then you get three option: Backup Exec, Backup Exec Agent for Windows and Simplified Disaster Recovery Disk Creation Wizard. To install Backup Exec, choose “Backup Exec”.
When you click Backup Exec then you get below option so click Install to begin installation
Once you click install then installation begins:
Next screen requires you to choose the license agreement then go next
During installation you get two option to choose Typical installation and Custom installation. Typical is regular installation and Custom options are as listed below
First phase of Backup Exec installation checks computer environment
The next window gives you the option to add the license which is optional. You can install it later also. By default Backup Exec comes with 60 days of trial and you can use all the agent and options.
The next window needs you to put admin password for Backup Exec administrator account which is different than your windows administrator account.
During Backup Exec installation it gives you the option to add one or more remote agent server which you want to backup. However this is optional and not mandatory now and can be done later as well.
Now the final installation begins which will take 20-30 minutes to finish
Now the installation completes
Post installation it requires a reboot
Post reboot of the server you see Backup Exec icon on the desktop
Finally here is the User Interface of the Backup Exec 20
This is the Backup Exec server which is also known as Media Server. Now post installing the Backup Exec software it is not ready to perform any operation. You need to configure storage devices.
You can also add remote servers which you want to backup / protect data. Any remote server which you want to add will require remote agent installation in order to communicate with Backup server.
Veritas Backup exec is a backup software which helps you protect your business environment which includes Windows, Linux and Virtual servers to storage devices like disk, tape and cloud.
Veritas Backup exec is a simplified backup solution suitable to protect small, medium and large scale of business environment. It offers very simple and easy to manage graphical user interface (GUI) which is easy to operate and optimize the day to day backup and restore operation.
History
Backup exec software was initially owned by Seagate Software in 1996. Later Seagate Software was acquired by Veritas Software in 1999 along with Backup exec. Now in 2005 Symantec acquired Veritas software including Backup exec.
In 2015, again Symantec separated it’s portfolio and it was decided that security software portfolio would remain with Symantec and Backup and other software would go to a new company formed which was named Veritas Technology Cooperation acquired by the Carlyle Group.
In year 2016 Veritas introduced itself as a new independent company which offered Backup exec, NetBackup and other software.
Backup exec versions of Veritas – 1999
VERITAS Backup exec 7.3
VERITAS Backup exec 8.0
VERITAS Backup Exec 8.6
VERITAS Backup Exec 9.0
VERITAS Backup Exec 9.1
VERITAS Backup Exec 10.0
Backup exec versions ofSymantec – 2005
Symantec Backup Exec 10d
Symantec Backup Exec 11d
Symantec Backup Exec 12
Symantec Backup Exec 12.5
Symantec Backup Exec 2010
Symantec Backup Exec 2012
Symantec Backup Exec 2014
Symantec Backup Exec 15
Backup exec versions of Veritas – 2016
Veritas Backup Exec 15
Veritas Backup Exec 16
Backup Exec versions Veritas – 2017
Veritas Backup Exec 20.1
Veritas Backup Exec 21
Backup Exec Architecture
UI (user interface): is very simple and easy to manage which provide the all the option for day to day backup operation
Management service: is responsible for performing all the operation and allows all the changes which takes place with every transaction
Metadata service: is responsible for keeping the track of all transaction and segments which are created with each and every operation a user performs
Business objects : Separates the client from directly accessing the backup end
All client go through bemsdk to business object
Client don’t talk to bengine, adamm, BEDB, etc
Browsing is the exception
Backend:
Media server
Data Server
ADAMM
Backup Exec Database (BEDB
Catalog
Media server (Backup Exec Job Engine Service):
The component which actually runs the job
Business objects are used to submit jobs to media server
Media server talks with the data server to read the data, then talk with ADAMM to write it storage device.
Process name is “bengine.exe”
Data Server (Backup Exec Remote Agent for Windows System Service):
Actually reads the data from file system during backup and writes it to file system during restore.
Resides on the client machine (machine to be backed up or restored)
Process name is “beremote.exe ”
ADAMM (Backup Exec Device and Media Service):
Writes \ reads from the Tape or B2D
Implements the media mgmt rules
Process name is “pvlsvr.exe”
BEDB:
BEDB is hosted in Microsoft SQL Application
Stores backup and restore jobs, and all the job settings
Media settings are stored in this database
Managed by Backup Exec Server Service
Default location of Backup Exec database is C:\Program Files\Veritas\Backup Exec\Data folder
Catalog:
Contains meta data such as which file is backed up, on which tape and on which location it lies
Restore browse view comes from Catalog
Catalogs store the information in files and also on the media
Default location of Catalog is C:\Program Files\Veritas\Backup Exec\Catalogs folder
Backup Exec Services:
Backup Exec Remote Agent Service
Backup Exec Device and Media service
Backup Exec Server Service
Backup Exec Job Engine Service
Backup Exec Agent Browser Service
Backup Exec Error Recording Service
Backup Exec PureDisk File System Service
Backup Exec Management Service
Backup Exec Remote Agent Service(beremote.exe)
Gets invoked on receiving control connection request from job engine.
Gets selection lists and job options from job engine.
Reads the data from the Data Server.
Formats the data into Microsoft Tape Format (MTF).
Sends formatted data over data connection
Also includes Data Store Selection Service (DSSS) (not a separate Window Service).
Does not depend on any other BE service
Backup Exec Device and Media Service (pvlsvr.exe)
Also known as ADAMM
Applies media management rules
The Job Engine communicates with ADAMM for Device requests (mount / unmount)
Depends on SQL Server Service
Backup Exec Server Service (beserver.exe)
Provides BEMSDK services via RPC interface.
BEMSDK has a rich set of classes e.g CBemJobHistory, CBemreport.
Schedules and dispatches jobs.
Manages utility jobs such as inventory, Lock, Unlock
Manages the BEDB
Depends on Backup Exec Device and Media Service
Backup Exec Job Engine Service (bengine.exe)
Engine is an NDMP client
Gets the selection list and job options from beservice.exe
Controls the Job Execution
Acquired device from ADAMM
Connects to Data Server
Gets data from Data Server and writes to tape using ADAMM mover interface
Also gets metadata during the backup to update catalogs and UI
Depends on BE Remote Agent, Device and Media service and BE Server service.
Backup Exec Agent Browser Service (benetns.exe)
Is responding for advertising between media server and clients
It detects the resources published by the remote agent
It has the function of adding remote servers in the Favorite Resources node of Backup selection list
Allows the Backup Exec job engine to discover the Backup Exec agents that are available on the network (specifically UNIX, Oracle and Macintosh)
Depends on Backup Exec Server Service
Backup Exec Error Recording Service (bedbg.exe)
BEDBG is automatically installed as a service during the Backup Exec installation
Continuously monitors the Backup Exec processes
Logs are located at the default location C:\Program Files\Veritas\Backup Exec\BEDBG folder
This service does not depend on any other Backup Exec services
Backup Exec PureDisk File System Service
Process name is PDVFSService.exe
Provides Backup and Restore functionality via an installable file system service
Loads the PDvFS DLL and maintains and open connection to the PD/PDDE server(s).
Does not depend on any other BE service
Backup Exec Management Service
Process name is BackupExecManagementService.exe
Used to capture Telemetry information from users
Installation, Performance and configuration data is periodically transmitted to Veritas (anonymously)
Introduced from Backup Exec 2010 R3
Does not depend on any other Backup Exec services
Ports used by Backup Exec Services:
Uses TCP Dynamic port range between 1025-65535 for Data transfer from Remote server to media server
