Re: Full VM Instant Restore error ans2411e rc=6523

2017-07-27 Thread Efim
Hi, did you configure iSCSI on ESXi and set VMISCSIServeraddress on datamover? Efim > 27 июля 2017 г., в 9:49, rou...@univ.haifa.ac.il > написал(а): > > Hello All > > Tried the new feature on TSM for VE 8.1.0.1 in the Restore section called > "Full VM Instant Restore" . Here what I got run

Re: Full VM Instant Restore error ans2411e rc=6523

2017-07-27 Thread rou...@univ.haifa.ac.il
Hello Efim I run the process on another ESXi and no problem the machine was created successfully. I will check with the VMware administrator the status of the iSCSI on this specific EXSi By the way another question , after the process finished successfully I check in the Instant Access/Restor

Re: Full VM Instant Restore error ans2411e rc=6523

2017-07-27 Thread Efim
I correct understood that you try to instant restore VM and can't see the current restore process status in the Restore -> Instant Access/Restore Status? Efim > 27 июля 2017 г., в 11:14, rou...@univ.haifa.ac.il > написал(а): > > Hello Efim > > I run the process on another ESXi and no problem

Re: Full VM Instant Restore error ans2411e rc=6523

2017-07-27 Thread rou...@univ.haifa.ac.il
In did . despite of the virtual machine was created successfully with the process Full VM instant restore Regards Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Efim Sent: Thursday, July 27, 2017 11:33 AM To: ADSM-L@VM.MARIST.EDU S

Re: Full VM Instant Restore error ans2411e rc=6523

2017-07-27 Thread Efim
I have no idea... try to run query vm * -vmrestoretype=instantrestore -detail Efim > 27 июля 2017 г., в 11:39, rou...@univ.haifa.ac.il > написал(а): > > In did . despite of the virtual machine was created successfully with > the process Full VM instant restore > > Regards Robert > > ---

2 nics on tsm server.

2017-07-27 Thread Bo Nielsen
Hi TSM's I have recently added one more NIC to my TSM server. The new NIC is connected directly to the server, for which archiving is required. >From DSM.SYS on the archiving server, who is a RHEL: COMMmethod TCPip TCPPort1500 TCPServeraddress 192.168.1.11 tcpclie

Re: 2 nics on tsm server.

2017-07-27 Thread Karel Bos
Hi, Start with the basics, OS tools like ping. You probably have no static route to this new/seperate network. Kind regards, Karel -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Bo Nielsen Verzonden: donderdag 27 juli 2017 11:10 Aan: ADSM-L@V

Re: 2 nics on tsm server.

2017-07-27 Thread Bo Nielsen
Hi, I can ping from both servers. There isn't routing. It's a direct connection between the two servers. Regards, Bo -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Karel Bos Sent: 27. juli 2017 11:27 To: ADSM-L@VM.MARIST.EDU Subject: Re: [A

AW: [ADSM-L] 2 nics on tsm server.

2017-07-27 Thread Schneck, Dennis
Hi, can you connecttelnet 1500 for example you should see: Connected to . Escape character is '^]'. Von: ADSM: Dist Stor Manager [ADSM-L@vm.marist.edu]" im Auftrag von "Bo Nielsen [boa...@dtu.dk] Gesendet: Donnerstag, 27. Juli 2017 11:50 An: ADSM-

Re: AW: [ADSM-L] 2 nics on tsm server.

2017-07-27 Thread Sasa Drnjevic
And what does arp say? -- Sasa Drnjevic www.srce.unizg.hr On 27.7.2017. 11:54, Schneck, Dennis wrote: > Hi, > > can you connecttelnet 1500 for example > > you should see: > > Connected to . > Escape character is '^]'. > > > > Von: ADSM: Dist Stor M

Re: 2 nics on tsm server.

2017-07-27 Thread Bo Nielsen
Hi I can't telnet. telnet: command not found Arp: Interface: 192.168.1.11 --- 0x17 Internet Address Physical Address Type 192.168.1.21 00-e0-ed-24-97-af dynamic 192.168.1.255 ff-ff-ff-ff-ff-ff static Regards Bo -Original Message- From: ADSM: D

Re: 2 nics on tsm server.

2017-07-27 Thread Sasa Drnjevic
On 27.7.2017. 12:11, Bo Nielsen wrote: > Hi > > I can't telnet. telnet: command not found http://www.sysprobs.com/install-and-enable-telnet-in-windows-8-use-as-telnet-client -- > > Arp: > > Interface: 192.168.1.11 --- 0x17 > Internet Address Physical Address Type > 192.168.

Re: Sloooow deletion of objects on Replication target server

2017-07-27 Thread Zoltan Forray
On Thu, Jul 27, 2017 at 2:24 AM, Chavdar Cholev wrote: > did you try server instrumentation... if there is an issue with storage or > network you should be able to identify from server instrumentation output.. > Not yet. My first objective right now is to upgrade from 7.1.6.3 to 7.1.7.300 to add

Re: Sloooow deletion of objects on Replication target server

2017-07-27 Thread Zoltan Forray
On Thu, Jul 27, 2017 at 12:56 AM, Stefan Folkerts wrote: > The read intensive ssd's can be the enterprise value type from lenovo, I will pitch the idea but am pretty sure I will be wasting my time. There are 2-other TSM servers that must be replaced/budgeted next year (we are state budget July

Re: tsm node replication fails no reason why

2017-07-27 Thread Stefan Folkerts
The reason is usually given just before the first line in your log on the source server, so the line above the one with the ANR0986I code. On Wed, Jul 26, 2017 at 8:07 PM, Tim Brown wrote: > TSM node replication fails , no indication why on source or target server? > > Source server > > 07/26/2

Re: Full VM Instant Restore error ans2411e rc=6523

2017-07-27 Thread Schneider, Jim
My VM backup proxy server has a backup network connection but the client does not. I have to disable the backup network NIC before starting the TSM Recovery Agent so that the client can see the iSCSI connection. Jim Schneider Essendant -Original Message- From: ADSM: Dist Stor Manager [