Hi,

I have an issue with a server that fails to backup the C: drive with an error Status 24: Socket Write Error. Yet the child jobs for the D:, E: & F: drives all work without any problems.

When i start a backup job it looks like its going to start okay. Looking in the detailed status of the job it gets down to where it says "begin writing" and starts to count up the files being written then we get this error;

Critical bpbrm(pid=) from client CLIENT1: FTL - socket write failed

NOTE: I cannot post any log files or outputs on here as these servers operate in our secure cloud environment. So posting logs/hostnames/IP is not allowed. Sorry.

This is a Windows 2012 R2 Virtual Machine and it was built at the same time as another server of the same design which works. We are running 7.5.0.6 client and 7.6.0.4 on the media and master servers.

I have read all sorts of posts about possible network issues or client timeouts but since this server with the problem is sat on the same ESX host as the second server built at the same time (which works perfectly) i cannot see networks this being the issue here.

So i was wondering if anyone might have any ideas where to start looking? 

Hi All,

I got some issues with the Backup exec 2014:

1. When the job backup to the tape and then the tape is fulled, but the job don't change to another tape in the same media set.

2. If I don't check "Eject the media after the job compleles", the job won't write to correct media set and will change to the "associate media" to the media set of the job.

3. What meaning of media overwrite options:

-  Overwrite scratch media before overwriting recylable media contained in the targeted media set.

-  Overwrite recyclable media contained in the targeted media set before overwriting scratch media.

anyone have solutions?

Thanks in adv!!!

I have an environment where I own a MasterServer and MediaServer in version 7.5.0.6 installed on windows servers Server 2008. I am doing the migration to version 7.7. I installed on a WIndows Server 2012 R2 Datacenter Virtual server the MasterServer with version 7.7.

What should I do first to perform the migration from version 7.5 to 7.7?

Good Morning,

We are having some issues determining if NetBackup Supports NSS open files for Linux. 

Does the NetBackup know how to back up OES/NSS following the links to the shadow volumes?

Suse Linux Version 10 is being used on the host servers.  There are several cluster nodes and there resources.

We are currently on version 7.6.0.3 on both our master server and client software.  We will begin rolling out 7.7.0.1 within the next few weeks.

I am sorry for this being vague, but I am not sure what other information is needed to make this determination. 

Thanks,

Eric

Hi All , Can someone please explain to me. With regards to the rention period on the default application schedule for sql, if i create other schedules like daily and weekly and give them their own retention periods, do they inherit the retention of the default application or not? if not please explain to me how this retention affects the backups

Hi,

We try to upgrade from 2010 R2 to 2010 R3, when run the browser.exe we cannot see the content of the install page.

we see this:

Any idea what causing this?

Hi,

I have Backup Exec 2015 on Windows server 2012. Std, and several Servers on Win 2003. When i try install agent on it, I get error :

11-11-2015,14:57:44 : C:\VCRedist\V10.0\vcredist_x64.exe /q /norestart /log "C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\V10.0_x64_msruntime_install.log"

+ 11-11-2015,14:57:44 : ERROR - 3: Failed to create process as user.

11-11-2015,14:57:44 : Return Value of Microsoft Visual C++ 2010 Redistributable (x64) : 1603

+ 11-11-2015,14:57:44 : V-225-299: ERROR: Failed to execute VC 10.0 runtime installer. Error code 1603. ***To search for information about this error, click here 

+ 11-11-2015,14:57:44 : Review this log file for details: C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\V10.0_x64_msruntime_install.log

11-11-2015,14:57:44 : The return value for Распространяемые пакеты Microsoft VC++ (x64) returned error code: 1603

11-11-2015,14:57:44 : Clean up Symantec installer keys.

11-11-2015,15:12:38 : AgentSeqDlgs::Misc_BE_CommonOps

11-11-2015,15:12:38 : Dialog Sequence Returning errorlevel 1603

+ 11-11-2015,15:12:38 : The Installation Failed!

I installed VC++ and msxml6-KB2957482-enu-amd64 but I still have this error.

Please help me.

Hi.

I plan to get a Dell R530 and connect it directly to my DR4100 Deduplication appliance via 10 GbE Direct Attach Cable. I don't have a 10 GbE switch so I decided to connect the DR4100 directly to my R530.

Question.

1. Can I still perform backups to my DR4100 as an OST storage ?

2. Should I use 

Enable the remote computer to access the storage device through the Backup Exec server and to perform Backup Exec server-side deduplication, if it is supported ?

Since, my DR4100 is not connected to the LAN. (Except for the management port)

3. Would I be abe to use this type of deduplication with my setup?

