Novell Brainshare 2010 Amsterdam

1. Migrating Novell ® Open Enterprise Server from NetWare ® to Linux Chris Beckett and Volkmar Ruzicka Technical Consultant / Technical Consultant NDS8 / NetAgents [email_address] / [email_address]

3. Lab Scenario / Migration Options

4. Tenets of a Successful Consolidation

5. Pre-Migration Checklist / Pre-Flight Checks

6. Building The Target Server / NetWare ® vs Open Enterprise Server Linux

7. Services Ported To Linux / Managing Your Open Enterprise Server

8. Linux User Management – When/Why?

9. Using The Migration Tool

10. Configure New Services on Open Enterprise Server 2

11. Wrap Up / Question and Answer

12. About Your Presenters

14. Over 14 years Novell ® products experience

16. Over 22 years Novell products experience

17. Specialised in GroupWise, NOESL Clustering BlackBerry Enterprise Server

18. Lab Scenario / Migration Options

20. Tree Certificate Authority

21. SYS and DATA NSS volumes

23. iPrint

24. NetStorage

25. QuickFinder

26. DNS/DHCP

27. Novell Storage Services ™ and eDirectory ™ (of course!)

28. Lab Scenario FS1 NetWare ® 6.5 SP8 eDirectory ™ 8.7 172.16.1.1 FS2 Open Enterprise Server 2 SP2 eDirectory 8.8 172.16.1.2

29. Migration Options

31. Consolidation – many to one server

32. GUI console with step by step guide

33. Installed with Open Enterprise Server 2 SP2, no separate download required

35. SCMT only supports NetWare ® /NT/2000/2003 to NetWare

37. GUI makes the process easy to follow, with options to re-do steps, should they fail

40. Familiarity with the Open Enterprise Server 2 installation process

41. Tenets of a Successful Consolidation

43. Step 2: Plan Your Migrations

44. Step 3: Create a Server Build Process

45. Step 4: The First Server

46. Step 5: All Other Servers

47. Step 6: Cleanup and Decommission

50. Review your Time Synchronisation, check all Servers

51. Are all Network Printers at least NDPS or iPrint connected

52. Clean up stale login scripts

53. Delete stale data

57. Start with utility servers that have redundancy (replica, ldap, etc.)

58. Move smaller work group server next as a pilot

59. SLP DA services should be last to move

60. Finish with critical file and print servers

62. Volume names and paths likely changed if consolidating

63. Export all current login scripts to text files for review

64. Change of Home-Dir

66. Now is the time for the scripted install with auto-update for future

71. Prepare a Linux User Management (LUM) design

74. Configure Linux User Management (LUM)

75. Patch the server to your standard patch level (eg. ZENworks ® Linux Management)

76. Use it for your LDAP server during subsequent server installs (using DNS for LDAP service)

78. Get used to your backup/restore software on the new platform

80. Configure Linux User Management (LUM)

81. Patch the server to your standard patch level (eg. ZENworks ® Linux Management)

82. Install all desired services including tape backup, anti-virus, monitoring, etc

83. Test all services before users are moved and affected

84. Did you backup just before migration starts?

85. Execute the migration with your checklist for each action

86. Have a subset of users from the business available for post migration tests

87. Disable access to the migrated services and data

90. Verify that ALL services are not used (ntp, dns, dhcp, slp, rsync, ...) by other servers or any client

92. Retired NDPS, iFolder2.x, ...

93. Pre-migration Checklist

95. Trustee backups on the source server

96. Identify tree CA requirements

97. License codes from Customer Center?

101. Building the Target Server

104. SLES10 SP2 + OES2 SP1

106. Slightly different installation than OES1, but more intuitive

109. Novell ® file share? Novell Storage Services ™

110. Consider partitioning /boot, /var, /tmp, /swap, / as a minimum

111. Use LVM Logical Volume Manager to be flexible

112. If it is a ZENworks ® Configuration Management Primary server, /var partition is a must

113. If partitions will rapidly grow in size, isolate them from other parts of the disk to avoid problems later

116. Pre-migration server pattern installed (mandatory)

117. gcc and kernel-sources packages for VMware Tools

119. Easier to remove at the start than later in the process when dependency chains make this difficult

121. NSS volumes on disk 1 Disk 0 SYS DATA Disk 0 Disk 1 / DATA

123. NetWare ® vs. Open Enterprise Server Linux

126. Critical security updates only

127. Knowledgebase / forums / documentation / existing patches

128. Transitionary step only !

130. Most code executes in protected memory, not all NLMs will allow this, but those that do must be configured appropriately

131. Technically, NLMs run with full server privileges

132. Linux daemons are similar to NLMs, but can be set to run as a specific (or “service user”) user to limit damage in case of hacking/software issue

134. ZENworks ® Configuration Management

136. .exe = Could be executable on Linux, could be spreadsheet for all we know!

138. RWX for POSIX (R=Read, W=Write, X=eXecutable)

140. Default file system in SUSE ® Linux Enterprise Server 10

142. Good for small files, journalling file system and good all purpose file system for use in most scenarios

143. Default file system in SUSE ® Linux Enterprise Server 11

144. Scalability issues with many files in a directory (>5000, without htree)

146. Rich feature set, including data shredding, snapshot, compression, quotas, salvage etc.

149. Consider noatime and nodiratime mount commands to improve throughput

150. Turn off functionality you don't explicitly need!

151. Services Ported to Linux

152. Services Ported To Linux Novell Storage Services ™ NetStorage QuickFinder IManager and ConsoleOne ® DNS / DHCP Novell Client ™ NCP ™ Access eDirectory ™ AFP iPrint Apache Web Server Backup / Restore (SMS) CIFS / DFS iFolder* Novell Cluster Services ™

