coganb's Posts

coganb's Posts

Hi, This should work.  You can have the same device accessible over IP and FC. -Bobby
Hi, If you do decide to go with creating a new SU, this example should help: 174255 : How to Create a NetWorker DDBoost Device in a non-default MTree             https://support.emc.c... See more...
Hi, If you do decide to go with creating a new SU, this example should help: 174255 : How to Create a NetWorker DDBoost Device in a non-default MTree             https://support.emc.com/kb/174255 -Bobby
If it's not obeying the 'clone storage node' field of the read source storage node, then that sounds like a bug.  Could be this one: 126779 : Clone Controlled Replication (CCR) does not honor... See more...
If it's not obeying the 'clone storage node' field of the read source storage node, then that sounds like a bug.  Could be this one: 126779 : Clone Controlled Replication (CCR) does not honor write storage node             https://support.emc.com/kb/126779 -Bobby
Hi, This may be expected behaviour depending on how you have setup the 'Clone Storage Nodes' field in the properties of sn1 (configuration tab). From the NetWorker Cloning Integration Guide... See more...
Hi, This may be expected behaviour depending on how you have setup the 'Clone Storage Nodes' field in the properties of sn1 (configuration tab). From the NetWorker Cloning Integration Guide: page 35 "Use the following criteria to determine the storage node to which the clone data will be written (write source): - The Clone Storage Node attribute of the read source storage node is used as the write source." If there is nothing in there, then the NetWorker server's equivalent field will be consulted.  If that has no value, the NetWorker server's Storage Node field (this time in the client properties, not the Storage Node properties) will be used. -Bobby
Hi Stefan, You might get what you need from: mminfo -S -q "ssid=[SSID of saveset]" -Bobby
Hi, The info you are looking for is contained in the Release Notes for each NetWorker version.  For example, for NetWorker 8.2, it's on page 14 of the Release Notes: https://support.emc.com... See more...
Hi, The info you are looking for is contained in the Release Notes for each NetWorker version.  For example, for NetWorker 8.2, it's on page 14 of the Release Notes: https://support.emc.com/docu53912 'Features Provided with Base Enablers' -Bobby
Hi, you mean it crashes in debug mode, but doesn't crash without debug?   You may need to open a Service Request with EMC Support in order to have the crash dump analysed.  There isn't much we... See more...
Hi, you mean it crashes in debug mode, but doesn't crash without debug?   You may need to open a Service Request with EMC Support in order to have the crash dump analysed.  There isn't much we can tell from the above, so we'd need to look at the full stack trace with windbg.  Alternatively, you can have a look at it yourself: windbg  file open crash dump !analyze -v k -Bobby
Hi, Further to crazyrov's suggestion, you can use nsradmin to start the group from the client: # cat nsradmin_start . type : NSR group; name : Ender update autostart : Start Now # nsra... See more...
Hi, Further to crazyrov's suggestion, you can use nsradmin to start the group from the client: # cat nsradmin_start . type : NSR group; name : Ender update autostart : Start Now # nsradmin -s vm-lego-121 -i nsradmin_start Then check back regularly to see if it's finished and run your post-script when it is: # cat nsradmin_check . type : NSR Group; name : Ender show status p # nsradmin -s vm-lego-121 -i nsradmin_check | grep status                       status: running; -Bobby
Hi, Run the backup with -D5 added to the backup command and check the sso logs in /nsr/logs/sg/[group name].  This should give you more details on the reason for the unavailability of the SAN ... See more...
Hi, Run the backup with -D5 added to the backup command and check the sso logs in /nsr/logs/sg/[group name].  This should give you more details on the reason for the unavailability of the SAN transport mode.  There's an example in the below article: 185186 : VADP backup fails indicating the "hotadd:san" transport modes are unavailable https://support.emc.com/kb/185186 -Bobby
Hi Dirk, Start by checking your pool configuration.  Is the data going to the correct pool or not?  If not, check the pool properties to see what selection criteria are there.  Also, check the... See more...
Hi Dirk, Start by checking your pool configuration.  Is the data going to the correct pool or not?  If not, check the pool properties to see what selection criteria are there.  Also, check the storage node field in the client properties to be sure that this is going to the correct storage node. -Bobby
Hi Hrvoje, You're right - AMM was being used a lot as a workaround to re-mount devices which were unmounting due to network issues.  However, there were some incidents where this caused proble... See more...
Hi Hrvoje, You're right - AMM was being used a lot as a workaround to re-mount devices which were unmounting due to network issues.  However, there were some incidents where this caused problems in certain circumstances and the official recommendation is now to not enable this for DDboost devices.    You'll see this in the NetWorker-VMware Integration Guide where it says: "Ensure that Auto media management is not selected. It does not apply to DD Boost devices." -Bobby
Hi, This doesn't tell us what caused the recover failure.  You could check the hostd.log and networkr.raw to see if there is any further info there.  Also, try changing the transport mode to n... See more...
Hi, This doesn't tell us what caused the recover failure.  You could check the hostd.log and networkr.raw to see if there is any further info there.  Also, try changing the transport mode to nbd which will rule out the possibility that it's the hotadd that's causing the problem. -Bobby
Hi, Enabling auto media management with DDBoost devices is not recommended as this has caused problems in the past.  The unmounting is probably due to a network issue.  You should look at the ... See more...
Hi, Enabling auto media management with DDBoost devices is not recommended as this has caused problems in the past.  The unmounting is probably due to a network issue.  You should look at the errors you see on the DD at the time and try setting the tcp keepalive to keep the connection open.  You'll find details here: 122960 : NetWorker AFTD intermittently unmounts at backup start with failure to verify label - volume not found in media index             https://support.emc.com/kb/122960 -Bobby
Hi Randy, Could you please provide more details on exactly what you are trying to do?  Are you trying to do a one-off operation or program replication at some level? -Bobby
Hi, Have a look at the 'Recommendations and Considerations' for Image level recovery of a full VM in the NetWorker VMware Integration Guide page 125 to be sure that you have everything setup t... See more...
Hi, Have a look at the 'Recommendations and Considerations' for Image level recovery of a full VM in the NetWorker VMware Integration Guide page 125 to be sure that you have everything setup the way it has to be for this to work.  Check also that your name resolution is working between vCenter, ESX, NetWorker server and proxy. If it still fails, copy here the full error message you are getting and we'll see if we can figure out what might be the problem. -Bobby
Hi Ed, The term virtual edition client is usually used in terms of licensing NetWorker for a virtual environment: From the NetWorker Licensing Guide: "Virtual Edition Client Connection lic... See more...
Hi Ed, The term virtual edition client is usually used in terms of licensing NetWorker for a virtual environment: From the NetWorker Licensing Guide: "Virtual Edition Client Connection license: A new license type, Virtual Edition Client Connection, works with all server virtualization environments supported by the NetWorker software. The physical host specified in the Client resource's Physical host attribute will consume one Virtual Edition Client Connection license, regardless of how many virtual clients are running on that host." The NetWorker Backup Appliance (VBA) is a VMware virtual appliance which allows you to backup your VMware VMs using NetWorker.  There are currently two methods of backing up VMware VMs with NetWorker and both are described in detail in the NetWorker VMware Integration Guide.  The method which uses the VBA is called NetWorker VMware Protection. -Bobby
Hi David, According to this article, it could be a problem with the java cache: https://support.emc.com/kb/108967 -Bobby
Just to clarify further - the above article covers the issue that Hrvoje mentioned.  The 'ignoring unrecognised option' NMC backup failure is covered here: NMC scheduled backup fails with "sav... See more...
Just to clarify further - the above article covers the issue that Hrvoje mentioned.  The 'ignoring unrecognised option' NMC backup failure is covered here: NMC scheduled backup fails with "savepsm: Ignoring unrecognized option '<option>', use '-h' to see usage and Backup of NMC DB failes with error "68641:savepsm: Usage: savepsm " -Bobby
Hi, The reference you need for this issue is NW159072.  Details are provided in this article. -Bobby
Hi, The 'physical host' field is only used to define whether you have enough licenses to cover your virtual machines.  It doesn't have to have a machine name which has NetWorker installed on i... See more...
Hi, The 'physical host' field is only used to define whether you have enough licenses to cover your virtual machines.  It doesn't have to have a machine name which has NetWorker installed on it. -Bobby