NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs

Purpose ......................................................................................................................................................... 2 Disclaimer...................................................................................................................................................... 2 Vendor Specific Information .......................................................................................................................... 2 Appliance Software Version Support History ................................................................................................ 3 Interface and Protocol Support Details ......................................................................................................... 3 Software Requirements for Use.................................................................................................................... 3 Earliest Version of NetVault: Backup Required ........................................................................................ 3 Additional Software Required ................................................................................................................... 3 Technical Implementation ............................................................................................................................. 3 Adding Data Domain Virtual Tape Library to NetVault: Backup Server ................................................... 3 Prerequisites......................................................................................................................................... 3 Data Domain VTL Sizing and Setup Guidelines .................................................................................. 3 NetVault: Backup and Data Domain VTL Setup Guidelines ................................................................ 4 Data Domain VTL Cleaning Cycles (Reclamation Cycles or Commonality Factoring)........................ 5 Adding NetVault: Backup Virtual Tape Library Hosted on Data Domain Appliance................................. 5 Prerequisites......................................................................................................................................... 5 NetVault: Backup Configuration Guidelines ......................................................................................... 5 NetVault: Backup Authentication Guidelines........................................................................................ 6 Interface and Protocol Guidelines ........................................................................................................ 7 NetVault: Backup VTL Sizing and Setup Guidelines............................................................................ 7 Using and Managing a NetVault: Backup VTL on Data Domain Unit .................................................. 9 NetVault: Backup VTL and Data Domain Cleaning Cycles................................................................ 10 Summary................................................................................................................................................. 11 Other information .................................................................................................................................... 11 Known Firmware Issues: .................................................................................................................... 11 Device Notes and Caveats................................................................................................................. 11 Appendix A: Sample scripts for reclamation of disk space ......................................................................... 16 NetVault: Backup Virtual Tape Library Hosted on DataDomain VTL / Gateway Series ............................. 16 Windows Platform................................................................................................................................... 16

Updated August 17, 2009

Page 1 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs PURPOSE
This document details how to deploy a Data Domain Appliance Virtual Tape Library (VTL), or Gateway Series for use with NetVault: Backup (NVBU).

DISCLAIMER
The information in this publication is provided As Is and is intended to be for reference purposes only. BakBone Software, Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties or merchantability or functional applicability for a particular purpose. BakBone Software, Inc. believes the information in this publication is accurate as of its publication date. The information is subject to change without notice of any kind. Use, copying, and distribution of the software information contained within this document requires a valid and applicable license. This version supersedes and replaces all previous versions. The information serves only as a guide for those configurations and products which BakBone Software, Inc. has qualified and is not the sole resource for system and software configuration. For more information or answers to questions not found in this document, please see BakBone Software, Inc. website, other BakBone Software, Inc. documentation, such as BakBone Software, Inc. Users Guides, relevant vendor documentation, or contact your BakBone Software, Inc. Sales or BakBone Software, Inc. Customer Service representative.

VENDOR SPECIFIC INFORMATION

Support Details Data Domain Appliance Virtual Tape Library and Gateway Series

VTL Emulations: Drive Models

Emulation Vendor: IBM Supported Models: Ultrium-TD3 Ultrium-TD2 Ultrium-TD1 Emulation Vendor: StorageTek Supported Models: L180 1 - 10000 1 - 64 1 - 128 Supported Virtual 0 10 Caps Supported

VTL Emulations: Library Modules

Slots Libraries Tape Drives Bar Code Type Tape Import/Export Slot

Updated August 17, 2009

Page 2 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs APPLIANCE SOFTWARE VERSION SUPPORT HISTORY
Date Nov-Dec 2008 Version OS 4.6.0.1-76126

INTERFACE AND PROTOCOL SUPPORT DETAILS

SCSI-HVD
1.

SCSI-LVD

SATA

SAS

Fibre X

iSCSI

CIFS X1

NFS X1

Interface and Protocol support for NVBU VTL

SOFTWARE REQUIREMENTS FOR USE

Earliest Version of NetVault: Backup Required
Date Nov. 25, 2008 Version Version 8.20 Build 23 GENUS

Additional Software Required

None

TECHNICAL IMPLEMENTATION

Adding Data Domain Virtual Tape Library to NetVault: Backup Server

Follow the instructions in the sections below to successfully add this device to the NetVault: Backup Server.

Prerequisites
Refer to the manufactures documentation for additional details on the following prerequisites. Ensure cabling and termination is configured correctly Attach Device to host system Configure interface protocol addressing Power ON Unit, if required, and allow for the completion of the devices POST (Power-On SelfTest) Power on and boot up host computer system

Data Domain VTL Sizing and Setup Guidelines

Due to various factors such as data set size, data set iteration or count, retention period, and change rate it can be very difficult to determine the best VTL size and configuration for any given situation. One of the best practices is to size the VTL to no more than 10x the physical available disk space or to asses how much data the customer has to backup and the required retention periods for each set of data so as to not exceed either one of these two guidelines when creating the virtual media for the virtual tape library and to set the drive count to equal the number of simultaneous jobs or data streams desired without exceeding the maximum guidelines set forth by the vendor.

Updated August 17, 2009

Page 3 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs
For example; When using 2.5TB of physical disk space intended to cope with about 4TB of data on a 4 week retention period the options would be to create a VTL with 16TB of space allocated to retain data at any one time or to simply create a VTL with 25TB of space allocation. In the example above we have 2.5TB of physical disk space, so we can define the size of the VTL to 25TB, approximately 10x the physical disk space or 16TB which is enough to accommodate the data set size and respective retention period and does not exceed the physical capacity guidelines outlined above. With the size of the VTL determined, consideration needs to be given to how we create the VTL itself. Each product can handle a set number of streams or emulated drives. We would consider writing to a NVBU VTL virtual drive as a stream. As a rule of thumb, consider creating virtual drives in the VTL only using what is needed to run concurrent jobs. Having too many drives could lead to poor performance. Never exceed the number of streams supported by the product when creating the NVBU VTL. Another best practice is to create media that properly sized and is not too big or too small. Having a large number of small media puts a strain on the NVBU Media Manager process and can cause a Windows 32bit machine to run out of resources.

NetVault: Backup and Data Domain VTL Setup Guidelines

Library Robotic Arm Selection
1. In the NVBU GUI, open the Device Management window (click Device Management on the toolbar or Large Buttons panel, or on the Administration menu, click Device Management). 2. On the Add menu, click Add Library. This opens the Library Selection tab in the Add Library window. 3. Under Choose Library, open the Server/Client node to which the device is connected (double-click the node, or right-click it and select Open). 4. Open the Robotic Libraries node. 5. Double-click the library or right-click and choose Select. The library picture, type and details are displayed under Selected Library.

Drive Selection
1. 2. 3. 4. In the Add Library window, click the Drive Selection tab. Open the Server/Client node to which the device is connected. Open the corresponding drive type node. The available drives are listed under this node. For libraries with a single drive, double-click the drive or right-click it and choose Select. The drive picture, type and details are displayed under Selected Drives. 5. For libraries with multiple drives, perform the following steps to assign the correct drive bay to each drive: a. Enter 1 in the Select for Drive Bay box. b. Under Choose Drives, double-click drive 1 or right-click it and choose Select. The drive picture, type and details are displayed under Selected Drives. c. Repeat steps a and b for the remaining drives, changing the drive number and bay for each drive 6. A default name will be given to the device in the Library Name field. Edit the Library Name if desired. 7. Do NOT save the device. Configuration options should be set before the device is saved. The configuration options are covered in the following section.

Optional Configuration for Optimum Performance

1. Select the Configure tab. Select the drive and right-click. Select Configure, to display the Configure Device window. 2. In the Configuration tab, increase the Media Block Size (KB) from the default setting of 32 KB. Ensure the operating system and drive can support the new value entered.

Updated August 17, 2009

Page 4 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs
3. In the Performance tab, increase the default Transfer Memory Buffer setting from the default setting of 257 KB. Ensure the operating system can support the new value entered. Important: The amount of memory to assign to transfer buffers (KB) is what is often referred to as the shared memory setting. The shared memory is allocated in 32 KB blocks with one additional byte. The optimum figure is dependent on the drive model, but the minimum value to use is at least 4x the block size setting for the drive. Ensure there is sufficient RAM (Windows) or Kernel Memory (UNIX). Use more shared memory if available and as required. 4. 5. 6. 7. Repeat steps 1 3 for each drive as required. Save device configuration by clicking the Save Details button in the top left corner. Select OK in the Device Added Successfully window. Close the Add Library window.

