Skip to main content
commvault.com commvault.com
Solved

old snapshot mounted on a linux proxy

B
Byte
Forum|alt.badge.img+14

Hello,

on my AWS environment,

I have 2 Windows MA and a linux machine that is used as a proxy to backup EFS (AWS NFS like)

Sicne yesterday the linux proxy machine stop responding.

When I connect to AWS console I see that a lot of volume labeled

_GX_BACKUP_SnapJob_210219_vol-086b61f123938a8f4 are mounted on it.

I dont know why these volumes should mounted on the Windows MA.

How to find from where they are mounted ?

I want to know thaht before investigate why the proxy is down. I think boot filesystem is corrupted.

 

Thanks !!

Best answer by Mike Struening RETIRED

Ok, now I get it.  so at some point by some trigger, older snapshots were mounted to the Linux proxy, but you need to find out why.

Can you run a Job Summary report for the Linux server/proxy for the time frame that the snapshots were mounted?  This should allow you to narrow the focus down sufficiently.

View original
Did this answer your question?

4 replies

Mike Struening
Vaulter
Forum|alt.badge.img+23

@Bloopa , do you mean regarding the Windows OS itself seeing these paths, or if they are attached to the MA within CV?

I would start with the OS itself seeing them (AWQS sees them mounted, though you might be able to browse the contents via the MA).

https://www.linkedin.com/in/michael-struening
B
Byte
Forum|alt.badge.img+14
  • Bloopa
  • Author
  • Byte
  • 115 replies
  • January 18, 2022

Thanks @Mike Struening  for you answer

I will try to explain better.

Normally, to backup ec2 instances, we have two Windows Media agent acting as access node for linux and Windows machines. When backup occurs for ec2 instances, the snapshots are mounted on those Windows MediaAgents only.

I want to understand why old volumes were mounted on the Linux proxy. Maybe this proxy is used in a subclient as access node also ?

we have detached manually those volumes from the linux proxy and now it works after a reboot.

this linux proxy should not have volume mounted on it by commvault.

 

Mike Struening
Vaulter
Forum|alt.badge.img+23

Ok, now I get it.  so at some point by some trigger, older snapshots were mounted to the Linux proxy, but you need to find out why.

Can you run a Job Summary report for the Linux server/proxy for the time frame that the snapshots were mounted?  This should allow you to narrow the focus down sufficiently.

https://www.linkedin.com/in/michael-struening
B
1 person likes this
  • B
    Bloopa
Mike Struening
Vaulter
Forum|alt.badge.img+23

Following up on this one, @Bloopa .  IS this still an issue for you?  Can you run a Job Summary report for the Linux server/proxy for the time frame that the snapshots were mounted?  This should allow you to narrow the focus down sufficiently.

https://www.linkedin.com/in/michael-struening

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings