Failed to log on to Microsoft Windows. Symantec backup Exec 2012 Error in Backup Job.

Or, Failed to log on to Microsoft Windows. Ensure that your logon credentials are correctly entered.

Symantec Backup Exec 2012 Schedule Job Error:

The job failed with the following error: Failed to log on to Microsoft Windows. Ensure that your logon credentials are correctly entered and that they meet the following minimum requirements to log on to a Windows computer: - The credentials used are a member of the Backup Operators group. - For Windows Vista/2008 and later, the credentials have the Log on as a batch job privilege. Additional privileges may be required to access resources on the Windows computer.

Solution:

1. Login to Client Server (For which backup is failing).

2. Right Click on Computer > Manage > Configuration > Local User and Group > Group

3. Right Click on Group > Properties > Add > Here add your logon account of backup server which is being used for taking backups (if you will edit credential setting of any backup job, you can see the logon account information which is being used for backups) > Ok.

4. Restart Backup Exec Remote Agent services on client server.

5. Now Login to Backup Exec Server

6. Restart Backup Exec Agent Browser Service.

7. Restart Backup Exec Job Engine Service.

Now you can check with browsing backup job setting of problematic backup client server, It will allow you to browse it's directories.

Run the backup job again, it should not throw this backup failure error again...

Cheers, Please write me back if you have any query or feedback.

Configuring tape library with backup exec server

Or, Storage has not been configured for the Backup Exec Server

Or, Backup Exec Error: Storage has not been configured for the Backup Exec Server

Descriptions: In this article, we will see how to configure tape library with backup exec server. Also, the tape library configuration is required the same way when you are encountered with the error ‘storage has not been configured for the backup exec server’.

This is very common scenario where you have done all the backed stuff to make sure tape library is reachable to backup exec server but you forgot to configure the drives, which will be used with backup jobs.

Environment:

Backup Exec Server Version: Symantec Backup Exec 2012

Tape Library: IBM 3537 TL

Tape Library Drive: IBM ULT3580-TD4

Error Screenshot:

Resolution/Steps:

Open Backup Exec Server Console

Go to “Storage Tab” and the Click on “Configure Storage” Option as highlighted in below screenshot:

Select “Tape Storage” and Click “Next” as shown below

Now Select “Configure Robotic Library Partition” Option and click “Next “as shown below:

Select your “Robotic Library” and Click “Next” as shown below:

Now check mark on “Reconfigure Robotic Library Partition” and click “Next” as shown below:

Now you can configure your tape library storage partitions as you wish (I configured my library partitions as shown below for your reference) and Click “Next” > Click Ok if prompt

Now, library will configure partitions on it’s own, wait till the configurations completed successfully.

IMP Note: If you have some backup job scheduled with specific partitions, then you must check your all backup job and re-assign library partition to each backup job.

Cheers…..please write me back if you have any query or feedback…

Data Backup/Restoration Very Slow in Symantec Backup Exec.

Or, Data Restoration Job Very Slow in Symantec Backup Exec Server. 

Or, Backup/Restoration Job Read/Write Speed Very Slow.

Descriptions: Its normal behavior of windows machines. Even if you have faster network, the read/write speed may be slower depending upon the Ethernet/LAN adapter level Speed and Duplex selections. If you have 1gbps connection, you should not have it set to 10mbps etc..

You should set this speed and duplex settings on both Backup Server and Backup Agent/Client.

Solution:

Correct the Speed & Duplex settings for LAN adapters on both servers (Backup Exec Server and Remote Agent Server).

Steps: To correct the settings:

Go to Run > Type ncpa.cpl > hit Enter > Right Click on LAN Adapter > Go to Properties > Select Internet Protocol Version 4 (TCP/IPv4) as below given reference screen shot:

Now Click on Configure button > Then Click on Yes if prompted (Screen shot given below for reference):

Go to Advance tab > Under Property section, select Speed & Duplex > Under Value section, select 1.0 Gbps Full Duplex > Now Click OK

Once you have configured “Speed & Duplex” on both the servers (Backup Server and Remote Agent Server), your data backup and restoration job will be speedup. 

More than 5GBof data rate (Read/Write) is archive in my case.

For example, you can see the below screen shot:

Cheers, please write me back if you have any query or feedback on this.

System State Backup in Windows Server 2012

Or, How to take System State Backup of Windows Server 2012 DCs?

Or, How to run system state backup using wbadmin utility?

Descriptions: As NTBACKUP utility is no more available in Window Server 2012 Operating System, you still have WBADMIN to perform system state backup of your servers. WBADMIN utility is part of Windows Server Backup feature in windows server 2012.