Backup Exec server-side deduplication with a deduplication disk storage device.

or

Appliance deduplication on an OpenStorage device.

Thanks,

Paul

Hi,

We try to upgrade from 2010 R2 to R3 for our Dell Tape library, the pre install shows 3 warning,

1. one says this machine is a Termial server.

2. one or more devices connected to this comuter are either not connected or not working.

about 4 month ago we had to replace the drive of the library after that we did remove the defect drive and the BE shows only one drive.

3. warning regarding the version, I did run the liveupdate and it says there is no update availble.

how can correct these warnings?

Thanks

Good day,

I keep getting the above error when doing an Incremental Backup to Disk. Please help as I've allready changed the password Credentials. The data we backup are user files and sql databases.

V-79-57344-5635
 

Thank You,

Hi,

As you may know we have an issue with upgrading the BE 2010 R2 to R3 we cannot use the brwoser.exe to install the R3 so I did try to run setup.exe from the BE\WinNT\Install\BEx64 and just to see if we pass the pre-chaeck, I went untill the step check services account and after that I did cancel the install after that I did check the logs and I can see there is an error with connecting with SQL server!!

This server has also SQL 2008 and if I use this version of sql server manager I can access nts59\backupexec

what this error means? can We goahead with upgrade? or this is not good?

Thanks