Data Domain VTL Cleaning Cycles (Reclamation Cycles or Commonality Factoring)

The Data Domain units are capable of running a cleaning cycle on a regular basis to recover resources that are no longer required by the de-duplication process or the respective data. When a virtual tape is overwritten by the backup application, the DataDomain software engine frees up any allocated resources used by the reused virtual media. It is not necessary to re-label or blank the virtual tape to reclaim unused space. Positioning to the beginning of the virtual media location on a virtual tape and overwriting data at this location causes the space used by the old data to be freed up. Using a Data Domain unit as a NVBU VTL or DD VTL will require periodic maintenance to achieve the best usage from the Data Domain unit. Please consult with the original equipment manufacturer for details.

Adding NetVault: Backup Virtual Tape Library Hosted on Data Domain Appliance
Prerequisites
Refer to the manufactures documentation for additional details on the following prerequisites. Ensure cabling and termination is configured correctly Attach Device to host system Configure interface protocol addressing Power ON Unit, if required, and allow for the completion of the devices POST (Power-On SelfTest) Power on and boot up host computer system NetVault: Backup v8.2 or Higher Data Domain unit configured with a network share of /backup exported via CIFS or NFS. IP address/DNS name of Data Domain device Domain name, username and password of user setup on Data Domain unit to provide full access to the /backup share.

NetVault: Backup Configuration Guidelines

In the NetVault: Backup Configurator and select the Plugin Options tab. Select Disk Devices Plugin sub tab.

Updated August 17, 2009

Page 5 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs
Deselect Check available disk space before creating libraries option as shown below and apply the changes.

NetVault: Backup Authentication Guidelines

To ensure proper operation, setup the account that the NetVault Process Manager Service will use to communicate to the Data Domain CIFS / NFS share such that it has full access to Read / Write / Delete / Create files and folders. Windows Environment Example: 1. Open Windows Control Panel > Administrative > Services. 2. Select the NetVault Process Manager Service, right click it and select Properties. 3. Select the Log On tab. 4. Select This Account to change the local system account to the account details previously setup to the Data Domain unit to allow access to the CIFS share.

Updated August 17, 2009

Page 6 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs

Important: If an account has not been previously configured to allow access to network shares for backup then you need to use a user account that is consistent across the NetVault: Backup Server, the network shares, and the Data Domain unit. 5. Restart the NetVault Process Manager Service. This will stop all current running jobs and close the NVBU GUI if it is open.

Interface and Protocol Guidelines

Ensure that the NVBU Server is running on a newer hardware platform with front side bus capable of supporting the performance requirements necessary to sustain proper transfer rates. Use a dedicated network card in the NVBU Server to have an isolated link to the Data Domain unit for NVBU VTL IO specifically.

NetVault: Backup VTL Sizing and Setup Guidelines

Due to various factors such as data set size, data set iteration or count, retention period, and change rate it can be very difficult to determine the best VTL size and configuration for any given situation. One of the best practices is to size the VTL to no more than 10x the physical available disk space and to set the drive count to equal the number of simultaneous jobs or data streams desired without exceeding the maximum guidelines set forth by the vendor or to asses how much data the customer has to backup and the required retention periods for each set of data so as to no exceed either one of these two guidelines when creating the virtual media for the virtual tape library.

Updated August 17, 2009

Page 7 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs
For example; When using 2.5TB of physical disk space intended to cope with about 4TB of data on a 4 week retention period the options would be to create a VTL with 16TB of space allocated to retain data at any one time or to simply create a VTL with 25TB of space allocation. So in the example above we have 2.5TB of physical disk space, so we can define the size of the VTL to 25TB, approximately 10x the physical disk space, or 16TB which is enough to accommodates the data set size and retention period and does not exceed the physical capacity guidelines mentioned above. With the size of the VTL determined, consideration needs to be given to how we create the VTL itself. Each product can handle a set number of streams or emulated drives. We would consider writing to a NVBU VTL virtual drive as a stream. As a rule of thumb, consider creating virtual drives in the VTL only using what is needed to run concurrent jobs. Having too many drives could lead to poor performance. Never exceed the number of streams supported by the product when creating the NVBU VTL. Another best practice is to create media that properly sized and is not too big or too small. Having a large number of small media puts a strain on the NVBU Media Manager process and can cause a Windows 32bit machine to run out of resources. Before the library creation takes place create a directory in the /backup share on the Data Domain unit. In our example we have created a directory called VTL. In our example we can create a VTL with 10 drives and 250 slots with a media size of 100 GB each. This gives us approximately 25 TB of usable VTL space.

