NIC Teaming Slow Throughput, any ideas?
Hey guys, We currently have 2Gig set up through NIC teaming for our backup exec setup.When we have backups running, it barely reaches 35-40% of the bandwith. I am using Backup Exec 2010. Has anyone else here set up NIC teaming before? What are some things that might cause slow performance? Are there any specific settings in Backup Exec that may help? Thanks!
SSR 2013 SRD Fails Boot on system with PERC H310 Raid Controller
I'm running SSR 2013 on a Dell 64 bit Precision T3600 independent workstation with a Xeon ES-1650.0 CPU, 16 GB of RAM and containing a PERC H310 Raid adapter that controlls two 1 TB HDs currently running as independant C: and D: drives (i.e., in non-RAID configuration). 2013 succdessfully backs up the C: (boot) drive to D: in weekly sets with offsite copy. However, attempting to restore C: from image using the 2013 SRD runs into an immediate probllem. When attempting to boot from the CD/DVD drive (preceded by the H310 boot from bios), even before the Windows logo appears, I get a blue screen stating: "Your PC needs to be repaired. There isn't enough memory available to create a ramdisk device. Error Code 0xC00000017." Attempting to use Lights Out produces the same result.. I attempted to customize the SRD with the H310 driver (percsas2.sys), but the SRD Wizard would not accept the .sys file. So I have two questions: 1. Could the problem be caused by something other than the H310? 2. If the probllem is the H310 controller (none of my other systems without controllers have SRD recovery problems), is there a fix short of removing the H310? -- Jim
Issues With Symantec Recovery Disk
Hi, I'm having serious problems with the symantec recovery disk. We are using Symantec System Recovery R2 Management Solution. PRevious to the R2 upgrade restores were tested using the downloaded recovery disk and everything worked fine now however I cant seem to get a test restore working. I'm trying to a test restore on a Dell Poweredge 2850 which is running Server 2008 R2. I've created so many recovery disks I'm going insane. The first issue I experienced was that the 64bit recovery disk would not boot this server after testing this disk on other servers I logged a call with Symantec who got me to test the disk on a PC and it worked... So I tried the 32bit disk and it boots properly andf I am able to get to the recovery utility. So now the main issue I am experiencing is that when I try to do the restore the target drive is always coming us as Invalid. At first I assumed thta this was because I had created the recovery disk on our management solution server which is a VM so the disk didnt contain the relevant drivers for the server so I went to the server and tried to edit the ISO, but because the server is running a 64 bit OS I cant edit the 32bit recovery disk ISO... I tried editing the 64bit ISO, but that still wont boot. So next I installed a full version of Symantec system recovery on a Windows 8.1 PC with a different license meaning I didnt have to create the recover disk through the management solution. Once again only the 32bit disk would boot the server and once again the target drive location comes up as invalid when I try to do the restore. This time I ran the driver validation tool on the server and it came back as all drivers installed, but I still cant do a restore. I still cant edit the iso because its a 64 bit server and 32bit ISO. I've tried adding in the perc 4 raid driver once in the restore environment and that doesnt work. So now I'm stuck, I cant work out if the problem is driver related, or because the server is built using MBR, but the restore file location is saved on a volume that is GPT.Does 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.
the same GUID on two computers
I have two computers with the same GUID in Altiris Agent. So I deleted them from SSR-MS, then reset Guid (AeXAgentUtil.exe /resetguid), and then restart agent. But when I checked them it had again the same new GUID. So I've found on Altiris KB some script: 'vbscript Change GUID then force client to update configuratin and send basic inventory Dim WshShell Set WshShell = WScript.CreateObject("WScript.Shell" ) Dim TypeLib, sNewGuid Set TypeLib = CreateObject("Scriptlet.TypeLib" ) sNewGUID = TypeLib.Guid Set TypeLib = Nothing sNewGuid = left(sNewGUID, len(sNewGUID)-2) ' wscript.echo " # Guid Generated " + sNewGuid WshShell.RegWrite "HKLM\Software\Altiris\Altiris Agent\MachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Altiris\Client Service\NSMachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Altiris\eXpress\MachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Altiris\eXpress\NS Client\MachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Computing Edge\Notification Server\MachineGuid" ,sNewGuid, "REG_SZ" Dim client Set client=WScript.CreateObject ("Altiris.AeXNSClient" ) ignoreBlockouts=1 sendIfUnchanged = 1 client.SendBasicInventory sendIfUnchanged, ignoreBlockouts client.UpdatePolicies ignoreBlockouts Probably it works well/better. Now in Resource Manager I see both computers. But when I click "Symantec System Recovery Details" in SSR-MS I have information that "The Symantec System Recovery configuration data is not available" What to do with this?
Error V-123-49 Operation failed(Status 114) when retrieve a point in time configuration
hi everyone i have a problem with win client restore A error occured when i bmr restore a win client Error V-123-49 Operation failed(Status 114) Here is my context: NBU Master server 7.5 (Suse 11 sp1_x64) NBU client 7.5 (win2008 standard x64) BMR backup client ok bmrd log ------------------------------------------------------- 11/25/13 18:04:57.079 [winStreamHeader.cpp:removeWinStreamHeader()] Found BACKUP_DATA, seek to 101991869142093903 11/25/13 18:04:57.081 [winStreamHeader.cpp:removeWinStreamHeader()] Exiting, line=144, return BMR_SUCCESS 11/25/13 18:04:57.128 [bmrdcommonunix.cpp:PlatformForkCommon()] Entering, newsockfd=17 11/25/13 18:04:57.129 [bmrdcommonunix.cpp:PlatformForkCommon()] Exiting, line=84, return pid=29445 11/25/13 18:04:57.129 [bmrdcommonunix.cpp:PlatformForkCommon()] Exiting, line=84, return pid=0 11/25/13 18:04:57.129 [bmrd.cpp:HandleThisConnection()] entering 11/25/13 18:04:57.129 [bmrd.cpp:HandleThisConnection()] call_fd=17 11/25/13 18:04:57.130 [bmrdcommon.cpp:DoVxssAuthentication()] Entering, line=45, fd=17 11/25/13 18:04:57.131 [bmrdcommon.cpp:DoVxssAuthentication()] Exiting, line=106, return rc=0 11/25/13 18:04:57.170 [bmrdcommon.cpp:AssertCompat()] entering 11/25/13 18:04:57.170 [bmrdcommon.cpp:AssertCompat()] fd=17 11/25/13 18:04:57.170 [bmrdcommon.cpp:AssertCompat()] exiting 11/25/13 18:04:57.170 [bmrd.cpp:HandleImportRequest()] entering 11/25/13 18:04:57.170 [bmrd.cpp:HandleImportRequest()] call_fd=17 11/25/13 18:04:57.187 V-128-906 [ImportCfg.cpp:ImportConfig()] Unable to extract either ./bmrcli.xml or bmrcli.xml file from bundle. Cannot import. 11/25/13 18:04:57.188 [bmrd.cpp:HandleImportRequest()] exiting 11/25/13 18:04:57.188 [bmrd.cpp:HandleThisConnection()] exiting 11/25/13 18:04:57.188 [bmrd.cpp:RetrieveClientConfiguration()] Unable to import configuration from bundle file /usr/openv/netbackup/baremetal/server/data/nc-128.1.100.154.bundle.dat. 11/25/13 18:04:57.188 [bmrd.cpp:RetrieveClientConfiguration()] Exiting, line=2323, return BMR_FAIL 11/25/13 18:04:57.190 [bmrd.cpp:HandleMethodExecute()] exiting 11/25/13 18:04:57.190 [bmrd.cpp:HandleThisConnection()] exiting 11/25/13 18:05:21.141 [logChanges.cpp:LogChangesCheck()] Config file change detected, reloading log objects. 11/25/13 18:05:21.145 [logChanges.cpp:LogChangesCheck()] Config file change detected, reloading log objects.