11-11-2015,16:22:24 : EnumProcesses Counts: 144
11-11-2015,16:22:24 : Windows Operating System Version: 6.1
11-11-2015,16:22:24 : GetProductInfo returned success. Checking for CORE OS values.
11-11-2015,16:22:26 : Executing managed _Setup:
11-11-2015,16:22:26 : F:\Install\ISOs\Backup_Exec_2010_R3_13.0.5204_ZOnder SP1\BE\WinNT\Install\BEx64\Install\_Setup.exe
11-11-2015,16:22:26 : Loading XML from:
11-11-2015,16:22:26 : F:\Install\ISOs\Backup_Exec_2010_R3_13.0.5204_ZOnder SP1\BE\WinNT\Install\BEx64\Install\IFProducts.xml
11-11-2015,16:22:26 : RawsDlgSequence::CheckInstMode
11-11-2015,16:22:27 : BEOperations::BE_GetInstalledProdCodeVersion()
11-11-2015,16:22:27 : Found 13.0.4164 BEWS Product.
11-11-2015,16:22:27 : RawsDlgSequence::CheckUpgrade
11-11-2015,16:22:27 : DJM was not found to be enabled. Not upgrading a CASO-MMS.
11-11-2015,16:22:27 : SSO key found for upgrade, value: 0
11-11-2015,16:22:27 : Dell Storage Provisioning was not found to be enabled.
11-11-2015,16:22:27 : DLO was not found to be enabled.
11-11-2015,16:22:27 : Backup Exec version 13.0.4164 is registered with the system.
11-11-2015,16:22:27 : Writing Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\13.0\Install\Upgrade Version: 13.0.4164.0)
11-11-2015,16:22:27 : Read Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\13.0\Install\Path: C:\Program Files\Symantec\Backup Exec\)
11-11-2015,16:22:27 : Writing Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\13.0\Install\PreviousDir: C:\Program Files\Symantec\Backup Exec\)
11-11-2015,16:22:27 : Wrote Install Registry Value (Software\Symantec\Backup Exec For Windows\Backup Exec\13.0\Install\DLO Upgrade Version: 0)
11-11-2015,16:22:27 : Launching UI Install
11-11-2015,16:22:28 : BeSeqDlgs::DlgBERemoteConfig
11-11-2015,16:22:28 : CopySupportFiles
11-11-2015,16:22:28 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
11-11-2015,16:22:28 : GetClusterUpgradeState returning 0
11-11-2015,16:22:28 : GetClusterUpgradeState returning 0
11-11-2015,16:22:28 : AgentSeqDlgs::Misc_BE_CommonOps
11-11-2015,16:22:28 : Executing BE_SetSQLxLangVersion. Setting language version of SQL Express BKUPEXEC instance.
11-11-2015,16:22:28 : English (1033) version of SQL BKUPEXEC instance found on this system. NLS upgrade not required.
11-11-2015,16:22:28 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
11-11-2015,16:22:28 : GetClusterUpgradeState returning 0
11-11-2015,16:22:28 : GetClusterUpgradeState returning 0
11-11-2015,16:22:28 : GetClusterUpgradeState returning 0
11-11-2015,16:22:28 : GetClusterUpgradeState returning 0
11-11-2015,16:22:32 : GetClusterUpgradeState returning 0
11-11-2015,16:22:32 : GetClusterUpgradeState returning 0
11-11-2015,16:22:36 : GetClusterUpgradeState returning 0
11-11-2015,16:22:36 : GetClusterUpgradeState returning 0
11-11-2015,16:22:36 : GetClusterUpgradeState returning 0
11-11-2015,16:22:36 : GetClusterUpgradeState returning 0
11-11-2015,16:22:37 : m_bUseNativeClient = 1
11-11-2015,16:22:37 : Executing SQL_GetServicePack.
11-11-2015,16:22:37 : DRIVER={SQL Native Client};SERVER=NTS59\BKUPEXEC;Trusted_Connection=Yes
11-11-2015,16:22:38 : Connected to SQL Server.
11-11-2015,16:22:38 : NTS59\BKUPEXEC is a SQL Server Product Level: 'SP4'
11-11-2015,16:22:38 : Executing SQL_GetSQLServerEdition.
11-11-2015,16:22:38 : DRIVER={SQL Native Client};SERVER=NTS59\BKUPEXEC;Trusted_Connection=Yes
11-11-2015,16:22:38 : Connected to SQL Server.
11-11-2015,16:22:38 : Executing SQL_GetServicePack.
11-11-2015,16:22:38 : DRIVER={SQL Native Client};SERVER=NTS59\BKUPEXEC;Trusted_Connection=Yes
11-11-2015,16:22:38 : Connected to SQL Server.
11-11-2015,16:22:38 : NTS59\BKUPEXEC is a SQL Server Product Level: 'SP4'
11-11-2015,16:22:38 : m_bUseNativeClient = 1
11-11-2015,16:22:38 : DRIVER={SQL Native Client};SERVER=NTS59;Trusted_Connection=Yes
11-11-2015,16:22:38 : Executing SQL_GetServicePack.
11-11-2015,16:22:38 : DRIVER={SQL Native Client};SERVER=NTS59;Trusted_Connection=Yes
11-11-2015,16:22:38 : Connected to SQL Server.
11-11-2015,16:22:38 : NTS59 is a SQL Server Product Level: 'SP1'
11-11-2015,16:22:38 : Executing SQL_GetSQLServerEdition.
11-11-2015,16:22:38 : There is no MSSQL$MSSQLSERVER Service
11-11-2015,16:22:38 : V-225-226: Unable to connect to SQL Server. ***To search for information about this error, click here
11-11-2015,16:22:38 : Executing SQL_GetServicePack.
11-11-2015,16:22:38 : DRIVER={SQL Native Client};SERVER=NTS59;Trusted_Connection=Yes
11-11-2015,16:22:38 : Connected to SQL Server.
11-11-2015,16:22:38 : NTS59 is a SQL Server Product Level: 'SP1'
11-11-2015,16:23:19 : m_bUseNativeClient = 1
11-11-2015,16:23:19 : AgentSeqDlgs::Misc_BE_CommonOps
11-11-2015,16:23:19 : GetClusterUpgradeState returning 0
11-11-2015,16:23:19 : GetClusterUpgradeState returning 0
11-11-2015,16:23:25 : GetClusterUpgradeState returning 0
11-11-2015,16:23:25 : GetClusterUpgradeState returning 0
11-11-2015,16:23:40 : GetClusterUpgradeState returning 0
11-11-2015,16:23:40 : mydomain\Administrator
11-11-2015,16:23:56 : Install is executing as the service account.
11-11-2015,16:23:56 : EUserName value successfully written to the registry.
11-11-2015,16:23:56 : EPassword value successfully written to the registry.
11-11-2015,16:23:56 : EDomain value successfully written to the registry.
11-11-2015,16:24:00 : GetClusterUpgradeState returning 0
11-11-2015,16:24:00 : GetClusterUpgradeState returning 0
11-11-2015,16:24:07 : The return code is: 1602
11-11-2015,16:24:07 : WARNING: Installation has been canceled.

Hello,

I´m using Backup Exec 12.5 on a Windows Server 2008R2. I have got two SDLT Tape Drives which are conncetd via SCSI to the server. 

I used the following configuration/solution https://www.veritas.com/support/en_US/article.TECH44676, but it doesn´t work :/

The catalog job failed after 3 hours with the following Errors:

Job ended: Wednesday, November 11, 2015 at 4:51:37 PM
Completed status: Failed
Final error: 0xe0000900 - The requested media is not listed in the media index and could not be mounted. To add the media's catalog information to the disk-based catalogs, run an inventory operation on the media and resubmit the Catalog operation.
Final error category: Backup Media Errors

For additional information regarding this error refer to link V-79-57344-2304

