1 © 2006 SolidWorks Corp. Confidential. Clustering  SQL can be used in “Cluster Pack” –A pack is a group of servers that operate together and share partitioned data. They are called a pack because they work together to manage and maintain services.  Server cluster Nodes –Server cluster nodes can be either active or passive.  Active Node –It is actively handling requests  Passive Node –It is idle, on standby waiting for another node to fail.  PDMWorks Enterprise is “clusterable”

2 © 2006 SolidWorks Corp. Confidential. Clustering  PDMWorks Enterprise can be configured in a Active/Passive configuration  Important: Individual cluster components added together do not represent an approved system for failover clustering. Only systems purchased as a cluster solution and listed in the cluster group are approved.  Special hardware compatibility testing is necessary when you implement a failover server cluster on a Storage Area Network (SAN).  References: – – –

3 © 2006 SolidWorks Corp. Confidential. Notes about Clustering  Customers typically use the failover clustering with Microsoft SQL Server rather than clustering the archive server(s).  Bear in mind that since SolidWorks Corp. does not test PDMWorks Enterprise in clustered environment, we at SolidWorks do not support this environment officially –There are many ways to setup a cluster, and it would be difficult for R&D and QA to cover all the scenarios  For the archive servers, you can only have one archive server per unique file vault –You need to set the archive server service to not automatically start on the redundant server system (i.e. set the service to manual). –The cluster management tool in Windows Server 2003 you should specify what services you want to start automatically on the failover server in case the master goes down, and the ‘PDMWorks Enterprise Archive Server’ service should be one.  Clients connected to one of the servers might need to restart/relogin if the server goes down in order to re-establish connection with the failover server.

4 © 2006 SolidWorks Corp. Confidential. Partitions  The NTFS partition could be as follow for a High Availability setup: C: Windows OS (Raid 1) D: Pagefile and SQL Application (Raid 1) L: SQL Logs (Raid 1) T: SQL Tempdb (Raid 5) V: SQL Database (Raid 10) Z: Backup temporary storage (Raid 5) (SQL writes backup to Z: and Z: is backed up to tape)  The NTFS partition could be as follow for a less expensive setup: C: Windows OS (Raid 1) D: Pagefile and SQL Application, Logs & Tempdb (Raid 1) V: SQL Database (Raid 5) Z: Backup temporary storage (SQL writes backup to Z: and Z: is backed up to tape)  The transaction Logs and the database should be on different I/O bus.  The boot and system partition (usually the C:\ drive) is where the OS files are installed. It should be ~15 GB or larger (For 64bit OS we recommend 20GB - A Standard Image is around 10GB in size for C Drive).  SQL installation folder is only 2GB but you should allow more room for logs and temporary files.  The Database size will be growing with the number of document and metadata stored in the vaults.  Please consider this information as guidelines, this should be verified by a certified SQL professional.