vmware esx 2 2.1 tape backup... · as a backup administrator, you should be aware of best practices...

Dell VMware ESX Server 2.1 Software Backup and Recovery

Guide

Version 1.0

Dell Enterprise Systems Group May 2004

Notes, Notices, and Cautions

NOTE: A NOTE indicates important information that helps you make better use of this product.

NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

CAUTION: A CAUTION indicates a potential for property damage, personal injury, or death.


Introduction .................................................................................................................................................. 4

1. Understanding Dell Backup Configurations..................................................................................... 5

2. Understanding Backup Components................................................................................................. 6

3. Backup Planning ................................................................................................................................. 7

4. Backup Server Installation................................................................................................................. 7

5. Backup Agent Solutions ..................................................................................................................... 8 5.1 Backup Agent in Service Console ................................................................................................... 8

5.1.1 Pre-Backup............................................................................................................................... 8 5.1.2 Backing up a VM after Shutdown............................................................................................ 9 5.1.3 Backing up a Running VM....................................................................................................... 9 5.1.4 Disaster Recovery of each VM .............................................................................................. 11 5.1.5 Backing up the Service Console............................................................................................. 11 5.1.6 Disaster Recovery of the Service Console ............................................................................. 11

5.2 Backup Agents in VMs.................................................................................................................. 11 5.2.1 Pre-Backup............................................................................................................................. 11 5.2.2 VM Agents for Backup .......................................................................................................... 12 5.2.3 VM Agents for Restore .......................................................................................................... 12 5.2.4 Granular Restore or Repair .................................................................................................... 12

6. Appendix A: Installing VMware Tools - VMXNET in the Guest OS .......................................... 13 6.1 Installing VMXNET in Linux Guest OS:....................................................................................... 13 6.2 Installing VMXNET in Windows 2003 or Windows 2000 Guest OS............................................. 14

7. Appendix B: Sample script to avoid the staging area on Service Console. .................................. 15

8. Appendix C: Additional Resources ................................................................................................. 15 8.1 Additional Web Information ......................................................................................................... 15 8.2 Technical Support Resources ....................................................................................................... 16 8.3 Newsgroups .................................................................................................................................. 16


Introduction This paper overviews best practices for IT and backup administrators in backing up and restoring VMware ESX 2.1 Virtual machines (VMs) and host Service Console on Dell™ PowerEdge™ 6650 Server to a PowerEdge 1750 Network Attached Backup Server (NABS). VMware® ESX Server® provides the rapid creation of multiple virtual machines (VMs) on a single physical server, as shown in Figure 1. These VMs each run in a resource-isolated, secure environment and include an operating system (OS) with their associated applications. ESX Server has a virtualization layer that allocates virtualized Dell resources to VMs and a Service Console, accessible for remote management.

Figure 1 - ESX Server Architecture

Virtual Machine data has the same operational maintenance as physical machine data, including backup and recovery. IT and backup administrators require:

• Ease of use for novices, yet flexible to protect large and complex data centers with comprehensive backup and granular recovery

• Cost effective data protection solution that can back up more data, with less hardware, in less time

• Scalable enough to grow form a single server into multi-server storage The primary question in selecting a backup recovery plan is “What do you need to recover from?” Data analysts identify three major types of failure and recovery:

• Local hardware failures • Disasters • File/data deletion and corruption

In all three failure types, backup can be used as the primary recovery mechanism. The other techniques mentioned below, can supplement backup to reduce recovery time or reduce data loss. Local hardware failures are mostly addressed with redundant data (ex: RAID1 or RAID5), redundant power, and redundant connections with path failover. Dell PowerEdge includes redundant power and VMware ESX 2.1 enables Host Bus Adapter path failover. Hardware redundancy is not sufficient for some rare hardware/firmware failures and human errors, such as


mounting the wrong drive, so traditional backup supplements redundancy and can also be used to restore data, but data is lost between the backup and restoration time.

For high availability purpose, RAID1 or RAID5 is recommended for an ESX operating system.

