Here's what I got from my open case...Better late than, well, nevermind this still stinks...It sounds kludgy.
I was always of the opinion that "new features" shouldn't be included in management/service packs.
Symantec below:
------------
Issue: After NB_60_6_M patch is applied the next backup creates a new STREAMS file named STREAMS<name_of_policy>. With this new feature if the next backup that is about to run is an incremental (INCR) backup, it will run as a FULL backup regardless if it is a regularly-scheduled or manually initiated backup. This is not a FULL schedule but rather defined as a FULL backup: A full backup backs up all files specified in the backup selections list for the policy, regardless of when the files were last modified or backed up.
Work-around:
Below are two work-around options that are available to you.
1. After a successful upgrade to NB_60_6_M, manually execute a FULL backup for all policies that include "Allow multiple data streams" for all clients.
This generates a new STREAMS file per client, per policy, and sets the last successful backup time.
This is recommended to ensure that pre-processing is valid, new STREAMS files are generated, and FULL backups complete successfully.
2. After a successful upgrade to NB_60_6_M but before running any backups, manually copy and rename the existing STREAMS file.
For example: The STREAMS file contains the last record of a successful backup for each SCHEDULE in the policy for each data stream.
T 0 0
1 1206547142 TEST FULL 0,0,604800 0 0 C:\temp
2 1206547144 TEST CINCR 0,0,604800 0 0 C:\temp
1 1206547143 TEST_2 FULL 0,0,604800 892691764 0 C:\temp
2 1206547145 TEST_2 CINCR 0,0,604800 0 0 C:\temp
1 1206547154 tesT_3 FULL 0,0,604800 0 0 C:\temp
2 1206547155 tesT_3 CINCR 0,0,604800 0 0 C:\temp
In the above example, three policies exist TEST, TEST_2 and tesT_3 each having two schedules CINCR and FULL with two streams per schedule.
The work-around is to create a copy of the original STREAMS file before starting a backup and rename it to the new format: STREAMS<policy_name>.
Note: The policy name is case sensitive. Rename the file to STREAMSTEST for a policy named TEST.
For example: The renamed file is: STREAMSTEST
T 0 0
1 1206547142 TEST FULL 0,0,604800 0 0 C:\temp
2 1206547144 TEST CINCR 0,0,604800 0 0 C:\temp
The STREAMSTEST file now contains stream data for the client for the policy TEST.
Note: For a successful work-around; all streams that are not related to the policy TEST must be removed and contained in a separate STREAMS<policy_name> file.
Using the same example, three STREAMS files are needed.
One STREAMS file is needed for STREAMSTEST, one for STREAMSTEST_2 and the third is needed for STREAMStesT_3. Each new streams file contains the stream records for the corresponding policy name.
For example, for policy tesT_3 the streams file contains only two stream records. Notice that the streams for policies TEST and TEST_2 have been removed.
T 0 0
1 1206547154 tesT_3 FULL 0,0,604800 0 0 C:\temp
2 1206547155 tesT_3 CINCR 0,0,604800 0 0 C:\temp
