Forums
Administration & IT
Moving Servers
Discussions
Resources
Mentions
Tags
Search the Community
More
Cancel
New
Replies
2 replies
Subscribers
338 subscribers
Views
18 views
Users
0 members are here
Related
Moving Servers
Jeanne DeVore
$organization
over 15 years ago
Good morning. I'm just looking for some reassurance here. I'm about to upgrade all my Tessitura servers. For those who have done it, do you have any advice? Did you cut over to all your new servers (production, cc, seat, report, api) at once, or did you do it in stages? Are there any "gotchas" I need to be aware of? I know I'll need to be completely down while I copy the database from one machine to the next, so I'm scheduling that for the middle of the night. FWIW, my production server will remain a stand-alone machine, but the others are being virtualized, as is my Test environment.
Thanks for any and all suggestions!
Jeanne DeVore
Technology Manager
Chicago Shakespeare Theater
jdevore@chicagoshakes.com
312 595-5603
www.chicagoshakes.com
Nancy Sheleheda
$organization
over 15 years ago
Hi Jeanne,
We did the same thing last year. I remember being surprised to learn that TranScend requires a unique key for the database server it resides on. I thought as long as I had only one Transcend running for that license, it would be okay. Wasn't... You'll need to contact Intrix ahead of rime with the specs for your new server and ask them for a key. And since they're support line is only open M-F from 9 am to 9 pm EST, you would be out if luck if you discovered the problem in the middle of the night.
Also, we did cut over all at once. We had our new environment in a colocated facility, which we had up and running weeks ahead for testing. When we cut over, we only had to be down long enough to drive the .bak over and restore.
Good Luck!
Nancy Sheleheda
Sent from my iPhone
On Oct 20, 2010, at 11:51 AM, "Jeanne DeVore" wrote:
> Good morning. I'm just looking for some reassurance here. I'm about to upgrade all my Tessitura servers. For those who have done it, do you have any advice? Did you cut over to all your new servers (production, cc, seat, report, api) at once, or did you do it in stages? Are there any "gotchas" I need to be aware of? I know I'll need to be completely down while I copy the database from one machine to the next, so I'm scheduling that for the middle of the night. FWIW, my production server will remain a stand-alone machine, but the others are being virtualized, as is my Test environment.
>
> Thanks for any and all suggestions!
>
>
> Jeanne DeVore
> Technology Manager
> Chicago Shakespeare Theater
> jdevore@chicagoshakes.com
> 312 595-5603
> www.chicagoshakes.com
>
>
> This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums.
>
> In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Cancel
Jeanne DeVore
$organization
over 15 years ago
Wow, thanks for the heads-up on that one. I'm sure I'd have missed that!
Jeanne
-----Original Message-----
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nancy Sheleheda
Sent: Wednesday, October 20, 2010 12:12 PM
To: Jeanne DeVore
Subject: Re: [Tessitura Technical Forum] Moving Servers
Hi Jeanne,
We did the same thing last year. I remember being surprised to learn that TranScend requires a unique key for the database server it resides on. I thought as long as I had only one Transcend running for that license, it would be okay. Wasn't... You'll need to contact Intrix ahead of rime with the specs for your new server and ask them for a key. And since they're support line is only open M-F from 9 am to 9 pm EST, you would be out if luck if you discovered the problem in the middle of the night.
Also, we did cut over all at once. We had our new environment in a colocated facility, which we had up and running weeks ahead for testing. When we cut over, we only had to be down long enough to drive the .bak over and restore.
Good Luck!
Nancy Sheleheda
Sent from my iPhone
On Oct 20, 2010, at 11:51 AM, "Jeanne DeVore" wrote:
> Good morning. I'm just looking for some reassurance here. I'm about to upgrade all my Tessitura servers. For those who have done it, do you have any advice? Did you cut over to all your new servers (production, cc, seat, report, api) at once, or did you do it in stages? Are there any "gotchas" I need to be aware of? I know I'll need to be completely down while I copy the database from one machine to the next, so I'm scheduling that for the middle of the night. FWIW, my production server will remain a stand-alone machine, but the others are being virtualized, as is my Test environment.
>
> Thanks for any and all suggestions!
>
>
> Jeanne DeVore
> Technology Manager
> Chicago Shakespeare Theater
> jdevore@chicagoshakes.com
> 312 595-5603
> www.chicagoshakes.com
>
>
> This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums.
>
> In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums.
In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Cancel