Updated August 17, 2009

Page 8 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs

In the previous figure, you can see how we use the UNC path to the Data Domain unit to create the NVBU VTL called DD150 in the \backup\VTL directory. Once the NVBU VTL has been created it can be added to the NetVault: Backup Server in the usual way.

Using and Managing a NetVault: Backup VTL on Data Domain Unit

General guidelines and best practices for using a NVBU VTL on a Data Domain unit: Only create enough media to cope with one full cycle of backups, and the relevant retention policies. Set the Automatically Label Blank Media parameter to off. So any free media items available, would not be used first, and which would then exclude the re-use of media. This helps to relieve the space reclamation problems. Use media groups to make the targeting of data, and re-use of media easier to plan and deploy.

In our example NVBU VTL, we should now begin to look into grouping the data to be backed up to work with media groups as target sets. For example, if we have 2 TB of data to backup, done on a weekly full backup basis, with retention of 4 weeks, we will need 8 TB of media. With media at 100 GB each, 80 pieces of media can be added to the target media group. The main reason for using media groups is so we can force the Data Domain unit to re-use media before using blank media. NVBUs media selection algorithm is

Updated August 17, 2009

Page 9 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs
Target media in a drive Target media in a slot Blank media Media marked for re-use.

As you can see blank media would be used before media marked for re-use. If we do not re-use media, the Data Domain unit will never be able to recover the space. By re-using media NVBU overwrites the previous contents once the header has been updated and reuses available space which otherwise would not be reclaimable by the Data Domain clean cycle. Keeping spare media that is not grouped blank will keep the usage of the Data Domain unit as low as possible. Because the Automatically Label Blank Media option is disabled, the backup may run out of media before it completes, especially if the data set is growing. This is the trade off when using a Data Domain unit, media management become necessary to allow best use of the unit. To alert administrators that a job has run out of media, NVBUs Global Notification can be used to send an email to the sys-op detailing that there is no suitable media to complete the job. The media request can then be placed on hold in the Device Management window. Blank media can be added to the relevant target media group and the media request taken off hold. While this is not ideal, it will allow the job to complete. Another recommendation would be automating a media utilization report (job ID 13) to be sent to the sysop on a reoccurring basis to track the media usage. This will allow the sys-op to pre-add media to help prevent the above scenario.

NetVault: Backup VTL and Data Domain Cleaning Cycles

The Data Domain units are capable of running a cleaning cycle on a regular basis to recover data space that is no longer required by the de-duplication process. Using a Data Domain unit as a NVBU VTL or DD VTL will require periodic maintenance to achieve the best usage from the Data Domain unit. As a DD VTL, if you have media that is marked for re-use but not being used in a current backup strategy, then this space can be reclaimed by simply reusing the media. When media is reused on a DD VTL it knows that the space can be reclaimed from its media on the next clean cycle. The NVBU VTL has a slightly different requirement. Even though NVBU can locate and blank media that is marked for reuse, the Data Domain unit will not know that NVBU has marked the media for reuse and will not reclaim the space on the next clean cycle. This is due to the fact that NVBU will only update the header on the media file and not scrub through and remove the old data as is required when the NVBU VTL is used. To ensure that the Data Domain clean cycle can reclaim space, the marked for reuse media must be identified, removed and then re-added as a new file. Since the new file no longer has any content, the Data Domain clean cycle can reclaim the resources that had been previously assigned to the virtual media file. IMPORTANT NOTE: A script can be run to build a list of the media, remove the media, and use the nvmakemedia utility to recreate the files. Refer to Appendix A for an example script.

