Re: DB Copy Issue
Hi, Yes, but you can still use a Fixed license on both servers with old/legacy/green licensing, as long as it is assigned to the same user. So if you have an account on both servers, you will only need one fixed license for that user. Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > I thought of two more items worth mentioning. The User records will be copied > over so to remain in compliance you will likely need to change most of your > user accounts to Read licenses after the DB copy. > > Also the entitlements for user licenses mentioned by Davin only apply to the > Blue pricing model. If you happen to be on the Legacy/Green model that is not > the case as licenses are purchased for production use at one cost and for > development use at a lower cost so they are not interchangeable. > > -Rick > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Davin Lindner-Green > Sent: Wednesday, February 11, 2015 2:38 PM > To: arslist@ARSLIST.ORG > Subject: Re: DB Copy Issue > > ** > A second vote to use the Remedy Restore Tool, plus some hints on licenses. In > version 7.x they are stored in the database so will get copied along with > everything else. > > Also, if you are on version 7 or newer the only license key that is tied to > your Host ID (your hardware) is the AR Server license. You should add the AR > Server license from DEV to your PROD environment before you copy the database. > That way it will be there when you start up DEV post-copy. > > In terms of entitlement, my understanding is that you are entitled to use AR > User Fixed licenses on any server in your environment as long as the users are > the same named users (which they will be after database copy). AR User > Floating licenses may be tied to a specific server (although not enforced by > the license key mechanism) so you might have to adjust that number after a > copy. However this depends on which licensing model you are under with BMC so > you might not have to adjust anything in terms of licensing. > > Last item, you may want to disable the email engine and any external > integrations on DEV before the copy, so you don't accidentally send duplicate > email notifications or trigger integration actions from DEV. Also, if you are > using custom Remedy applications at all, any server references you may have > included for integrations and the like won't be detected and changed by Remedy > Restore Tool. It is oriented primarily at ITSM and ARS core forms only. > > Thanks > Davin > > > > On Feb 11, 2015, at 3:27 PM, Rick Westbrock > mailto:rwestbr...@24hourfit.com>> wrote: > > ** > Check out the Remedy Restore Tool by Carl Wilson > (http://communities.bmc.com/docs/DOC-7710<https://communities.bmc.com/docs/DOC-7710> > ), it handles nearly all the deprodification steps required when copying a > production database to a non-prod environment. I normally adjust the licenses > manually myself but it depends on your version of ARS. If you are on version 7 > or newer (I think) it’s quite easy to just change the numbers in the > console; if you are on 6.x or older it will be a lot more painful due to the > old licensing model. > > -Rick > > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Scott Hallenger > Sent: Wednesday, February 11, 2015 2:14 PM > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > Subject: DB Copy Issue > > ** > Wondering if anyone can offer some advice on this issue. Can I copy our > production db to our dev server as an means of syncing dev to production. The > end goal being to make my dev look just like production. Our dev server does > not have the same number of licenses as production naturally. Is this > something that can be done with a basic db copy. > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "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" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: DB Copy Issue
I thought of two more items worth mentioning. The User records will be copied over so to remain in compliance you will likely need to change most of your user accounts to Read licenses after the DB copy. Also the entitlements for user licenses mentioned by Davin only apply to the Blue pricing model. If you happen to be on the Legacy/Green model that is not the case as licenses are purchased for production use at one cost and for development use at a lower cost so they are not interchangeable. -Rick From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Davin Lindner-Green Sent: Wednesday, February 11, 2015 2:38 PM To: arslist@ARSLIST.ORG Subject: Re: DB Copy Issue ** A second vote to use the Remedy Restore Tool, plus some hints on licenses. In version 7.x they are stored in the database so will get copied along with everything else. Also, if you are on version 7 or newer the only license key that is tied to your Host ID (your hardware) is the AR Server license. You should add the AR Server license from DEV to your PROD environment before you copy the database. That way it will be there when you start up DEV post-copy. In terms of entitlement, my understanding is that you are entitled to use AR User Fixed licenses on any server in your environment as long as the users are the same named users (which they will be after database copy). AR User Floating licenses may be tied to a specific server (although not enforced by the license key mechanism) so you might have to adjust that number after a copy. However this depends on which licensing model you are under with BMC so you might not have to adjust anything in terms of licensing. Last item, you may want to disable the email engine and any external integrations on DEV before the copy, so you don't accidentally send duplicate email notifications or trigger integration actions from DEV. Also, if you are using custom Remedy applications at all, any server references you may have included for integrations and the like won't be detected and changed by Remedy Restore Tool. It is oriented primarily at ITSM and ARS core forms only. Thanks Davin On Feb 11, 2015, at 3:27 PM, Rick Westbrock mailto:rwestbr...@24hourfit.com>> wrote: ** Check out the Remedy Restore Tool by Carl Wilson (http://communities.bmc.com/docs/DOC-7710<https://communities.bmc.com/docs/DOC-7710> ), it handles nearly all the deprodification steps required when copying a production database to a non-prod environment. I normally adjust the licenses manually myself but it depends on your version of ARS. If you are on version 7 or newer (I think) it’s quite easy to just change the numbers in the console; if you are on 6.x or older it will be a lot more painful due to the old licensing model. -Rick From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Scott Hallenger Sent: Wednesday, February 11, 2015 2:14 PM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: DB Copy Issue ** Wondering if anyone can offer some advice on this issue. Can I copy our production db to our dev server as an means of syncing dev to production. The end goal being to make my dev look just like production. Our dev server does not have the same number of licenses as production naturally. Is this something that can be done with a basic db copy. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "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"
Re: DB Copy Issue
A second vote to use the Remedy Restore Tool, plus some hints on licenses. In version 7.x they are stored in the database so will get copied along with everything else. Also, if you are on version 7 or newer the only license key that is tied to your Host ID (your hardware) is the AR Server license. You should add the AR Server license from DEV to your PROD environment before you copy the database. That way it will be there when you start up DEV post-copy. In terms of entitlement, my understanding is that you are entitled to use AR User Fixed licenses on any server in your environment as long as the users are the same named users (which they will be after database copy). AR User Floating licenses may be tied to a specific server (although not enforced by the license key mechanism) so you might have to adjust that number after a copy. However this depends on which licensing model you are under with BMC so you might not have to adjust anything in terms of licensing. Last item, you may want to disable the email engine and any external integrations on DEV before the copy, so you don't accidentally send duplicate email notifications or trigger integration actions from DEV. Also, if you are using custom Remedy applications at all, any server references you may have included for integrations and the like won't be detected and changed by Remedy Restore Tool. It is oriented primarily at ITSM and ARS core forms only. Thanks Davin > On Feb 11, 2015, at 3:27 PM, Rick Westbrock wrote: > > ** > Check out the Remedy Restore Tool by Carl Wilson > (http://communities.bmc.com/docs/DOC-7710 > <https://communities.bmc.com/docs/DOC-7710> ), it handles nearly all the > deprodification steps required when copying a production database to a > non-prod environment. I normally adjust the licenses manually myself but it > depends on your version of ARS. If you are on version 7 or newer (I think) > it’s quite easy to just change the numbers in the console; if you are on 6.x > or older it will be a lot more painful due to the old licensing model. > > -Rick > > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Scott Hallenger > Sent: Wednesday, February 11, 2015 2:14 PM > To: arslist@ARSLIST.ORG > Subject: DB Copy Issue > > ** > Wondering if anyone can offer some advice on this issue. Can I copy our > production db to our dev server as an means of syncing dev to production. The > end goal being to make my dev look just like production. Our dev server does > not have the same number of licenses as production naturally. Is this > something that can be done with a basic db copy. > _ARSlist: "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"
Re: DB Copy Issue
Check out the Remedy Restore Tool by Carl Wilson (http://communities.bmc.com/docs/DOC-7710<https://communities.bmc.com/docs/DOC-7710> ), it handles nearly all the deprodification steps required when copying a production database to a non-prod environment. I normally adjust the licenses manually myself but it depends on your version of ARS. If you are on version 7 or newer (I think) it’s quite easy to just change the numbers in the console; if you are on 6.x or older it will be a lot more painful due to the old licensing model. -Rick From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Scott Hallenger Sent: Wednesday, February 11, 2015 2:14 PM To: arslist@ARSLIST.ORG Subject: DB Copy Issue ** Wondering if anyone can offer some advice on this issue. Can I copy our production db to our dev server as an means of syncing dev to production. The end goal being to make my dev look just like production. Our dev server does not have the same number of licenses as production naturally. Is this something that can be done with a basic db copy. _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"
DB Copy Issue
Wondering if anyone can offer some advice on this issue. Can I copy our production db to our dev server as an means of syncing dev to production. The end goal being to make my dev look just like production. Our dev server does not have the same number of licenses as production naturally. Is this something that can be done with a basic db copy. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
