Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy Connect 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
1. When a free tape is added to the Backup\Prinergy media pool, and there is already at least one allocated tape in that pool, the backup scripts will wrongly add the new tape into the Backup\SpannedTapes list in the registry. 2. This will also happen when the new tape is added while Prinergy 2.0 backup is running. |
|
|
|
||
Cause |
The free tape, when moved into the Backup\Prinergy pool, does not get allocated until NTbackup is launched. When the code checks for new tapes in the pool, it doesn't detect any because the new tape doesn't have a Logical GUID assigned yet. | |
|
|
||
Solution |
After moving the free tape into the Backup\Prinergy pool, launch NTbackup and make sure the new tape gets Allocated status. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
||
Date submitted |
||