Updated August 17, 2009

Page 10 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs
Summary
With careful planning and adhering to the best practices, the Data Domain units can be used as an effective disk based backup technology with a small physical footprint offering a large usable capacity. There will always be a trade off between the administration required and the space usage. Although they may be sold as a fit and forget technology, as NAS this can be true, but as a NVBU VTL it will require a management overhead to ensure that continued protection is delivered through the NVBU product within these environments.

Other information
Known Firmware Issues:
None

Device Notes and Caveats

Data Domain VTL
When creating virtual tape cartridges within the Data Domain DD530 VTL CLI the cartridges will be placed in the vault. The vault is a storage area for tapes in the event that a user opts to destroy the library but desires to retain the used cartridges. When cartridges are placed in the vault they are not visible to the NVBU GUI through the NVBU Device Management screen until exported into the VTL using the DD530 command line interface (CLI). Exporting Virtual Media When exporting a tape first perform an Open Door operation in the NVBU Device Management GUI. The tape can be exported using the DD530 CLI. Once the user prompt is returned in the CLI perform a Close Door operation in the NVBU Device Management window. The tape should no longer be visible to NVBU. Importing Virtual Media The importing of virtual tape cartridge(s) cannot be done through Entry/Exit Ports. When importing virtual tape cartridge(s), first perform an Open Door operation in the NVBU Device Management window and then use the DD530 CLI utility to move the virtual tape cartridge(s) from the vault to the configured library. Once the CLI is updated, perform a Close Door operation in the NVBU Device Management window. The virtual tape cartridge(s) will now show up in the NVBU Device Management window in a slot. Do not attempt to move virtual tapes in/out of library slots or drives using the DD530 CLI while NVBU is running. Always use the NVBU Device Management window. If the DD530 CLI utility is used to load/unload tapes to/from the library or drives while NVBU has control over the library, unexpected behavior will result. To take the library OFFLINE in NetVault, perform an Open Door operation. To bring the library back ONLINE in NVBU, perform a Close Door operation. Compression ratios for Windows Currently Data Domain does not have a NVBU specific tape marker-type selection. If the compression performance for Windows backups is below current expectations set by Data Domain then please contact Data Domain support for the creation procedure of a custom tape marker-type that is more favorable to NVBU.

NVBU VTL/Disk Devices Plugin

NVBU Disk Device Creation

Updated August 17, 2009

Page 11 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs
With Data Domain de-duplication it is possible to create NVBU VTLs that are larger than size of the physical disk space. To allow this in NVBU open the NVBU Configurator and select the Plugin Options tab. Select the Disk Devices sub tab. Deselect the Check available disk space before creating libraries option as shown below and apply the changes.

NetVault: Backup User Access to Data Domain CIFS Share On the NetVault: Backup Server: 1. Open Windows Control Panel > Administrative > Services. 2. Select the NetVault Process Manager Service, right click it and select Properties. 3. Select the Log On tab. 4. Select This Account to change the local system account to the account details previously setup to the Data Domain unit to allow access to the CIFS share. NOTE: if this has already been done to allow access to network shares for backup then you need to use a user that is consistent across the network shares and the Data Domain unit. Restart the NetVault Process Manager Service. Disk Space Reclamation Blanking of used media in NVBU VTL created on the Data Domain share will not reclaim physical disk space. To reclaim this space the nvmakemedia utility must be used to create a clean identical .media file, in name and size, to replace the old media file. Before this is done all drives must be unloaded and Open Door command issued in NetVault: Backup Device Manager. Once all the desired media have been cleaned, the Close Door option can issued. Check that all media appear correctly in Device Manager and Media Manager. The recovered space will be reflected after the next Data Domain clean cycle completes. Refer to the NetVault: Backup Command Line Interface Users Guide at

Updated August 17, 2009

Page 12 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs
www.bakbone.com/documentation for more information on performing disk space reclamation with a Data Domain unit.

Updated August 17, 2009

Page 13 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs
Disk Space Availability Due to the nature of deduplication and various factors surrounding compression yield and disk space utilization, users must avoid running out of physical disk space. Failing to do so will result in erroneous behaviour with the backup software. Refer to NVBU Jira NVG-4306, NVG-4307, and NVG-4308 for details.

