VMWare Backups with File Level Restore on 7.5.0.1
Having found out that we cannot exclude the data disks whilst using dynamic disks (see my previous post on the subject) I thought that I would backup the whole server and look at the file level restore for this particular server; however, I have stumbled across another issue............. The server has two disks, C drive is 60Gb and D drive is 100Gb both are set as dynamic disks, on top of this we are using the built in windows disk management system to mirror the D drive, the backup is set as a VMWare backup in the policy and all the default options are set in the advanced section so all disks are covered, the backup completes and I can restore 3 vmdk files but cannot do any individual file restores, we have tried breaking the mirror and re-running the backup but we get the same results. Having read the VMWare Admin Guide this does mention that using raid software on Linux will result in not being able to restore individual files, is this the same for Windows??? Have Symantec got any plans to change the VM backups to do what Veeam can do as at the moment it looks like our plan to remove Veeam from the estate will have to be put on hold until Netbackup can do the same as Veeam in relation to backup/restore. KevSolved583Views15likes1CommentCross restore problme. cannot write data to socket, 10054
Hi again. So, I am trying to do a cross restore, but keep getting this error message. I have tried a bunch of things, yet nothing seems to work. Server: Windows 2008 R2, Netbackup 7.1.0.4 Source client: windows 2003, netbackup 7.1.0.4 client. Physical server. Destination client: Windows 2008 R2, Netbackup 7.1.0.4. Virtual server, with VMware. Has a 1tb lun assigned. This is a file server I am trying to virtualize, so I want to move all my data from the source to the destination. I tried restoring files from the source to the source, and the destination, to the destination. No problem there. But each time I try to go from Source to Destination, I keep getting the same error: 22/08/2012 05:26:46 p.m. - begin Restore 22/08/2012 05:28:45 p.m. - 1 images required 22/08/2012 05:28:45 p.m. - media HPZ950 required 22/08/2012 05:28:45 p.m. - media HPZ963 required 22/08/2012 05:28:48 p.m. - restoring image kamino_1345355900 22/08/2012 05:28:49 p.m. - Info bpbrm(pid=7872) korasa is the host to restore to 22/08/2012 05:28:51 p.m. - Info bpbrm(pid=7872) telling media manager to start restore on client 22/08/2012 05:28:53 p.m. - Info bptm(pid=5528) Waiting for mount of media id HPZ950 (copy 1) on server myarsw00403bk01. 22/08/2012 05:28:53 p.m. - started process bptm (5528) 22/08/2012 05:28:53 p.m. - mounting HPZ950 22/08/2012 05:28:53 p.m. - Info bptm(pid=5528) INF - Waiting for mount of media id HPZ950 on server myarsw00403bk01 for reading. 22/08/2012 05:28:53 p.m. - requesting resource HPZ950 22/08/2012 05:28:53 p.m. - granted resource HPZ950 22/08/2012 05:28:53 p.m. - granted resource HP.ULTRIUM4-SCSI.000 22/08/2012 05:28:54 p.m. - Info bpbrm(pid=7120) korasa is the host to restore to 22/08/2012 05:28:56 p.m. - connecting 22/08/2012 05:28:57 p.m. - Info bpbrm(pid=7120) start tar32 on client 22/08/2012 05:28:59 p.m. - Info tar32(pid=3644) Restore started. 22/08/2012 05:28:59 p.m. - connected; connect time: 00:00:03 22/08/2012 05:29:33 p.m. - mounted; mount time: 00:00:40 22/08/2012 05:29:33 p.m. - Info bptm(pid=5528) HPZ950 22/08/2012 05:29:34 p.m. - Info bptm(pid=5528) INF - Waiting for positioning of media id HPZ950 on server myarsw00403bk01 for reading. 22/08/2012 05:29:34 p.m. - positioning HPZ950 to file 81 22/08/2012 05:30:50 p.m. - positioned HPZ950; position time: 00:01:16 22/08/2012 05:30:52 p.m. - begin reading 22/08/2012 05:30:53 p.m. - Error bptm(pid=5516) cannot write data to socket, 10054 22/08/2012 05:30:53 p.m. - Info bpbrm(pid=7872) child done, status 13 22/08/2012 05:30:53 p.m. - Info bpbrm(pid=7872) sending message to media manager: STOP RESTORE kamino_1345355900 22/08/2012 05:30:53 p.m. - Error bptm(pid=5516) The following files/folders were not restored: ********************** a bunch of files ****************** 22/08/2012 05:30:53 p.m. - Error bptm(pid=5516) more than 10 files were not restored, remaining ones are shown in the progress log. 22/08/2012 05:32:56 p.m. - Warning bprd(pid=5896) Restore must be resumed prior to first image expiration on 19/09/2012 02:58:20 a.m. 22/08/2012 05:32:56 p.m. - end Restore; elapsed time: 00:06:10 socket write failed(24) 22/08/2012 05:32:56 p.m. - Info bpbrm(pid=7872) media manager for backup id kamino_1345355900 exited with status 150: termination requested by administrator **************************************************************** So now I am stuck, tried opening the firewall, putting everything in the host file, tried bptestbpcd, bpclntcmd, bpcoverage, bpgetconfig, and I can see every single thing, yet, I can not do a restore. The backups work ok. What might I have missed? Please assist. Thanks.2.7KViews7likes8CommentsRecently upgraded to 7.5 and now the VM browsing doesn't work?
I have windows 2008 R2 x64 Master and an MSDP server which acts as a backup host. I recently upgraded them to 7.5 and since then the browse feature didn't work. If you have a large VMware environment then you have likely enable the registry key "DisableIPResolution" - http://www.symantec.com/business/support/index?page=content&id=TECH128037 The upgrade appears to now require that this registry key to be a "DWORD (32-bit) Value" with the data value of 1 INSTEAD of a string value. If you don't change this then you will likely see the following error in the bpVMutil log: 11:48:13.485 [4520.5008] checkBackupRegEntry: searching configuration for disableIPResolution 11:48:13.485 [4520.5008] get_integer_value failed 11:48:13.485 [4520.5008] checkBackupRegEntry: searching configuration for UseNicIpaddress 11:48:13.485 [4520.5008] get_integer_value failed Hope this helps those that upgrade to 7.5 and face this issue Cheers555Views6likes2CommentsFailed to backup in query mode when one of your Vcenter is down
Hi everyone, First, i'm sorry for my English :) With my team, we found a problem with the query mode when one of your Vcenter is not accessible in 7.6.0.3 The QUERY request will try to connect to all vcenter by default to check his request. At this time, if one of Vcenter added in credential is not accessible, the query will fail with status 4234 (VMware server login failure) even if the Vcenter whereby the QUERY must go is UP. Of course you can delete in credential the Vcenter who are down. But a option is more effective i think in Vmware policy. In this policy, go to Vmware Tab --> Advanced --> Vmware server list Then add the Vcenter who must be used by the QUERY. With this action, the QUERY request will inspect only this vcenter and not all Vcenter added in credential. More information about Netabckup infra : NBU Verison :7.6.0.3 Master/MDSP : Windows 2008 R2 SP1 Standard. I'm not sure if this action is a bug or not but i think is dangerous to check all vcenter when just one is needed. Previously, in 7.5.x, the job parent was in partially successful and not in failed. Regards, Johan4KViews5likes5CommentsNetbackup Solaris Media Server to 5230 Appliance Migration
Environment : Solrais 10 Master Server with 7.6.0.1 version and 7.5.0.6 Media servers with Solaris 10. Clarification Needed As we are going to migrate our Physical master server to Virtual master server with the same name ( Catalog Migration) And Going to decommission our solaris media servers to Netbackup 5230 appliance . My Concern here is after catalog migration to new server (virtual master) am going to decommision the Media servers used in old master. Will it effects me in new infra for restores using old disk pools with new appliance and how it works. Or while decommission my old disk pools will also be get deleted ..?Solved2.8KViews4likes5CommentsNBU 5220 Performance
We recently deployed a 5220 appliance into our environment as it was to be the savior in our battle against a backup window we were no longer able to meet. When we finally got it online and into our NBU environment the initial performance was great. The area we were to most benefit was with VMware backups. The data stores mounted directly to the appliance would allow direct access to the snapshots for a fast and efficient backup. Before this, we were performing client side backups so the impact on the hosts every night was significant as we tried backing up 600+ vms. The plan was to be able to move all Dev and test off-host backups to the middle of the day as the performance impact was minimal and the end result was an increased window to complete things. As we started with noon-time backups deduplication rates were high and so were the speeds. However, this performance gain was short lived, as we began increasing the load we suddenly saw performance drop to a point of concern. Backups were no longer speedy, 3500KB per second to 10,000KB. There are some that might pop to 24,000KB, but in a sample size of 15 as I write this, only one is showing 24,000. Now, I do have a few ideas. 1. We have a 72TB appliance, therefore, 2 disk trays, during the backups, the one disk tray is going crazy, all the lights are flashing and you can really see that it is working. However, the second tray is doing nothing. While you might see a blink here or there, it is almost nothing compared to the other disk tray. Is this to be expected? When we looked at the disk configuration, it shows concat, is this normal? 2. Too much data at once and we are simply burying the appliance. In reality, what sort of performance should I be able to expect from the appliance? 3. Relating to number 2, since we only have the one appliance right now while we wait to get the remote appliance in place, we are duping off to tape. This is running at the same time as a backup, so this means at the same time the appliance is writing a lot of data, it is also reading it back to tape. 4. We are overloading the data store so that read speed is bad from source to destination. We have fewer hosts,therefore, if we limit the jobs per host we limit the number of machines backing up at once (obviously). This means that backups take way long, so we removed the limit per host and just set a limit per data store. As we are new to it all, I am not sure what impact where, but again, I am trying to list any and all ideas from the start. 5. The appliance does not support multi-pathing, therefore, we only have a single path to the disk. Beyond that I am not sure, but this is something that doesnt help with the showcasing of the appliances to management at the moment. However, given the initial performance I am confident we can get back there.Solved3.2KViews4likes50Comments