Disaster recovery is mostly addressed with remote replication, but requires the cost of a remote, second data center. Traditional backups stored offsite can also be used to recover from disasters. This helps to greatly reduce costs, but again data is lost between the backup and restoration time. Human deletions are usually files and are usually detectable, while application corruption of files can remain very subtle. Files from snapshots or backups are the initial basis for recovery. Versioned files are catalogued in Dell/EMC SAN products for exact, point-in-time snapshots. Traditional backups are not versioned or catalogued, so data is lost between the backup and restoration time. For complex application corruptions, restored files will still require additional database logs and transaction-level recovery tools.

NOTICE: See related Veritas Backup Exec database agents for granular recovery and additional repairs from messaging or database corruption.

1. Understanding Dell Backup Configurations Dell configurations of ESX 2.1 Tape Backup allow users to:

• Leverage all major features of Veritas™ Backup Exec (VBUE) 9.1 • Implement all major features of physical backup and restore, including complete,

incremental, and differential. • Backup and restore specific files, an entire VM, or any number of VMs hosted on the ESX

Server • Backup and restore ESX Service Console configuration files • Best practices for scalability, high availability, and reliability of Virtual Center databases

and Gold Master templates on attached storage. For this release, Dell supports the following Network Attached Backup Server (NABS) configurations:

Veritas Backup Exec 9.1 for Windows Server • Qualified on Microsoft® Windows Server™ 2003 or Microsoft Windows Server 2000 on

Dell PowerEdge 1750 • Internet Explorer 5.5 or higher, for managing VBUE Server • A single ESX 2.1 server on PowerEdge 6650 can be used in a “stand-alone” mode, or

one or more servers can be attached to a shared backup server • Dell PowerVault™ 110T (DLT, SDLT, LTO-1, LTO-2) SCSI Tape Drive or PowerVault™

122T (DLT, SDLT, LTO) Single Drive Tape Autoloader • See www.dell.com/vmware, ESX 2.1 Deployment Guide, for PowerEdge 1750 supported

configurations for VMware Virtual Center™ and remote VMware ESX management Veritas Backup Exec agents • ESX 2.1 VMs can include VBUE 9.1 agents on RedHat® Enterprise Linux® 3.0,

Microsoft Windows Server 2003, Microsoft Windows Server 2000, and Microsoft Windows NT® Server

• VBUE agent on ESX 2.1 Service Console • See www.dell.com/vmware, ESX 2.1 Deployment Guide, for Dell PowerEdge 6650

supported configurations for VMware ESX Server 2.1


http://www.dell.com/vmware

http://www.dell.com/vmware

Tape Backup Testing - Physical Topology

Virtual Machines

VirtualizationLayer

PE 6650Hardware

LAN

SAN

FC

FC

SCSI

SCSI

NIC

0

NIC

1

VirtualSwitch

ServiceConsole

VBUE Client

VM 2VBUE Client

VBUE 9.1 ServerOn PE1750

LocalDisk

110T

122T

RAID

VM 1VBUE Client

SCSI

VMXNET VMXNET

In the first configuration, the Veritas Backup agent was qualified on VMware ESX 2.1 Service Console to back up the VM infrastructure; i.e., the ESX Service Console configuration files and VM’s virtual disks files to a network attached Veritas Backup Exec (VBUE) 9.1 for Windows Server.

In the second configuration, the Veritas Backup agent was qualified on a VM to back up its specific files to a network attached Veritas Backup Exec (VBUE) 9.1 for Windows Server, as shown in VM1 and VM2 above. This is identical to VBUE agent on a physical machine to backup the OS and application.

NOTE: Best practice includes replacing each VM’s default vlance virtual NIC with the much faster vmxnet virtual NIC as shown above. See Appendix A. Installing VM Tools VMXNET in the Guest OS for details.

2. Understanding Backup Components Backup components include Dell hardware, VMware virtualization, and Veritas backup software.

• Network Attached Backup Server – Veritas™ Backup Exec 9.1 for Windows Server on Windows Server 2003 on PowerEdge 1750 with Internet Explorer browser for Management User Interface (MUI).

NOTE: The Virtual Center is often on the same server as Backup Server, where best

practice is to manage and backup no more than 50 ESX Servers or 1000 VMs with a single Management Server. All system management information of the Virtual Center should be stored in the external VC database, which can be clustered. For production, use Oracle® or SQL Server as the repository for Virtual Center. Data size can be shrunk by reducing the polling, which defaults to 5-minute frequency and weekly aggregation.


• Dell PowerVault 110T (DLT, SDLT, LTO-1, LTO-2) SCSI Tape Drive or Dell PowerVault 122T (DLT, SDLT, LTO) Single Drive Tape Autoloader

• VMware ESX Server(s) to be backed up – VBUE 9.1 backup agents are installable in the Service Console and each VM on VMware ESX 2.1 on PowerEdge 6650

3. Backup Planning As a backup administrator, you should be aware of best practices for VMware ESX 2.1 backup operational guidelines at each lifecycle step: Planning, Installation, Disaster Recovery, and additional Restore or Repair.

There are three major components of ESX Server that you should back up regularly using the VBUE agent in the Service Console. There is an additional, optional component to backup if you require backup and recovery at the file-level. All four are listed in priority order in the table below with recommended backup and archive policies.

VBUE Agent

What to Back Up (in priority order)

Recommended Backup Policy

Recommended Archive Policy

Service Console

1. Data disk image *.dsk of each VM (.dsk file containing application and other data)

Daily backup with real-time data replication

Weekly full backup

Service Console

2. Boot disk image of each VM (.dsk file with the boot image of each VM)

Weekly1 differential backup

Weekly full backup

Service Console

3. Directory for VM’s configuration files such as /root/vmware or /vpx/vms.

Weekly differential backup

Monthly full backup

VMs 4. Physical files in a VM Daily incremental backup

Weekly full backup

Boot disk: Store the operating system of a virtual machine in a dedicated VMFS partition, separate from all other data and application data. This enables:

• A smaller VMFS operating system partition for faster cloning, exporting, and backing up • Separate backup policies for the VMFS operating system partition and the VMFS data disks • Increased reliability and scaling of backups

4. Backup Server Installation Follow instructions in Veritas Backup Exec 9.1 for Windows Server Administrators Guide chapter 2: Installing Backup Exec to:

• Install VBUE Server on Microsoft Windows Server 2003 or Microsoft Windows Server 2000 on Dell PowerEdge 1750

NOTE: Microsoft Windows Server 2003 is recommended over Windows Server 2000

and is required for Backup Exec Web Administration Console.

• Schedule the backup and manage the 110T or 122T tapes

1 Weekly is sufficient, since this is very large and there are few changes.


5. Backup Agent Solutions Dell qualifies two network attached backup options on ESX 2.1 with high-level insights listed in the following table. The Service Console column is recommended for disaster recovery, while the second option extends this for file-level backup and recovery.

Single Agent in Service Console Agent in Each VM Disaster recovery only File-level restore or disaster recovery Network backup of each VM’s: 1. Application data 2. Boot OS 3. ESX Server console config files

Supplements the Service Console agent when file-level application data backup and recovery is required

Single source suitable for rapid redeployment

Identical to physical backup and recovery

Single agent to license, tune, and configure. Single bottleneck and failure point, but best practices below (See Section 5.1.1) reduce performance impact.

Many clients. Must install agent software in each VM.

Easy to boot a restored virtual disk Recovery requires two steps: 1. Restore OS 2. Restore files into running VM

VM shutdown is required unless 2 REDO logs are used (see 5.1 Backup Agent in Service Console).

VMs does not require shutdown

5.1 Backup Agent in Service Console The following backup and recovery best practices are exclusive to network attached and to the single VBUE agent in the Service Console.

5.1.1 Pre-Backup Perform the following one-time operations for the Service Console to provide full disaster recovery on a Dell PowerEdge 6650:

1. Install VBUE agent in ESX 2.1 Service Console as described in Veritas Backup Exec 9.1 for Windows Server Administrators Guide

NOTE: Do not set a password during the initial install of the VBUE agent in the

Service Console; otherwise, the auto-detection of the Unix Agent on Service Console will fail. The password can be set later after installation.