Windows Server Backup Feature can be installed using Server Manager’s Roles and Features installation wizard.

Yes, please!! You must install this feature before you think of using WBADMIN for system state backup.

Steps: Using WBADMIN for system state backup

Open CMD (run as administrator)

Type the command below and hit enter

wbadmin start systemstatebackup -backuptarget:E: -quiet

you can choose the backup target as per your scenario. In my case, I am using E:\ drive as a backup target.

The Backup will be initiate now, wait till it completed successfully.

Cheers, Please write be back if you have any query or feedback.

Error ‘the value for option backuptarget is missing’ on Windows Server 2012

Or, WBADDMIN Error (Systemstatebackup): the value for option backuptarget is missing

Descriptions: Even when you are trying correct commands to perform systemstate backup on windows server 2008 or 2012 using wbadmin (e.g. the command ‘wbadmin start systemstatebackup -backuptarget:E: -quiet’ is correct but ends with error), it is being encountered with error ‘the value for option backuptarget is missing’.

Guys, if you don’t do, my suggestion is, always think of reboot after installing any role, feature or components on windows operating systems as per your convenience. No matter the type of installation is required reboot or not. Anyways, it’s your choice at all. J

Possible Reason: You have recently installed powershell along with windows backup feature and trying to perform systemstate backup without taking server reboot after the installation of this feature. Remember, I said always think of taking reboot after installing anything on windows operating systems.

Solution/Workaround:  Reboot your server > run CMD as administrator > try to re-execute the command... it should work… in my case it worked well…

Wait till the backup is completed successfully.

Cheers...please write me back if you have any query or feedback.

Creating date wise log file in Robocopy backup.

Or, How to take backup of shared or local folders using Robocopy?

Or, Robocopy command to take backup and exporting backup log files date wise.

Descriptions: Using Robocopy for shared folders or local folders backup is one of the good way to perform flat files/data backup in Windows. It’s an inbuilt utility in windows by Microsoft, no need to download or purchase it separately.

Normally, administrators do use robocopy with source, destination and export logs arguments in the robocopy command and rename the log files manually everyday... that’s waste of time frankly... J

Here in this article, we will see how we can set the robocopy command to take backup of data, export log in a txt file and keep the log file name with execution date included. We are going to get it done with batch script..

e.g. If the log file name is fileserverbackup.txt, it should be exported with name fileserverbackup-YYYYMMDD.txt

Please note, I have used some special switched to for best backup output. you should understand the behaviour of special switches before using them.

You can use Robocopy /? for more help on robocopy command and switches.

Commands and batch file:

General command with no special switches

robocopy C:\TestSourceFolder E:\DestFolder

Customized command as per suitable requirements with some special switches

robocopy C:\TestSourceFolder E:\DestFolder /E /ZB /SEC /R:3 /W:3 /TEE /UNILOG+:C:\FileServerBackup.txt

the above mentioned command will take backup well, but it will create a log file FileServerBackup.txt with no date inserted in the file name.

Recommended:

Batch script to take backup using robocopy command and then creating log files every day with date specified/added in the file name.

--------------------------------------------------------------------------------------------------------------------------

@echo off

echo wscript.echo year(date) ^& right(100 + month(date),2) ^& right(100+day(date),2)  > "%temp%\dateparts.vbs"

for /f "tokens=1 delims=" %%a in ('cscript //nologo "%temp%\dateparts.vbs"') do set yyyymmdd=%%a

echo Today is %yyyymmdd%

robocopy C:\TestSourceFolder E:\DestFolder /E /ZB /SEC /R:3 /W:3 /TEE /UNILOG+:C:\FileServerCopy-%yyyymmdd%.txt

--------------------------------------------------------------------------------------------------------------------------

Copy and paste the above given script in a text files > save as filename.bat > use this bat file in windows task scheduler.

