Σχόλια 0

Το κείμενο του εγγράφου

Upgrading fromSurround SCM 2008 and EarlierSurround SCM2009 and later includes RDBMS support and label enhancements,both of which requireuser intervention to upgrade.The following information is provided for administrators who are upgradingthe Surround SCMServer.If you need to performa new installation or upgrade the Surround SCMClient,see the Surround SCMInstallation Guide (www.seapine.com/documentation).FAQsDo I have to use an RDBMS database?Yes.The old proprietary database format is no longer supported.Why did the database format change?An RDBMS gives you more control over Surround SCMperformance,where databases are stored,andhow they are managed.You can leverage your existing database administration processes and usestandard database tools for tasks such as data analysis,manipulation,and backups.What is stored in the database?All Surround SCMdata except the RDBMS server connection information.Each Surround SCMServerhas a server database,which is a set of tables that store user,security group,workflow,customfield,and TestTrack integration connection information.Each mainline branch has a mainline database,whichis a set of tables that store all file information.What RDBMS can I use?Currently,PostgreSQL is the default database type for all platforms.Oracle is also supported on allplatforms and Microsoft SQL Server is supported on Windows.See the Surround SCMRDBMS Supportknowledgebase article (www.seapine.com/kb/questions/1497) for supported platforms and versions.I do not have an RDBMS.How do I install one?Surround SCM2009 and later includes installation files for PostgreSQL,which is an open source,cross-platformRDBMS.You can install the PostgreSQL database services when you upgrade Surround SCM.The database service configuration is handled for you.Use PostgreSQL if you do not have databaseadministration experience.Seapine does not provide support for installing,configuring or maintaining Oracle or SQL Server.I have an existing PostgreSQL,Oracle,or SQL Server installation.How do I use it forSurround SCMdata?During installation,you can add connection information for an existing RDBMS.The Surround SCMServer can automatically add the required database tables when the server starts for the first time.Seethe Surround SCMInstallation Guide (www.seapine.com/documentation) for information.How do I migrate my existing Surround SCMdata to RDBMS format?The server database is automatically upgraded to RDBMS format the first time you start the SurroundSCMServer after installation.You must upgrade mainline branches to RDBMS format in the SurroundSCMClient before users can access them.See Upgrading mainline branches,page 4.1Before instal l ationIs my existing data affected during the data migration?No,except some fields with unlimited sizes in Surround SCM2008 and earlier now have size restrictionsdue to the database format change.Name fields,such as file and repository names,have a 255 characterlimit.Description fields have a 1024 character limit.If field values exceed the database size limit,they aretruncated during the upgrade.Why are labels affected by the upgrade?Surround SCM's labeling feature was completely rewritten to provide many enhancements.Labelscreated in earlier versions were applied to the file version in all branches.Now,you can create labels for amainline branch or a specific branch.Labels are not automatically applied to files and must be manually upgraded before they can be used.Upgrading legacy labels allows you to choose the existing labels to import and the branches to applythemto.See Upgrading legacy labels,page 5.How long does it take to upgrade?The time it takes to performan upgrade depends on the size of your existing installation.The majority oftime is spent upgrading mainline branches,which may take a few minutes to an entire day depending onthe database size and number of files.You upgrade mainline branches individually after installation,soyou can choose when to upgrade themdepending on when users need access to the files in the mainline.Before installationPerformthe following tasks before you upgrade to Surround SCM2009 or later.Review the Surround SCM Server system requirementsThe Surround SCMServer SystemRequirements knowledgebase article(www.seapine.com/kb/questions/1173) includes minimumsystemrequirements and recommendedsystemconfigurations for optimal server performance.Choose an RDBMS type and configurationYou need to decide which type of RDBMS database you want to store the Surround SCMServer andmainline databases in.All the database tables are installed in a single RDBMS database.Oracle,PostgreSQL,and SQL Server are supported.The database configuration you use depends on your installation and environment.At any time,you canconvert the RDBMS type or location for the server or mainline databases or distribute mainline branchesacross multiple RDBMS database instances.If you do not know how you want to configure thedatabases,use the default PostgreSQL installation.Check the RDBMS server securityReview the operating systemand database firewall settings on the RDBMS server to make sure theSurround SCMServer databases are secure.Some RDBMS servers must be configured to allow remotecomputers to access databases.2During instal l ationRun the Surround SCM Analyze UtilityWe strongly recommend that you run the Surround SCMAnalyze Utility to analyze and repair any dataintegrity issues in the Surround SCMServer database.Note:Before upgrading fromSurround SCM2008.1.x,it is strongly recommended that you run thelatest Surround SCM2008.1.x Analyze Utility to address any database issues.The most recentversion of the utility can be downloaded fromSeapine's Surround SCMUpgrades web page(www.seapine.com/scmupgrades).Back up databasesYou should always back up the Surround SCMServer database,mainline database,and Seapine LicenseServer database before installation.If you upgrade fromSurround SCM5.x or later,the server database is automatically upgraded to SurroundSCM2008 format before it is upgraded to RDBMS format.You cannot revert back to the flat file databaseformat after upgrading,which makes it important to have a backup copy of the database.Plan for future database backupsYour Surround SCMbackup strategy will no longer work after the upgrade because the database formatand location are different.Make sure you create a new backup strategy before upgrading.During installationDuring the installation,you are prompted to select the RDBMS database type.See the Surround SCMRDBMS Support knowledgebase article (www.seapine.com/kb/questions/1497) for supported platformsand versions.About PostgreSQLPostgreSQL is the default database type,which you can use if you do not have an existing RDBMSinstallation.The PostgreSQL database services can be installed during the Surround SCMinstallation.The default database,and usernames and passwords for the database and database service,areautomatically created.For reference,the default service account name is postgres and the password isP0stgreSQL.The default database username is seapine and the password is s34p1n3.We stronglyrecommend changing the username and password during installation,but you can use PostgreSQLcommands to change the credentials at a later time.Refer to the PostgreSQL documentation forinformation.If have an existing PostgreSQL installation,you are prompted to enter the connection information anddatabase username and password.The Surround SCMtables are created in the database when theSurround SCMServer starts and connects to the database for the first time after installation.3After instal l ationAbout OracleIf you use Oracle for the Surround SCMdatabase,you must have an existing Oracle installation.Makesure you have the database connection information and database username and password beforeupgrading.The Surround SCMtables are created in the database when the Surround SCMServer startsand connects to the database for the first time after installation.About SQL ServerIf you use SQL Server for the Surround SCMdatabase,you must have an existing SQL Serverinstallation.Make sure you have the database connection information and database username andpassword before upgrading.The Surround SCMtables are created in the database when the SurroundSCMServer starts and connects to the database for the first time after installation.After installationPerformthe following steps after installation.1.Start the Seapine License Server and Surround SCMServer.The Surround SCMServer database isautomatically upgraded when the server starts.2.Upgrade mainline branches to RDBMS format.You must upgrade mainline branches before userscan access them.See Upgrading mainline branches,page 4.3.Optionally upgrade labels.If you use labels to mark related file versions,you must upgrade thembefore users can apply them.See Upgrading legacy labels,page 5.Upgrading mainline branchesMainline branches created in Surround SCM2008 or earlier must be upgraded to RDBMS format inSurround SCM2009 or later.Mainline branches that require upgrading before they can be used areappended with'non-RDBMS database'.Keep the following in mind.n A database cannot include two mainline branches with the same name.If the destination databasealready includes a mainline with the same name as the mainline you are upgrading,you must select adifferent destination database.n During the upgrade,Surround SCMattempts to match users and security groups in the mainlinebranch to users and groups on the Surround SCMServer.If matching names are found,SurroundSCMassumes they are the same user or group.If users in the mainline do not exist on the server,they are created without assigned licenses.If security groups in the mainline do not exist on theserver,they are created without any security commands enabled.Surround SCMalso tries to matchTestTrack connection information.n If you are upgrading a mainline branch fromSurround SCM5.x or earlier,you are prompted toautomatically upgrade the branch to Surround SCM2008 format before it is upgraded to RDBMSformat.n After mainline branches are upgraded,you must manually upgrade labels.See Upgrading legacylabels,page 5.Note:Back up the mainline branch directory before you upgrade it.4After instal l ation1.Select the mainline branch you want to upgrade and choose Tools > Administration > UpgradeMainline Branch.2.Click Yes when you are prompted to upgrade the mainline branch.3.Select the Destination database for the upgraded mainline branch and click OK.Note:Only select the Ignore errors during upgrade option if you have already used theSurround SCMAnalyze Utility and were unable to repair issues causing errors.The upgrade information is sent to the Surround SCMServer for validation. n If the validation succeeds,the upgrade starts and the Upgrade Status dialog box opens.n If the destination database does not include any Surround SCMtables,you are prompted to createthem.n If the validation fails,the Test Connection dialog box opens with error information.You can copy andpaste the text into an email or text file and email it to your DBA for help.Note:The old database is not deleted fromthe original location during the upgrade.You may want tomanually delete the directory after verifying the branch is successfully upgraded to RDBMS format.Upgrading legacy labelsWhen you upgrade fromSurround SCM2008 and earlier,labels are not automatically applied to files andmust be manually upgraded before they can be used.Labels created in earlier Surround SCMversions were applied to the file version in all branches.Now,youcan create labels for a mainline branch or a specific branch.Upgrading legacy labels allows you to choosethe existing labels to import and the branches to apply themto.Note:The timestamp and comments fromexisting labels are copied to the label history during theupgrade.1.Select the mainline branch that includes the legacy labels to upgrade and choose Tools >Administration > Upgrade Legacy Labels.2.Select the label you want to upgrade and click Upgrade.To select multiple labels,Ctrl+click eachlabel.3.Select the branch to apply the label to in the Upgrade Legacy Labels dialog box and click OK.Toinclude snapshot branches in the branch list,select Show snapshot branches.To select multiplebranches,Ctrl+click each branch.If you select a branch that did not previously include any files with the label applied,the label is notapplied to any files.Tip:The File count field displays the total number of files the label can be applied to.Comparethis number to the File Count column for each branch to determine the branches to apply the labelto.Typically,you will apply the label to the branch with the highest file count because it is a goodindicator of the branch the label is intended for.You may also apply the label to other branchesdepending on how it is used.File count information not displayed if you are upgrading multiplelabels.5