Catalog
The media for sequence number 1 in this media family has not been inventoried. No sets on this media may be cataloged. The media for sequence number 2 in this media family has not been inventoried. No sets on this media may be cataloged. The media for sequence number 3 in this media family has not been inventoried. No sets on this media may be cataloged. 

Thanks for your help,

Henning

Now that Veritas have tacken BE back, is this still the primary BE community, or should there be one on Veritas somewhere? Only I had a look and couldn't find one.

Hallo 

Es ist nicht möglich eine erfolgreiche GRT Sicherung von Hyper-V VMs durch zuführen. 

Der Hyper-V ist ein Windows Server 2012R2 

Alle VMs sind Windows Server 2012R2 

Der Backup Server ist installiert mit BE 2015 FP2 und auch auf ein Windows Server 2012 R2 

Die Sicherung der VMs läuft durch. Bei Katalog kommt dann der Fehler. 

Der Agent ist auf allen VM installiert. Die Maschinen sind online. 

Fehler: 

V-79-40960-38531 - Bei Granular Recovery Technology (GRT)-Vorgängen konnten die erforderlichen Startkonfigurationsdateien nicht geladen werden. Backups, für die GRT aktiviert war, können u.U. nicht wiederhergestellt werden.

Über die Wiederherstellungsansicht sehen die Festplatten so aus 

C: 

EFI-Systempartition und Systemstatus kommen von einer Agent Sicherung 

Es scheint so als ob bei jeder Sicherung eine neuen Platten ID erzeugt wird. 

Kann einer Helfen ?

Runnel 

Just wondering before I need to do it for real how folks deal with oracle backups with agent that are offline and under cluster control.

Hot / online backups...no problem the db stays running , the cluster is happy.

But we may be needing cold backups due to excessive arcredo space...now this will try and shutdown the db and the cluster wont like it.

Would ordinarily use OIP but might need a change of direction.

I'm guessing one needs pre/post scripts to clrg offline the oracle db component and online afterwards: but what happens to the command issued via netbackup to offline the db...does it fail? Does it then affect the running backup? Sounds messy...is there value in just doing a flat file backup and put the clrg commands around that backup? Thanks in advance, Jim

Hi Carig,

We did run the upgrade to R3 and it says completed successfully but we must reboot the server I will do it tonight after office hours.

I will plan en upgrade to BE 15 but I must first see how the licenses must be upgraded.

Thanks you for you support.

On the serveryou want to updatethe agentonthe servercan notrestart.How do I resolvethis issue?Soafter the updateservice BackupExecAgentAccelerator does not start. Server is working365/24/7.

Hi, We are using symantic veritas 6.5.6 to backup all unix and windows servers.

Our backup server is on win2k8 enterprise 64 bit.

We recently come across issue where backup of One sun server is failing.OS details of server is as below.

[sun1280@root--]/--->cat /etc/release
Solaris 9 s9_58shwpl3 SPARC Copyright 2002 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 15 April 2002
[sun1280@root--]/--->uname -a
SunOS sun1280 5.9 Generic_117171-02 sun4u sparc SUNW,Netra-T12

In that server i have run the following command and it worked fine.

bash-3.00# /usr/openv/netbackup/bin/bpcd –standalone

The server is rebooted and we again ran the same command.
Now i am unable to connect client with my backup server and in client it is showing as no netbackup process running

[sun1280@root--]/--->/usr/openv/netbackup/bin/bpcd -standalone
[sun1280@root--]/---> [sun1280@root--]/--->/usr/openv/netbackup/bin/bpps -a
NB Processes ------------

Kindly suggest what needs to be done.

I'm trying to set up an AWS S3 cloud storage in BE 15, but I'm getting this error: "BEMSDK failure code: A0009B23"

I have followed this article to the letter: https://www.veritas.com/support/en_US/article.000081253

There are 3 things that I've thought of which could be causing the problem:

1. That article only tells you to setup an AWS S3 bucket and an AWS IAM user and create a key, but it doesn't say anything about linking the user to the bucket. I'm new to AWS so no experience with this. I have granted my IAM user permission to an "AmazonS3FullAccess" policy but that's not made any difference. Am I missing a key step here?
2. Do I need to allow any specific ports through my firewall to access the S3 bucket?
3. Do I need to allow access from my IP to the S3 bucket? I can't see any security options against the S3 module.

I've attached images of the BE error, and my storage configuration (obviously the real username is my Amazon account access key)

Can anyone help?

When trying to do a restore of the terminal services licensing database, it was discovered that there were no files being backed up in the C:\windows\system32\lserver.  It showed that the directory export under that directory was being backed up, but no files.  AOF is turned on with automatically select open file technology.  The terminal services licensing database is on a 2003 server.  Is there a different option I need to set?