That’s it, backup will be executed and file name will be created date wise automatically. Please make sure you tested the script carefully and deploy[ in production if it works 100% as per your requirement.

If you have any query or feedback, please write me back...

Installing Veritas Backup Exec 16 on Windows Server 2012 R2.

Or, Step by step installation guide for Veritas Backup Exec 16.

Or, Veritas Backup Exec 16 installation Steps..

Descriptions: First things first, please make sure you have fully patched windows server 2012 R2 and .Net 3.5 installed already before proceeding with installation of Veritas Backup Exec 16. Its required for properly functioning of windows server as well for smooth error free installation of veritas backup exec 16 on windows server 20112 R2. Internet connectivity is also required if in case SQL Express installation needs it while installing Veritas Backup Exec 16 on the windows server.

Rest of the process of installing Veritas Backup Exec is just simple as Next, Next, and Finish.. J Thanks to Veritas for making it so simple and less time consuming….

Steps: Installing Veritas Backup Exec 16

Right Click on the ISO image you downloaded for Veritas Backup Exec > Click on Mount

Browse CD-ROM > Right Click on Browser > Click on Run as administrator > Click Yes/OK if prompted

Click OK

Click on Backup Exec

Wait for Processing to be completed

Choose I accept the terms of the license agreement > Click Next

Choose Typical Installation > Click Next

Click Next

If you have licenses handy, give the details here and Click Next or You can Click Next without entering the license key for Trial Installation. (In my case I am using Trial Installation).

Say OK > Click Next

Fill out the required fields and Click Next

Click Next

Click Install

Wait for installation to be completed and Click Finish once done. You can now open the Backup Exec Console and start deploying agents for backup.

Cheers, please write me back if you have any query or feedback on this...

Symantec Backup Dashboard Cannot Start

or "Error - Backup Exec cannot Start because there is a pending request from Backup Exec to restart computer".

There are Two Solutions available you can choose any of the solutions to fix this issue.

Solution 1 - Simply plan downtime and restart the server...

Solution 2 –Open windows registry..

Run >> regedit >>HKEY_Local_Machine  >> Software >>Symantec >> "reboot" ( delete reboot).

Now you can access Backup Exec software....

How to backup ManageEngine Op Manager?

Or, How to take backup of ManageEngine Op Manager?

Don't know why ManageEngine is not developing the way to schedule and take automated backup of monitoring tools like, OPManager and App Manager. It has always been a pain area to take backup of these applications manually every time.

Anyways, below are the steps that I have already followed to take backup of my OpManager application.

Steps:

1. Stop the OpManager service.

2. Rename the logs to logs-old under the OpManager Installation Home directory.

3. On the Op Manager Server open CMD as administrator privileges (do open CMD run as Administrator):

Example:

C:\>OpManager\bin\backup>BackupDB.bat

4. Wait for backup to be completed

5. Copy the output file from directory: OpManagerInstallationDirectory\ working\backup

Good Luck, please write me back if you have any query or feedback..

How to backup ManageEngine Applications Manager?

Or, How to take backup of ManageEngine Applications Manager?

Steps:

1. Open CMD (run as administrator)

2. Locate to Installation directory of Application Manager (cd ApplicationManager\Bin).

3. Run the command “BackupPGSQLDB.bat/.sh”

4. Wait for backup to be completed

5. Copy the output file from directory: ApplicationManagerInstallationDirectory\ working\backup

Any query or feedback, please write me back..

How to Backup DHCP Server?

Or, How to perform DHCP Server backup in Windows Server 2012?

Or, Steps to perform DHCP server backup in Windows Server 2012.

Steps:

1. Open DHCP management console (Go to run > type dhcpmgmt.msc > press Enter)

2. Right click on the DHCP server > Click on Backup (reference screenshot shown below)

3. Choose the path where to backup > Click on Ok (reference screenshot given below):

Default backup path of DHCP Server backup?

Or, Where is DHCP server backup located by default?
Or, DHCP Server backup default path?

The default folder path of DHCP Server Backup directory is C:\Windows\System32\DHCP\Backup

bemsdk failure code 000006ba in Symantec Backup Exec?

In Symantec Backup Exec 2012 or later version when we try to run scheduled backup jobs. Sometimes Back exec throws an error bemsdk failure code 000006ba. 
So in this situation backup Exec doesn’t allow to run any backup Jobs.

Cause - One of the Backup Exec server Services is stopped. Go check in services (command - services.msc). 
Solution - Restart all Backup Exec services, after completing 100% , we can run backup jobs Smoothly.

How to perform manual backup using Druva inSync Agent?

Or, How to run the backup manually using Druva inSync Agent?

1. Go to Windows Notification Area > Click on the Druva inSync Agent Icon (Green Colored) Highlighted in below screenshot:

2. A Separate agent console window will appear (as shown in below screenshot) > Click on the “Backup” option (highlighted in red square in below screenshot) > Now the Backup will be initiated.

Wait for the backup to be completed successfully.

How to resume backups of hold backup job in Symantec Backup Exec 2014 ?

Just follow this below steps to un-check hold option in Symantec Backup Exec 2014.

•   Open Symantec Backup exec console.
•  Go to Job Monitor Tab.
•   Click on List.
• All Backup Job Occurrence will come in Jobs items just below.
• Choose which job you want to unhold, Just right click to that and unhold it.

Now you have done it....