BE 2012 and Data Domain w/ DDBoost
Background: So we have Backup Exec 2012 and two Data Domain DD620's. We have all the required licensing including the Data Domain DD Boost and replication licenses. I have installed the Open Storage Technology (OST) plugin 2.5.0.3 as suggested for the version of BE. Both DD boxes are visable and connected to my BE server. I have foud some documentation and a video that explains some of what I am looking for but not entirely and most of it is for BE2010. The BE 2012 documentation from DD is not up to date yet. I am trying to setup backups as my tape drive has had enough and is not working properly. Anyone I have talked to just says you backup to it, then I continue finding little things that need to be done. No verify, no precompression, some said no deduplication in the job, other said server side dedupe because DDBoost manages it with OST plugin. Too much information and not enough people knowing what to tell me. The DD weekend support guys don't know the software titles they just know the hardware. I need help now unfortunately... Question: What settings do I use for Backups? I have Active Directory, Exchange, SharePoint, and SQL agents.6.4KViews1like32CommentsCatalog error on one particular sever
Hi I'm back. After small issue to upgrade to backup exec 2012 sp1a, I have a very strange error. If I make a full backup of my virtual servers (CSV cluster), the backup to disk works just fine. But when the jobs start to make a duplication to tape, I receive an error saying 'An error was encountered writing to the on-disk catalogs'. the final error is The job failed with the following error: An error occurred while retrieving catalog information I found this article http://www.symantec.com/business/support/index?page=content&id=TECH53393 but it was no solution. The error is only generated on a particular server.5.3KViews1like10CommentsV-79-57344-794 - Error: Unable to query the Team database meta-data. Sharepoint2007 BE2012
This is driving me nuts, Envirement: Sharepoint 2007 on Win2k3 SP2 (workgroup and not on the domain) BE2012 on Win2k8 R2 Hello peeps, I hope i will find a life saver here, our two sharepoint server are standalons and when trying to back up their databases i'm getting this wired errors. Backup- Shared Search Index\Search-DB 1 (SPServer\OFFICESERVERS\SharedServices1_Search_DB_d696b2ed-0af1-423c-95e1-50625736b8ec) V-79-57344-794 - Error: Unable to query the Team database meta-data. Backup- SharedServices1\Services-DB 1 (SPServer\OFFICESERVERS\SharedServices1_DB_c7706c2f-cecb-4ca4-95e9-7862636c19cf) V-79-57344-794 - Error: Unable to query the Team database meta-data. Permissions are correct and agent installed localy (Tried to run the job with the local admin account or the Service account but no luck) backing up the jobs using the Microsoft Sharepoint Ressources as it has been advised on this forum and not using the MS SQL Server Instance. Appreciate your help guysSolved3.9KViews0likes16CommentsSharePoint backup on SBS 2011
We are a small business with a single SBS 2011 Standard server using Backup Exec 2012 Small Business Edition to backup onto RDX cartridges. I'm not particularly familiar with Backup Exec or SharePoint but hopefully the following questions make sense. Earlier this week we installed Hotfix 189571 and Hotfix 180964. Since then we started getting the following exception: Backup- \\[domain].local\C:V-79-57344-33925 - Error: SharePoint_AdminContent_deed[...].mdf is a component of a SharePoint server farm. It must be backed up using the Backup Exec Agent for Microsoft SharePoint Portal Server. Select it for backup from the Microsoft Server SharePoint Server Farms node. The same exceptions are also reported for the following files: SharePoint_AdminContent_deed[...]_log.LDF, SharePoint_ConfigurationDatabase.mdf, SharePoint_ConfigurationDatabase_log.LDF, ShareWebDb.mdf, ShareWebDb_log.LDF, WSS_Search_[server].mdf, and WSS_Search_[server]_log.LDF. We don't appear to have a "Microsoft Server SharePoint Server Farms" node that I can see, only "Microsoft SharePoint Resources" (and the exceptions occur regardless of whether that is selected or not). According to the Backup Exec License Informaton window we have "Agent for Microsoft SharePoint" but there is no mention of "Agent for Microsoft SharePoint Portal Server" are they two different things? According to the following technote: http://www.symantec.com/business/support/index?page=content&id=TECH51230 "In order to completely protect the SBS Sharepoint environment, a license for the Backup Exec Sharepoint agent must be purchased and implemented." That technote appears to be referring to an older version of Backup Exec but as mentioned previously our License Information window says we do have "Agent for Microsoft SharePoint" (we didn't purchase it separately, it must be part of Backup Exec 2012 Small Business Edition). Does this mean that Backup Exec 2012 Small Business Edition doesn't back up the version of Sharepoint that comes with SBS 2011 Standard? In order to allow the backups to complete without exception I followed the workaround in TECH51230, it mentions renaming bedssps2.dll but in our install there is also a bedssps3.dll. I renamed both, is that correct for Backup Exec 2012? We don't use SharePoint at the moment so my main concern is whether the issues above and the workaround would affect Simplified Disaster Recovery. The following technote gives separate instructions for restoring SharePoint: http://www.symantec.com/business/support/index?page=content&id=TECH179341 What would happen in our situation since we do not have specific SharePoint backup? Would the backup of C: and of the SHAREPOINT database suffice to get the server fully operational after a disaster recovery? Thanks.3.4KViews0likes18CommentsNetbackup, Sharepoint 2007 Cross farm restore - lab enviroment creator
I have to make restore of one SharePoint 2007 farm to another farm which will be used for lab and developing purposes, so both farm have to work in same time but with different names. GRT full and Full Non-GRT backup complete successfully without any warning. I’ve read checklist from article TECH148598, and clarify all settings. http://www.symantec.com/business/support/index?page=content&id=TECH148598 Restore process doesn’t start when I try to restore of SharePoint Web application as is advised in article HOWTO47543. I can restore without problems files from GRT backup. http://www.symantec.com/business/support/index?page=content&id=HOWTO47543 I’m just not sure how to configure properly Distributed Application Restore Mapping settings. In “NBU for SharePoint admin guide” there are not any examples. All backup goes to disk. NBU server is Netbackup 7.1 onto Windows Server 2008 R2. Production and lab frontend servers are SharePoint 2007 running onto Windows Server 2008 SP2 / 64 bits. SQL server is cluster, SQL 2008. I have following server configuration: Production SharePoint Farm: Intranet – Virtual name of NLB frontend SPSNode1 – Sharepoint frontend SPSNode2 - Sharepoint frontend ProdSQL – SQL cluster virtual name, backend in SharePoint config SQLnode1 – first node in SQL cluster SQLnode2 - second node in SQL cluster Lab SharePoint Farm: TESTintranet - Virtual name of NLB frontend TESTnode1 – frontend TESTnode2 – frontend TESTsql – SQL server, backend in SharePoint config Do you have any idea how to configure Distributed Application Restore Mapping? Any other ideas are welcome. I've just opena case let see who will be helpfull community or Tech Support :)Solved2.2KViews0likes15CommentsBackupExec 2012 Small Business Edition nightmare!!
We have a single SBS2003 server that we have been backing up to an external drive for over 2 years without any issues. Last month, as suggested by Symantec Support, upgraded to BackupExec 2012; my nightmare started at that moment. Called Symantec Support (3 weeks back) and they tried various settings just to get me off their backs. Now 3 weeks later, I am still without a good backup set. File system I am backing up manually to another disk just in case. The messages on Mailboxes are cached on workstations so no immediate threat. Of course, it is not going to be fun in the server misbehaves (touch wood). The backup error suggests that the agent of AD, Exchange, SQL serverand SharePoint farms are missing hence cannot backup any of those. Yesterday I realized, reading through one of the support cases that they should be included which the tech support at times says yes and many other times they suggest that I should purchase the license seperately. Some of them sounds clueless. I verified the license key they sent me as part of the upgrade to 2012, that is indeed a BackupExec Small Business Edition 2012. Could someone in the community help this poor soul who is walking thin-line with this issue. Any assistance or guidance will be highly appreciated. - JojuSolved2.1KViews0likes11Commentsslow sharepoint backup
Hello I have an issue with a Sharepoint GRT backup with NBU 7.6.1.2. The architecture is the following : - Sharepoint 2010, 2 Front web servers, 2 application servers, 1 Clustered SQL Server - all servers are virtual machines - Service account used for legacy Network, legacy client and client services is domain admin + local admin and has the required 4 rights in local security policy - DNS is OK (hosts has been also updated with short and long names - just in case) - non-GRT backup is runing fine - GRT backup is starting well, but after "some time" is slowing down ... - I have enabled verbose loging on SQL server and the following messages appear in bpkar log file : 21:54:06.290 [1708.7048] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 21:54:06.290 [1708.7048] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 21:54:06.290 [1708.7048] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 21:54:06.290 [1708.7048] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 21:54:06.290 [1708.7048] <8> vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1544] in failed cache ERR=10109 NAME=SVBLL-WI05Q SVC=bpspsserver 21:54:06.290 [1708.7048] <8> vnet_cached_getaddrinfo: [vnet_addrinfo.c:1267] vnet_cached_getaddrinfo_and_update() failed 6 0x6 21:54:06.290 [1708.7048] <8> init_remote_connect_recs: [vnet_connect.c:949] vnet_cached_getaddrinfo() failed, status=6, OS ret=10109, host=SVBLL-WI05Q, service=bpspsserver 21:54:06.290 [1708.7048] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 0 0x0 21:54:06.290 [1708.7048] <8> init_connect_recs: [vnet_connect.c:868] init_remote_connect_recs() failed 6 0x6 21:54:06.290 [1708.7048] <2> init_connect_recs: [vnet_connect.c:880] Ignoring some failures. Success count 2 0x2 21:54:06.290 [1708.7048] <2> async_connect: [vnet_connect.c:1499] connect in progress 1 0x1 21:54:06.304 [1708.7048] <2> vnet_pbxConnect: pbxConnectEx Succeeded 21:54:15.974 [1708.7048] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:1995] VN_REQUEST_SERVICE_SOCKET 6 0x6 21:54:15.974 [1708.7048] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2009] service bpspsserver 21:54:16.484 [1708.7048] <2> do_pbx_service: [vnet_connect.c:2159] via PBX/via VNETD bpspsserver CONNECT FROM 10.225.64.101.64646 TO 10.225.64.106.1556 fd = 1280 21:54:16.485 [1708.7048] <2> async_connect: [vnet_connect.c:1691] connect async CONNECT FROM 10.225.64.101.64646 TO 10.225.64.106.1556 fd = 1280 21:54:16.485 [1708.7048] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO SVBLL-WI05Q 10.225.64.106 bpspsserver VIA pbx 21:54:16.485 [1708-7048] vnetdSendRequest Sending message 0xf331 21:54:16.485 [1708-7048] vnetdProcessMessage received a reply successfully for message 0xf331 21:54:20.175 [1708.7072] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 21:54:20.175 [1708.7072] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 21:54:20.175 [1708.7072] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 21:54:20.175 [1708.7072] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 21:54:20.176 [1708.7072] <8> vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1544] in failed cache ERR=10109 NAME=SVBLL-WI05Q SVC=bpspsserver 21:54:20.176 [1708.7072] <8> vnet_cached_getaddrinfo: [vnet_addrinfo.c:1267] vnet_cached_getaddrinfo_and_update() failed 6 0x6 21:54:20.176 [1708.7072] <8> init_remote_connect_recs: [vnet_connect.c:949] vnet_cached_getaddrinfo() failed, status=6, OS ret=10109, host=SVBLL-WI05Q, service=bpspsserver 21:54:20.176 [1708.7072] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 0 0x0 21:54:20.176 [1708.7072] <8> init_connect_recs: [vnet_connect.c:868] init_remote_connect_recs() failed 6 0x6 21:54:20.176 [1708.7072] <2> init_connect_recs: [vnet_connect.c:880] Ignoring some failures. Success count 2 0x2 21:54:20.176 [1708.7072] <2> async_connect: [vnet_connect.c:1499] connect in progress 1 0x1 21:54:20.190 [1708.7072] <2> vnet_pbxConnect: pbxConnectEx Succeeded 21:54:24.119 [1708.7072] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:1995] VN_REQUEST_SERVICE_SOCKET 6 0x6 21:54:24.119 [1708.7072] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2009] service bpspsserver 21:54:24.725 [1708.7072] <2> do_pbx_service: [vnet_connect.c:2159] via PBX/via VNETD bpspsserver CONNECT FROM 10.225.64.101.64653 TO 10.225.64.106.1556 fd = 1280 21:54:24.725 [1708.7072] <2> async_connect: [vnet_connect.c:1691] connect async CONNECT FROM 10.225.64.101.64653 TO 10.225.64.106.1556 fd = 1280 21:54:24.725 [1708.7072] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO SVBLL-WI05Q 10.225.64.106 bpspsserver VIA pbx 21:54:24.726 [1708-7072] vnetdSendRequest Sending message 0xf331 21:54:24.726 [1708-7072] vnetdProcessMessage received a reply successfully for message 0xf331 I am worried (but maybe i am wrong) byvnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1544] in failed cache ERR=10109 NAME=SVBLL-WI05Q SVBLL-W05Q is the front web server used as client in the NBU policy. Thanks in advance for any clue/help Best regards2KViews1like11CommentsDoes More than one Techn work at Symantec?????
1. NO ONE IS ANSWERING THE PHONE ANYWHERE AT SYMANTEC 2. YOUR PHONE SYSTEM IS REPORTING 1 MIN THEN OVER AN HOUR 3. I WAS ON HOLD OVER TWO HOURS 4. I HAVE ANOTHER ISSUE WITH BACKUP EXEC 5. EVEN YOUR SYMANTEC OPERATORS CANT GET THROUGH TO SUPPORT 6. MY ONLINE SUPPORT IS IN AN ORIENTAL LANGUAGE 7. YOUR ONLINE CHAT SUPPORT DOESNT WORK. NOONE IS THERE EITHER I've been on hold all morning. Don't listen to "The Customer Hold the Longest. is X min. It goes up and down and noone ever answers.2KViews2likes7CommentsBackup to Disk Issue for SharePoint 2007
Recently added licenses for backup of MOSS (2007)Farm to our BE2010 solution. We have one volume for B2D (14TB)and it is configuredfor dedupe.All B2D jobs are Full Backups and then Duplicate to Tape, point to the same Media Sets andrun fine except for MOSS. The job fails with a security error(see below)every time on the same SiteContent and causes the whole job to report as "Failed" even though it appears that the data is there. The account used tobackup the Farmcan login to all site content.The error for the SiteContent is "Error: e0008445 - The media operation was terminated by the user.". The jobhistory showsError CodeE0001602. There is a Duplicate job associated to thed2djob and it subsequently failsevery time (approx. 50-60MBdata copied)with the following error "Final error: 0xe00084e4 - The DC2000 cartridge has was formatted with an unrecognized format. Final error category: Backup Media Errors (jobhistory shows Error CodeE00084E4).Iassume that the Duplicate job fails because it sees that there was a media error withthe parent job. We followed the best practices guide when setting up the job and I cannot see why it would be failing.The job log makes it look like the issue is related to the B2D media set. Perhaps I need to setup a different media set for MOSS? The settings are pretty generic so I cannot see a reason for failure. This is a new solution for us... aDell PowerVault DLBackup to Disk DL2200 with an iSCSI attached MD1200 with 12 2TB drives (RAID5)so we may have something misconfigured. Thanks in advance for any help. Job name : SharePoint Farm1-SharePoint-Full Backup Job type : Backup Job status : Failed Job log : C:\Program Files\Symantec\Backup Exec\Data\BEX_IUBEXEC01_00084.xml Server name : IUBEXEC01 Selection list name : SharePoint Device name : B2D - Dedupe:6 Target name : B2D - Dedupe Media set name : Daily Media Set 1 All Media Used OST00000038-467AB5B0E2F9FE78 Error category : Security Errors Error : e0001602 - Access is denied (Share point backup). For additional information regarding this error refer to link V-79-57344-5634 AOFO: Started for resource: "Board Site\Content-DB 1 (Server1\BoardMemberSiteContent)". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). The following volumes are dependent on resource: "E:" . The snapshot provider used by VSS for volume E: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Set Information -Board Site\Content-DB 1 (Server1\BoardMemberSiteContent) Backup Set Information Family Name: "Media created 3/4/2011 6:00:02 PM" Backup of "Board Site\Content-DB 1 (Server1\BoardMemberSiteContent)" Backup set #1 on storage media #1 Backup set description: "Daily full backup of SharePoint" Backup Method: Full - Back up entire database The option to enable the restore of individual items from the database backup was selected for this backup. Backup started on 3/4/2011 at 6:25:43 PM. Backup Set Detail Information Media Label: IMG000145 GRT backup set folder: \\.pdvfs\BEXEC01\2\BEData\IMG000145 This operation is being coordinated through the server: Server0 Backup completed on 3/4/2011 at 6:28:01 PM. Backup Set Summary Processed 52,316,452 bytes in 2 minutes and 18 seconds. Throughput rate: 21.7 MB/min Compression Type: None This backup set may not contain any data.Solved2KViews0likes18Comments