2 Under normal circumstances, the VSS database should not exceed 3 ~ 5GB (although it can be unlimited). Store unrelated items in different databases, can also move items to another via Archive and RESTORE tools.
2 Configure the administrator to follow the following steps to run an Analyze tool once a week (1 month 1):
1. Lock the database (via the Tools-> Lock SourceSafe Database) of the administrator interface;
2. Run Analyze VSS DB;
3, run Analyze & Fix VSS DB.
2 Before running VSS and Analyze, it is guaranteed that there is a 1-fold database in the same disk that has been able to create a complete database copy, especially Analyze.
2 Backup files and Analyze cannot run at the same time.
2 Avoid sharing and branching across the highest list, which is complex when archiving a project and recovered to another database.
2 Synchronize a clock per week (by command: Net Time //192.168.1.31 / set) to ensure check out / in, label is ordered.
2 Do not create a new database by copying an existing database because the GUID in um.dat cannot be the same.
2 Do not restore a fully backed up database to an existing database, which will make the connection and version of the files chaos.
2 Turn off VSS before power off to prevent power failure from causing the loss of the database. UPS protection can be used.
2 Do not modify and delete any files of the VSS Server shared directory.
2 Backup files take full backup mode, not incremental backups. The incremental backup is difficult to recover.
2 Run admin-> Tools-> Cleanup Temp Directory every other month to clear the contents of the temporary directory. Before run, you have to ensure that no one uses VSS and VSS Administrator.
