Hi Guys,

I am having an issue where my Backup Exsec Management Service is not starting. I have found the following in the Event Log. Does anyone know why this is happening?

An exception occured starting remoting services for Backup Exec Management Service:

System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint 0.0.0.0:50104. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations. ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted

at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)

at System.Net.Sockets.Socket.Bind(EndPoint localEP)

at System.ServiceModel.Channels.SocketConnectionListener.Listen()

--- End of inner exception stack trace ---

at BackupExec.Management.Server.RemotingManager.ActivateHosts()

at BackupExec.Management.Server.ServerCommon.Start()

I am using BExec 2010 R3 Rev 5204 with a PowerVault 124T tape device connected via SAS. My current issue is that backup jobs job status goes into a "queued" state indefinitely. (No other jobs are running).

Interestingly, catalog jobs instead fail with an error of "Unable to acquire device for the specified pool and media". Sometimes a catalog job will also error with "Error - Mount failed Physical Volume Library Drive not found."

Device Manager shows:

1. "Tape Drive"> IBM Ultrium

2. "Medium Changer Devices"> Dell Powervault 124T Autoloader

Ideas are all appreciated!

Had an issue last week and it was caused by installing SEP on a windows server 2008 R2 with BE2014. It caused my job to stay active : Queued and would not recognize the d:drive where the backup data was being stored. Turns out support disabled the SEP firewall to get it to run. Exceptions in SEP would not work or allow the backup to run. They left off that I should contact SEP support since a recent update may have caused this. My issue occurred immediately after installtion but maybe an update it brought in caused the issue? Anyone else with this issue?

Hello my friends,

Why microsoft outlook stays starting for a long time when backup is running?
Many times I have to close DLO Agent and reboot Outlook.
This problem is not often, but if it happens with many users in the company.
Please some comments would be helpful.
I attach the picture of my problem.

Thanks

As my last post, I did not set MMS to stand alone properly before reinstalling BE2014 and db on CAS. Then I cannot open MMS console with error cannot connect to database.

After I reinstalled BE2015 and DB on CAS I can now open the BE2014 on MMS. But found it cannot detect the drive which has ever created  storage when setup jobs in CAS. When I tried to create storage on MMS, it  did not  provide the drive with BEData folder in it.

What can I do to make MMS to use the storage drive which has ever been used by CAS jobs? Thanks

Hello,

Since last few days we are facing issues with our Netbackup Drives getting fulled. While we were able to delete the logs from the Netbackup\Logs directory but the logs are getting created quite fastly.

So I thought of changing the Unified Logging for our nb variables but unable to. Is that a problem with our nblog.conf ?

See this.

C:\Documents and Settings\xvgera4>vxlogcfg.cmd -p 51216 -o 118 -l
Configuration settings for originator 118, of product 51,216...
LogDirectory = D:\Veritas\NetBackup\logs\nbrb\
DebugLevel = 1
DiagnosticLevel = 6
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = FileSize
LogRecycle = False
MaxLogFileSizeKB = 51200
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 3
OIDNames = nbrb
AppMsgLogging = ON
L10nLib = D:\Veritas\NetBackup\bin\vxextwincat_1.dll
L10nResource = nbrb
L10nResourceDir = D:\Veritas\NetBackup\resources
NtEventLogSourceName = nbrb
NtEventLogCategory = 0
LogFileSDDL = (null)

C:\Documents and Settings\xvgera4>vxlogcfg.cmd -a -p 51216 -o 118 -s DebugLevel=
0 -s DiagnosticLevel=0

C:\Documents and Settings\xvgera4>vxlogcfg.cmd -p 51216 -o 118 -l
Configuration settings for originator 118, of product 51,216...
LogDirectory = D:\Veritas\NetBackup\logs\nbrb\
DebugLevel = 1
DiagnosticLevel = 6
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = FileSize
LogRecycle = False
MaxLogFileSizeKB = 51200
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 3
OIDNames = nbrb
AppMsgLogging = ON
L10nLib = D:\Veritas\NetBackup\bin\vxextwincat_1.dll
L10nResource = nbrb
L10nResourceDir = D:\Veritas\NetBackup\resources
NtEventLogSourceName = nbrb
NtEventLogCategory = 0
LogFileSDDL = (null)

This is happening for nbrb,nbpem,nbjm & nbemm. We have tried restarting NB Services multiple times but with no luck. Any advise. ?

Soon we'll be removing the four 1TB disk RAID5 array (GPT and NTFS) which has the OS partition and media partition on it, from an HP X1400 G2 solution. Windows Server 2008 R2 with Backup Exec 2012 SP4 installed, no SAN, NAS or tapes at this time.

We'll be using four 3TB disks to replace the current four 1TB disks for primairy media storage and use the 1TB disks in a NAS to use as a secondary media storage. The HP X1400 G2 only has 4 HDD bays so we need to replace the disks all at once. Replacing a single disk, rebuild, repeat might also work but I'm not sure this will allow me to expand the volume when done.

The most logical way to do this to me seems to make a Windows Server Backup image on a 3TB WD NAS we have available, so we can replace the disks, use the Windows Server install DVD and start the recovery using the Windows Server Backup image on the NAS. Then when everything is up and running, I can expand the volume from the 2.7TB to the 8.x TB. It is no issue to halt backups until then, we are not in a production "time is money" environment.

Is this going to cause problems ?

Need help on NDMP failure with error code 84

ALL cifs and nfs streams running successfully. A job with the file names imagenow/osm_01.00001 got failed .What could be a reason for this is similar files from same policy are completed successfully.

05/04/2015 08:48:34 - Info nbjm (pid=28528) starting backup job (jobid=5930722) 
for client isilonbkp, policy PROD_NFS_IMAGENOW_osm_1, schedule DLY_INCR 
05/04/2015 08:48:34 - Info nbjm (pid=28528) requesting STANDARD_RESOURCE resources 
from RB for backup job (jobid=5930722, request id:{41A92AE4-F264-11E4-B86F-CF01C23B3EE4}) 
05/04/2015 08:48:34 - requesting resource STU_DDR1_DALMEDIA3 
05/04/2015 08:48:34 - requesting resource nbutx2.NBU_CLIENT.MAXJOBS.isilonbkp 
05/04/2015 08:48:34 - requesting resource nbutx2.NBU_POLICY.MAXJOBS.PROD_NFS_IMAGENOW_osm_1 
05/04/2015 08:48:34 - granted resource  nbutx2.NBU_CLIENT.MAXJOBS.isilonbkp 
05/04/2015 08:48:34 - granted resource  nbutx2.NBU_POLICY.MAXJOBS.PROD_NFS_IMAGENOW_osm_1 
05/04/2015 08:48:34 - granted resource  MediaID=@aaae7;DiskVolume=ddr1_vw;DiskPool=DDR1_DP;
Path=ddr1_vw;StorageServer=ddr1;MediaServer=dalmedia3 
05/04/2015 08:48:34 - granted resource  STU_DDR1_DALMEDIA3 
05/04/2015 08:48:34 - estimated 37417771 kbytes needed 
05/04/2015 08:48:34 - Info nbjm (pid=28528) started backup (backupid=isilonbkp_1430747314) 
job for client isilonbkp, policy PROD_NFS_IMAGENOW_osm_1, schedule DLY_INCR on storage unit STU_DDR1_DALMEDIA3 
05/04/2015 08:48:34 - started process bpbrm (pid=12509) 
05/04/2015 08:48:34 - connecting 
05/04/2015 08:48:35 - connected; connect time: 0:00:00 
05/04/2015 08:48:36 - Info bptm (pid=12560) start backup 
05/04/2015 08:48:37 - begin writing 
05/04/2015 13:25:36 - Critical bptm (pid=12560) image write failed: error 2060046: plugin error 
05/04/2015 13:25:36 - Critical bptm (pid=12560) sts_get_image_prop failed: error 2060046: plugin error 
05/04/2015 13:25:38 - Error bptm (pid=12560) cannot write image to disk, Invalid argument 
05/04/2015 13:25:38 - Error ndmpagent (pid=12559) NDMP backup failed, 
path = /ifs/HMS/imagenowapp/imagenow/ImageNow6/osm_01.00001 
05/04/2015 13:25:41 - Info ndmpagent (pid=12559) isilonbkp: Filetransfer: Transferred 12658688 
bytes in 16622.546 seconds throughput of 0.744 KB/s 
05/04/2015 13:25:41 - Info ndmpagent (pid=12559) isilonbkp: Filetransfer: Transferred 12658688 total bytes 
05/04/2015 13:25:41 - Info ndmpagent (pid=12559) isilonbkp: CPU  user=51.328257  sys=4683.290557  
ft=16622.538847  cdb=0.000000 
05/04/2015 13:25:41 - Info ndmpagent (pid=12559) isilonbkp: maxrss=114340  in=710112  out=57  vol=5126083  inv=3738523 
05/04/2015 13:25:41 - Error ndmpagent (pid=12559) isilonbkp: Failed to write data at offset 8462336 
05/04/2015 13:25:41 - Info bptm (pid=12560) EXITING with status 84<---------- 
05/04/2015 13:25:41 - Info ndmpagent (pid=0) done. status: 84: media write error 
05/04/2015 13:25:41 - end writing; write time: 4:37:04 
media write error  (84)

How can I install DLO for domain desktop client PC?

I have re installed windows and now I want to setup DLO.

Can I install after join domain or before join domain?

It is needed to select backup folder’s location or it is auto configured?

DLO Version 7.5 SP1

Hello. 

Im trying to restore a Exchange2010 database. Getting this error.

Master server: win2k8  with Netbackup Admin console 7.6.0.1

Win2k8 server with the RDB database on - Netbackup client 7.6.0.1

Selecting Point in time recovery - then adressing it to Microsoft Information Store:\RDB

I have tryed to restore from tape and disk. Same result. I have also tryed diffrent MB  ( MB01 - MB10 ), no go. 

Any tips i can try?   I have run this successfully before with no errors. 4-6 months ago.  i have tryed to look up any changes in our envirement but can`t find any changes from last time i did a MB restore....  

05.05.2015 14:17:05 - begin Restore
05.05.2015 14:17:08 - restoring image dag01-Kjeller_1430695087
05.05.2015 14:17:18 - Info bprd(pid=8836) Restoring from copy 1 of image created 05/04/15 01:18:07 from policy APT-Exchange2010-MB03 
05.05.2015 14:17:21 - Info bpbrm(pid=4596) APREMSRESTORE01 is the host to restore to      
05.05.2015 14:17:21 - Info bpbrm(pid=4596) reading file list for client        
05.05.2015 14:17:23 - connecting
05.05.2015 14:17:23 - Info bpbrm(pid=4596) starting bptm           
05.05.2015 14:17:29 - Info tar32(pid=4596) Restore started           
05.05.2015 14:17:29 - connected; connect time: 0:00:06
05.05.2015 14:17:29 - Info bptm(pid=4324) start            
05.05.2015 14:17:29 - started process bptm (4324)
05.05.2015 14:17:29 - Info bptm(pid=4324) reading backup image          
05.05.2015 14:17:29 - Info bptm(pid=4324) using 30 data buffers         
05.05.2015 14:17:29 - Info bptm(pid=4324) spawning a child process         
05.05.2015 14:17:29 - Info bptm(pid=4324) child pid: 5792          
05.05.2015 14:17:29 - Info bptm(pid=5792) start            
05.05.2015 14:17:29 - started process bptm (5792)
05.05.2015 14:17:32 - begin reading
05.05.2015 14:17:34 - Error bptm(pid=5792) cannot write data to socket, 10054       
05.05.2015 14:17:34 - Info tar32(pid=4596) done. status: 185          
05.05.2015 14:17:35 - Error bptm(pid=5792) The following files/folders were not restored:       
05.05.2015 14:17:36 - Error bptm(pid=5792) UTF - /Microsoft Exchange Database Availability Groups/dag01-Kjeller/Microsoft Information Store/DAG01-Kjeller-MB03/Database    
05.05.2015 14:17:36 - Error bptm(pid=5792) UTF - /Microsoft Exchange Database Availability Groups/dag01-Kjeller/Microsoft Information Store/DAG01-Kjeller-MB03/Logs_1430695040    
05.05.2015 14:17:36 - Info bptm(pid=4324) EXITING with status 24 <----------        
05.05.2015 14:17:36 - Info tar32(pid=4596) done. status: 24: socket write failed       
05.05.2015 14:17:36 - Error bpbrm(pid=4596) client restore EXIT STATUS 24: socket write failed     
05.05.2015 14:17:37 - restored image dag01-Kjeller_1430695087 - (socket write failed(24)); restore time 0:00:29
05.05.2015 14:17:42 - end Restore; elapsed time: 0:00:37
MS-Exchange-Server policy restore error(2810)

We are currently using Backup Exec 2010 R2 running differential backups 6 days a week and a full backup on the 7th day.  The full backup method is set to "full -copy the files" and the differential's and set to "Differential - Using modified time".  The issue we are having is that we are using a 3rd party archiving solution which is set to archive and stub by last modify date but every time the full backup runs all the files are un-archived.  Is there a way to skip files that have been set to "Files is ready for archiving" or some other way to stop this from happening? The backups were originally set to "Using archive bit (reset archive bit)" and I changed them to using "modified time" for the full backups and all files were still un-archived.  Any help would be greatly appreciated.

Hello
Faced with the problem of adding a master server in vsphere client

Plug-in are installing exact documentation
Plug-in is available for Backup Monitoring, Reporting, I can see the VM.
port on the master server 8443 is configured and tested

log recoveryportal.log:
[http-9445-2] 05 May 2015 11:33:13 INFO  com.symantec.nbu.netbackup4j.http.NBHttpClient : GET method url:https://crm1-nb01:8443/nbwebservice/server/master/crm1-nb01/timezone
[http-9445-2] 05 May 2015 11:33:13 INFO  com.symantec.nbu.netbackup4j.http.NBHttpClient : Setting socket timeout to 300000 mili seconds
[http-9445-2] 05 May 2015 11:33:13 ERROR com.symantec.nbu.netbackup4j.http.NBHttpClient : Failed to parse NetBackup Error Code from the response due to JsonParseException: org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
 at [Source: java.io.StringReader@c1aa936; line: 1, column: 2]
[http-9445-2] 05 May 2015 11:33:13 ERROR RecoveryPortal : Application threw exception
java.lang.Exception: Failed to communicate with server using supplied auth token. Error: com.symantec.nbu.netbackup4j.model.NBException:  EC:0. Please verify that NetBackup Master Server name, port and auth token are valid
    at com.symantec.nbu.recoveryplugin.controller.NetBackupMgr.validateServer(Unknown Source)

Master - 7.6.1.1
vCenter server - 5.5
UTC date and correct on Master and Plug-in and vCenter server

it possible to advise in this situation?

PS previous version Plug-in 7.6.0.4 without any problems was registered

Hello all,

I must to decomission one old media server tester, but the nbdecomission procedure doesn' t work fine.

Below the particoular procedure:

nbdecommission -oldserver INTESATD1-99-8
You want to decommission INTESATD1-99-8. Is that correct? (y/n) [n]: y

Administrative Pause set for machine INTESATD1-99-8

One or more of the following jobs could be running on media server INTESATD1-99-8:
JOBID           TYPE            POLICY            CLIENT                       
5655013         IMAGEDELETE                                                    
Before proceeding further, please make sure that none of these jobs are
running on media server INTESATD1-99-8. This command may not be able to
decommission the media server with active jobs on it.

Continue? (y/n) [n]: y

Server INTESATD1-99-8 is a member of the following media sharing groups:
    UNRESTRICTED_SHARING_GROUP


Media referencing server INTESATD1-99-8

Media generation rules on host INTESATD1-99-8:


Drive paths found on server INTESATD1-99-8

Robots attached to INTESATD1-99-8

Processing tape storage units

Processing media referencing server INTESATD1-99-8

Processing drives attached to INTESATD1-99-8

Processing robots attached to INTESATD1-99-8

Processing basic disk storage units

Processing SnapVault/NearStore disk storage units

Processing advanced disks
INTESATD1-99-8 is not a AdvancedDisk storage server

Processing shared disks
INTESATD1-99-8 is not a SharedDisk storage server

Processing OST devices
List of storage servers accessible to INTESATD1-99-8:

Storage Server: ccmdd04
Server Type: DataDomain (9)
Segmentation Fault (core dumped)

Master server:   SunOS sgemop54 5.10 Generic_144488-11 sun4u sparc SUNW,Sun-Fire-V490

Symantec NBU:   # cat /usr/openv/netbackup/version
HARDWARE SOLARIS
VERSION NetBackup 7.1.0.1
RELEASEDATE Sun Jun 12 12:31:43 CDT 2011
BUILDNUMBER 20110612

I remain at desposal for any question,

thank you

Hi all,

I'm running NB 7.6 on Linux.
I have a script in which I backup few files, then label and expire 5% of the medias, and eventually I verify some medias.
I have 5GB medias and ~4GB files (None of them is bigger then 5)

The problem occures when trying to verify:

05/05/2015 15:59:56 - begin Verify
05/05/2015 15:59:56 - Warning bpverify (pid=8930) Skipping backup id vh_dd5-x_2_1430804615, there is no fragment 1

So what happend is I backed up a file, and it splittes over two medias. Then I erased one media, and tries to verify a fragment that it's other half is delted.
I'm looking for a way to backup those files without splitting them over two medias. is there a way to do it? Please notice that I want to verify by media id and not by images.
If not, how can I expire those fragments?

Thanks for your help!

I'm attaching the comamnds I'm using of my script:

"/usr/openv/netbackup/bin/bpbackup -p %s -i -h %s -S %s -t 0 -w 0" %(policy_prefix+str(i), client_name, client_name)    #backup the files
"/usr/openv/netbackup/bin/admincmd/bpmedialist -l |awk '{print $1,$9}               #for creating list of files I'll expire or verify
"/usr/openv/netbackup/bin/admincmd/bpexpdate -d 0 -m %s -force" %(cart_id)   #label some medias
"/usr/openv/netbackup/bin/admincmd/bplabel -m %s -d hcart3 -o" %(cart_id)      #expire some medias
"/usr/openv/netbackup/bin/admincmd/bpverify -id %s" %(cart_id)                        #verify the rest of the medias from the list

Please find below tar logs

5:57:27.739 PM: [7920.9692] <4> ov_log::OVInit: INF - Starting log file: C:\Program Files\Veritas\NetBackup\logs\TAR\050715.log

5:57:27.740 PM: [7920.9692] <4> ov_log::OVInit: GENERAL Log Level: 0
5:57:27.740 PM: [7920.9692] <4> ov_log::OVInit: TCP Log Level: 0
5:57:27.740 PM: [7920.9692] <4> ov_log::OVInit: INF - the log mutex: 508
TAR  NetBackup TAR  7.5GA  [Jun 10 2013]
Copyright c 1993 - 2013 Symantec Corporation, All Rights Reserved.
All Rights Reserved.

5:57:27.754 PM: [7920.9692] <2> WinMain: DAT - _pgmptr = 'C:\Program Files\Veritas\NetBackup\bin\tar32.exe'
5:57:27.754 PM: [7920.9692] <2> WinMain: DAT - lpCmdLine = '-x -v -Y -p -P -I 1430992434 -U 13 -E /C/Program??iles/Veritas/NetBackup/logs/ALTPATH/ALTPATH.004 -J clnt_lc_messages=zh_TW.BIG-5 -J clnt_lc_time=zh_TW.BIG-5 -J clnt_lc_ctype=zh_TW.BIG-5 -J clnt_lc_collate=zh_TW.BIG-5 -J clnt_lc_numeric=zh_TW.BIG-5 -J restoreid=113225.001 -J job_total=1 -J client=pfissrv001.bochk.com -J requesting_client=pfissrv001.bochk.com -J browse_client=itdfs -J backup_time=1430582425 -L /C/Program??iles/Veritas/NetBackup/logs/user_ops/sa53580/logs/NBWIN004 -J priority=90000 -f - '
5:57:27.756 PM: [7920.9692] <2> date_debug: DAT - timezone: China Standard Time, offset=-28800, dst: NONE
5:57:27.757 PM: [7920.9692] <2> date_debug: DAT - current time: 1430992647, 5/7/2015 5:57:27 PM
5:57:27.757 PM: [7920.9692] <2> date_debug: DAT - 01/01/94 UCT:  757382400, 1/1/1994 8:00:00 AM
5:57:27.757 PM: [7920.9692] <2> date_debug: DAT - 07/01/94 UCT:  773020800, 7/1/1994 8:00:00 AM
5:57:28.289 PM: [7920.9692] <2> WinMain: DAT - standard input handle = 580
5:57:28.302 PM: [7920.9692] <2> WinMain: DAT - standard output handle = 584
5:57:28.303 PM: [7920.9692] <2> WinMain: DAT - standard error handle = 588
5:57:28.313 PM: [7920.9692] <16> validName_Server2PC: Unable to open requested file: C:\Program??iles\Veritas\NetBackup\logs\ALTPATH\ALTPATH.004 (WIN32 22: The device does not recognize the command. )
5:57:28.313 PM: [7920.9692] <4> tar_process_restore_args: INF - changed name of file: /C/Program??iles/Veritas/NetBackup/logs/ALTPATH/ALTPATH.004 to file: :??5:57:28.313 PM: [7920.9692] <4> backup_list: INF - creating restore object
5:57:28.316 PM: [7920.9692] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
5:57:28.316 PM: [7920.9692] <16> validName_Server2PC: Unable to open requested file: C:\Program??iles\Veritas\NetBackup\logs\ALTPATH\ALTPATH.004 (WIN32 22: The device does not recognize the command. )
5:57:28.316 PM: [7920.9692] <4> tar_process_restore_args: INF - changed name of file: /C/Program??iles/Veritas/NetBackup/logs/ALTPATH/ALTPATH.004 to file: C:\Program Files\Veritas\NetBackup\logs\ALTPATH\ALTPATH.004
5:57:28.316 PM: [7920.9692] <4> tar_restore_tfi::create: INF - dwJobData: ffffffff
5:57:28.317 PM: [7920.9692] <4> tar_restore_tfi::create: INF -     dwJob: ffffffff
5:57:28.317 PM: [7920.9692] <4> base_restore::tfs_enable_restore_privileges: INF - restore privileges enabled, previous = 0
5:57:28.317 PM: [7920.9692] <4> base_restore::tfs_enable_restore_privileges: INF - backup privileges enabled, previous = 0
5:57:28.317 PM: [7920.9692] <4> base_restore::tfs_enable_restore_privileges: INF - security privileges enabled, previous = 0
5:57:28.318 PM: [7920.9692] <4> base_restore::tfs_enable_restore_privileges: INF - create token privileges enabled, previous = 0
5:57:28.318 PM: [7920.9692] <4> base_restore::tfs_enable_restore_privileges: INF - take ownership privileges enabled, previous = 0
5:57:29.306 PM: [7920.9692] <4> OVGetRestoreToken: INF - successfully wrote restore information to named pipe
5:57:29.306 PM: [7920.9692] <4> base_restore::tfs_enable_restore_privileges: INF - no access token: server directed restore
5:57:29.307 PM: [7920.9692] <16> tar_restore_tfi::create: ERR - can't open progress file C:\Program??iles\Veritas\NetBackup\logs\user_ops\sa53580\logs\NBWIN004 for write (????????)
5:57:29.307 PM: [7920.9692] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
5:57:29.307 PM: [7920.7736] <4> tar_base::keepaliveThread: INF - keepalive thread is active with an interval of 30 seconds
5:57:29.311 PM: [7920.9692] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
5:57:29.347 PM: [7920.5836] <2> ov_log::V_GlobalLog: WRN - ubsVerifyMIS():Microsoft Exchange Information Store is not installed.
5:57:29.348 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - BEDS_Init() Enter InitFlags:0x0
5:57:32.223 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: C:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: D:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: G:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: H:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: I:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: J:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: K:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: L:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: M:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: N:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: O:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: P:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: W:
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: EFI>System>Partition
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Terminal Services
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Windows Network
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Symantec SNAC Network Provider
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: System?State
5:57:32.224 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Active Directory Application Mode
5:57:32.365 PM: [7920.9692] <4> ncfLogConfiguration: INF - Module: libncf, Release: 7.5.0.6 , Build: 06/10/2013 19:55:39 CDT (20130610)
5:57:32.377 PM: [7920.9692] <4> ncfLogConfiguration: INF - Windows version: 6.2.9200, Platform: 2 (), Service pack: 0.0, Suite: 272, Product type: 3
5:57:32.390 PM: [7920.9692] <4> ncfLogConfiguration: INF - Process architecture: 9, Page size: 4096, Process type: 48, Process level: 8664, Processor revision: 6
5:57:32.402 PM: [7920.9692] <4> NcfString::logLocale: INF - Current code page: WINDOWS: 950   (ANSI/OEM - Traditional Chinese Big5), Max. character width: 2, Substitution character: 0x3F [?], Unicode substitution character: 0x003f [?.]
5:57:32.404 PM: [7920.9692] <4> WinMain: INF - DFSR Metadata is not avilable
5:57:42.047 PM: [7920.9692] <2> tar_base::V_vTarMsgM: CKP - 113225.001 1430992662 0 0 0 1 0 T 173 /M/???????????????????IT)/11_??????/Call Centre Team/VRU/Common Section/??????/?????2008????????2008??BBA??????(V1.1).doc
5:57:42.049 PM: [7920.9692] <2> tar_base::V_vTarMsgW: WRN - error writing file: O:\?????\???????(IT)\11_????\Call Centre Team\VRU\Common Section\????\???\2008?????\2008?CBBA????(V1.1).doc (err=WIN32 13: Unknown error)
5:57:42.049 PM: [7920.9692] <2> tar_base::V_vTarMsgW: WRN - error writing byte: 0
5:57:42.049 PM: [7920.9692] <2> tar_base::V_vTarMsgW: WRN - wanted buffer size: 2660
5:57:42.049 PM: [7920.9692] <2> tar_base::backup_finish: TAR - restore:                     1 files
5:57:42.049 PM: [7920.9692] <2> tar_base::backup_finish: TAR - restore:          file data:       2660 bytes
5:57:42.049 PM: [7920.9692] <2> tar_base::backup_finish: TAR - restore:         image data:       6144 bytes
5:57:42.050 PM: [7920.9692] <2> tar_base::backup_finish: TAR - restore:       elapsed time:         10 secs          614 bps
5:57:42.062 PM: [7920.9692] <8> tar_restore::processStateEOT: WRN - processStateEOT before keepalive
5:57:42.062 PM: [7920.7736] <4> tar_base::keepaliveThread: INF - keepalive thread terminating (reason: WAIT_OBJECT_0)
5:57:42.062 PM: [7920.9692] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
5:57:42.062 PM: [7920.9692] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
5:57:42.063 PM: [7920.9692] <2> tar_base::V_Close: closing...
5:57:42.063 PM: [7920.9692] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
5:57:42.064 PM: [7920.5836] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): enter - InitFlags:0x00000001
5:57:42.074 PM: [7920.9692] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
5:57:42.074 PM: [7920.9692] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
5:57:42.075 PM: [7920.9692] <4> OVStopCmd: INF - EXIT - status = 0
5:57:42.075 PM: [7920.9692] <4> OVShutdown: INF - Finished process
5:57:42.081 PM: [7920.9692] <4> WinMain: INF - Exiting C:\Program Files\Veritas\NetBackup\bin\tar32.exe
5:57:44.082 PM: [7920.9692] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\Veritas\NetBackup\logs\TAR\050715.log

Hi 

I will be installing BE 2014 and customer has purchased HP MSA 2040 which will be configured as dedup storage. 

I am trying to understand the pre requisites in setting this up. 

Apart from the license is there any plugin that needs to be installed on the backup server ?

Kindly advice. 

Thanks in advance

Hallo,

ich habe fürs erste mit den vorhandenen Powershellscripts bereits was brauchbares vorbereitet. Nun möchte ich das backup zusätzlich mit einem Kennwort versehen. Da ich leider keine Ahnung von Powershell habe tue ich mich da echt schwer. Ich habe das CreateImageNow.ps1 Script genommen, ich denke ich muss diese Zeile bearbeiten oder?

 $v2iAuto.DoImageJob($oImageJob.ID, $oImageJob.Constants.ImageTypeFull)

Habe gesehen es gibt den Parameter Encryprion, weiß aber nicht wie ich das hier verwenden kann. Wäre super wenn mir das jemand sagen könnte.

Running 7601 on solaris and my windows guy patched a bunch of nodes as per subject.

All backups continued fine apart from sql cluster nodes and they fail with error 50.

The issue is related to vss. If I disable snapshot the backup completes, but we rather want vss.

And our results indicate it only affects clustered sql, we have single nodes running sql tha are unaffected.

Anyone else encountered/fixed?

Thanks in advance,Jim

Hi everyone,

I'm backing on my servers and only have space for one full backup + weekly incrementals on our our primary MMS server.  We DeDupe the data to a secondary MMS server that allows for Full backups + incrementals to be retained for 4 weeks.

In previous versions of BUE we'd set our B2D media to expire after 24 hours, so that the next full backup could overwrite the .BKF files.  However, with BUE 15 and DLM I cannot see a why to achieve this without having DLM actually going ahead and delete the data.

So whilst all my backups are duplicated to DeDupe storage, at the moment I image there is a small period where technically it does not contain a full backup.

...is my understanding correct here?

For 1 Full weekly backup plus dialy incrementals, what 'Keep For' period should I set?  Should it be 167 hours for both the full and incrementals (ie, retain the data for one full week minus one before the next fulls are due to run)?

Thanks in advance

Danny