Updated August 17, 2009

Page 14 of 17

NETVAULT: BACKUP APPLIANCE APPLICATION NOTES DATA DOMAIN VTL & GATEWAY SERIEs

Updated August 17, 2009

Page 15 of 17

APPENDIX A: SAMPLE SCRIPTS FOR RECLAMATION OF DISK SPACE NETVAULT: BACKUP VIRTUAL TAPE LIBRARY HOSTED ON DATADOMAIN VTL / GATEWAY SERIES
Windows Platform
@echo off set nvutil=%ProgramFiles%\BakBone Software\NetVault\util set vtlpath=<path to the NVBU VTL directly> set logfile=%nvutil%\logdd430-1clean.log echo Stage 1 - Completed :: :: ==================================================================== :: All virtual medias in the VTL start with this prefix :: ==================================================================== set media_prefix=<input VTL media prefix> set library_name=<assign VTL name> set media_size=<assign media size> @echo. >> "%logfile%" @echo. >> "%logfile%" @echo ======================================================== >>"%logfile%" @echo Start Media Start>> "%logfile%" date/t >> "%logfile%" time/t >> "%logfile%" @echo ======================================================== >>"%logfile%" echo Stage 2 - Completed :: :: :: ================================================ :: Look for all media in the NVBU VTL with status :: "expired" and only print lines with media infos :: ================================================ "%nvutil%\nvreport.exe" -class "media" -include "%%reuse = yes" -format "%%Label %%MediaGroup" -sort "%%Label" | find "%media_prefix%" > "%tmp%\~media.txt FOR /F "tokens=1,2 delims= " %%i IN (%tmp%\~media.txt) DO ( SET ML=%%i SET GL=%%j call :_clean %%i ) echo Stage 3 - Completed goto :eof :: :: ****************************************************** :: * * :: * Main Routine for every found media * :: * Eventually adapt Timeout * :: * according to machine type * :: * * :: ****************************************************** :_clean @echo ===========================================

@echo Clean Media with Label %ML% @echo Clean Media with Label %ML% >> "%logfile%" @echo =========================================== :: ============================================== :: Open and close I/O Port, to remove a :: remaining media, wait 3 seconds :: ============================================== @echo "%nvutil%\nvopeneeport.exe" -libraryname "%library_name%" "%nvutil%\nvopeneeport.exe" -libraryname "%library_name%" choice /T 1 /C jn /N /D j >NUL: "%nvutil%\nvcloseeeport.exe" -libraryname "%library_name%" choice /T 3 /C jn /N /D j >NUL: echo Stage 4 - Completed :: :: :: ============================================== :: Export expired media and open :: I/O Port. Library cannot load media :: into a drive anymore :: ============================================== echo "%nvutil%\nvexportmedia.exe" -barcode %ML% "%nvutil%\nvexportmedia.exe" -barcode %ML% choice /T 1 /C jn /N /D j >NUL: "%nvutil%\nvopeneeport.exe" -libraryname "%library_name%" echo Stage 5 - Completed :: :: :: =============================================== :: Media is now unreachable for the library :: in I/O Slot, now we cheat NetVault ! :: :: For security reasons: Rename old media first :: After that, create new media with old name :: Deletion in next step :: =============================================== if exist "%vtlpath%\media\%ML%.disabled" erase "%vtlpath%\media\%ML%.disabled" ren "%vtlpath%\media\%ML%" %ML%.disabled "%nvutil%\nvmakemedia.exe" %media_size% mediafiles "%vtlpath%\media\%ML%" "%nvutil%\nvcloseeeport.exe" -libraryname "%library_name%" choice /T 3 /C jn /N /D j >NUL: "%nvutil%\nvblankmedia.exe" -barcode %ML% -wait if %GL% == None ("%nvutil%\nvlabelmedia.exe" -barcode %ML% -newlabel %ML%) else ("%nvutil%\nvlabelmedia.exe" -barcode %ML% -newlabel %ML% -newgroup %GL%) if exist "%vtlpath%\media\%ML%.disabled" erase %vtlpath%\media\%ML%.disabled" choice /T 3 /C jn /N /D j >NUL: echo Stage 6 - Completed goto :eof echo Stage 7 - CompleteD