banking & finance

46 Topics

Backup failed with error code 71 (EXIT STATUS 71: none of the files in the file list exist). The server rebooted automatically on 28th march and after that the backups are failing.
Problem description : Backup failed with error code 71 (EXIT STATUS 71: none of the files in the file list exist). The server rebooted automatically on 28 th march and after that the backups are failing. The network drives are Netapp storage Shares and it is mapped to the client COLLECTIONSRV. The drives are accessible from OS using the user “USER1”. The netbackup client service is having the logon credentials of user “USER1”. In the policy the “ Backup Network drive” option is selected. The path is also specified properly. Also tried with the mapped drive letter “Y:\”. But the backups are failing with the same error code. The server has been rebooted manually but still the same issue. BPBRM: 03:02:59.482 [3339] <4> bpbrm handle_backup: from client COLLECTIONSRV: TRV - object not found for file system backup: \\10.10.5.138\evsqlbkp\SQLFULL\ BPBKAR: 10:58:04.857 AM: [1136.2856] <2> tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received 10:58:05.107 AM: [1136.2856] <2> tar_backup::V_SetupFileDirectives: TAR - backup filename = \\10.10.5.138\evsqlbkp\SQLFULL\ 10:58:05.107 AM: [1136.5844] <4> tar_base::V_KeepaliveThread: INF - The Keepalive thread is active. Keepalive interval 60 Seconds 10 …. 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - ================================================================================ 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - job tracking estimate: start 10:58:07.794 AM: [1136.2856] <2> tar_base::V_vTarMsgW: TRV - object not found for file system backup: \\10.10.5.138\evsqlbkp\SQLFULL\ 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - job tracking estimate: stop 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - job tracking time: 0 secs 10:58:07.841 AM: [1136.5844] <4> tar_base::V_KeepaliveThread: INF - Keepalive Thread Terminating. Mutex:WAIT_OBJECT_0 10:58:07.841 AM: [1136.2856] <4> tar_base::V_StopKeepaliveThread: INF - The Keepalive Thread has Exited. Wait Reason:WAIT_OBJECT_0 10:58:07.841 AM: [1136.2856] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 71: none of the files in the file list exist 10:58:07.841 AM: [1136.2856] <4> tar_backup::backup_done_state: INF - ================================================================================ 10:58:09.856 AM: [1136.2856] <16> dtcp_read: TCP - failure: recv socket (460) (TCP 10053: Software caused connection abort) 10:58:09.856 AM: [1136.2856] <4> OVShutdown: INF - Finished process 10:58:09.872 AM: [1136.2856] <4> WinMain: INF - Exiting C:\Program Files\VERITAS\NetBackup\bin\bpbkar32.exe 10:58:11.872 AM: [1136.2856] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\VERITAS\NetBackup\logs\BPBKAR\040312.LOG
Mohankumar_K
4 years ago Place NetBackup
4.6KViews
0likes
7Comments
Backup Exec log files 38GB
We've had an issue with our server due to lack of free space. We've examined the contents of the drive and "C:\Program Files\Symantec\Backup Exec\Logs\" is taking up 38GB of space. Can you tell me why it would take up this much space please? More importantly how do i cap it at say 10GB? We are using Backup Exec 2010 R3 on a windows 2007 sbs server. All our backups are backup to disk folders on removable drives and we backup also backup exchange and SQL. Thanks, your help is appreciated Thanks
Solved
resolver101
6 years ago Place Backup Exec
13KViews
1like
4Comments
Enterprise Vault DataBase Migration SQL 2014 (EV 9.0.1.1073)
Dear community, We are planning to move the DATABASES of Enterprise Vault to another SQL server. Can you tell me, if the following setup is working/supported? Current architecture: SQL setup: SQL instance: SQL 2005 (9.00.4060) SQL instance collation: Latin1_General_CI_AS OS SQL Host: W2k8R2 EV setup: OS EV Host: W2k3 R2 Enterprise, SP2 SW Version: Symantec Enterprise Vault 9.0.1.1073 Destination setup: (already exists, sql cluster) OS Setup: W2k12R2 Enterprise SQL instance: SQL 2014 Enterprise SP1 CU1 (12.04416.0) SQL instance collation: Latin1_General_CI_AS Migration procecure: Looks stright forward and should not be a problem regarding database migration. All steps clear. Instructions: https://support.symantec.com/en_US/article.TECH35744.html Question: - Is the database supported within the new configuration setup? - Based on the compatibility chart, only default compatibility levels of the sql instance will be supported. What that mean in the case of EV - use the 2005 compatibiltiy mode or upgrade to naive 2014 db support. Ressources: - SQL Versions: http://sqlserverbuilds.blogspot.ch/#sql2005 - Instruction DB Move Symantec EV: https://support.symantec.com/en_US/article.TECH35744.html - Compatibilty Chart (older versions): https://symwisedownload.symantec.com/resources/sites/SYMWISE/content/live/SOLUTIONS/38000/TECH38537/en_US/compatibility_charts.pdf?__gda__=1442440249_6e76e8bedb1b71a2f0e2db07b93fc00 Many thanks, best regards, A.F.
Solved
teggra
10 years ago Place Enterprise Vault
1.4KViews
0likes
4Comments
Problem with restoring a whole server with W2k8 r2
I have a problem with Symantec Backup Exec 2012. I'm full backuping 2 of my servers which run with W2k8 r2 SP1. For testing purposes I have decided to restore machines in my Disaster Recovery site. Type of machines are the same in both locations. Restoring procedure is performed without problems. Unfortunately when I restart the machine to finish recovery process of Windows OS then appear "blue" problem: "PROCESS1_INITIALIZATION_FAILED" and system restart. Like with everything in Microsoft problem with blue screen might be various. In most of cases problem is with file Bootcat.cache or with booting procedure. I have checked both scenarios and from my point of view everything is allright. I have even delete Bootcat.cache and repair the boot. Anyway this is problem of Windows. Source of my troubles is restoring procedure in Symantec BackupExec 2012. With other OS like W2k3 there is no problems. I have tried both Simplified Recovery and standard restore on MiniOS earlier installed on server in Disaster Recovery and both finished with blue screens. All Backup Exec products are up to date. Please help.
karol_urbaniak
10 years ago Place Backup Exec
402Views
0likes
1Comment
job status - complete with exceptions
there are some backup jobs run in Backup Exec 2012 , only two full backup jobs complete with exceptions in the lastest backup task. The credential of this backup job test result was failed. we haven't change any password or credential of this job. Exceptions Details: can't open this item \\posdb1\[ROOT]/oracle/app/grid/product/11.2.0/log/posdb1/srvm/eonsd_0.log.lck - skiped. can't open this item \\posdb1\[ROOT]/var/run/iscsid.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/multipathd.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/atd.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/sm-client.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/sendmail.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/iscsiuio.pid - skiped.
Solved
zoujuan
11 years ago Place Backup Exec
2.4KViews
1like
8Comments
Enterprise Vault 10.0.4 Outlook add-in not displaying - Outlook 2013
Good afternoon, My co-worker recently installed Office 2013 64-bit on his Windows 7 (x64-bit) laptop. He installed the Outlook 10.0.4 CHF3 add-in and it is not showing up. Here is a list of troubleshooting steps that we've tried. -ResetEVClient.exe -Uninstalling/Reinstalling (running as Admin) -Checked to make sure Valkyrie.dll was in the EVClient folder and it was. -log off/log on and a reboot. I know that last year I had this issue, but I was working on so many other projects that I put it on the backburner and I remember it just showing up one day.
JKormos
11 years ago Place Enterprise Vault
2.1KViews
1like
4Comments
Backup exec vs Netbackup
i have the the folllowing setup 2 servers; the main server is on a windows platform and the remote server is running linux attached toremote server are tape drives. i need to backup a banking application T24. i had personally chosen netbackup as opposed to backup exec but because of financial constraints management is keen on backup exec. what are the advantages of using netbackup as compared to backup exec?
Solved
ITnyans
11 years ago Place NetBackup
2.2KViews
1like
3Comments
Volume Manager: Cannot import diskgroup on second node
Hello @all, hoping this is the right forum. Installing SFHA6.1 on two Solaris 10 nodes. After reinstalling our two nodes via Jumpstart server, we're facing problems with importing the diskgroups on the second node. When we reinstall the nodes, at frist we delete all diskgroups vxdg import dg vxdg destroy dg and vxdiskunsetup all disks. This procedure is well tested and works like a charm. Yesterday an update from our SAN group was made in our SAN and I don't know if the update is the reason for our problem. Today when I reinstall my two nodes I cannot vxdiskunsetup my disks: pri720[root]~ {CONSOLE}: vxdisk list DEVICE TYPE DISK GROUP STATUS disk_0 auto:ZFS - - ZFS disk_1 auto:ZFS - - ZFS emc0_0351 auto:cdsdisk - - online emc1_1fec auto:cdsdisk - - online thinrclm emc1_1fe4 auto:cdsdisk - - online thinrclm emc1_1fe8 auto:cdsdisk - - online thinrclm emc1_1ff0 auto:cdsdisk - - online thinrclm emc1_1ffc auto:cdsdisk - - online thinrclm emc1_1ff4 auto:cdsdisk - - online thinrclm emc1_1ff8 auto:cdsdisk - - online thinrclm emc1_0204 auto:cdsdisk - - online thinrclm emc1_2000 auto:cdsdisk - - online thinrclm emc1_2004 auto:cdsdisk - - online thinrclm emc1_2008 auto:cdsdisk - - online thinrclm emc2_0bf7 auto:cdsdisk - - online thinrclm emc2_22ab auto:cdsdisk - - online thinrclm emc2_22af auto:cdsdisk - - online thinrclm emc2_22a3 auto:cdsdisk - - online thinrclm emc2_22a7 auto:cdsdisk - - online thinrclm emc2_228b auto:cdsdisk - - online thinrclm emc2_228f auto:cdsdisk - - online thinrclm emc2_229b auto:cdsdisk - - online thinrclm emc2_229f auto:cdsdisk - - online thinrclm emc2_2293 auto:cdsdisk - - online thinrclm emc2_2297 auto:cdsdisk - - online thinrclm pri720[root]~ {CONSOLE}: vxdiskunsetup -C emc1_1fec VxVM vxdisk ERROR V-5-1-531 Device emc1_1fec: destroy failed: SCSI-3 PR Reservation Conflict error VxVM vxdiskunsetup ERROR V-5-2-5052 emc1_1fec: Disk destroy failed. The second point is, that all disks have status "online thinrclm", but before reinstallation only "online"! I know thinrclm is "Thin Reclamation" but don't know if this is part of our problem!!! This works: vxdisksetup -i <disk> and we can create a diskgroup vxdg init arena ARENA00=emc1_1fec vxdg -g arena adddisk ARENA01=emc1_1fe4 vxdg -g arena adddisk arena00=emc2_22ab vxdg -g arena adddisk arena01=emc2_22af which is imported on the first node. But when I deport this group on the first node and import it on the second node we got an error: pri620[root]~ {NSH}: vxdg import arena VxVM vxdg ERROR V-5-1-10978 Disk group arena: import failed: SCSI-3 PR Reservation Conflict error Honestly I'm not sure if this is a problem of our SAN or a misconfiguration of SFHA6.1! Any help would be appreciated! Regards, Heinz
Cluster_Server
11 years ago Place Storage Foundation
3.4KViews
0likes
3Comments
Should PGP really die?
I think Symantec should write an article commenting or debating this Article: http://thehackernews.com/2014/08/cryptography-expert-pgp-encryption-is_19.html Some of our customers, who have read the article, have reached us asking if PGP product line will continue or not. Not to mention prospects reading this article. The views of this expert have been translated into spanish and also reproduced in servera security portals, we would like to know, and be able to share with our clients the product roadmap, and how is Symantec planning to overcome some of the issues that the product may have. Besides changing the product name, rebranding and repackaging, what else should we expect to see in the Symantec encryption product line Juan Carlos Alvarez
juanam
11 years ago Place General Veritas
859Views
0likes
0Comments
Overwritable and Appendable media issues
I have issues with Backup Exec 2014 (clean install) on windows 2012 64 bits std. We have a weekly full backup every week and after the recyclable tape come back from the vault, I can see the tape show overwriteable and appendable. The tape status Blue bar is 95% (overwritable 1.3TB), and 5% (2GB) remain appendable. I also check the overwritable media set in the tape are all expried. On the backup exec setting -> storage _> Media overwrite protection level I have set to partial - protect only allocated media. Issues I am facing is during the weekly backup start, backup exec will backup 2GB data to appendable space on the tape and mark the tape overwrite protected instead of reuse the overwritable space. Once the tape been marked as overwrite prtected, the system will not able to write to it and ask me for new tape. Has anyone experience the same issues? What is the resolution?
Solved
Ag_BC
11 years ago Place Backup Exec
582Views
0likes
1Comment