Microsoft SQL 2005 backup / replace script

USE database;

BACKUP DATABASE database

TO DISK = ‘Y:\MSSQL_copy\database.Bak’

WITH FORMAT,

MEDIANAME = ‘databasebackup’,

NAME = ‘Full Backup off database’;

RESTORE FILELISTONLY

FROM DISK = ‘Y:\MSSQL_copy\database.Bak’

esx console problem, can not connect

– ssh to your ESX box
– add the following to /etc/vmware/config:

vmauthd.server.alwaysProxy=TRUE

Changing ESX Service Console memory

During default ESX installation, Service Console will be allocated 272MB of memory. Most of time, it is sufficient. However, if you have third party software installed in Service Console, or you have a powerful server (like Sun Fire x4600, with 8 Dual core CPU, 64GB memory) that can support more than 50 vCPUs, I strongly suggest to change the Service Console memory to 512MB. In ESX 2.x, VMware suggested 512MB should be used to support more than 32 vCPUs. Since ESX 3.x has a much more effect method to manage its memory, it runs 50 to 60 vCPUs without any problems with 512MB. If you have other third party software in the Service Console, you might want to increase to more than 512MB.

Microsoft SQL 2005 backup / replace script

Microsoft SQL 2005 backup / replace script

esx console problem, can not connect

Changing ESX Service Console memory

Categories