July 2, 2012 at 7:29 am
I had a couple questions I encountered over the weekend when I tried migrating the database from the old database cluster 10.15.1.124 to the new cluster 10.15.1.174. The first one, during the configuration I know it it’s a good idea to change from the c: drive to another drive to break up the install and the backup and configuration and I apologize since it’s been a while since I’ve run through the configuration of SQL server 2008 r2, but it should, I thought, let you choose which volumes for data, logs etc… The reason I’m asking is because when I went to restore the database it was only letting me setup on the E: drive only and I couldn’t separate out the data and log files to separate volumes.
The second thing was when connecting from the dmz webservers,
Pinn-XPORT1 172.21.1.26
Pinn-XPORT2 172.21.1.27
SIS-XWEB1 172.21.1.20
SIS-XWEB2 172.21.1.23
I was under the impression the new cluster like the old cluster would be listening for external traffic on port 8017, like the old one. I know on the new cluster, for internal traffic it listens on port 1433 for all sql traffic but wanted to check to see if I should request this one to be listening for external traffic as well or if there was a different port that I needed a request to be opened for.
July 2, 2012 at 8:32 am
surma.sql (7/2/2012)
I had a couple questions I encountered over the weekend when I tried migrating the database from the old database cluster 10.15.1.124 to the new cluster 10.15.1.174. The first one, during the configuration I know it it’s a good idea to change from the c: drive to another drive to break up the install and the backup and configuration and I apologize since it’s been a while since I’ve run through the configuration of SQL server 2008 r2, but it should, I thought, let you choose which volumes for data, logs etc… The reason I’m asking is because when I went to restore the database it was only letting me setup on the E: drive only and I couldn’t separate out the data and log files to separate volumes.The second thing was when connecting from the dmz webservers,
Pinn-XPORT1 172.21.1.26
Pinn-XPORT2 172.21.1.27
SIS-XWEB1 172.21.1.20
SIS-XWEB2 172.21.1.23
could you explain a little more clearly please
surma.sql (7/2/2012)
I was under the impression the new cluster like the old cluster would be listening for external traffic on port 8017, like the old one. I know on the new cluster, for internal traffic it listens on port 1433 for all sql traffic but wanted to check to see if I should request this one to be listening for external traffic as well or if there was a different port that I needed a request to be opened for.
what port did you configure in sql server configuration manager??
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply