Solved!
Go to Solution4275
0
Posted August 6th, 2009 04:00
As RRR said first thing I do is a symcfg discover or I restrict it with a -sid xxxx and you can also do a symcfg -sid xxxx verify to bounce the database against the machine to check that its up to date.4275
0
Posted August 6th, 2009 07:00
i found its not risky but lengthy4275
0
Posted August 7th, 2009 00:00
If your Symm has 10k symdevs it can be lengthy yes.... But nondisruptive4275
0
Posted August 11th, 2009 08:00
lengthy is a good word for it. I have a hard time getting the guys to run it before doing config work since we have ~16k devices on the local symm and another ~20k on a remote symm with an SRDF/A link
Sometimes I'm tempted to skip it myself!4275
0
Posted August 12th, 2009 03:00
And I was thinking 10k was a lot... I feel tiny all of a sudden...4275
0
Posted August 17th, 2009 13:00
Well, when you have mainframe mixed in with the Open Systems, and the mainframe guys still insist on using MOD-3 devices for most of their capacity... it adds up to a lot of devices. On our Prod array they account for about 20% of our capacity and about 80% of the devices (by count).
RRR
6 Operator
•
5739 Posts
4275
0
Posted August 6th, 2009 03:00