You haven't mentioned what version of VM so:
http://www.symantec.com/docs/TECH47620 (HCL for 5.0)
http://www.symantec.com/docs/TECH74012 (HCL for 5.1)
Enjoy.
From: Romeo Theriault romeotheria...@gmail.com
To: veritas-vx@mailman.eng.auburn.edu
Sent: Wed, 6
Can you do it ? Yes
Should you do it ? No
VM will let you grow any volume BUT since your /opt on slice 5 it WILL NOT
resize the underlying partition.
So if you need to un-encapsulate you will end up with /opt being the size of
s5, NOT what you resized it to under VM.
The problem here is the DMP device tree is confused after reboot and that is
due to the disk.info
The clean up DMP device tree:
1. rm /etc/vx/disk.info
2. rm /dev/vx/dmp/*
3. rm /dev/vx/rdmp/*
4. vxconfigd -k
- Original Message
From: joel j...@saldino.net
To:
First of all, there is not such command as vxvol deport
Anway couple of things to check here.
What version of Volume Manger and File System did you install ?
What version of Volume Manger and File System is on the old system ?
Is your volume part of an RVG ?
If this is a VxFS file system easy. Firstly shrink the volume by the size of
disk03 and then when you run vxprint you will not see the disk are part of the
volume anymore. You can delete to your hearts content then
- Original Message
From: ssloh ss...@singnet.com.sg
To:
You don't need a rootdg in 4.x
Why didn't you just run vxinstall to just configure the vxconfid deamon ??
- Original Message
From: Artur Baruchi mail.baru...@gmail.com
To: veritas-vx@mailman.eng.auburn.edu
Sent: Thursday, 29 January, 2009 9:08:11 PM
Subject: [Veritas-vx] Strange
Try the following (will clear reread volume manager links only ) :
cd /dev/vx/dmp; rm *
cd /dev/vx/rdmp; rm *
cd /etc/vx; rename the disk.info file
vxconfigd -k
vxdiskadm number 5
- Original Message
From: Bryan Bahnmiller bryan.bahnmil...@managedmail.com
To: Robinson, Greg
Install MP2
--- Reshma Syed [EMAIL PROTECTED] wrote:
Hi ,
How to take backup for dg backup on VXVM3.5
connected to solaris 9 ,
h\w-SunFire V240 .
There is the backup facility on VXVM 4.0 as pasted
the command
# vxconfigbackup-l /anyDir dgname
But there is no
You are running PowerPath, therefore what you are seeing is 100% correct.
Remove powerpath and install the ASL for you array if you want DMP.
- Original Message
From: ajay raghuraj [EMAIL PROTECTED]
To: veritas-vx@mailman.eng.auburn.edu
Sent: Wednesday, 31 October, 2007 9:59:17 PM
A shared diskgroup means mounted on both nodes of the cluster at the same time.
There is no failover. For this you need CVM and CFS
As far as how to make diskgroup sharable, you don't have to do anything with
the diskgroup. Just make sure both servers can see the disks in the DG.
-
Please read the Admin Guide and in particular the man page for vxassist.
vxassist -g dg_name mirror volume alloc=disk_name
- Original Message
From: ajay raghuraj [EMAIL PROTECTED]
To: VeritasUsers Veritas-vx@mailman.eng.auburn.edu
Sent: Wednesday, 15 August, 2007 5:14:38 AM
This is gonna be to hard to fix via email. Since this is raid5 at software
level (yuk!!) you need to be EXTREMELY careful what you do here. Once false
move and bye bye data.
I would strongly suggest logging a call with tech support to help you out with
these volumes
- Original Message
mount -o ro /dev//mnt
Does it mount read only ? If so take a backup first then fsck it.
- Original Message
From: Asif Iqbal [EMAIL PROTECTED]
To: Darren Dunham [EMAIL PROTECTED]
Cc: Veritas-vx@mailman.eng.auburn.edu
Sent: Friday, 6 July, 2007 3:06:40 PM
Subject: Re:
So from this output:
v ccbappl -ENABLED ACTIVE 421458352 SELECT -fsgen
pl ccbappl-01 ccbappl ENABLED ACTIVE 421458352 CONCAT -RW
sd oraappdg02-01 ccbappl-01 oraappdg02 0 85946368 0 Disk_1 ENA
sd oraappdg05-01 ccbappl-01
That process whould be vxconfigbackupd -
Stop the process at your own peril.
- Original Message
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: veritas-vx@mailman.eng.auburn.edu
Sent: Tuesday, 27 February, 2007 4:18:21 AM
Subject: [Veritas-vx] /etc/vx/cbr/bk directory
What vx process
Trying doing a vxconfigd -k
That should resolve any confusion VM may have
- Original Message
From: George Done Veritas [EMAIL PROTECTED]
To: veritas-vx@mailman.eng.auburn.edu
Sent: Saturday, 10 March, 2007 1:44:40 AM
Subject: [Veritas-vx] vxprint and vxdg free report highly conflicting
Please read the man page for vxresize. File system must be mounted.
- Original Message
From: Caleb Guinn [EMAIL PROTECTED]
To: veritas-vx@mailman.eng.auburn.edu
Sent: Tuesday, 17 April, 2007 8:23:54 AM
Subject: [Veritas-vx] cannot resize a file system
!--
/* Style Definitions
VM4.x offers dymanic lun resizing. vxdisk resize
- Original Message
From: Jarkko Airaksinen [EMAIL PROTECTED]
To: veritas-vx@mailman.eng.auburn.edu
Sent: Thursday, 29 March, 2007 12:33:20 AM
Subject: [Veritas-vx] resizing a device
!--
/* Style Definitions */
p.MsoNormal,
All you need ie step by step upgrade procedures are in the install guide for 4.0
- Original Message
From: Gummadidala, Ramu (GE, Corporate, consultant) [EMAIL PROTECTED]
To: Veritas-vx@mailman.eng.auburn.edu
Sent: Thursday, 22 March, 2007 11:53:33 PM
Subject: [Veritas-vx] Veritas Upgrade
Disk appears in error state which means access to the disk was lost. If you
look at the vtoc of the disk I think you will find that it does still have tag
15.
Look at vxdisk list EVA8_10 I suspect you will see the path disable.
If I'm correct try to enable the path vxdmpadm enable (it
From memory there is point patch available for such issue. Please call
Symantec tech support
- Original Message
From: Jarkko Airaksinen [EMAIL PROTECTED]
To: Veritas-vx@mailman.eng.auburn.edu
Sent: Friday, 30 March, 2007 2:09:58 AM
Subject: [Veritas-vx] vxdmp question
Hello,
Would
Follow the procedure to un-encapsulate again.
After you boot from the mirror disk of the solaris partitions, run vxinstall
and encapsulate your mirror disk (#2 custom install and leave all your other
disks alone)
Now the thing to keep is mind is what disk your system will boot from when you
I had a small LUN assigned that is used for nothing, just a place holder in
the rootdg. So now my two boot disks are not under veritas control so I
can mirror them. But after I did this I wondered: what if the box comes up
one day and tries to start Veritas before the HBA presents the LUN to
Politely suggest to the Netapp TSE to stick to what he knows and leave the VM
part to the experts.
If you don't want enclosure based names then run vxdiskadm and yes you can do
it on the fly.
Since your running 4.1 try this first.
1. mv /etc/vx/disk.info /etc/vx/disk.info.old
2. cd
Do you actually have 6 paths to the disk to begin with ?
If you don't have 6, then what did you expect DMP to do ?
If you do have 6, have you excluded the 2 other paths ?
- Original Message
From: Munish Dhawan [EMAIL PROTECTED]
To: veritas-vx@mailman.eng.auburn.edu
Sent: Tuesday, 28
Install all the require packages for the GUI
- Original Message
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: veritas-vx@mailman.eng.auburn.edu
Sent: Thursday, 16 November, 2006 11:04:41 PM
Subject: [Veritas-vx] StorageFoundation_v5.0_Basic, (vea) Veritas Enterprise
Administrator
Hi
From VM4.x onwards, devices that have not been formated for VM use will be shown on "online invalid"What others says about the disk showing error as normal is total rubbish. This is not a normal state, the disks should NOT be in an error state.Now if the state changes from online to error then one
Install PP first. - Original Message From: Aharon Atlan [EMAIL PROTECTED]To: Veritas-vx@mailman.eng.auburn.eduCc: IT-Storage Team [EMAIL PROTECTED]Sent: Thursday, 2 November, 2006 4:06:55 AMSubject: [Veritas-vx] Integration Veritas 5 + Powerpath + clarrion case
Hi
I
Ok found what I was looking for.
One solution to fix /var not getting mounted at boot is to add a sleep command
(sleep 10) at the beginning of the script /etc/rcS.d/S70buildmnttab.sh.
- Original Message
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: Veritas-vx@mailman.eng.auburn.edu
As I explained, only way is to deport and import. Log a case with Symantec and they will tell you the same thing.
- Original Message From: Biju Krishnan [EMAIL PROTECTED]To: robertinoau [EMAIL PROTECTED]Cc: veritas-vx@mailman.eng.auburn.edu; Atif Munir [EMAIL PROTECTED]Sent: Thursday, 19
You cannot deport rootdg on a VX3.x , it must always
be imported.
This is perfect example of why dont put everything in
rootdg.
You will have to split all but one disk into another
diskgroup and then deport that DG.
--- [EMAIL PROTECTED] wrote:
Hello,
how do i deport rootdg from boxA
Yes it will work.
--- Asiye Yiðit [EMAIL PROTECTED] wrote:
Hi All,
I have SF RAC 5.0 license. I am searching whether
that license will work SFRAC 4.1 MP1 or not. Could
you please help me?
Regards,
___
Veritas-vx maillist -
No other way other than deport them import.
- Original Message
From: Atif Munir [EMAIL PROTECTED]
To: veritas-vx@mailman.eng.auburn.edu
Sent: Friday, 6 October, 2006 3:14:02 PM
Subject: [Veritas-vx] disabled dg
How can I get the disabled the dg back as enabled without any
downtime. I
Hope you have a good backup them
- Original Message
From: Atif Munir [EMAIL PROTECTED]
To: veritas-vx@mailman.eng.auburn.edu
Sent: Monday, 9 October, 2006 1:59:39 PM
Subject: Re: [Veritas-vx] Veritas-vx Digest, Vol 6, Issue 9
yes its the situation but that requires an outage and I am
What are the following versions of:
1. HP
2. VM
3. Array
Does the syslog shows that vxdmp is disabling paths ?
- Original Message From: Mike Fernandes [EMAIL PROTECTED]To: veritas-vx@mailman.eng.auburn.eduSent: Thursday, 12 October, 2006 11:43:08 PMSubject: [Veritas-vx] Disabled
What kind of HDS array and why is it added a JBOD ?
c6 JBODENABLEDjbod0
c7 JBODENABLEDjbod0
--- Tony T. [EMAIL PROTECTED] wrote:
Hi all,
We had a situation recently on an old 450 with dual
LP9002L cards. It's
connected to a
Yes
I had some problem yesterday. I only had Storage
Foundation. When I installed Storage Foundation
Enterprise key it worked.
--- Joe Fomenko [EMAIL PROTECTED] wrote:
Sorry - old subject now, but...
Does anyone know if this new 5.0 feature is a
_licensed_ feature?
Sure hope not, but:
remove /etc/vx/disk.info
vxconfigk -k
--- [EMAIL PROTECTED] wrote:
Hello.
Not sure if this a Veritas 4.1 issue or not.
We are using SVM for our boot disk and mirror. VxVM
for application data.
=
Sunfire
Solaris 8
Foundation Suite 4.1
I am seeing devices in a
Known issue, log case with tech support.
Can't remember solution of the top of my head
--- Cameron, Derek [EMAIL PROTECTED] wrote:
Greetings folks.
Solaris 2.9, Veritas 4.1, EMC storage.
I've discovered a new san lun in the usual manner
(cfgadm, devfsadm,
format, vxdctl) but when I
3.x default private region is 1024
4.x default private region is now 2048
Whenever you use vxdiskadm in 4.x it will ask if you
want to use it's default private region. Obviously if
the disk was initialized with 3.x you don't want to
use the default.
That answer your questions ?
Now with
40 matches
Mail list logo
