Hi Robert.
We had something similar recently and it turned out to be because the MAC
address of the VM had changed. vSphere had given the restored VM a new MAC
address as the original was still assigned to the original (powered off) VM.
Linux saw this as a new, unconfigured device. I don't k
Hi James
You are right ...
When you restore original VM to Original location the VM is saving the Unique
UUID and MAC address on Network adapter,
but when you restore the VM to alternate location and the original VM still
exist VMware will generate new UUID and MAC address for Network adapter
This just appeared on the FTP site - says it was posted yesterday? Any
idea what it addresses?
--
*Zoltan Forray*
TSM Software & Hardware Administrator
BigBro / Hobbit / Xymon Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be
At least 2 of the items causing me grief.
http://www-01.ibm.com/support/docview.wss?uid=swg1IT02571
http://www-01.ibm.com/support/docview.wss?uid=swg1IT02717
I also heard that 7.1.1.0 is schedule for end of September.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MA
This patch is the first opportunity to test an upgrade using the new
installation manager. I did two upgrades today and the results are:
TSM 7.1 Windows 200R2 was upgraded using the Installation Manager GUI. No
problems.
TSM 7.1 Linux was upgraded using console (text) mode. The installation
http://www-01.ibm.com/support/docview.wss?uid=swg21681525
tsm server 7.1 causes data loss!
with best regards
stefan savoric
