Re: Extending VNX NAS Checkpoint Retention

I was just asked to retain some specific snapshots/checkpoints on our VNX hosted NAS file system, that will hit their expiration date in a couple of days. I suspect this is a command line process, which I am not very familiar with. I have been reviewing EMC docs and online resources, but not making much progress.

Is this an “fs_ckpt” command or a “naviseccli -h SPA snap -modify” command?

I am getting very concerned about the expiration of these before I figure it out.

I would greatly appreciate some guidance and examples on this, please.

Thank you

Bryan

Related:

  • No Related Posts

Key Center license expiration date has passed, software still functioning

We have set an expiration date of 10/31/2017 in our key center for a handleful of users. With that date now passed, the users did not receive a notification of expiration and their software still functions. Can you help me understand how that expiration date(set by us) is supposed to work? The license type is authorized user.

Related:

ILOG ODM Enterprise intermittent data corruption issue

Hi, I am using IBM ILOG ODM Enterprise – ODM Planner studio version 3.8 for supply planning business. We are experiencing the intermittent and unusual error which “Check Data” process is failed due to missing foreign key/ missing mandatory field. The steps are below.
1. Create a new scenario
2. “Check Data” process is passed and “Solve” process is completed.
3. When execute “Check Data” again, it fails as missing data (Foreign key or mandatory field).

We have checked all the log files in Opti server and Data Server and couldn’t find any error during “Solve” process. We suspect that populating data for saving back to database has some issue and it cause the corrupted data. As said earlier, the error happens intermittently.
Please help advise how to fix it.

Related:

Table error: Object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) B-tree level mismatch, page P_ID1. Level LEVEL1 does not match level LEVEL2 from previous P_ID2.

Details
Product: SQL Server
Event ID: 2531
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC_BTREE_SIBLING_LEVEL_MISMATCH
Message: Table error: Object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) B-tree level mismatch, page P_ID1. Level LEVEL1 does not match level LEVEL2 from previous P_ID2.
   
Explanation

There are two pages linked as immediate neighbors on a level of a B-tree. The level, LEVEL2, on the right page, P_ID2, does not match the level, LEVEL1, on the left page, P_ID1.

To determine which page is incorrect, examine the surrounding pages and the contents of the two pages in question. Also, look for MSSQLEngine_8931 errors that indicate B-tree parent-child level mismatches.

Look for Hardware Failure

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs.

If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor.

Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system.

Restore from Backup

If the problem is not hardware related and a known clean backup is available, restore the database from the backup.

Run DBCC CHECKDB

If no clean backup is available, run DBCC CHECKDB without a REPAIR clause to determine the extent of the corruption. DBCC CHECKDB will recommend a REPAIR clause to use. Then, run DBCC CHECKDB with the appropriate REPAIR clause to repair the corruption.

Caution:

If you are not sure what effect DBCC CHECKDB with a REPAIR clause has on your data, contact your primary support provider before running this statement.

If running DBCC CHECKDB with one of the REPAIR clauses does not correct the problem, contact your primary support provider.

Results of Running REPAIR Options

REPAIR will rebuild the index.

Related:

Unable to start the Microsoft Exchange Information Store. Error {error code}.

Details
Product: Exchange
Event ID: 1005
Source: MSExchangeIS Public Store
Version: 6.0
Component: Information Store
Symbolic Name: msgidFailedStart
Message: Unable to start the Microsoft Exchange Information Store. Error {error code}.
   
Explanation
File or disk corruption caused the startup of Information Store to fail. In a cluster environment, the routing groups may not be set up correctly.
   
User Action
If the error is file corruption, repair, reinstall, or replace the corrupted file. If a disk error occurred, run the Chkdsk.exe utility with the /r option on the hard disk. If this message reappears, run hardware diagnostics on the disk drive and its controller.In a cluster environment, verify the set up of your routing groups.

Related: