Re: BMC should have made upgrades easier - Customers loosing interests

2014-03-12 Thread Vivek Patil
Hi All,
   BMC has a dedicated AMIGO Team to assist and guide customers in their 
upgrade plan .   
If needed , ITSM Customer Engineering [ i mean RD ] Team will step in to 
unblock customer upgrade issue .

With 8.1 SP1 , we have shipped CONFIGCHECKER tool ; previously known as 
pre-checker .
a] Tool and its read-me file is available within the AR 8.1 SP1 installer zip . 
b] Before one starts the fresh install or upgrade , one can execute all checks 
using the config checker .
c] It checks configurations as well as ITSM Id violations which will point out 
the violations if any.
d] This way , most of the install  upgrade issues are fixed before starting 
the upgrade.
e] There is BPCU Tool to find out improper customizations and fix them before 
upgrade.

**IMPORTANT** :
1] We have published Cook-book for ITSM Suite 81 Upgrade document on BMC 
Remedy Community group.  Please click here to check the BMC Community blog post 
:

https://communities.bmc.com/community/bmcdn/bmc_it_service_support/blog/2013/08/07/upgrading-to-bmc-remedy-81-things-that-you-really-need-to-know

2]  AMIGO Assistance Program FAQ's :
A] Do we have any template for the data we need from customers ?
## BMC AMIGO team has developed a collateral that we will be providing 
customers and using this collateral the expectation is that customer will 
describe the a detailed upgrade plan. Once the plan has been developed they 
will come back to BMC Support and our AMIGO team will review their detailed 
plan and provide feedback on any red flags and/or reinforce crucial steps of 
the upgrade. 

B] Where can we track/check all this data ? Will it be  the BMC communities or 
a dedicated AMIGO site having the current status for each AMIGO support case.
## In the AMIGO process customers will contact Support via a Support ticket and 
these tickets will be tagged with the keyword AMIGO in the Memo field and this 
how it is tracked. 


 We look forward to help customers in the upgrade or  migration  to latest 
 8.1 SP1 ITSM Suite .

Thanks,
Vivek Patil

Disclaimer: 
a] This document compliments and DOES NOT replace the existing product 
documentation. Please follow the blog post to receive more updates. 
b] The opinions, statements, and/or suggested courses of action expressed in 
this E-mail do not necessarily reflect those of BMC Software, Inc. 
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Server Group Environment without Load Balancing

2014-03-12 Thread Sivarama Velicheti
Hi Group,

  We have a server group environment but not leveraging load balancing 
capabilities. Here is a brief overview on the production servers we have in 
place. I am trying to understand or find some documentation to best utilize the 
servers we have at hand. We have 3 application servers in which remedy is 
installed (server group environment) i) AppServerA ii) AppServerB  and iii) 
AppServerC . We further have two webservers for midtier i) webServerA and ii) 
webServerB. Here are somethings I am trying to wrap my head around. If we want 
to set Domain Name Alias am I correct in assuming we need to only set it for 
the primary server AppServerA (since no load balancer) and use the Operations 
Group ranking form to manage our load? We have two webservers and we need to 
set up the DNS alias for them as well. I have no idea as to how to use both of 
them in our environment without a load balancer. Any ideas or links to any 
documentation would be greatly appreciated. I went through the installing and 
configuring Server groups guide but have no ideas. We are on Remedy 8.1, 
Windows environment. 

Thanks
Siva

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Migration from MS SQL 5 to MS SQL 2012

2014-03-12 Thread Jason Miller
Either way should work pretty easy.  In the Remedy world a SQL upgrade
seems to be one of the easiest/least painful upgrades encountered.  Largely
Remedy doesn't care about the SQL version.  AR System more or less uses
standard DBMS functionality and doesn't get into using the more advanced
features where you might really notice a chance between SQL versions.

We are switching our SQL 2005 DB server(s) for 2012 servers right now.  We
just started with our test environment last week.  I need to test a little
more (more so validating all of our db linked servers still work) but so
far it is looking good.  The DBAs built a new SQL 2012 and restored a db
backup of the 2005 db.  All I did was change the db server reference in the
ar.cfg file and the system started right up.

Besides what I mentioned above we haven't upgraded a system from of 2005
system to 2012 but we have done 2008 to 2012 and AR System never knew the
difference.  I suspect you would see similar results with 2005 to 2012.

Jason


On Wed, Mar 12, 2014 at 6:48 AM, Himanshu kohl...@gmail.com wrote:

 Hi

 Our Current env details are

 ARS  ITSM 7.6.04 SP2
 Win 2003
 MS SQL 2005

 We are planning to migrate our DB SQL 2005 to SQL 2012

 Please advise if anyone of you have used following method and suggest
 which one will be better

 1) In place upgrade of SQL 2005 to SQL 2012 and than migrate upgraded DB
 2012 to new DB Server SQL 2012 ( old DB box needs to retire).

 2) Install DB SQL 2012 on new server and than take a backup of Remedy SQL
 2005 DB and restore on New SQL 2012.

 Please share your exp and timeline on DB and OS upgrade with migration to
 new underline infrastructure.


 Thanks  Regards
 Himanshu Kohli

 ___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
 Where the Answers Are, and have been for 20 years


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Migration from MS SQL 5 to MS SQL 2012

2014-03-12 Thread Himanshu
Hi 

Our Current env details are

ARS  ITSM 7.6.04 SP2
Win 2003
MS SQL 2005

We are planning to migrate our DB SQL 2005 to SQL 2012

Please advise if anyone of you have used following method and suggest which one 
will be better

1) In place upgrade of SQL 2005 to SQL 2012 and than migrate upgraded DB 2012 
to new DB Server SQL 2012 ( old DB box needs to retire).

2) Install DB SQL 2012 on new server and than take a backup of Remedy SQL 2005 
DB and restore on New SQL 2012.

Please share your exp and timeline on DB and OS upgrade with migration to new 
underline infrastructure.


Thanks  Regards
Himanshu Kohli
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Migration from MS SQL 5 to MS SQL 2012

2014-03-12 Thread Himanshu
Thanks for sharing your exp Jason

Sounds like a plan !

Thanks  Regards
Himanshu

 On Mar 12, 2014, at 3:17 PM, Jason Miller jason.mil...@gmail.com wrote:
 
 **
 Either way should work pretty easy.  In the Remedy world a SQL upgrade seems 
 to be one of the easiest/least painful upgrades encountered.  Largely Remedy 
 doesn't care about the SQL version.  AR System more or less uses standard 
 DBMS functionality and doesn't get into using the more advanced features 
 where you might really notice a chance between SQL versions.
 
 We are switching our SQL 2005 DB server(s) for 2012 servers right now.  We 
 just started with our test environment last week.  I need to test a little 
 more (more so validating all of our db linked servers still work) but so far 
 it is looking good.  The DBAs built a new SQL 2012 and restored a db backup 
 of the 2005 db.  All I did was change the db server reference in the ar.cfg 
 file and the system started right up.
 
 Besides what I mentioned above we haven't upgraded a system from of 2005 
 system to 2012 but we have done 2008 to 2012 and AR System never knew the 
 difference.  I suspect you would see similar results with 2005 to 2012.
 
 Jason
 
 
 On Wed, Mar 12, 2014 at 6:48 AM, Himanshu kohl...@gmail.com wrote:
 Hi
 
 Our Current env details are
 
 ARS  ITSM 7.6.04 SP2
 Win 2003
 MS SQL 2005
 
 We are planning to migrate our DB SQL 2005 to SQL 2012
 
 Please advise if anyone of you have used following method and suggest which 
 one will be better
 
 1) In place upgrade of SQL 2005 to SQL 2012 and than migrate upgraded DB 
 2012 to new DB Server SQL 2012 ( old DB box needs to retire).
 
 2) Install DB SQL 2012 on new server and than take a backup of Remedy SQL 
 2005 DB and restore on New SQL 2012.
 
 Please share your exp and timeline on DB and OS upgrade with migration to 
 new underline infrastructure.
 
 
 Thanks  Regards
 Himanshu Kohli
 ___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
 Where the Answers Are, and have been for 20 years
 
 _ARSlist: Where the Answers Are and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years