2. Create a directory in the Service Console to stage VMs for backup. A best practice is to

point this staging directory to a remote Windows share on the VBUE Server via Samba Service. A sample shell script setup-NT-share.sh2 is available in the Appendix B of this paper.

2 All sample scripts referenced are provided on an “as-is basis” for reference purposes only.


NOTE: This staging area can help minimize storage impact to the Service Console by physically residing on a separate server such as the VBUE Server:

• Alternatively, advanced Linux users may avoid the need for a staging area by

posting the files directly on the VBUE server, which is done by piping the vmkfstools command to a file transfer command, such as ncftp, a useful text-only FTP client that includes the ncftpget command, useful for unattended FTP downloads. For syntax and details on vmkfstools get the command line manual with man vmkfstools.

5.1.2 Backing up a VM after Shutdown The simplest way to perform a full backup is to shut down the VM for the entire time of the backup. To back up a running VM requires using two redo logs and is described in the following section. Repeat the following operations in the Service Console for each VM to be shut down and backed up: 1. Shutdown the VM, either via VMware remote console or from MUI. 2. Use vmkfstools3 command line tool to create, manipulate and manage files stored in VMFS volumes. To export each VM file to the staging area, the command line options is –e for export, <source_path> is the absolute path of the VM disk file to export, and <destination_path> is the absolute path of the exported VM disk file on the service console staging area, which by virtual of the Pre-backup setup described above, can be physically located on the VBUE Server. vmkfstools -e <destination_path> <source_path>

NOTE: You must be logged in as root to use vmkfstools. Vmkfstools is required to copy (export) files larger than 2GB to the staging area, since NTFS cannot handle such large files. If you use Virtual Center for one-to-many ESX management, then the file extension is *.vmdk.

3. Copy the VM configuration file from /vpx/vms/<VM-Name>/ (if VM was deployed through Virtual Center) or /vmware/<VM-Name>/ (if MUI was used for VM deployment) to the staging area. 4. Backup the VM disk and configuration files in the staging area from the VBUE Server. Consult Veritas Backup Exec 9.1 for Windows Server Administrators Guide for detailed instructions. 5. Re-start the VM.

