PDXpert PLM Software
On-line Help Guide
This help topic describes the current PDXpert PLM release. Earlier releases may be different. To view your release's version of this topic, open PDXpert and press the F1 key or select the Help menu.
Back up the database and library
You should back up your database and library (file attachments) frequently to insure against data loss.
Microsoft recommends backing up a SQL Server database to an internal fixed drive. The operation may fail—possibly without any warning—if you select a compressed, network-mapped, or external volume. Make sure that a backup that's saved to the selected device can be restored.
The selected backup location must have sufficient free disk space for the backup file. The server disk also must have free disk space to build the temporary backup file.
Do not add files to the server's \Data folder or its subfolders. Unrecognized files may interfere with proper operation or may be deleted without warning. If the folder has been moved, the actual name may not be \Data but perhaps \PLM-Data, \PDXpert, or something else.
Microsoft SQL Server databases are not backwards compatible. A database backup can only be restored into the same, or higher, SQL instance.
For example, SQL Server 2016 (version 13.0) can restore a SQL Server 2016 (13.0) database, as well as upgrade an older SQL Server 2014 (version 12.0) database. After upgrading, the database can't be used with the older SQL Server.
SQL Server can't "downgrade" a higher-level database backup; for example, restoring a backup file from SQL Server 2017 (version 14.0) into an earlier SQL Server 2016 (13.0).
PDXpert releases are not backwards compatible. A backup made by a specific PDXpert Server release can only be restored into the same, or higher, PDXpert Server. If it's restored into a higher release, the backup file is automatically upgraded to the PDXpert Server's release.
Using the manual backup tool §
On the PDXpert Application Server window:
Click on Manage.
In the Maintenance area, click the button to open the Save Backup As dialog.
The default backup format is Database with Library (*.pdxz). This is a simple way to save your database and all library files into a single compressed ("zip") file. The file contains the SQL Server backup (.BAK) file, an XML manifest file, and the library file attachments.
Files that are downloaded from the internet or compressed in other operating systems (like Linux or MacOS) may not work well in Windows. Before saving a compressed file attachment in PDXpert, always expand and then re-compress these files using Windows File Explorer or another Windows compression tool. See the File tab help topic. Or, use only the Database without Library (*.bak) backup format.
The PDXZ format is convenient as you're starting out, but it's intended only to support smaller systems. Use a commercial backup solution before the \Database and \Library subfolders reach 1GB. See Automating your backup, below.
The alternative backup format is Database without Library (*.bak). This saves the "raw" SQL Server database without including the library files. This is a much faster backup, and is useful for maintenance, but is incomplete without the file attachments.
To have a complete backup, you must use Windows or a backup tool to copy all of your library files that are stored in the \Library subfolder.
Copy the \Library folder contents after the database backup is done.
If more than 2GB of files are in the \Database and \Library subfolders, you can only save the SQL Server database without the library files. This will be shown by the DATABASE ONLY - NO LIBRARY (*.bak) format type.
Choose the location where you want your backup file to be saved, and click thebutton.
The backup database file does not carry any security limits, and includes your software license key. It may be loaded into a different PDXpert instance, and the database element can be extracted and loaded into any SQL Server database engine. Secure your backups to prevent unauthorized access to archival data.
The backup file name includes information about the correct SQL Server version (like ...-15_0.bak). Before the backup database is restored, the file name's SQL Server version is compared to the installed instance to warn of incompatibility.
The PDXZ file is constructed in the \Temp folder. Temporary files are normally deleted after the PDXZ file is transferred to the selected location. If a backup error (such as disk full) prevents automatic deletion, all files can be manually deleted after all users exit the PDXpert client application.
To restore the backup, see the Restore data from a backup help topic.
Automating your backup §
Your server backup software must be compatible with SQL Server. Consumer-grade backup utilities may not be capable of correctly backing up a SQL Server database, and can even damage or delete your original database. Search the web for sql server backup software. Some less-capable tools may back up the SQL Server database only, and you may need a separate utility for backing up the files contained in the library folder.
It's very important to have a scheduled backup procedure that automatically saves the database and the library to a safe archive. As your database and file library grow, the compressed .PDXZ backup file will take longer to finish, consume more system resources, and be increasingly vulnerable to file system errors.
Data that must be backed up §
There are two essential PDXpert data elements that you must protect:
- The SQL Server database in which all of the product data is maintained (for example, files like PDXpertDB.mdf and PDXpertDB_log.ldf), and
- A Windows folder, called the \Library folder, that contains all files that have been attached to PDXpert's items.
Both of these data elements work together. Therefore, they must be backed up as a set.
Finding the data to be backed up §
The options are:
- Back up the entire server computer.
- Back up the entire disk drive that contains the PDXpert \Data folder.
- Within the disk drive, back up the entire content of the \Data folder.
Within the \Data folder, back up only the content of these two folders:
- SQL Server database files: \Database
- PDXpert library files: \Library
The disk drive and the location of the data folder are shown on Manage.
Automation practices §
Regularly assess your backup & recovery risks, procedures and technologies. Develop and maintain a robust data backup and disaster recovery plan in consultation with your IT specialist. Always validate the results of a new or revised backup procedure.
Your Windows operating system may have the necessary software utilities to make a reliable backup procedure. There are also many commercial tools available to perform this important task.
When developing your data backup and disaster recovery plan, consider these practices:
- Schedule backups during quiet periods: backup jobs consume a lot of I/O resources.
- Ensure that the backup interval reflects how quickly your data ages, and balance this interval with users' time to reproduce lost data after the most recent backup's been restored.
- Avoid propagating viruses by scanning file attachments before saving them into the library.
- Some antivirus software can interfere with the PDXpert Application Server, and should be tested for problems while users perform normal database and library file tasks.
- Do not use your production database/library disk as the primary backup device. Use a separate physical disk and not simply a partition on the same disk.
- After a backup is complete, copy the backup file(s) from the primary backup drive to a secondary device. This secondary device should be secured, and logically and physically separate from the production network. Use disk-to-disk or disk-to-cloud technology for secondary backups. Avoid tape.
- If you don't control your off-site storage location, consider encrypting your saved data.
- To minimize downtime, ensure that off-site backups can be retrieved quickly.
- Don't be too aggressive in purging old backups. In a very large historical file library, a monthly snapshot going back a few years may provide that one crucial file that was corrupted long ago but only recently discovered.
- Periodically make sure that your hardware, particularly disk subsystem, is functioning properly.
- Test the data integrity of your backup procedure by restoring the backup file(s) into a fresh configuration. Regularly validate that the backup procedure is making correct backup files.
Help Guide Contents [as PDF]
- 0001. Welcome!
- 0002. Help styles
- 0100. PDXpert Application Server
- 0101. Server overview
- 0200. How to...
- 0300. Console reference
- 0400. How to start the PDXpert client
- 0500. PDXpert introduction
- 0600. How to set up PDXpert
- 0700. How to use the Item Explorer
- 0800. How to use the Collection Explorer
- 0900. How to work with documents
- 0901. How to work with documents
- 1000. How to start a document
- 1003. Fill in the new document
- 1004. Add or remove references
- 1005. Start and update a task
- 1006. Save your document
- 1007. Remove your document
- 1008. Release your document
- 1009. Manage a released document
- 1010. Revise a released document
- 1011. Cancel a released document
- 1100. How to work with parts
- 1101. How to work with parts
- 1200. How to start a part
- 1203. Fill in the new part
- 1204. Add, modify or remove BOM parts
- 1205. Import a CAD BOM
- 1206. Add or remove approved sources
- 1207. Add or remove references
- 1208. Add or remove materials
- 1209. Start and update a task
- 1210. Save your part
- 1211. Remove your part
- 1212. Release your part
- 1213. Revise a released part
- 1214. Manage a released part
- 1215. Cancel a released part
- 1300. How to revise multiple markups
- 1400. How to work with change forms
- 1401. Processing a change
- 1500. How to start a change form
- 1503. Start and update a task
- 1504. Analyze a submitted change
- 1505. Fix change form routing errors
- 1506. Remove your change form
- 1507. Review a routed change
- 1508. Resolve an on-hold change
- 1509. Analyze an accepted change
- 1510. Use a released change
- 1511. View a completed change
- 1512. Analyze a stopped change
- 1513. View a rejected change
- 1514. Remove a canceled change
- 1515. Return a submitted change
- 1600. How to work with file attachments
- 1700. How to report, import & export
- 1701. Run a report
- 1702. Export a PDX package
- 1703. Use the DataGrid
- 1704. Use the Report/Export Wizard
- 1800. Import & update items
- 1801. Use the Batch Importer
- 1802. Item Master import
- 1803. Iteration-level relational imports
- 1804. Bill of materials import
- 1805. References import
- 1806. Revision files import
- 1807. Sources import
- 1808. Item-level relational imports
- 1809. Item files & links import
- 1810. Materials import
- 1811. Groups collection import
- 1812. Materials collection import
- 1813. Organizations collection import
- 1814. Persons collection import
- 1815. Custom collection import
- 1900. View & export via ODBC
- 1901. View database objects
- 1902. Create an ODBC connection
- 1903. ItemViews reference
- 1904. ReferencePairViews reference
- 1905. SourcePairViews reference
- 1906. SourceItemMasterView reference
- 1907. StructurePairViews reference
- 1908. ChangeViews reference
- 1909. ChangePairViews reference
- 1910. FilePairMasterView reference
- 2000. How to do other tasks
- 2100. Menu reference
- 2200. Document reference
- 2300. Part reference
- 2400. Change Form reference
- 2500. System Rules reference
- 2501. System Rules tool
- 2502. General: Copy files to snapshot
- 2503. General: Copy previous tasks
- 2504. General: Item uniqueness definition
- 2505. General: Reviewer comment required
- 2506. Default File Access
- 2507. Password Policy
- 2508. References Tabs
- 2509. BOM: Limit part to one row
- 2510. BOM: Lock part unit of measure
- 2511. BOM: Allow partner parts
- 2600. Collections reference
- 2601. Managing collections
- 2602. Custom attributes
- 2700. Places/Organizations/Persons
- 2800. General
- 2900. Documents
- 3000. Parts
- 3100. Changes
- 3108. Custom collections
- 3200. Other reference topics
- 3300. Software licenses & legal notices