To run a performance test

1. Create a policy specifically for performance testing.
2. Leave the schedule's Start Window field blank.

   This policy prevents the NetBackup scheduler from initiating any backups automatically for that policy.

3. To prevent the NetBackup scheduler from running backup jobs unrelated to the performance test, consider setting all other backup policies to inactive.

   You can use the Deactivate command from the NetBackup Administration Console. You must reactivate the policies after the test, when you want to start running backups again.

4. Before you start the performance test, check the Activity Monitor to make sure no NetBackup jobs are in progress.
5. To gather more logging information, set the legacy and unified logging levels higher and create the appropriate legacy logging directories.

   By default, NetBackup logging is set to a minimum level. Note that higher log levels may reduce performance, depending on the tests and the log levels.

   For details on how to use NetBackup logging, refer to the logging chapter of the NetBackup Logging Reference Guide. Keep in mind that higher logging levels consume more disk space and can affect NetBackup performance. The best practice for performance testing is to keep the default log level setting initially and increase the log level only if need to troubleshooting a specific performance issue.

6. From the policy you created for testing, run a backup on demand.

   Click Actions > Manual Backup in the NetBackup Administration Console.

   Or, you can use a user-directed backup to run the performance test. However, the Manual Backup option is preferred. With a manual backup, the policy contains the entire definition of the backup job. The policy includes the clients and files that are part of the performance test. If you run the backup manually from the policy, you can be certain which policy is used for the backup. This approach makes it easier to change and test individual backup settings, from the policy dialog.

7. During the performance test, check for non-NetBackup activity on the server and try to reduce or eliminate it.
8. Check the NetBackup Activity Monitor after the performance test for any unexpected activity that may have occurred during the test, such as a restore job.