155. Free 20 user starter pack for Novell Teaming is available for download

158. Managing Your Open Enterprise Server

160. Standard snapins include users and storage

161. Non OES2 product snapins include Groupwise ®

163. Reduces learning curve for NetWare administrators

164. Functionally equivalent to NetWare, with same plug-ins

167. Load/unload NLMs

168. Stop/start/restart services (GroupWise ® MTA F6, for example)

169. Mount/dismount/check/repair/create volumes

172. Same functionality as above

176. /etc/init.d/ndsd start

177. /etc/init.d/ndsd status

178. On Linux, we can also query the status of a service

180. rcgrpwise stop

182. /var used for variable length files, generally log files, but other data may also be pathed here, such as the ZENworks ® Configuration Management Content Repository

183. /tmp used for temporary files

184. /home used for Linux user home areas ( not eDirectory ™ users)

185. /bin and /sbin used for binary executables

186. /media used as a temporary mount point for DVD/USB etc

187. /etc used for configuration files for server and services

188. /srv used for services such as WWW, FTP, Tomcat

189. /proc used for server processes

191. /boot is used for boot files

192. /lib is used for shared libraries

193. /mnt is used for temporary mount points

195. NFS storage on another server on the network

196. ISO file on a server (handy for installing software!)

198. Init 1 – single user only, no network or services (aka “safe mode”)

199. Init 2 – multiuser access, no network or services

200. Init 3 – multiuser access, networking, services, no GUI

201. Init 4 – unused/user definable

202. Init 5 – multiuser access, networking, services, GUI, default SLES runlevel

205. NCP ™

206. iPrint

207. Novell Cluster Services ™

208. AFP/CIFS/NFS

211. /var/opt/novell/log/ncpserv.log

212. /var/opt/novell/log/ncpcon.log

213. /var/opt/novell/log/iprint/ipsmd.log

214. /var/opt/novell/log/iprint/idsd.log

216. /var/opt/novell/log/zenworks (ZCM)

218. NSSMU at the server console (must be root)

220. NSS volumes provide compression, quotas and all the good stuff you get on NetWare currently

222. SYS volume on an OES2 Linux server is an NCP volume

224. When you want compression, quotas, salvage etc.

225. When you want rich permission sets

226. Physical disk should be separate from OS disk, so we don't have to configure EVMS

228. Can be useful to expose part of the Linux file system to Novell Clients

229. For example, an installation point (GroupWise ® SDD)

230. Linux User Management - When/Why?

232. Linux has it's own local database of users, much like Windows in some respects

233. Linux native services such as FTP, rlogin, SSH etc assume the presence of a local user, or configured authentication source such as LDAP, NIS etc.

234. LUM allows eDirectory ™ users to access Linux servers using their current eDirectory username and login credentials

236. iPrint, Samba

237. Defaults generally work quite well

238. Using The Migration Tool

240. Can be accessed via YaST menu or by running miggui from a command prompt/terminal window

243. Many migration scenarios involve a one to one migration of data and services away from NetWare ®

246. Remember, data is copied , so you lose nothing!

248. Configure New Services In Open Enterprise Server 2

251. iFolder 2.x had one to one relationship with user and server

252. iFolder 3.x allows folders to be shared with other iFolder users

253. Re-written in Mono ® , so Linux only

254. Clients for Mac, Linux and Windows XP/Vista/7

255. iFolder data store migration utility available in YaST

256. Can be clustered, if required

258. Server volumes have shadow volumes defined

259. Depending in the policy, files can be transparently moved from the “main” volume to the shadow volume

260. For example, policy states MP3's are to be stored on the shadow volume, along with files not accessed since 2008

261. Free in OES, perhaps on of the best app in the whole suite Saves a lot of money!

262. Allows backup times to be reduced to keeping stale data away from the live data

263. Prevents old/non-mission critical data from clogging up expensive storage

265. Can apply policies to both Novell Storage Services ™ (NSS) and NCP ™ volumes

266. Decide on how you want to manage your data before you think about how you want to configure DST policies

267. Use the inventory functionality available to you to find out what is on your NSS volumes before you decide on your DST policies

268. Don't forget a Novell Client™ is installed on the OES2 Linux server, so don't be afraid to use that to check if your policies are working, you don't need a Windows client as such

269. Wrap Up / Question and Answer

271. Build, test, break, rinse, repeat

273. Remember to catalogue all of your apps, including GroupWise ® , ZENworks ® , Novell Identity Manager etc. Will they run on Linux? Third party products, GWAVA, anti-virus etc.

275. Windows 7 clients look for OpenSLP Directory Agents

276. Consider DNS names in login scripts for faster script processing

278. TID 7000901 - Troubleshooting OES2 Novell ® iPrint Migration Tool

279. TID 7004455 - iPrint Migration Best Practices

280. TID 3150078 - Updates Catalog Missing after Registration of OES2

281. TID 3503915 - LUM Enabling Pure-ftpd

282. TID 7004574 - OpenSLP vs. NetWare ® SLP

283. TID 7001449 - eDirectory ™ not registering with SLP

284. TID 7001767 - Troubleshooting data migrations with migfiles from Netware 6.5 to OES Linux

285. TID 3884721 OES2 Novell DNS Install Error: Failed to configure DNS server

286. TID 10085156 DNS Administration fails after Migration

288. If you see us in the hallway, to come and say Hello!

290. Don't forget the EMEA Summit in Vienna in November, even more hands on labs with the Open Horizons experts!

291. Have a look on http://www.open-horizons.net/training for your knowledge upgrade

292. http://www.open-horizons.net for further information

294. Unpublished Work of Novell, Inc. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.