Jairo Cetina

Error: V-79-10000-11233 - VSS Snapshot error. A Microsoft Volume Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot can run at a time.  Try running the job later. Error using NTBackup Backup Status Operation: Backup Active backup destination: File Media name: "TitanSystemState.bkf created 12/03/2010 at 06:00" Volume shadow copy creation: Attempt 1. Error returned while creating the volume shadow copy:0x80042316. Error returned while creating the volume shadow copy:80042316 Aborting Backup. Cause This warning is given typically when the Volume Shadow Copy Service (VSS) is unable to run due to another instance of VSS already running. When Backup Exec System Recovery (BESR) and Backup Exec (BE) backup conflicts. Solution BE jobs use Microsoft VSS service and BESR jobs use Symantec SymSnap VSS provider. To resolve this issue, unregister the Symantec SymSnap VSS provider and BESR will als...

Error: Unable to retrieve health data from “https://<VC servername or IP address>/converter/health.xml” in VMware vCenter Server 4.1. Note: The URL https://xx.xx.xx.xx/converter/health.xml can be accessed via an Internet browser on the vCenter Server machine. Resolution: This issue has been resolved in vCenter Server 4.1 Update 1. Workaround: To solve this issue, try using a fully qualified domain name or IP address to register vCenter Converter with vCenter Server. This may help in some cases. Alternatively, replace the thumbprint entry of Converter in the ADAM LDAP database with the vCenter Server thumbprint. To replace the Converter thumbprint with the vCenter Server thumbprint: Caution: This workaround has only been tested for configurations where vCenter Server and Converter co-exist on the same machine. Do not perform this workaround if vCenter Server and Converter are on different servers. To connect to the LDAP server running on vCenter Server: ...

There was an interesting question posted on a forum recently, asking how can you tell which sqlservr.exe process (shown in task manager) is mapped to which specific instance of SQL Server running on a server, if you have a multi-instance server and the account running each separate SQL Service is the same. I won’t go into the details of the post, but I thought the answer worth of a post of my own. As with most things in SQL Server there is more than one way to obtain this information. Hands-on: Open up SQL Configuration Manager On the SQL Services tab right click on the SQL instance that you want to match up to a process Select <Properties> and click the <Services> tab On the general tab you should see a process id property.

Use filemonitor or ProcessExplorer to diagnostic. C:\WINDOWS\setupapi.log contains information about application installation, it log file is used to trace the cause of problems should they arise after an installation of a device or drivers. Incident: In my case file C:\WINDOWS\setupapi.log is big and WINLOGON. EXE consume high CPU went users login in the server. Workaround: Open your registry editor. Go to “HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Setup\LogLevel” registry key. Set LogLevel key to 0 Restart server. More Info: http://msdn.microsoft.com/en-us/library/ff550845(v=vs.85).aspx http://support.microsoft.com/kb/958909/es

Error: Error "unable to create selection list" occurs while editing or creating a selection list associated with a backup job in Backup Exec for Windows Servers. Workaround: Open the registry editor and go to HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Server Create a new DWORD value "MaxRpcDatablockSize" and set the Hexadecimal value to "ffffffff". Restart the BE services. Check if the issue still persists. More Info: http://www.symantec.com/docs/TECH59032 http://www.symantec.com/connect/forums/selection-list-limitation

IOPS (Input/Output Operations Per Second, pronounced i-ops) is a common performance measurement used to benchmark computer storage devices like hard disk drives (HDD), solid state drives (SSD), and storage area networks (SAN). As with any benchmark, IOPS numbers published by storage device manufacturers do not guarantee real-world application performance.   IOPS can be measured with applications such as Iometer (originally developed by Intel), as well as IOzone and FIO and is primarily used with servers to find the best storage configuration.   The specific number of IOPS possible in any system configuration will vary greatly depending upon the variables the tester enters into the program, including the balance of read and write operations, the mix of sequential and random access patterns, the number of worker threads and queue depth, as well as the data block sizes. There are other factors which can also affect the IOPS results including the system setup, storage dri...

Problem: My server's CPU utilization high when my Windows virtual machine is mostly inactive. Workaround: To determine what HAL your virtual machine is using, then determine if you are running with the correct vCPU count for the HAL: Right-click the My Computer icon, and choose Properties . Click the Hardware tab. Click the Device Manager tab. Double-click the Computer icon to see which HAL is currently loaded. In the vSphere or VMware Infrastructure client, click on the virtual machine, then click the Summary tab and see how may vCPU's are configured. If you have 1 vCPU and your virtual machine operating system is configured for a Uniprocessor ACPI, your configuration is correct. If your virtual machine operating system is configured for 2 or more vCPUs and it is running with a Multiprocessor ACPI, your configuration is correct. Note : Downgrading the HAL from multiprocessor to uniprocessor is ...