Vergrößerung MSDP Pool unter 7.6.0.4

[Thomas_Schulz_3]

Hallo.

Ich habe vier Redhat Media Server mit je einem 32TB großen MSDP Pool.

Nun muss der MSDP Pool vergrößert werden und ich frage mich wie das funktioneirt.

Bin mir sicher das nur das MSDP Filesystem vergrößert werden muss und Netbackup dann automatisch den "Mehrplatz" verwendet, d.h in Netbackup gar nichts gemacht werden muss.

Richtig?

[RamNagalla]

https://translate.google.com/

Hello.

I have four Redhat Media Server with one 32TB large MSDP pool.

Now the MSDP pool must be increased and I wonder how the funktioneirt.

Am sure that only the MSDP file system must be increased and Netbackup then automatically uses the "Multi", ie nothing has to be done in Netbackup.

Right?

[RamNagalla · Accepted solution]

hello,

you  needs to increase the FS size in OS level and consider the below that you need to take care from Netbackup end.

Approach
Expanding the storage capacity depends on the OS and disk layout. The steps to extend the file system depend on the OS/Volume Manager/File system.
The user must stop the MSDP services before continuing with the expansion to avoid any possible data corruptions.
It is recommended to remove the <STORAGE_LOCATION>/data/journal/datastore.hdr & datastore.hdr_tlog files as they contain cached information about the size of the file system (number of containers, which can be created). These files are recreated on a restart of the services.
Note: The restart and file creation makes the initial startup of the services slightly slower.
These files are basically the transaction logs for data store changes (for example, write to container, container creation, and so on) and contain general information about the file system, the amount of free space, number of containers, and so on. These files contain binary data that is read by spoold.
Each time the spoold starts up, it calculates the maximum number of containers by using the file system information, which it gets from statvfs (using file system size / 256M ), 256M is the container size.
Also, if these two journal files are NOT present when spoold is started, they are created and used for storing the header information from all the containers present in the system (as spoold reads all the container headers *.bhd to populate the information into these files - this is a one-time performance penalty).
If a file system is being expanded, then restarting spoold is sufficient for it to recognize the new size of storage. However, if the file system needs to be shrunk at any point, these journal files MUST be removed after stopping spoold.
While doing storage expansion it is also recommended that you shutdown the NetBackup media server services where MSDP is configured. Though the underline file system supports online expansion of storage; a shutdown of the services is highly recommended as there are multiple processes reading/writing to the disk.

[RiaanBadenhorst]

Right, Once you increase the FS you'll need to re-invetory the diskpool to reflect the change. A service restart might also be required.

[n_ludwig]

Hallo Thomas,

einfach über das OS vergrößern, dann über die GUI auf den DiskPool -> Inventory Disk -> Start Inventory -> update Configuration -> freude am backup´en haben

du mußt keine dienste (daemons) neustarten