5.1.3 Backing up a Running VM The following alternative removes the need to shut down, but requires two redo logs. 1. Add two redo logs The sample scripts in VMware’s “VMware ESX Server Backup Planning” technical note (see URL http://www.vmware.com/pdf/ESXBackup.pdf for details) can be used for this purpose. After 3 For details see http://www.vmware.com/support/esx21/doc/esx21admin_vmvkfstools.html


http://www.vmware.com/pdf/ESXBackup.pdf

http://www.vmware.com/support/esx21/doc/esx21admin_vmvkfstools.html

obtaining the sample scripts, addredo.pl, commitnext.pl from this pdf file (use Text Select Tool for the pdf file), copy commitnext.pl as committop.pl, then in committop.pl, change the arguments in function call commit() from $err = $vm->commit($disk, 1, 0, 1); to $err = $vm->commit($disk, 0, 0, 1); To add one redo log to a running VM, issue:

perl addredo.pl <vm-cfg-file> where <vm-cfg-file> represents the absolute path to the VM’s config file. Once this script finishes successfully, a file named VM-name.dsk.REDO or VM-name.vmdk.REDO (for VM deployed via Virtual Center) is created in the VMFS file system. 2. Use vmkfstools command line tool to export VM files to the staging area. Issue: vmkfstools -e <destination_path> <VM-disk>

NOTE: Your original redo log and virtual disk remain unchanged. You must be logged in as root to use vmkfstools. We recommend using the vmkfstools to export VM *.dsk files to the staging area. Vmkfstools is required to copy files larger than 2GB to the staging area, since NTFS cannot handle such large files. If you use Virtual Center for one-to-many ESX management, then the file extension is *.vmdk.

3. Once step 2 is finished gracefully. Add the second redo log, so we can backup the first redo log. Issue

perl addredo.pl <vm-cfg-file>

one more time. A VM-name.vmdk.REDO.REDO file is created in the VMFS file system. 4. If the first redo log, VM-name.vmdk.REDO, is less than 2 GB, copy it over to the staging area. Otherwise, use vmkfstools to export it just like step 2. 5. Copy the VM configuration file from /vpx/vms/<VM-Name>/ (if VM was deployed through Virtual Center) or /vmware/<VM-Name>/ (if MUI was used for VM deployment) to the staging area. 6. Backup the exported files in the staging area for the VM from VBUE 9.1 Server. Consult Veritas™ Backup Exec 9.1 for Windows Server Administrators Guide for detailed instructions. 7. Commit the REDO logs to the base disk to get it up to date. Sample script commitnext.pl and committop.pl can be used for this purpose. Issue

perl commitnext.pl <VM-config-file> for the “next to top” redo log. Once this script finishes successfully, only one redo log will remain. To be totally back to the normal processing state for production VM with persistent disk, issue

perl committop.pl <VM-config-file>


Zero redo log shall remain now.

5.1.4 Disaster Recovery of each VM Since the running VM redo logs were committed, the files are complete snapshots, just as the simpler suspended backups, so disaster recovery is the same for both backup types. Perform the following steps for each VM that requires full, disaster recovery. 1. Restore the needed backup files from type on VBUE Server to staging area. 2. Import the source virtual disk file that was previously exported

vmkfstools -i <console_source_file> <vm_destination_file>

NOTE: The destination device must have space for the entire size of the virtual disk, even if it is mostly free space, as the complete contents of the source disk are copied. Also, <vm_destination_file> needs to be the exact path to the original VM disk file.

3. Copy VM configuration file from staging area to /vpx/vms/<VM-Name>/ or /vmware/<VM-Name>/ depending on VM deployment using VC or MUI respectively. 4. Restart the VM.

5.1.5 Backing up the Service Console We do not recommend backing up the entire ESX Server, since new installations are automated and faster than full restore. So only back up the ESX Server configuration data, which can be re-applied after the restore. Back up ESX Service Console configuration directories from VBUE 9.1 Server under the Remote Selections/UNIX Agents sub-tree. If you use Virtual Center 1.0.1 for VM provisioning, the configuration files are in /vpx/vms.

5.1.6 Disaster Recovery of the Service Console

1. Reinstall ESX (on new disks) 2. Install VBUE 9.1 Agent on Service Console. 3. Restore backed up configuration directories. Consult Veritas™ Backup Exec 9.1 for

Windows Server Administrators Guide for details. 4. Restore the VM disks you backed up earlier back on the ESX Server and reboot.

5.2 Backup Agents in VMs

The following backup best practices are also network attached, but exclusive to having a VBUE agent in each VM, where file-level backup behaves the same way as on any other physical machine with a backup client installed.

5.2.1 Pre-Backup Replace the vlance network adapter driver with vmxnet, which is much faster for faster network such as 1 GB Ethernet switch. For step-by-step instructions, see Appendix A: Installing VMware Tools VMXNET in the Guest OS.


5.2.2 VM Agents for Backup Follow instructions in Veritas Backup Exec 9.1 for Windows Server Administrators Guide on Backup Exec Agent backup operations.

5.2.3 VM Agents for Restore Follow instructions in Veritas Backup Exec 9.1 for Windows Server Administrators Guide on Backup Exec Agent restore operations.

5.2.4 Granular Restore or Repair Since backup agents in VMs are identical to agents in physical machines, additional Dell products provide more granular file restore and repair. Traditional file backups are not versioned or catalogued, so data is lost between the backup and restoration time. Versioned files are catalogued in Dell/EMC SAN products for exact, point-in-time snapshots. For product details see www.dell.com/EMC. For complex application corruptions, restored files will still require additional database log and transaction-level recovery tools. See www.Veritas.com/products for additional Veritas Backup Exec 9.1 database agents for granular recovery and additional repairs from messaging or database corruption.


http://www.dell.com/EMC

6. Appendix A: Installing VMware Tools - VMXNET in the Guest OS

Installing VMware tools in each guest OS is highly recommended for performance, and backup performance, and key management scripting features. It is not possible to install VMware tools until the OS install is completed. VMware tools can be installed either from:

• The Remote Console by choosing Settings VMware tools Install which attaches a virtual CD-ROM ISO file onto the VMs CD-ROM drive. Or

• Automatically launch on Windows guest OSes with CD Autorun enabled. See www.vmware.com for complete features of VMware tools. Features related to Tape Backup include:

• For Windows 2000 only: For performance reasons, update the Microsoft Buslogic driver with VMware SCSI

• VMware tools provide a guest OS service, VMwareService.exe, for: • Executing OS commands including shutdown or reboot. • Sending a heartbeat to ESX Server to notify guest OS status to enable notification,

failover, backup, and other services. • Executing VM commands including ESX asking the guest OS to gracefully power

down and reset. The main advantage of installing VMware tools, is that it allows you to replace the vlance network adapter driver with vmxnet, which is much faster for faster network adapters such as 1 GB.

6.1 Installing VMXNET in Linux Guest OS: 1. After the Virtual Machine is installed, you need to install VMware tools. Ensure that you know the

location of the VMXNET driver, vmxnet.o, which came with the VMware tools installation. To find it, use:

# find . –name ‘vmxnet.o’ –exec ls {} \;

from the $HOME directory of the root user, who installed the VMware tools. 2. If you have multiple copies of vmxnet.o, find which one is for your platform. To check, use:

# uname –a For example, “2.4.21-4.ELsmp #1 SMP…i686…” means you’re using RedHat Enterprise Linux 3.0 AS on i686 architecture. Then your driver is in $HOME_of_Root/vmware-tools-distrib/lib/modules/binary/smp-2.4.21-4.i686-RHAS3.0/objects. Change into the above directory and copy vmxnet.o to /lib/modules/2.4.21-4.ELsmp/kernel/drivers/net. Make sure that vmxnet.o has the right file permission. Issue `chmod 755 vmxnet.o” after changing into /lib/modules/2.4.21-4.ELsmp/kernel/drivers/net.

3. Modify configuration file /etc/module.conf to point eth0 to vmxnet instead of pcnet32. You make a backup copy of module.conf before changing it using your favorite text editor like “vi”. After making the change, you can run “diff” command to ensure that only the intended changes are made: alias eth0 vmxnet


http://www.vmware.com/

4. Shutdown the Virtual Machine gracefully. #sbin/halt Click on “Power Off” button once you see the “System halted” message. To edit the Network Adapter virtual device listing In the MUI, click on the name of the Virtual Machine to bring up its Status/Configuration

page. Next to Configuration, click the Hardware link. Click Edit next to Network Adapter Ensure that Virtual Device is listed as vmxnet. If not, click the drop-down and change it.

When done, click OK.

5. Start your Virtual Machine and verify network connectivity. 5.1 In the MUI, Power On the Virtual Machine. 5.2 Once booted, verify network connectivity by pinging another device on the network (ESX Server, another Virtual Machine, the default gateway, etc)

6.2 Installing VMXNET in Windows 2003 or Windows 2000

Guest OS 1. Assume that you have installed the VMware tools after defining the Guest OS. Disable and

uninstall the default NIC, vlance, from the Gust OS. Right click on “My Computer”, select Manage. In “Computer Management” application, click “Device Manager”. Expand the “Network adapters”, right click “AMD PCNET Family PCI Ethernet Adapter”, select Disable. Right click it again. Select Uninstall. This will get rid all information about the vlance NIC from the Windows registry.

2. Shuts down Windows gracefully. 3. After the Windows machine is virtually powered off. From the MUI, click on the Windows

machine shutdown in the previous step. Click “Hardware”. For “Network Adapter”, if the default vlance is still listed as Virtual Device, click Edit. Replace vlance with vmxnet from the drop-down list. When done, click OK.

4. Start your Virtual Machine 5. If VMware tools were installed before changing the network to vmxnet, you will be prompted

to install a driver for vmxnet. "Choose Install from a list or specific location", click Next. 6. For Windows 2003: Click "Search for the best driver in these locations," uncheck "Search

removable media" and check "Include this location in the search". For Windows 2000: Click "Search for a suitable driver for my device", click Next. Make sure that "Specify a location" is the only option checked.

7. Click "Browse" and browse to the VMware tools\Drivers\vmxnet directory (the default location is %systemdrive%\Program Files\VMware. Click "Next" (“OK” for Windows 2000).

8. Answer "Yes" when prompted about installing unsigned software. 9. After the install is complete, reboot Tips: Since VMware tools also laid down some .inf files in %windir%\inf directory, including the one for vmxnet, typically called oem5.inf., Steps 6 and 7 above can be simplified by just clicking the “Next” button in the Wizard.


7. Appendix B: Sample script to avoid the staging area on Service Console. The following sample script is provided on an “as-is” basis, and it assumes that the NT share setup has been done. Log on as root to run the script. #!/bin/sh echo 'This is to mount some NTFS share drive under /mnt using smbfs' echo ' so we can export .dsk file into it directly using vmkfstools.' mkdir -p /mnt/backup-NT-share/110T-ddrive umount /mnt/backup-NT-share/110T-ddrive ls -l /mnt # ---------------------------------------------------------------- # now mount it. # Note that 172.16.49.102 is the IP address of the VBUE 9.1 Server. # “ddrive” is the NT share name of D: drive on that Windows machine. # ------------------------------------------------------------------ mount -t smbfs //172.16.49.102/ddrive /mnt/backup-NT-share/110T-ddrive -o \ username=administrator,workgroup=administrators,rw,uid=0,gid=0 echo "the return code is $?" # end of script

8. Appendix C: Additional Resources Complete and current documentation for Dell supported VMware configurations is available at http://www.dell.com/vmware. 8.1 Additional Web Information

1. Dell products: www.dell.com see servers, storage, or tape, then product literature 2. Veritas at http://www.veritas.com/products for information on Veritas Backup Exec 9.1 for

Windows 3. EMC Support Matrix (ESM) at http://www.emc.com/horizontal/interoperability/ 4. VMware Virtual Center 1.0.1 at

• Features: http://www.vmware.com/products/vmanage/vc_features.html • Documents: http://www.vmware.com/support/vc/ • Troubleshooting: http://www.vmware.com/support/vc/doc/releasenotes_vc.html

5. VMware ESX 2.1 at • Features: http://www.vmware.com/products/server/esx_features.html • Documentation: http://www.vmware.com/support/esx2/doc/ Includes Install Guide, Admin

Guide, Scripting Guide, etc. • Troubleshooting:http://www.vmware.com/support/esx2/ Includes? install, configure, guest OS

(also see the KnowledgeBase)


http://www.dell.com/

http://www.dell.com/

http://www.veritas.com/products

http://www.emc.com/horizontal/interoperability/

http://www.vmware.com/products/vmanage/vc_features.html

http://www.vmware.com/support/vc/

http://www.vmware.com/support/vc/doc/releasenotes_vc.html

http://www.vmware.com/products/server/esx_features.html

http://www.vmware.com/support/esx2/doc/

http://www.vmware.com/support/esx2/


8.2 Technical Support Resources

1. Dell-specific VMWare information at http://www.dell.com/vmware/ 2. VMware support website at http://www.vmware.com 3. Dell hardware support at http://www.dell.com/support 4. Dell deployment and professional services http://www.dell.com/services

8.3 Newsgroups

1. VMWare Newsgroups at news.vmware.com

THIS GUIDE IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND. Information in this document is subject to change without notice.

Dell, the DELL logo, PowerVault and PowerEdge are trademarks of Dell Inc. VMware is a registered trademark of VMware, Inc. EMC is a registered trademark of EMC Corporation. Linux is a registered trademark of Linus Torvalds. Netware is a registered

trademark of Novell Inc. Microsoft , Windows and Microsoft Server are registered trademarks of Microsoft Corporation. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.

© 2004 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. For information contact Dell.

http://www.dell.com/vmware/

http://www.vmware.com/

http://www.dell.com/support

http://www.dell.com/services