Backup sequence in NB 7.1.0.2 with HP MSL4048 LTO5

[stevenfoo]

We have setup several policies to perform a backup.

eg.

1. Policy: WIN-Daily-Weekly

2. Client: abc, def ghi

3. Schedule: Full - weekly, Incr - Daily

4. Media Pool: AK0001, AK0002,  AK0003, AK0004, AK0005

When the backup run for daily Incr, it took the tape AK0004 and backup all the clients.

When the backup run for full backup, it took the tape AK0005 and backup all the clients.

Questions:

How could we force or setup that it take only 1 tape to backup everything in the same policy for both Incr and Full backup ?

We want the tape to be full only, then it use the second available tape.

Any workaround?

Thanks.

[Andy_Welburn]

have the same retention period?

By default NetBackup does not mix retentions on media.

[Mark_Solutions]

If you are happy to mix retentions on the same tape (and it is not generally reccomended) then on the Master Server Host Properties - Media Tab check the box to "Allow multiple retentions per media"

[stevenfoo]

both have same retention period.

[stevenfoo]

schedule and policy setting have same retention period.

out goal is to have 1 policy - 2 schedules, backup to same tape until it full, then only use next available tape in the media pool.

[Mark_Solutions]

I am surprised that it uses 2 different tapes here, it does suggest that something is different.

However, as a test (or a solution) if you right click on the volume pool that you are using for these backups and select "Change" and then set the Maximum number of partially full media to 1.

[Andy_Welburn]

different media are being used, you could look at setting the "Maximum number of partially full media" for the volume pool.

From the "Help" section:

Maximum number of partially full media

Does not apply to the None pool, catalog backup pools, or scratch volume pools.

Enter or specify the number of partially full media to allow in the volume pool. The default value is zero, which does not limit the number of full media that are allowed in the pool.

NetBackup writes data only to the number of partially full media.

When the number of partially full media is reached, NetBackup queues backup jobs until media becomes available. If a media becomes full, NetBackup assigns another media for use if one is available in the pool or in a scratch pool.

Frozen, suspended, and imported media do not count against Maximum number of partially full media. Therefore, if you unfreeze or unsuspend the media that are partially full, you may exceed the Maximum number of partially full media value. Also, if you lower the Maximum number of partially full media value, you may exceed the limit. If you exceed the Maximum number of partially full media value, NetBackup uses all of the partially full media until the limit is reached.

This option lets you maximize your media usage. NetBackup writes data to the media until they are full, assigns other media to which it writes data until they are full, and so on.

This option also lets you control how many drives are used for backup jobs. For example, if you have 10 drives and want to reserve two for restore operations, set the Maximum number of partially full media to 8. If all of the media is in one pool, NetBackup uses only 8 drives to write backup data. NetBackup can use the two other drives for restore operations even while backups occur.

***EDIT***

One possible catch with this - if you use this particular volume pool for any other policies/schedules then this setting will also apply to those jobs. I would also imagine that it will take into account any media removed from your library?

[memodude04]

I have setup a test policy to resolve your question, see the following

1. Policy: test-incr-full

2. Client: a  b

3. Schedule: Full - weekly, Incr - Daily

4. Retention Level is the same on both Schedules (Retention Level 2)

5. Media Pool: ER1551, ER1552, ER1553

* Allow multiple data streams is DISABLED

* Under Full-weekly schedule Atrributes - Media multiplexing is set to 4

* Under Incr-Daily schedule Attributes - Media multiplexing is set to 4

Test 1

When the backup run for daily Incr, it took the tape ER1551 and backup all the clients.

When the backup run for full backup, it took the tape ER1551 and backup all the clients.

4 jobs ran simultaneously.

Test 2

When the backup run for daily Incr, it took the tape ER1551 and backup all the clients.

2 jobs ran simultaneously and completed

When the backup run for full backup, it took the tape ER1551 and backup all the clients.

2 jobs ran simultaneously and completed.

Hope this helps!

-Guillermo Hayashi

[Mark_Solutions]

I dont think it will count if it is no longer in the library - this tech note gives you an idea of how it works:

http://www.symantec.com/docs/HOWTO33855

[Andy_Welburn]

Not something we utilise - another thing that could catch you out as to why jobs are queueing!